dbcve.org
Linux KernelOperating system · Linux

CVE-2026-31453

HIGH · 7.8 CVSS v3.1 Published 2026-04-22
Fix available
A fix is available. Upgrade to 6.1.168 / 6.6.131 or later.
See remediation →
80/100
Remediation priority · High
Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis
How this class of weakness works · CWE-476

The code follows a pointer that is null, crashing the process. An attacker who can reliably trigger it turns the crash into a denial of service. The fix is checking for null before use and handling the failure path gracefully.

General guidance for the null pointer dereference class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Linux KernelOperating system
Affected:>= 5.9, < 6.1.168>= 6.2, < 6.6.131>= 6.7, < 6.12.80>= 6.13, < 6.18.21>= 6.19, < 6.19.11= 7.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 6.1.168 / 6.6.131 / 6.12.80 or later
Fixed in 6.1.1686.6.1316.12.80
Vendor patch git.kernel.org →
Recommended fix High confidence

Upgrade to the first fixed kernel version in your current branch: 6.1.168, 6.6.131, 6.12.80, or 6.18.21 depending on your running kernel branch

  1. 1. Identify the currently running Linux kernel version using `uname -r`
  2. 2. Determine which version branch your kernel falls into based on the affected ranges (5.9-6.1, 6.2-6.6, 6.7-6.12, or 6.13-6.18)
  3. 3. For kernels in the 6.1.x branch: upgrade to kernel version 6.1.168 or later
  4. 4. For kernels in the 6.2.x through 6.6.x branch: upgrade to kernel version 6.6.131 or later
  5. 5. For kernels in the 6.7.x through 6.12.x branch: upgrade to kernel version 6.12.80 or later
  6. 6. For kernels in the 6.13.x through 6.18.x branch: upgrade to kernel version 6.18.21 or later
  7. 7. After upgrade, reboot the system to load the fixed kernel
  8. 8. Verify the fix is applied by checking the kernel version with `uname -r` and confirming it meets the minimum fixed version for your branch
Caveat Kernel upgrades may require rebuilding third-party kernel modules; ensure driver compatibility before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $3,200. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-31453 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-31453 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data