Answer in brief
CVE-2026-68259 records a Unknown severity vulnerability in drm/amdkfd: Check bounds in allocate_event_notification_slot. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <85eedff5f0c4aba5a66bc37a1bd6bcecd0d77b53 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <4622214f0542f64b02c250db0f9c677eeb032d9b || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <50319efb865f72db45f191c8709511746d58ee0a || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <abeeb1947d81610c65349db4d89c6151f270e136 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <bb52249fbbe948875155ccd45cd8d74bf4ae747b || >=0 <6.6.148 || >=0 <6.12.101 || >=0 <6.18.42 || >=0 <7.1.6 | 85eedff5f0c4aba5a66bc37a1bd6bcecd0d77b53, 4622214f0542f64b02c250db0f9c677eeb032d9b, 50319efb865f72db45f191c8709511746d58ee0a, abeeb1947d81610c65349db4d89c6151f270e136, bb52249fbbe948875155ccd45cd8d74bf4ae747b, 6.6.148, 6.12.101, 6.18.42, 7.1.6 |
Published upstream
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 10, 2026
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)
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-68259 records a Unknown severity vulnerability in drm/amdkfd: Check bounds in allocate_event_notification_slot. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <85eedff5f0c4aba5a66bc37a1bd6bcecd0d77b53 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <4622214f0542f64b02c250db0f9c677eeb032d9b || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <50319efb865f72db45f191c8709511746d58ee0a || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <abeeb1947d81610c65349db4d89c6151f270e136 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <bb52249fbbe948875155ccd45cd8d74bf4ae747b || >=0 <6.6.148 || >=0 <6.12.101 || >=0 <6.18.42 || >=0 <7.1.6 | 85eedff5f0c4aba5a66bc37a1bd6bcecd0d77b53, 4622214f0542f64b02c250db0f9c677eeb032d9b, 50319efb865f72db45f191c8709511746d58ee0a, abeeb1947d81610c65349db4d89c6151f270e136, bb52249fbbe948875155ccd45cd8d74bf4ae747b, 6.6.148, 6.12.101, 6.18.42, 7.1.6 |
Published upstream
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 10, 2026
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)
Quoted source text, attributed separately from HOL analysis.