xfs: save ailp before dropping the AIL lock in push callbacks
Summary
| CVE | CVE-2026-31454 |
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-04-22 14:16:39 UTC |
| Updated | 2026-04-22 14:16:39 UTC |
| Description | 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. |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected 90c60e16401248a4900f3f9387f563d0178dcf34 edd1637d4e3911ab6c760f553f2040fe72f61a13 git |
Not specified |
| CNA |
Linux |
Linux |
affected 90c60e16401248a4900f3f9387f563d0178dcf34 19437e4f7bb909afde832b39372aa2f3ce3cfd88 git |
Not specified |
| CNA |
Linux |
Linux |
affected 90c60e16401248a4900f3f9387f563d0178dcf34 6dbe17f19c290a72ce57d5abc70e1fad0c3e14e5 git |
Not specified |
| CNA |
Linux |
Linux |
affected 90c60e16401248a4900f3f9387f563d0178dcf34 75669e987137f49c99ca44406bf0200d1892dd16 git |
Not specified |
| CNA |
Linux |
Linux |
affected 90c60e16401248a4900f3f9387f563d0178dcf34 d8fc60bbaf5aea1604bf9f4ed565da6a1ac7a87d git |
Not specified |
| CNA |
Linux |
Linux |
affected 90c60e16401248a4900f3f9387f563d0178dcf34 50f5f056807b7bed74f4f307f2ca0ed92f3e556d git |
Not specified |
| CNA |
Linux |
Linux |
affected 90c60e16401248a4900f3f9387f563d0178dcf34 4c7d50147316cf049462f327c4a3e9dc2b7f1dd0 git |
Not specified |
| CNA |
Linux |
Linux |
affected 90c60e16401248a4900f3f9387f563d0178dcf34 394d70b86fae9fe865e7e6d9540b7696f73aa9b6 git |
Not specified |
| CNA |
Linux |
Linux |
affected 5.9 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 5.9 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 5.10.253 5.10.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 5.15.203 5.15.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.1.168 6.1.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.6.131 6.6.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.12.80 6.12.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.18.21 6.18.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.19.11 6.19.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.0 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/d8fc60bbaf5aea1604bf9f4ed565da6a1ac7a87d |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/50f5f056807b7bed74f4f307f2ca0ed92f3e556d |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/394d70b86fae9fe865e7e6d9540b7696f73aa9b6 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/4c7d50147316cf049462f327c4a3e9dc2b7f1dd0 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/edd1637d4e3911ab6c760f553f2040fe72f61a13 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/6dbe17f19c290a72ce57d5abc70e1fad0c3e14e5 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/75669e987137f49c99ca44406bf0200d1892dd16 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/19437e4f7bb909afde832b39372aa2f3ce3cfd88 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.