CVE-2026-80536

HIGHPre-NVD 8.48.4
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 8.4 from GitHub Security Advisory (severity: HIGH) published 2026-08-27. A secondary CVSS source baseline 8.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week
8.4EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 8.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

xfs: bounds-check buffer log item's dirty bitmap

xlog_recover_do_reg_buffer() replays each dirty region described by a buffer log item's bitmap into the buffer read for that item:

memcpy(xfs_buf_offset(bp, (uint)bit << XFS_BLF_SHIFT), item->ri_buf[i].iov_base, nbits << XFS_BLF_SHIFT);

The destination offset (bit/nbits, from the logged dirty bitmap) and the buffer size (from the logged blf_len) are both attacker-controlled and otherwise unrelated, yet the only thing bounding the copy is an ASSERT(), which compiles away on production kernels. A crafted image logging a small blf_len together with a bitmap bit past the end of that buffer drives the memcpy() past the buffer's allocation, corrupting adjacent kernel heap during mount-time log recovery. This is reachable by anyone who can get a crafted image mounted -- the malicious-filesystem threat model XFS already guards against elsewhere.

Turn the ASSERT() into a real XFS_IS_CORRUPT() check that aborts recovery of the buffer with -EFSCORRUPTED, consistent with the validate-and-fail idiom already used in xlog_recover_do_inode_buffer() and xfs_dquot_item_recover.c. xlog_recover_do_reg_buffer() therefore becomes STATIC int and its three callers propagate the error.

Found and confirmed with KASAN on a CONFIG_XFS_DEBUG=n build: the crafted image trips a slab-out-of-bounds write before this change and fails recovery cleanly with -EFSCORRUPTED after it.

CVSS v3
8.4
EG Score
8.4HIGHmedium confidence
EG Risk
38
EG Risk 38/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity84% × 45%
Impact severity (EG Severity): CVSS 8.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.1%
EPSS %ILE
3rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.4): severity, escalated by confirmed exploitation. This CVE's 8.4 is its impact severity (EG Severity), not escalated.

EG Severity
8.4 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 26, 2026

Last Modified

October 16, 2026

Advisory Details (3)

Auto-updated Aug 27, 2026
Patch available.
Web page

xfs: bounds-check buffer log item's dirty bitmap - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f8288214459ead7e87d26e5822f62c14a4f2ed6b
Web page

xfs: bounds-check buffer log item's dirty bitmap - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/edaf5b6bd625356893da20d69a259b34a9de2694
Web page

xfs: bounds-check buffer log item's dirty bitmap - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/813f8136a2ce1fee266d02a7df73db6e8a541604

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1036.39) @ noble2026-10-16ubuntu

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

(4 across 3 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (56 versions)
  • every version up to 6.1.187-1: fixed in 6.1.187-1
—
linux-6.126.12.100-1~deb12u1, 6.12.101-1~deb12u1
  • every version up to 6.12.107-1~deb12u1: fixed in 6.12.107-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (34 versions)
  • every version up to 6.12.107-1: fixed in 6.12.107-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (169 versions)
  • every version up to 7.1.10-1: fixed in 7.1.10-1
—

Additional Vendor Advisories

(1)

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 14× in last 7d / 117× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 224 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 124 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-80536?
CVE-2026-80536 is a high-severity vulnerability; its CVE record was published on August 26, 2026. In the Linux kernel, the following vulnerability has been resolved: xfs: bounds-check buffer log item's dirty bitmap xlogrecoverdoregbuffer() replays each dirty region described by a buffer log item's bitmap into the buffer read for that item: memcpy(xfsbufoffset(bp, (uint)bit << XFSBLFSHIFT),…
When was the CVE record for CVE-2026-80536 published?
The CVE record for CVE-2026-80536 was published on August 26, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 16, 2026; the record at its source may have been updated since.
Is CVE-2026-80536 actively exploited?
CVE-2026-80536 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (3rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-80536?
CVE-2026-80536 has a CVSS base score of 8.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-80536?
A fix for CVE-2026-80536 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-80536 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-80536?

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