# kmsan: fix out-of-bounds access to shadow memory

CVE record · `CVE-2025-40008`

- **Identifiers:** `CVE-2025-40008`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 20 Oct 2025
- **Updated:** 23 May 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 20 Oct 2025, 15:26 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `9ff078f5bad8990091f1639347de5e02636e9536 to before e6684ed39edc35401a3341f85b1ab50a6f89a45d` (git)
  - affected: `19e85d939001946671643f4c16e1de8c633a6ce0 to before df1fa034c0fc229a63d01ffb20bb919b839cb576` (git)
  - affected: `2ef3cec44c60ae171b287db7fc2aa341586d65ba to before f84e48707051812289b6c2684d4df2daa9d3bfbc` (git)
  - affected: `2ef3cec44c60ae171b287db7fc2aa341586d65ba to before 5855792c6bb9a825607845db3feaddaff0414ec3` (git)
  - affected: `2ef3cec44c60ae171b287db7fc2aa341586d65ba to before 85e1ff61060a765d91ee62dc5606d4d547d9d105` (git)
  - affected: `abeede7011da6c88e83ed260b909c140b8c9c250` (git)
  - affected: `6.1.94 to before 6.1.155` (semver)
  - affected: `6.6.34 to before 6.6.109` (semver)
  - affected: `6.9.5 to before 6.10` (semver)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `6.10`
  - unaffected: `before 6.10` (semver)
  - unaffected: `6.1.155 to 6.1.*, inclusive` (semver)
  - unaffected: `6.6.109 to 6.6.*, inclusive` (semver)
  - unaffected: `6.12.50 to 6.12.*, inclusive` (semver)
  - unaffected: `6.16.10 to 6.16.*, inclusive` (semver)
  - unaffected: `6.17 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0024, the 15th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the CVE Program, published 20 Oct 2025. New records show when each source confirmed them.

## Sources

- [CVE List: CVE-2025-40008](https://www.cve.org/CVERecord?id=CVE-2025-40008)
- [NVD: CVE-2025-40008](https://nvd.nist.gov/vuln/detail/CVE-2025-40008)

### References from the CNA

- <https://git.kernel.org/stable/c/e6684ed39edc35401a3341f85b1ab50a6f89a45d>
- <https://git.kernel.org/stable/c/df1fa034c0fc229a63d01ffb20bb919b839cb576>
- <https://git.kernel.org/stable/c/f84e48707051812289b6c2684d4df2daa9d3bfbc>
- <https://git.kernel.org/stable/c/5855792c6bb9a825607845db3feaddaff0414ec3>
- <https://git.kernel.org/stable/c/85e1ff61060a765d91ee62dc5606d4d547d9d105>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2025-40008>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2025-40008/>. Everything for agents: <https://agentprime.io/llms.txt>.
