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

> Local attackers can trigger kernel errors by accessing unsupported sysfs attributes in the Intel Xe GPU driver for Virtual Functions.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Oct 2025
- **Updated:** 11 May 2026
- **Also known as:** BELL-CVE-2025-40023, DEBIAN-CVE-2025-40023, GHSA-m3f2-pghf-98q6, UBUNTU-CVE-2025-40023

## What is CVE-2025-40023?

CVE-2025-40023 is a denial of service vulnerability in Linux, published on 24 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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)

## Which versions are affected by CVE-2025-40023?


## How do I fix CVE-2025-40023?

Apply the vendor's patch.

## Is CVE-2025-40023 being exploited?

There is no known exploitation of CVE-2025-40023 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-40023 and fix it if it is affected.

What it is: CVE-2025-40023 is a denial of service vulnerability in Linux, published on 24 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-40023 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-40023/ (Markdown: https://insights.sbomify.com/CVE-2025-40023/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-40023
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-40023
- OSV: https://osv.dev/vulnerability/CVE-2025-40023

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-40023/
Summaries are generated and may contain mistakes; the official description above is the record.