# KVM: x86: Use scratch field in MMIO fragment to hold small write values

CVE record · `CVE-2026-31588`

- **Identifiers:** `CVE-2026-31588`
- **State:** Confirmed
- **Severity:** CVSS 8.8 High
- **Critical:** No
- **CNA:** Linux
- **Weakness (CWE):** [CWE-416](https://cwe.mitre.org/data/definitions/416.html)
- **Tags:** [Memory corruption](https://agentprime.io/advisories/tag/memory-corruption.md)
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 24 Apr 2026
- **Updated:** 19 Oct 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 24 Apr 2026, 14:42 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: `f78146b0f9230765c6315b2e14f56112513389ad to before 019d0bd32b9a4646ba35d904907452039e2db700` (git)
  - affected: `f78146b0f9230765c6315b2e14f56112513389ad to before 4569c66dd9e94a22cd0796b6514a8b25ffff16a1` (git)
  - affected: `f78146b0f9230765c6315b2e14f56112513389ad to before 52570e73d48f1c73836d37e594667117b4c2a5a8` (git)
  - affected: `f78146b0f9230765c6315b2e14f56112513389ad to before dc6a6c3db3a4eca7e747cfc46e22c08d016c68f7` (git)
  - affected: `f78146b0f9230765c6315b2e14f56112513389ad to before b5a02d37eb0739f462fa12df449ab9b3480c783b` (git)
  - affected: `f78146b0f9230765c6315b2e14f56112513389ad to before 22d2ff69d487a32a8b88f9c970120fc2daa08a77` (git)
  - affected: `f78146b0f9230765c6315b2e14f56112513389ad to before 2b83d91e9ae92fe1258d7040a32430bbb3bb7d6e` (git)
  - affected: `f78146b0f9230765c6315b2e14f56112513389ad to before 3a7b6d75c8f85b09dea893f64a85a356bcf6c3fe` (git)
  - affected: `f78146b0f9230765c6315b2e14f56112513389ad to before 0b16e69d17d8c35c5c9d5918bf596c75a44655d3` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `3.5`
  - unaffected: `before 3.5` (semver)
  - unaffected: `5.10.258 to 5.10.*, inclusive` (semver)
  - unaffected: `5.15.209 to 5.15.*, inclusive` (semver)
  - unaffected: `6.1.175 to 6.1.*, inclusive` (semver)
  - unaffected: `6.6.136 to 6.6.*, inclusive` (semver)
  - unaffected: `6.12.83 to 6.12.*, inclusive` (semver)
  - unaffected: `6.18.24 to 6.18.*, inclusive` (semver)
  - unaffected: `6.19.14 to 6.19.*, inclusive` (semver)
  - unaffected: `7.0.1 to 7.0.*, inclusive` (semver)
  - unaffected: `7.1 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

- 8.8 High, CVSS 3.1: `CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`, from CNA (Linux)

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

## Timeline

- 24 Apr 2026, 15:16 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-31588)

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/019d0bd32b9a4646ba35d904907452039e2db700>
- <https://git.kernel.org/stable/c/4569c66dd9e94a22cd0796b6514a8b25ffff16a1>
- <https://git.kernel.org/stable/c/52570e73d48f1c73836d37e594667117b4c2a5a8>
- <https://git.kernel.org/stable/c/dc6a6c3db3a4eca7e747cfc46e22c08d016c68f7>
- <https://git.kernel.org/stable/c/b5a02d37eb0739f462fa12df449ab9b3480c783b>
- <https://git.kernel.org/stable/c/22d2ff69d487a32a8b88f9c970120fc2daa08a77>
- <https://git.kernel.org/stable/c/2b83d91e9ae92fe1258d7040a32430bbb3bb7d6e>
- <https://git.kernel.org/stable/c/3a7b6d75c8f85b09dea893f64a85a356bcf6c3fe>
- <https://git.kernel.org/stable/c/0b16e69d17d8c35c5c9d5918bf596c75a44655d3>

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

---

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