# Input: cros_ec_keyb - fix an invalid memory access

CVE record · `CVE-2025-40263`

- **Identifiers:** `CVE-2025-40263`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 4 Dec 2025
- **Updated:** 2 Jun 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 4 Dec 2025, 16:08 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: `ca1eadbfcd36bec73f2a2111c28e8c7e9e8ae6c0 to before d74864291cb8bd784d44d1d02e87109cf88666bb` (git)
  - affected: `ca1eadbfcd36bec73f2a2111c28e8c7e9e8ae6c0 to before 9cf59f4724a9ee06ebb06c76b8678ac322e850b7` (git)
  - affected: `ca1eadbfcd36bec73f2a2111c28e8c7e9e8ae6c0 to before 6d81068685154535af06163eb585d6d9663ec7ec` (git)
  - affected: `ca1eadbfcd36bec73f2a2111c28e8c7e9e8ae6c0 to before 2d251c15c27e2dd16d6318425d2f7260cbd47d39` (git)
  - affected: `ca1eadbfcd36bec73f2a2111c28e8c7e9e8ae6c0 to before e08969c4d65ac31297fcb4d31d4808c789152f68` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `5.19`
  - unaffected: `before 5.19` (semver)
  - unaffected: `6.1.159 to 6.1.*, inclusive` (semver)
  - unaffected: `6.6.118 to 6.6.*, inclusive` (semver)
  - unaffected: `6.12.60 to 6.12.*, inclusive` (semver)
  - unaffected: `6.17.10 to 6.17.*, inclusive` (semver)
  - unaffected: `6.18 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.0021, the 10th percentile, on 19 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 4 Dec 2025. New records show when each source confirmed them.

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/d74864291cb8bd784d44d1d02e87109cf88666bb>
- <https://git.kernel.org/stable/c/9cf59f4724a9ee06ebb06c76b8678ac322e850b7>
- <https://git.kernel.org/stable/c/6d81068685154535af06163eb585d6d9663ec7ec>
- <https://git.kernel.org/stable/c/2d251c15c27e2dd16d6318425d2f7260cbd47d39>
- <https://git.kernel.org/stable/c/e08969c4d65ac31297fcb4d31d4808c789152f68>

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-40263>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

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