Linux vulnerability

In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: Check bounds for allocate_sdma_queue restore_sdma_id allocate_sdma_queue has an option where the sdma queue id can be specified (used by CRIU). We weren't bounds-checking that value. Confirm it's less than the maximum number of queues.

Published 24 Sep 2026Updated 28 Sep 20263 sources
CVSS 7.8

What happened

In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: Check bounds for allocate_sdma_queue restore_sdma_id allocate_sdma_queue has an option where the sdma queue id can be specified (used by CRIU). We weren't bounds-checking that value. Confirm it's less than the maximum number of queues.

Affected versions

Linux: 2485c12c980a36bb9e23ababb07d73c4ac6a45af through before 42f2bd50236b61ad0aeb2c233c990ee0d615fdad (git); 2485c12c980a36bb9e23ababb07d73c4ac6a45af through before dd2870ca036e1d51baa59f942007b36a595b5890 (git); 2485c12c980a36bb9e23ababb07d73c4ac6a45af through before bfe9a7545b2a7be1c543f1741e16f2d5ec4116ae (git); 5.18 Fixed: See vendor advisory.

Why it matters

Review the vendor advisory and exposure of the affected product to determine operational impact.

Detection & mitigation

  • Apply vendor-provided updates or mitigations.
  • Review affected product exposure and access logs.

Public PoC references

No public PoC reference has passed the current publication threshold.