# ext4: fix use-after-free in update_super_work when racing with umount

CVE record · `CVE-2026-31446`

- **Identifiers:** `CVE-2026-31446`
- **State:** Confirmed
- **Severity:** CVSS 7.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:** 22 Apr 2026
- **Updated:** 10 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 22 Apr 2026, 13:53 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: `52c3a04f9ec2a16a4204d6274db338cb8d5b2d74 to before c8fe17a1b308c3d8c703ebfb049b325f844342c3` (git)
  - affected: `b98535d091795a79336f520b0708457aacf55c67 to before c4d829737329f2290dd41e290b7d75effdb2a7ff` (git)
  - affected: `b98535d091795a79336f520b0708457aacf55c67 to before 9449f99ba04f5dd1c8423ad8a90b3651d7240d1d` (git)
  - affected: `b98535d091795a79336f520b0708457aacf55c67 to before 034053378dd81837fd6c7a43b37ee2e58d4f0b4e` (git)
  - affected: `b98535d091795a79336f520b0708457aacf55c67 to before c97e282f7bfd0c3554c63d289964a5ca6a1d2ffe` (git)
  - affected: `b98535d091795a79336f520b0708457aacf55c67 to before 08b10e6f37fc533a759e9833af0692242e8b3f93` (git)
  - affected: `b98535d091795a79336f520b0708457aacf55c67 to before d15e4b0a418537aafa56b2cb80d44add83e83697` (git)
  - affected: `585ef03c9e79672781f954daae730dfe24bf3a46` (git)
  - affected: `afe490e48d47df1b3f64012835c1bc2f075a8c8b` (git)
  - affected: `5.15.38 to before 5.15.203` (semver)
  - affected: `5.10.114 to before 5.11` (semver)
  - affected: `5.17.6 to before 5.18` (semver)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `5.18`
  - unaffected: `before 5.18` (semver)
  - unaffected: `5.15.203 to 5.15.*, inclusive` (semver)
  - unaffected: `6.1.168 to 6.1.*, inclusive` (semver)
  - unaffected: `6.6.131 to 6.6.*, inclusive` (semver)
  - unaffected: `6.12.80 to 6.12.*, inclusive` (semver)
  - unaffected: `6.18.21 to 6.18.*, inclusive` (semver)
  - unaffected: `6.19.11 to 6.19.*, inclusive` (semver)
  - unaffected: `7.0 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

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

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

## Timeline

- 22 Apr 2026, 13:53 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2026-31446)
- 22 Apr 2026, 14:16 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-31446)

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/c8fe17a1b308c3d8c703ebfb049b325f844342c3>
- <https://git.kernel.org/stable/c/c4d829737329f2290dd41e290b7d75effdb2a7ff>
- <https://git.kernel.org/stable/c/9449f99ba04f5dd1c8423ad8a90b3651d7240d1d>
- <https://git.kernel.org/stable/c/034053378dd81837fd6c7a43b37ee2e58d4f0b4e>
- <https://git.kernel.org/stable/c/c97e282f7bfd0c3554c63d289964a5ca6a1d2ffe>
- <https://git.kernel.org/stable/c/08b10e6f37fc533a759e9833af0692242e8b3f93>
- <https://git.kernel.org/stable/c/d15e4b0a418537aafa56b2cb80d44add83e83697>

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

---

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