CVE-2026-68259

Unknown

Last modified

CVE-2026-68259 is a vulnerability of currently unknown severity. In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: Check bounds in allocate_event_notification_slot The valid event ids go from 0 to KFD_SIGNAL_EVENT_LIMIT allocate_event_notification_slot has an option to specify an event id to allocate at, used by CRIU. We weren't checking the bounds on that value. Check them. v2: Lower bounds check is unecessary because of idr_alloc already rejecting negative numbers.

Description

In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: Check bounds in allocate_event_notification_slot The valid event ids go from 0 to KFD_SIGNAL_EVENT_LIMIT allocate_event_notification_slot has an option to specify an event id to allocate at, used by CRIU. We weren't checking the bounds on that value. Check them. v2: Lower bounds check is unecessary because of idr_alloc already rejecting negative numbers. Upper bounds check should be KFD_SIGNAL_EVENT_LIMIT since the signal mode mappings might not yet exist (cherry picked from commit 6853f1f6cbbeb3f53ebbbd7286536aeb2c5d5f50)

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 85eedff5f0c4aba5a66bc37a1bd6bcecd0d77b53; >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 4622214f0542f64b02c250db0f9c677eeb032d9b; >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 50319efb865f72db45f191c8709511746d58ee0a; >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < abeeb1947d81610c65349db4d89c6151f270e136; >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < bb52249fbbe948875155ccd45cd8d74bf4ae747b; < 6.6.148; < 6.12.101; < 6.18.42; < 7.1.6
LinuxLinuxAll versions

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-68259?
In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: Check bounds in allocate_event_notification_slot The valid event ids go from 0 to KFD_SIGNAL_EVENT_LIMIT allocate_event_notification_slot has an option to specify an event id to allocate at, used by CRIU. We weren't checking the bounds on that value. Check them. v2: Lower bounds check is unecessary because of idr_alloc already rejecting negative numbers. Upper bounds check should be KFD_SIGNAL_EVENT_LIMIT since the signal mode mappings might not yet exist (cherry picked from commit 6853f1f6cbbeb3f53ebbbd7286536aeb2c5d5f50)
How severe is CVE-2026-68259?
Severity scoring for CVE-2026-68259 is pending analysis.
How do I fix CVE-2026-68259?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-68259?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST