CVE-2026-64187

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-07-20. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

xfs: fail recovery on a committed log item with no regions

If the first op of a transaction is a bare transaction header (len == sizeof(struct xfs_trans_header)), xlog_recover_add_to_trans() adds an item but no region, leaving it on r_itemq with ri_cnt == 0 and ri_buf == NULL.

The header can be split across op records, so later ops may still add regions; the item is only invalid if the transaction commits with none. The runtime commit path never emits such a transaction, so this only happens on a crafted log. It came from an AI-assisted code audit of the recovery parser.

xlog_recover_reorder_trans() calls ITEM_TYPE() on the item, which reads *(unsigned short *)item->ri_buf[0].iov_base and faults on the NULL ri_buf. Reject it there, before the commit handlers that also read ri_buf[0].

KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007] RIP: 0010:xlog_recover_reorder_trans (fs/xfs/xfs_log_recover.c:1836) xlog_recover_commit_trans (fs/xfs/xfs_log_recover.c:2043) xlog_recover_process_data (fs/xfs/xfs_log_recover.c:2501) xlog_do_recovery_pass (fs/xfs/xfs_log_recover.c:3244) xlog_recover (fs/xfs/xfs_log_recover.c:3493) xfs_log_mount (fs/xfs/xfs_log.c:618) xfs_mountfs (fs/xfs/xfs_mount.c:1034) xfs_fs_fill_super (fs/xfs/xfs_super.c:1938) vfs_get_tree (fs/super.c:1695) path_mount (fs/namespace.c:4161) __x64_sys_mount (fs/namespace.c:4367)

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/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
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

July 20, 2026

Last Modified

August 17, 2026

Advisory Details (7)

Auto-updated Aug 11, 2026
No patch confirmed yet.
generic

xfs: fail recovery on a committed log item with no regions - kernel/git/stable/linux.git - Linux kernel stable tree

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

xfs: fail recovery on a committed log item with no regions - kernel/git/stable/linux.git - Linux kernel stable tree

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

xfs: fail recovery on a committed log item with no regions - kernel/git/stable/linux.git - Linux kernel stable tree

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

xfs: fail recovery on a committed log item with no regions - kernel/git/stable/linux.git - Linux kernel stable tree

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

xfs: fail recovery on a committed log item with no regions - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5105426424ad6981db827cc1ada835a488fab035
generic

xfs: fail recovery on a committed log item with no regions - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/226a3c8bea7163c39fe0a1c0ffc7ab7410ef3ba4
generic

xfs: fail recovery on a committed log item with no regions - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2094dab19d45c487285617b7b68913d0cc0c1211

Vendor Advisories for CVE-2026-64187(2)

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

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-31.31) @ resolute2026-09-11ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1013.13) @ resolute2026-09-11ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-09-11ubuntu

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

(6 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (500 versions)——
linux-6.16.1.106-3~deb11u1 ... 6.1.177-1~deb11u1 (22 versions)6.1.180-1~deb11u1—
Debian:12(2)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (55 versions)6.1.180-1—
linux-6.12—6.12.100-1~deb12u1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.95-1~bpo12+1 (30 versions)6.12.96-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (158 versions)7.1.4-1—

Weakness Classification(1)

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

Additional Vendor Advisories

(3)

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 21× in last 7d / 92× 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 247 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-64187?
CVE-2026-64187 is a medium vulnerability published on July 20, 2026. In the Linux kernel, the following vulnerability has been resolved: xfs: fail recovery on a committed log item with no regions If the first op of a transaction is a bare transaction header (len == sizeof(struct xfstransheader)), xlogrecoveraddtotrans() adds an item but no region, leaving it on…
When was CVE-2026-64187 disclosed?
CVE-2026-64187 was first published in the National Vulnerability Database on July 20, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64187 actively exploited?
CVE-2026-64187 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 98.3% of all scored CVEs.
What is the CVSS score of CVE-2026-64187?
CVE-2026-64187 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-64187?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64187, 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-64187

Explore →

Is Your Infrastructure Affected by CVE-2026-64187?

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

Start Free Scan →Browse All CVEs