CVE-2026-31454
What it is
In the Linux kernel, the following vulnerability has been resolved: xfs: save ailp before dropping the AIL lock in push callbacks In xfs_inode_item_push() and xfs_qm_dquot_logitem_push(), the AIL lock is dropped to perform buffer IO. Once the cluster buffer no longer protects the log item from reclaim, the log item may be freed by background reclaim or the dquot shrinker. The subsequent spin_lock() call dereferences lip->li_ailp, which is a use-after-free. Fix this by saving the ailp pointer in a local variable while the AIL lock is held and the log item is guaranteed to be valid.
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
- Modified
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-31454.md and follow it. Check whether this project is affected by CVE-2026-31454. 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/19437e4f7bb909afde832b39372aa2f3ce3cfd88
- https://git.kernel.org/stable/c/394d70b86fae9fe865e7e6d9540b7696f73aa9b6
- https://git.kernel.org/stable/c/4c7d50147316cf049462f327c4a3e9dc2b7f1dd0
- https://git.kernel.org/stable/c/50f5f056807b7bed74f4f307f2ca0ed92f3e556d
- https://git.kernel.org/stable/c/6dbe17f19c290a72ce57d5abc70e1fad0c3e14e5
- https://git.kernel.org/stable/c/75669e987137f49c99ca44406bf0200d1892dd16
- https://git.kernel.org/stable/c/d8fc60bbaf5aea1604bf9f4ed565da6a1ac7a87d
- https://git.kernel.org/stable/c/edd1637d4e3911ab6c760f553f2040fe72f61a13
References
- https://git.kernel.org/stable/c/19437e4f7bb909afde832b39372aa2f3ce3cfd88
- https://git.kernel.org/stable/c/394d70b86fae9fe865e7e6d9540b7696f73aa9b6
- https://git.kernel.org/stable/c/4c7d50147316cf049462f327c4a3e9dc2b7f1dd0
- https://git.kernel.org/stable/c/50f5f056807b7bed74f4f307f2ca0ed92f3e556d
- https://git.kernel.org/stable/c/6dbe17f19c290a72ce57d5abc70e1fad0c3e14e5
- https://git.kernel.org/stable/c/75669e987137f49c99ca44406bf0200d1892dd16
- https://git.kernel.org/stable/c/d8fc60bbaf5aea1604bf9f4ed565da6a1ac7a87d
- https://git.kernel.org/stable/c/edd1637d4e3911ab6c760f553f2040fe72f61a13