CVE-2026-31453: xfs: avoid dereferencing log items after push callbacks
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.
Security readout for executives and security teams
Plain-English summary
A Linux XFS flaw can access a log item after another kernel task has freed it. A low-privileged local user may be able to trigger memory corruption, potentially affecting confidentiality, integrity, or availability. The supplied evidence does not establish practical exploitation or attacks in the wild.
Executive priority
Treat as a high-priority kernel update for multi-user systems, shared hosting, and XFS-backed infrastructure. The local-access requirement reduces internet-facing urgency, but potential kernel-level impact supports timely remediation. Validate distribution-specific exposure before emergency action because the supplied version mapping is incomplete.
Technical view
After an XFS AIL push callback releases its lock, inode reclaim or the quota shrinker can free the log item. Subsequent tracepoint handling dereferences that stale pointer. The fix captures the item type, flags, and log sequence number before the callback and changes tracing to use those saved values.
Likely exposure
Exposure requires a vulnerable Linux kernel, use of XFS, and access to the affected local kernel path. The supplied version data identifies several releases but does not clearly map every release to a fixing commit. Distribution backports may also change exposure, so kernel package provenance and vendor advisories must be checked.
Exploitation context
CVSS 3.1 scores this 7.8 with local access, low complexity, low privileges, and no user interaction. CISA KEV status is false, and the supplied sources contain no evidence of active exploitation or a public exploit. Real-world exploitability beyond a crash or memory-safety failure remains unconfirmed.
Researcher notes
The reported condition is a post-callback stale-pointer dereference associated with XFS AIL tracing. The bundle supplies six stable-kernel commits but no CWE, reproducer, affected configuration details, or definitive branch-to-fix mapping. Analysis should distinguish vulnerable code presence from reachability and should account for distribution backports.
Mitigation direction
Install a vendor-supported kernel containing the applicable cited stable fix.
Prioritize XFS hosts accessible to untrusted or low-privileged local users.
Use vendor guidance to map distribution kernels and backports to the fixing commits.
Reboot affected systems into the updated kernel after installation.
Validation and detection
Inventory running kernel versions and identify systems mounting XFS filesystems.
Check distribution changelogs for CVE-2026-31453 or the applicable fixing commit.
Confirm the active kernel after reboot matches the remediated vendor package.
Monitor affected hosts for kernel faults involving XFS AIL, reclaim, quotas, or tracepoints.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2026-31453 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
0ADP providers
7Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.