LiveActive security incident?Get immediate response
CVE Record

CVE-2026-43280: drm/xe: Add bounds check on pat_index to prevent OOB kernel read in madvise

In the Linux kernel, the following vulnerability has been resolved: drm/xe: Add bounds check on pat_index to prevent OOB kernel read in madvise When user provides a bogus pat_index value through the madvise IOCTL, the xe_pat_index_get_coh_mode() function performs an array access without validating bounds. This allows a malicious user to trigger an out-of-bounds kernel read from the xe->pat.table array. The vulnerability exists because the validation in madvise_args_are_sane() directly calls xe_pat_index_get_coh_mode(xe, args->pat_index.val) without first checking if pat_index is within [0, xe->pat.n_entries). Although xe_pat_index_get_coh_mode() has a WARN_ON to catch this in debug builds, it still performs the unsafe array access in production kernels. v2(Matthew Auld) - Using array_index_nospec() to mitigate spectre attacks when the value is used v3(Matthew Auld) - Put the declarations at the start of the block (cherry picked from commit 944a3329b05510d55c69c2ef455136e2fc02de29)

HighCVSS 7.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A locally authenticated user may abuse the Linux Intel Xe graphics driver to read beyond a kernel array and potentially expose sensitive kernel memory or disrupt the system. This is not a remote-entry vulnerability, but multi-user systems and workloads granting users direct graphics-device access deserve prompt review.

Executive priority

Treat as a high-priority local privilege-boundary issue, especially on shared compute, desktop, or container hosts exposing Xe graphics devices. Patch through supported kernel channels promptly. Internet-facing status alone does not determine risk because exploitation begins from local access.

Technical view

The Xe DRM madvise IOCTL passes a user-controlled pat_index to xe_pat_index_get_coh_mode() without first confirming it is below xe->pat.n_entries. Production kernels consequently access xe->pat.table out of bounds. The published resolution adds bounds validation and uses array_index_nospec() when consuming the index.

Likely exposure

Exposure requires a kernel containing the vulnerable Xe driver path and a low-privileged local user able to reach its madvise IOCTL. The supplied version metadata is ambiguous, so determine exposure using distribution advisories, kernel build provenance, and the referenced stable fixes rather than version strings alone.

Exploitation context

The CVSS vector describes local, low-complexity exploitation requiring low privileges and no user interaction, with high confidentiality and availability impact but no integrity impact. The bundle marks this CVE as absent from KEV and provides no evidence of active exploitation, public weaponization, or a remote attack path.

Researcher notes

The unsafe access occurs during argument validation: madvise_args_are_sane() calls xe_pat_index_get_coh_mode() before validating the user-supplied index. A debug WARN_ON does not prevent the production read. Exact vulnerable and fixed release boundaries cannot be established confidently from the flattened version data supplied; validate using commit ancestry and distributor backports.

Mitigation direction

  • Apply a vendor-supported kernel update containing the applicable referenced stable fix.
  • Check distribution guidance for backported fixes; do not rely solely on displayed kernel versions.
  • Prioritize shared systems where untrusted users receive direct Xe graphics-device access.
  • Restrict unnecessary local or container access to affected graphics devices until patched.

Validation and detection

  • Inventory kernels and identify systems using or exposing the Xe DRM driver.
  • Compare kernel provenance against vendor advisories and the three referenced stable commits.
  • Confirm the installed update includes pat_index bounds validation and array_index_nospec handling.
  • Reassess graphics-device permissions for local users, containers, and virtualized workloads.
Prepared
Confidence
high
Sources
5

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-2026-43280 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.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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.1CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H1.85.2Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.1High
CVSS 3.1 vector shape for CVE-2026-43280Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxada7486c5668db542a7d361268df931aca5b726a, ada7486c5668db542a7d361268df931aca5b726a, ada7486c5668db542a7d361268df931aca5b726aunaffected
LinuxLinux6.18, 0, 6.18.16, 6.19.6, 7.0affected
Weakness

CWE details

No CWE listed

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