LiveActive security incident?Get immediate response
CVE Record

CVE-2025-40023: drm/xe/vf: Don't expose sysfs attributes not applicable for VFs

In the Linux kernel, the following vulnerability has been resolved: drm/xe/vf: Don't expose sysfs attributes not applicable for VFs VFs can't read BMG_PCIE_CAP(0x138340) register nor access PCODE (already guarded by the info.skip_pcode flag) so we shouldn't expose attributes that require any of them to avoid errors like: [] xe 0000:03:00.1: [drm] Tile0: GT0: VF is trying to read an \ inaccessible register 0x138340+0x0 [] RIP: 0010:xe_gt_sriov_vf_read32+0x6c2/0x9a0 [xe] [] Call Trace: [] xe_mmio_read32+0x110/0x280 [xe] [] auto_link_downgrade_capable_show+0x2e/0x70 [xe] [] dev_attr_show+0x1a/0x70 [] sysfs_kf_seq_show+0xaa/0x120 [] kernfs_seq_show+0x41/0x60 (cherry picked from commit a2d6223d224f333f705ed8495bf8bebfbc585c35)

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

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue affects the xe graphics driver when GPU SR-IOV virtual functions are used. The driver exposed sysfs attributes that virtual functions cannot safely access, causing inaccessible register or PCODE access errors. The public sources do not show active exploitation, CVSS scoring, or business-impact details.

Executive priority

Treat as a targeted infrastructure hygiene item, not an emergency, unless your environment relies on xe GPU virtualization. Patch through normal kernel maintenance, with higher priority for shared virtualization hosts using GPU SR-IOV.

Technical view

The fix removes xe VF sysfs attributes requiring access to BMG_PCIE_CAP register 0x138340 or PCODE. VFs cannot read that register, and PCODE access is already gated by info.skip_pcode. Accessing affected attributes can trigger driver error paths such as xe_gt_sriov_vf_read32 during sysfs reads.

Likely exposure

Exposure appears limited to Linux systems using the xe DRM driver with SR-IOV virtual functions. The CVE record lists Linux kernel versions including 6.16, 6.16.10, and 6.17 as affected, but the provided version data is not fully clear.

Exploitation context

No source in the bundle reports active exploitation, KEV listing, public exploit code, or remote attackability. The described trigger is sysfs attribute access in a VF context, so assess local access paths and virtualization exposure rather than assuming internet-facing risk.

Researcher notes

Evidence is narrow and kernel-specific. The sources describe a resolved upstream driver bug and log trace, but do not provide CVSS, CWE, exploitability analysis, or affected distribution mapping. Validate against distro backports before declaring systems vulnerable.

Mitigation direction

  • Update to a kernel containing the referenced stable fixes.
  • Check your Linux distribution advisory for the exact fixed kernel package.
  • Prioritize hosts using Intel xe GPU SR-IOV virtual functions.
  • If no fixed package exists, follow vendor guidance for temporary controls.

Validation and detection

  • Identify systems running affected Linux kernel versions from the CVE record.
  • Confirm whether the xe DRM driver and GPU SR-IOV VFs are in use.
  • Verify the kernel package includes the referenced stable commits or equivalent backports.
  • Review kernel logs for inaccessible register errors tied to xe VF sysfs reads.
Prepared
Confidence
medium
Sources
4

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-40023 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
3Source 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
LinuxLinux0e414bf7ad012e55c8a0aa4e91f68cb1cf5801ff, 0e414bf7ad012e55c8a0aa4e91f68cb1cf5801ffunaffected
LinuxLinux6.16, 0, 6.16.10, 6.17affected
Weakness

CWE details

No CWE listed

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