# arm64/fpsimd: Discard stale CPU state when handling SME traps

CVE record · `CVE-2025-38170`

- **Identifiers:** `CVE-2025-38170`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 3 Jul 2025
- **Updated:** 5 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 3 Jul 2025, 08:36 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: `8bd7f91c03d886f41d35f6108078d20be5a4a1bd to before de89368de3894a8db27caeb8fd902ba1c49f696a` (git)
  - affected: `8bd7f91c03d886f41d35f6108078d20be5a4a1bd to before 43be952e885476dafb74aa832c0847b2f4f650c6` (git)
  - affected: `8bd7f91c03d886f41d35f6108078d20be5a4a1bd to before 6103f9ba51a59afb5a0f32299c837377c5a5a693` (git)
  - affected: `8bd7f91c03d886f41d35f6108078d20be5a4a1bd to before c4a4786d93e99517d6f10ed56b9ffba4ce88d3b3` (git)
  - affected: `8bd7f91c03d886f41d35f6108078d20be5a4a1bd to before d3eaab3c70905c5467e5c4ea403053d67505adeb` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `5.19`
  - unaffected: `before 5.19` (semver)
  - unaffected: `6.1.142 to 6.1.*, inclusive` (semver)
  - unaffected: `6.6.94 to 6.6.*, inclusive` (semver)
  - unaffected: `6.12.34 to 6.12.*, inclusive` (semver)
  - unaffected: `6.15.3 to 6.15.*, inclusive` (semver)
  - unaffected: `6.16 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.0017, the 6th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 3 Jul 2025, 08:36 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2025-38170)
- 3 Jul 2025, 09:15 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2025-38170)

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/de89368de3894a8db27caeb8fd902ba1c49f696a>
- <https://git.kernel.org/stable/c/43be952e885476dafb74aa832c0847b2f4f650c6>
- <https://git.kernel.org/stable/c/6103f9ba51a59afb5a0f32299c837377c5a5a693>
- <https://git.kernel.org/stable/c/c4a4786d93e99517d6f10ed56b9ffba4ce88d3b3>
- <https://git.kernel.org/stable/c/d3eaab3c70905c5467e5c4ea403053d67505adeb>

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

---

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