LiveActive security incident?Get immediate response
CVE Record

CVE-2025-71099: drm/xe/oa: Fix potential UAF in xe_oa_add_config_ioctl()

In the Linux kernel, the following vulnerability has been resolved: drm/xe/oa: Fix potential UAF in xe_oa_add_config_ioctl() In xe_oa_add_config_ioctl(), we accessed oa_config->id after dropping metrics_lock. Since this lock protects the lifetime of oa_config, an attacker could guess the id and call xe_oa_remove_config_ioctl() with perfect timing, freeing oa_config before we dereference it, leading to a potential use-after-free. Fix this by caching the id in a local variable while holding the lock. v2: (Matt A) - Dropped mutex_unlock(&oa->metrics_lock) ordering change from xe_oa_remove_config_ioctl() (cherry picked from commit 28aeaed130e8e587fd1b73b6d66ca41ccc5a1a31)

HighCVSS 7.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A flaw in the Linux kernel’s Xe graphics metrics code can let a locally authenticated user trigger access to freed memory. Successful exploitation could potentially compromise confidentiality, integrity, or availability, although the supplied sources do not demonstrate a working exploit or active attacks.

Executive priority

Prioritize affected multi-user systems, shared compute platforms, and endpoints where untrusted users have local access. Treat remediation as high priority but not an internet-wide emergency: the attack is local, requires privileges, and has no substantiated active-exploitation signal in the supplied evidence.

Technical view

A race in xe_oa_add_config_ioctl() dereferences oa_config->id after releasing metrics_lock, which protects the object’s lifetime. A concurrent removal request could free the object first, causing a use-after-free. The correction caches the ID while holding the lock. Practical exploitation impact is not established in the supplied evidence.

Likely exposure

Exposure requires an affected Linux kernel using the drm/xe OA interface and a low-privileged local attacker able to invoke the relevant operations. The bundle lists 6.11, 6.12.64, 6.18.4, and 6.19, but also contains an anomalous “0” entry; exact distribution package boundaries require vendor confirmation.

Exploitation context

The CVSS 3.1 score is 7.8 with local access, low complexity, low privileges, and no user interaction. Exploitation depends on winning a timing race. The CVE is not listed as KEV, and the supplied sources provide no evidence of active exploitation or a public proof of concept.

Researcher notes

The source establishes a lock-lifetime race and potential use-after-free but does not identify a CWE, proven exploitation primitive, or demonstrated impact. Version metadata is incomplete or malformed, so affected-range conclusions should be verified against distribution advisories and the referenced stable commits. Avoid treating theoretical high CIA impact as confirmed code execution.

Mitigation direction

  • Install a vendor-supported kernel release containing the referenced lifetime-handling correction.
  • Consult your Linux distribution’s security guidance for exact fixed package versions and reboot requirements.
  • Until patched, reduce untrusted local access to systems confirmed to use the affected interface.

Validation and detection

  • Inventory deployed kernel versions and identify systems using the Linux drm/xe driver.
  • Map distribution kernel packages against vendor advisories and the referenced stable fixes.
  • After updating, confirm systems booted into the corrected kernel rather than retaining the vulnerable release.
  • Review local access controls on exposed systems while remediation remains pending.
Prepared
Confidence
medium
Sources
5

Public sources used

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.

cve · low confidence lookup

CVE-2025-71099 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
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

Official CVE source material

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.

1CVSS vectors
3Timeline events
0ADP providers
4Source links

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.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2025-71099Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxcdf02fe1a94a768cbcd20f5c4e1a1d805f4a06c0, cdf02fe1a94a768cbcd20f5c4e1a1d805f4a06c0, cdf02fe1a94a768cbcd20f5c4e1a1d805f4a06c0unaffected
LinuxLinux6.11, 0, 6.12.64, 6.18.4, 6.19affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.