CVE-2026-31455
What it is
In the Linux kernel, the following vulnerability has been resolved: xfs: stop reclaim before pushing AIL during unmount The unmount sequence in xfs_unmount_flush_inodes() pushed the AIL while background reclaim and inodegc are still running. This is broken independently of any use-after-free issues - background reclaim and inodegc should not be running while the AIL is being pushed during unmount, as inodegc can dirty and insert inodes into the AIL during the flush, and background reclaim can race to abort and free dirty inodes. Reorder xfs_unmount_flush_inodes() to stop inodegc and cancel background reclaim before pushing the AIL. Stop inodegc before cancelling m_reclaim_work because the inodegc worker can re-queue m_reclaim_work via xfs_inodegc_set_reclaimable.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 0.1% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.1% in the next 30 days (EPSS).
- Severity: 7.8 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.1% · EPSS, next 30 days
- Weakness
- CWE-416 · Use after free
- Record status
- Analyzed
Affected
- Linux Kernel < 5.10.253
- Linux Kernel < 5.15.203
- Linux Kernel < 6.1.168
- Linux Kernel < 6.6.131
- Linux Kernel < 6.12.80
- Linux Kernel < 6.18.21
- Linux Kernel < 6.19.11
- Linux Kernel 7.0
Attack profile CVSS 3.1 · 7.8
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-31455.md and follow it. Check whether this project is affected by CVE-2026-31455. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/239d734c00644072862fa833805c4471573b1445
- https://git.kernel.org/stable/c/4f24a767e3d64a5f58c595b5c29b6063a201f1e3
- https://git.kernel.org/stable/c/558e3275d8a3b101be18a7fe7d1634053e9d9b07
- https://git.kernel.org/stable/c/8147e304d7d32fd5c3e943babc296ce2873dc279
- https://git.kernel.org/stable/c/a89434a6188d8430ea31120da96e3e4cefb58686
- https://git.kernel.org/stable/c/bda27fc0b4eb3a425d9a18475c4cb94fbe862c60
- https://git.kernel.org/stable/c/d38135af04a3ad8a585c899d176efc8e97853115
- https://git.kernel.org/stable/c/e6cc490048f78b009259a5f032acead9f789c34c
References
- https://git.kernel.org/stable/c/239d734c00644072862fa833805c4471573b1445
- https://git.kernel.org/stable/c/4f24a767e3d64a5f58c595b5c29b6063a201f1e3
- https://git.kernel.org/stable/c/558e3275d8a3b101be18a7fe7d1634053e9d9b07
- https://git.kernel.org/stable/c/8147e304d7d32fd5c3e943babc296ce2873dc279
- https://git.kernel.org/stable/c/a89434a6188d8430ea31120da96e3e4cefb58686
- https://git.kernel.org/stable/c/bda27fc0b4eb3a425d9a18475c4cb94fbe862c60
- https://git.kernel.org/stable/c/d38135af04a3ad8a585c899d176efc8e97853115
- https://git.kernel.org/stable/c/e6cc490048f78b009259a5f032acead9f789c34c