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.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 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)
EPSS
2.6%
KEV
Not listed

Published

April 22, 2026

Last Modified

May 6, 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.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 40× 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 158 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

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 May 6, 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 2.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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

Explore the affected products and dependency analysis for 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