Security readout for executives and security teams
Plain-English summary
A race condition in Linux’s Intel i915 graphics driver can access GPU fence state after it is no longer safe, potentially crashing the kernel or causing broader system compromise. Exploitation requires local, low-privileged access; this is not described as remotely exploitable.
Executive priority
Schedule expedited patching for exposed Intel graphics systems, especially shared workstations and multi-user hosts. Treat this as a serious local privilege and availability risk, but not as an internet-wide emergency because active exploitation is not established.
Technical view
Fence-register revocation can race with completion callbacks still using the fence. The missing wait for fence activity to become idle creates a potential use-after-free condition. CI reproduced kernel BUG failures on Alder Lake-P and other platforms. The upstream correction waits for fence idleness before revocation.
Likely exposure
Exposure is limited to systems running an affected Linux kernel with the Intel i915 graphics driver and relevant GPU hardware. The supplied version data indicates multiple kernel branches beginning with 5.8, but exact distribution package status should be confirmed through vendor advisories.
Exploitation context
The CVSS 3.1 score is 7.8 with local access, low complexity, low privileges, and no user interaction. The supplied sources establish sporadic crashes during graphics-driver testing, but provide no evidence of public exploitation or CISA KEV listing.
Researcher notes
The observed failure occurs during i915 hangcheck self-tests and involves parallel fence revocation and request-completion callbacks. The evidence demonstrates a kernel BUG and identifies a potential use-after-free, but does not establish reliable privilege escalation, affected-hardware completeness, or real-world exploitation.
Mitigation direction
- Install a vendor-supported kernel containing the applicable stable i915 fix.
- Prioritize multi-user systems where untrusted local users can access Intel GPU functionality.
- If immediate updating is impossible, consult the distribution vendor for supported mitigations.
- Reboot into the corrected kernel after installation.
Validation and detection
- Inventory kernel versions, Intel GPU hardware, and whether the i915 module is active.
- Compare installed kernel packages with the CVE record and distribution security advisories.
- Confirm the running kernel changed after patching and rebooting.
- Monitor kernel logs for i915 fence-revocation BUG messages or related crashes.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2024-41092 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9LinuxVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/f771b91f21c46ad1217328d05e72a2c7e3add535CVE reference, Linux
- https://git.kernel.org/stable/c/29c0fdf49078ab161570d3d1c6e13d66f182717dCVE reference, Linux
- https://git.kernel.org/stable/c/ca0fabd365a27a94a36e68a7a02df8ff3c13dac6CVE reference, Linux
- https://git.kernel.org/stable/c/06dec31a0a5112a91f49085e8a8fa1a82296d5c7CVE reference, Linux
- https://git.kernel.org/stable/c/414f4a31f7a811008fd9a33b06216b060bad18fcCVE reference, Linux
- https://git.kernel.org/stable/c/996c3412a06578e9d779a16b9e79ace18125ab50CVE reference, Linux
- https://lists.debian.org/debian-lts-announce/2025/01/msg00001.htmlCVE reference, CVE
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.