CVE-2026-31454

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-04-22. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

April 22, 2026

Last Modified

August 5, 2026

Advisory Details (8)

Auto-updated May 6, 2026
No patch confirmed yet.
generic

xfs: save ailp before dropping the AIL lock in push callbacks - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/edd1637d4e3911ab6c760f553f2040fe72f61a13
generic

xfs: save ailp before dropping the AIL lock in push callbacks - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d8fc60bbaf5aea1604bf9f4ed565da6a1ac7a87d
generic

xfs: save ailp before dropping the AIL lock in push callbacks - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/75669e987137f49c99ca44406bf0200d1892dd16
generic

xfs: save ailp before dropping the AIL lock in push callbacks - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6dbe17f19c290a72ce57d5abc70e1fad0c3e14e5
generic

xfs: save ailp before dropping the AIL lock in push callbacks - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/50f5f056807b7bed74f4f307f2ca0ed92f3e556d
generic

xfs: save ailp before dropping the AIL lock in push callbacks - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4c7d50147316cf049462f327c4a3e9dc2b7f1dd0
generic

xfs: save ailp before dropping the AIL lock in push callbacks - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/394d70b86fae9fe865e7e6d9540b7696f73aa9b6
generic

xfs: save ailp before dropping the AIL lock in push callbacks - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/19437e4f7bb909afde832b39372aa2f3ce3cfd88

Vendor Advisories for CVE-2026-31454(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 5.10.253—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (53 versions)5.10.257-1—
linux-6.16.1.106-3~deb11u1 ... 6.1.164-1~deb11u1 (16 versions)6.1.170-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (48 versions)6.1.170-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (124 versions)6.19.11-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(24)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 5× in last 7d / 27× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 252 total refreshes for this CVE.

  1. 2026-09-13 16:47 UTCEPSS rescore
  2. 2026-09-12 15:01 UTCEPSS rescore
  3. 2026-09-11 14:52 UTCEPSS rescore
  4. 2026-09-10 09:34 UTCEPSS rescore
  5. 2026-09-08 22:00 UTCEPSS rescore
  6. 2026-09-07 16:01 UTCEPSS rescore
  7. 2026-09-06 13:47 UTCEPSS rescore
  8. 2026-09-06 13:47 UTCEPSS rescore
  9. 2026-09-04 05:06 UTCEPSS rescore
  10. 2026-09-02 14:11 UTCEPSS rescore
  11. 2026-09-02 03:04 UTCOSV refresh
  12. 2026-09-01 13:53 UTCEPSS rescore
  13. 2026-09-01 04:39 UTCEPSS rescore
  14. 2026-09-01 04:39 UTCEPSS rescore
  15. 2026-08-30 19:17 UTCEPSS rescore
  16. 2026-08-30 01:22 UTCEPSS rescore
  17. 2026-08-28 21:41 UTCEPSS rescore
  18. 2026-08-27 14:25 UTCEPSS rescore
  19. 2026-08-25 13:49 UTCEPSS rescore
  20. 2026-08-24 14:17 UTCEPSS rescore
  21. 2026-08-23 00:19 UTCEPSS rescore
  22. 2026-08-21 23:49 UTCEPSS rescore
  23. 2026-08-20 22:55 UTCEPSS rescore
  24. 2026-08-20 22:55 UTCEPSS rescore
  25. 2026-08-19 17:03 UTCEPSS rescore
Show 75 more
  1. 2026-08-17 13:47 UTCEPSS rescore
  2. 2026-08-16 14:56 UTCEPSS rescore
  3. 2026-08-16 06:01 UTCEG score recompute
  4. 2026-08-16 06:01 UTCVendor advisory
  5. 2026-08-16 06:01 UTCGHSA enrichment
  6. 2026-08-16 02:14 UTCEPSS rescore
  7. 2026-08-15 01:30 UTCEPSS rescore
  8. 2026-08-14 16:03 UTCVendor advisory
  9. 2026-08-14 16:03 UTCGHSA enrichment
  10. 2026-08-14 04:20 UTCEG score recompute
  11. 2026-08-14 04:20 UTCVendor advisory
  12. 2026-08-14 04:20 UTCGHSA enrichment
  13. 2026-08-13 22:00 UTCEPSS rescore
  14. 2026-08-13 08:39 UTCVendor advisory
  15. 2026-08-13 08:39 UTCGHSA enrichment
  16. 2026-08-12 18:32 UTCEG score recompute
  17. 2026-08-12 18:32 UTCVendor advisory
  18. 2026-08-12 18:32 UTCGHSA enrichment
  19. 2026-08-12 13:50 UTCEPSS rescore
  20. 2026-08-11 16:47 UTCVendor advisory
  21. 2026-08-11 16:47 UTCGHSA enrichment
  22. 2026-08-11 02:22 UTCEG score recompute
  23. 2026-08-11 02:22 UTCVendor advisory
  24. 2026-08-11 02:22 UTCGHSA enrichment
  25. 2026-08-11 00:00 UTCEPSS rescore
  26. 2026-08-10 02:59 UTCVendor advisory
  27. 2026-08-10 02:59 UTCGHSA enrichment
  28. 2026-08-09 15:16 UTCEG score recompute
  29. 2026-08-09 15:16 UTCVendor advisory
  30. 2026-08-09 15:16 UTCGHSA enrichment
  31. 2026-08-09 13:46 UTCEPSS rescore
  32. 2026-08-09 03:33 UTCEG score recompute
  33. 2026-08-09 03:33 UTCVendor advisory
  34. 2026-08-09 03:33 UTCGHSA enrichment
  35. 2026-08-08 16:37 UTCEPSS rescore
  36. 2026-08-08 12:29 UTCVendor advisory
  37. 2026-08-08 12:29 UTCGHSA enrichment
  38. 2026-08-08 00:32 UTCEG score recompute
  39. 2026-08-08 00:32 UTCVendor advisory
  40. 2026-08-08 00:32 UTCGHSA enrichment
  41. 2026-08-07 12:50 UTCEG score recompute
  42. 2026-08-07 12:50 UTCVendor advisory
  43. 2026-08-07 12:50 UTCGHSA enrichment
  44. 2026-08-06 13:46 UTCEPSS rescore
  45. 2026-08-06 12:06 UTCVendor advisory
  46. 2026-08-06 12:05 UTCGHSA enrichment
  47. 2026-08-06 00:22 UTCEG score recompute
  48. 2026-08-06 00:22 UTCVendor advisory
  49. 2026-08-06 00:22 UTCGHSA enrichment
  50. 2026-08-05 19:17 UTCEPSS rescore
  51. 2026-08-05 12:40 UTCEG score recompute
  52. 2026-08-05 12:40 UTCVendor advisory
  53. 2026-08-05 12:40 UTCGHSA enrichment
  54. 2026-08-04 15:10 UTCEPSS rescore
  55. 2026-08-04 10:38 UTCEPSS rescore
  56. 2026-08-03 21:15 UTCEG score recompute
  57. 2026-08-03 21:15 UTCVendor advisory
  58. 2026-08-03 21:15 UTCGHSA enrichment
  59. 2026-08-03 10:36 UTCEPSS rescore
  60. 2026-08-03 00:42 UTCVendor advisory
  61. 2026-08-03 00:42 UTCGHSA enrichment
  62. 2026-08-02 12:31 UTCEG score recompute
  63. 2026-08-02 12:31 UTCVendor advisory
  64. 2026-08-02 12:31 UTCGHSA enrichment
  65. 2026-08-02 02:27 UTCEPSS rescore
  66. 2026-08-01 04:16 UTCEPSS rescore
  67. 2026-07-30 16:27 UTCEPSS rescore
  68. 2026-07-30 01:30 UTCEPSS rescore
  69. 2026-07-28 15:36 UTCEPSS rescore
  70. 2026-07-26 14:54 UTCEPSS rescore
  71. 2026-07-26 14:54 UTCEPSS rescore
  72. 2026-07-25 14:18 UTCEPSS rescore
  73. 2026-07-25 14:17 UTCEPSS rescore
  74. 2026-07-24 14:17 UTCEPSS rescore
  75. 2026-07-23 14:18 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-31454?
CVE-2026-31454 is a high vulnerability published on April 22, 2026. In the Linux kernel, the following vulnerability has been resolved: xfs: save ailp before dropping the AIL lock in push callbacks In xfsinodeitempush() and xfsqmdquotlogitem_push(), the AIL lock is dropped to perform buffer IO. Once the cluster buffer no longer protects the log item from reclaim,…
When was CVE-2026-31454 disclosed?
CVE-2026-31454 was first published in the National Vulnerability Database on April 22, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31454 actively exploited?
CVE-2026-31454 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.4% of all scored CVEs.
What is the CVSS score of CVE-2026-31454?
CVE-2026-31454 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-31454?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31454, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-31454

Explore →

Is Your Infrastructure Affected by CVE-2026-31454?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs