In the Linux kernel, the following vulnerability has been resolved:
drm/i915: Fix potential bit_17 double-free
A userspace with multiple threads racing I915_GEM_SET_TILING to set the
tiling to I915_TILING_NONE could trigger a double free of the bit_17
bitmask. (Or conversely leak memory on the transition to tiled.) Move
allocation/free'ing of the bitmask within the section protected by the
obj lock.
[tursulin: Correct fixes tag and added cc stable.]
(cherry picked from commit 10e0cbaaf1104f449d695c80bcacf930dcd3c42e)
Security readout for executives and security teams
Plain-English summary
This is a local Linux kernel flaw in Intel i915 graphics handling. A low-privileged local user could trigger a race that causes a double free, with potential confidentiality, integrity, and availability impact. It is not remotely exploitable based on the supplied CVSS vector.
Executive priority
Prioritize patching shared Linux systems and endpoints with Intel graphics where untrusted local users or workloads exist. Treat as high priority, but below internet-facing remote-code-execution issues unless GPU access is broadly exposed.
Technical view
The drm/i915 I915_GEM_SET_TILING path could race when multiple userspace threads set tiling to I915_TILING_NONE, causing double-free of the bit_17 bitmask or memory leakage. The fix moves bitmask allocation and free operations inside the object lock.
Likely exposure
Exposure is most relevant on Linux systems using the Intel i915 DRM driver where low-privileged users or workloads can access graphics GEM interfaces. Multi-user desktops, developer workstations, and containerized workloads with GPU device access deserve attention.
Exploitation context
The bundle marks KEV as false and provides no cited evidence of active exploitation. The vulnerability requires local low-privileged access, no user interaction, and a race condition involving concurrent graphics tiling requests.
Researcher notes
The supplied record identifies CWE-415 and CVSS 7.8 local privilege context. Version data appears partly commit-based and partly release-based, so use vendor backport evidence and the linked stable commits for precise remediation mapping.
Mitigation direction
Apply vendor or stable Linux kernel updates containing the referenced drm/i915 fix.
Check distribution advisories for backported fixes before relying on upstream version numbers.
Reduce untrusted local access to systems exposing Intel i915 graphics interfaces until patched.
Review GPU device exposure in containers and shared compute environments.
Validation and detection
Inventory Linux kernel versions and vendor package changelogs for the referenced fix.
Identify systems using Intel i915 DRM graphics support.
Confirm which users or workloads can access exposed GPU device nodes.
Track remediation evidence through endpoint inventory or kernel package compliance reporting.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
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.
cwe · low confidence lookup
CWE-415: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
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.
1CVSS vectors
3Timeline events
1ADP providers
5Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We 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.