Kernel memory corruption via fence revocation race
Published Jul 29, 2024 · Updated Aug 5, 2026
Use-after-free in Linux kernel i915 GGTT fencing from 5.8 allows local users with render-node access to corrupt kernel memory. i915_vma_revoke_fence calls fence_write without first waiting for fence->active to become idle, so completion callbacks can run while fence registers are revoked and reference freed i915 VMA or GEM objects. Reachability requires an Intel i915 GPU and low-privilege access to a DRM render node; exploitation supports kernel memory reads and writes, control-flow hijacking, or a full system crash.
Summary
What happened
Use-after-free in Linux kernel i915 GGTT fencing from 5.8 allows local users with render-node access to corrupt kernel memory. i915_vma_revoke_fence calls fence_write without first waiting for fence->active to become idle, so completion callbacks can run while fence registers are revoked and reference freed i915 VMA or GEM objects. Reachability requires an Intel i915 GPU and low-privilege access to a DRM render node; exploitation supports kernel memory reads and writes, control-flow hijacking, or a full system crash.
The record
- CVE
- CVE-2024-41092
- Published
- Jul 29, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-416, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 29, 2024CVE publishedPublication date reported by the CVE source.
- Aug 5, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0d86ee35097ae0f1c2c50f2b8035ef480e25e4f1 <06dec31a0a5112a91f49085e8a8fa1a82296d5c7
- Affected versionversion=0d86ee35097ae0f1c2c50f2b8035ef480e25e4f1 <29c0fdf49078ab161570d3d1c6e13d66f182717d
- Affected versionversion=0d86ee35097ae0f1c2c50f2b8035ef480e25e4f1 <414f4a31f7a811008fd9a33b06216b060bad18fc
- Affected versionversion=0d86ee35097ae0f1c2c50f2b8035ef480e25e4f1 <996c3412a06578e9d779a16b9e79ace18125ab50
- Affected versionversion=0d86ee35097ae0f1c2c50f2b8035ef480e25e4f1 <ca0fabd365a27a94a36e68a7a02df8ff3c13dac6
- Affected versionversion=0d86ee35097ae0f1c2c50f2b8035ef480e25e4f1 <f771b91f21c46ad1217328d05e72a2c7e3add535
- Affected versionversion=5.8
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo