CVE-2026-31453
What it is
In the Linux kernel, the following vulnerability has been resolved: xfs: avoid dereferencing log items after push callbacks After xfsaild_push_item() calls iop_push(), the log item may have been freed if the AIL lock was dropped during the push. Background inode reclaim or the dquot shrinker can free the log item while the AIL lock is not held, and the tracepoints in the switch statement dereference the log item after iop_push() returns. Fix this by capturing the log item type, flags, and LSN before calling xfsaild_push_item(), and introducing a new xfs_ail_push_class trace event class that takes these pre-captured values and the ailp pointer instead of the log item pointer.
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-476 · NULL pointer dereference
- Record status
- Modified
Affected
- 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-31453.md and follow it. Check whether this project is affected by CVE-2026-31453. 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/451c6329d9afa45862c36fe6677eb7750db60617
- https://git.kernel.org/stable/c/7121b22b0bac89394cc4c6a54b5aebc15347bdf5
- https://git.kernel.org/stable/c/79ef34ec0554ec04bdbafafbc9836423734e1bd6
- https://git.kernel.org/stable/c/95fb5d643cc70959baa54cd17f52f80ffc3295e7
- https://git.kernel.org/stable/c/c4d603e8e58a3bf35480135ccca2b4f7238abda5
- https://git.kernel.org/stable/c/c8a2ab339b88d10fc34a3318c92f07d8a467019d
References
- https://git.kernel.org/stable/c/451c6329d9afa45862c36fe6677eb7750db60617
- https://git.kernel.org/stable/c/7121b22b0bac89394cc4c6a54b5aebc15347bdf5
- https://git.kernel.org/stable/c/79ef34ec0554ec04bdbafafbc9836423734e1bd6
- https://git.kernel.org/stable/c/95fb5d643cc70959baa54cd17f52f80ffc3295e7
- https://git.kernel.org/stable/c/c4d603e8e58a3bf35480135ccca2b4f7238abda5
- https://git.kernel.org/stable/c/c8a2ab339b88d10fc34a3318c92f07d8a467019d