Local kernel memory corruption via XFS use-after-free
Published Apr 22, 2026 · Updated Apr 22, 2026
Use-after-free in XFS AIL push callbacks in Linux Kernel allows local users to trigger kernel memory corruption through filesystem activity. The callbacks release the AIL lock for buffer I/O, permitting reclaim to free an inode or dquot log item before spin_lock dereferences its stale li_ailp pointer. A low-privilege user needs write access to an already mounted XFS filesystem; filesystem churn can race the asynchronous xfsaild callback and crash or destabilize the kernel.
Summary
What happened
Use-after-free in XFS AIL push callbacks in Linux Kernel allows local users to trigger kernel memory corruption through filesystem activity. The callbacks release the AIL lock for buffer I/O, permitting reclaim to free an inode or dquot log item before spin_lock dereferences its stale li_ailp pointer. A low-privilege user needs write access to an already mounted XFS filesystem; filesystem churn can race the asynchronous xfsaild callback and crash or destabilize the kernel.
The record
- CVE
- CVE-2026-31454
- Published
- Apr 22, 2026
- Updated
- Apr 22, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-416, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 22, 2026CVE publishedPublication date reported by the CVE source.
- Apr 22, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.9
- Affected versionversion=90c60e16401248a4900f3f9387f563d0178dcf34 <19437e4f7bb909afde832b39372aa2f3ce3cfd88
- Affected versionversion=90c60e16401248a4900f3f9387f563d0178dcf34 <394d70b86fae9fe865e7e6d9540b7696f73aa9b6
- Affected versionversion=90c60e16401248a4900f3f9387f563d0178dcf34 <4c7d50147316cf049462f327c4a3e9dc2b7f1dd0
- Affected versionversion=90c60e16401248a4900f3f9387f563d0178dcf34 <50f5f056807b7bed74f4f307f2ca0ed92f3e556d
- Affected versionversion=90c60e16401248a4900f3f9387f563d0178dcf34 <6dbe17f19c290a72ce57d5abc70e1fad0c3e14e5
- Affected versionversion=90c60e16401248a4900f3f9387f563d0178dcf34 <75669e987137f49c99ca44406bf0200d1892dd16
- Affected versionversion=90c60e16401248a4900f3f9387f563d0178dcf34 <d8fc60bbaf5aea1604bf9f4ed565da6a1ac7a87d
- Affected versionversion=90c60e16401248a4900f3f9387f563d0178dcf34 <edd1637d4e3911ab6c760f553f2040fe72f61a13
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo