LiveActive security incident?Get immediate response
CVE Record

CVE-2025-71076: drm/xe/oa: Limit num_syncs to prevent oversized allocations

In the Linux kernel, the following vulnerability has been resolved: drm/xe/oa: Limit num_syncs to prevent oversized allocations The OA open parameters did not validate num_syncs, allowing userspace to pass arbitrarily large values, potentially leading to excessive allocations. Add check to ensure that num_syncs does not exceed DRM_XE_MAX_SYNCS, returning -EINVAL when the limit is violated. v2: use XE_IOCTL_DBG() and drop duplicated check. (Ashutosh) (cherry picked from commit e057b2d2b8d815df3858a87dffafa2af37e5945b)

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This Linux kernel flaw lets local userspace request an overly large synchronization count in the drm/xe OA open path, which can trigger excessive memory allocation. The business risk is mainly local availability impact, not confirmed remote compromise. Public sources do not provide CVSS scoring or evidence of exploitation.

Executive priority

Treat as a routine-to-priority kernel availability issue where shared Linux workstations, GPU-enabled hosts, or multi-user systems are in scope. Escalate if business-critical systems allow untrusted local shell or container access to relevant graphics interfaces.

Technical view

The drm/xe/oa open parameters failed to validate num_syncs. A userspace caller could supply arbitrarily large values, leading to oversized allocations. The resolved fix caps num_syncs at DRM_XE_MAX_SYNCS and returns -EINVAL when exceeded. No CWE, CVSS, or exploit evidence is provided in the source bundle.

Likely exposure

Exposure appears limited to Linux systems running affected kernels with the drm/xe OA path reachable by local userspace. The supplied affected data lists Linux kernel versions and commits, but does not identify distributions, configurations, or device prerequisites.

Exploitation context

No active exploitation is indicated. The CVE is not marked KEV, and the provided sources describe the bug and fix only. Based on the description, exploitation would require local userspace access to the relevant kernel interface.

Researcher notes

The source record is sparse: no CVSS, CWE, distribution mapping, or exploit report is included. The useful anchor is the kernel fix: validation of num_syncs before allocation in drm/xe/oa, returning -EINVAL above DRM_XE_MAX_SYNCS.

Mitigation direction

  • Apply a kernel update containing one of the referenced stable fixes.
  • Check your Linux distribution advisory for exact fixed package versions.
  • Prioritize systems where untrusted local users can access graphics device interfaces.
  • If no update exists, follow vendor guidance for temporary controls.

Validation and detection

  • Inventory kernel versions and compare them with the affected source data.
  • Confirm whether systems use the drm/xe driver and OA functionality.
  • Verify the running kernel includes the num_syncs limit to DRM_XE_MAX_SYNCS.
  • Review vendor advisories for distribution-specific affected and fixed builds.
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-71076 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

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

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
LinuxLinux803d418b73387fda392ddd83eace757ac25cf15d, c8507a25cebd179db935dd266a33c51bef1b1e80, c8507a25cebd179db935dd266a33c51bef1b1e80, 6.12.17unaffected
LinuxLinux6.13, 0, 6.12.64, 6.18.3, 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.