Quick answers
- Is CVE-2026-99147 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-99147 being exploited in the wild.
- How severe is CVE-2026-99147?
- Informational severity, published 28 October 2026.
- Which products and versions are affected?
- Linux kernel 6.6 and later.
- Is there a fix for CVE-2026-99147?
- Yes: fixed in Linux kernel 6.6+ stable series with commit 26401a4999f1596a515b2e704e7066ac09306488. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-99147 attacked?
- It is attacked with local access, in an operating system.
- Am I affected by CVE-2026-99147?
- Check whether you run Linux kernel at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: Linux kernel 6.6+ stable series with commit 26401a4999f1596a515b2e704e7066ac09306488
Technical details
The vulnerability exists in the drm_exec mechanism used for locking Graphics Execution Memory (GEM) buffer objects. When a contention is detected, the code pre-locks a contended object that may be scheduled for destruction, but fails to add it to the locked object array until explicitly locked again by the driver. This causes a mismatch in the number of reserved fence slots when drm_exec_for_each_locked_object() iterates over locked objects, leading to potential buffer overflow and memory corruption.
Affected products
- Linux kernel 6.6 and later
Timeline
- 2026-10-28: disclosed
- 2026-10-14: patched