CVE-2026-31453
Last modified
CVE-2026-31453 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. 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.. EPSS estimates a 0.13% chance of exploitation in the next 30 days.
Description
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 5.9, < 6.1.168 | — |
| Linux | Linux Kernel | >= 6.2, < 6.6.131 | — |
| Linux | Linux Kernel | >= 6.7, < 6.12.80 | — |
| Linux | Linux Kernel | >= 6.13, < 6.18.21 | — |
| Linux | Linux Kernel | >= 6.19, < 6.19.11 | — |
| Linux | Linux Kernel | 7.0 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-31453?
How severe is CVE-2026-31453?
How do I fix CVE-2026-31453?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-31448In the Linux kernel, the following vulnerability has been re…9.4
- CVE-2026-31449In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-3145A flaw has been found in libvips up to 8.18.0. The affected …7.8
- CVE-2026-31450In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-31451In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-31452In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-31454In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-31455In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-31456In the Linux kernel, the following vulnerability has been re…4.7
- CVE-2026-31457In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-31458In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-31459In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2026-31453?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
