Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-31453xfs: avoid dereferencing log items after push callbacks

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.

Timeline

  1. ID reserved

    By Linux

  2. · 44 days later

    Published

  3. · 6 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-31453, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.13% · top 97% of all CVEs (13 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected 90c60e16401248a4900f3f9387f563d0178dcf34 – < c8a2ab339b88d10fc34a3318c92f07d8a467019d
    • affected 90c60e16401248a4900f3f9387f563d0178dcf34 – < 7121b22b0bac89394cc4c6a54b5aebc15347bdf5
    • affected 90c60e16401248a4900f3f9387f563d0178dcf34 – < c4d603e8e58a3bf35480135ccca2b4f7238abda5
    • affected 90c60e16401248a4900f3f9387f563d0178dcf34 – < 95fb5d643cc70959baa54cd17f52f80ffc3295e7
    • affected 90c60e16401248a4900f3f9387f563d0178dcf34 – < 451c6329d9afa45862c36fe6677eb7750db60617
    • affected 90c60e16401248a4900f3f9387f563d0178dcf34 – < 79ef34ec0554ec04bdbafafbc9836423734e1bd6
  • Linux · Linux

    • affected 5.9
    • unaffected < 5.9
    • unaffected 6.1.168 – ≤ 6.1.*
    • unaffected 6.6.131 – ≤ 6.6.*
    • unaffected 6.12.80 – ≤ 6.12.*
    • unaffected 6.18.21 – ≤ 6.18.*
    • unaffected 6.19.11 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-31453 badge
[![CVE-2026-31453](https://cveledger.app/badge/CVE-2026-31453.svg)](https://cveledger.app/cve/CVE-2026-31453)

Record last updated .