CVE-2026-74723

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreHIGH confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-22. a secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
9.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: 9.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:

btrfs: lzo: reject inline extents without valid headers

[BUG] For a crafted btrfs image, the following KASAN can be triggered when reading an inline lzo compressed file extent:

BUG: KASAN: slab-out-of-bounds in lzo_decompress+0x57d/0x700 Read of size 4 at addr ffff888006f2e644 by task btrfs_lzo_inlin/77

Call Trace: dump_stack_lvl+0x5b/0x70 print_report+0xd1/0x610 kasan_report+0xe0/0x110 __asan_report_load_n_noabort+0x13/0x20 lzo_decompress+0x57d/0x700 btrfs_decompress+0x140/0x1c0 uncompress_inline+0x147/0x1b0 btrfs_get_extent+0xb23/0x10a0 btrfs_do_readpage.constprop.0+0x538/0x1ac0 btrfs_readahead+0x32f/0x5f0 read_pages+0x16f/0x850 page_cache_ra_unbounded+0x296/0x490 do_page_cache_ra+0xd9/0x130 page_cache_sync_ra+0x3ee/0x6f0 filemap_get_pages+0x306/0x15c0 filemap_read+0x329/0xd00 btrfs_file_read_iter+0x1f8/0x2b0 vfs_read+0x4ef/0x720 ksys_read+0xf8/0x1d0 __x64_sys_read+0x71/0xb0 x64_sys_call+0x1ab0/0x1b70 do_syscall_64+0x61/0x470 entry_SYSCALL_64_after_hwframe+0x4b/0x53

[CAUSE] For an inline lzo compressed file extent, there should always be one lzo header, recording the total length of the compressed data, followed by one segment header, recording the compressed lzo payload.

But if a crafted inline lzo compressed file extent contains only an lzo header, without the segment header or payload, lzo_decompress() will still try to read the segment header, causing a read beyond the item boundary.

Furthermore if the inline lzo compressed file extent is the first item of the leaf, it will be at the extent buffer boundary. The above out-of-boundary read will go beyond the extent buffer boundary, triggering the above KASAN report.

[FIX] Validate the total length of the inlined lzo compressed file extent, to make sure there is at least one LZO header and one segment header, and a non-zero payload.

[ Rework the commit message to remove slop ]

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

Published

August 22, 2026

Last Modified

August 25, 2026

Advisory Details (2)

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

btrfs: lzo: reject inline extents without valid headers - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0fa78ef637deb5dbe341582f88553a4bce496de0
generic

btrfs: lzo: reject inline extents without valid headers - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/fc50b475ad27f50b4dcc98fc4c44e8802bc1b248

Vendor Advisories for CVE-2026-74723(1)

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

Data Freshness Timeline

(refreshed 44× in last 7d / 47× 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.

  1. 2026-08-30 06:23 UTCGHSA enrichment
  2. 2026-08-30 02:09 UTCEG score recompute
  3. 2026-08-30 02:09 UTCGHSA enrichment
  4. 2026-08-30 01:22 UTCEPSS rescore
  5. 2026-08-29 21:54 UTCGHSA enrichment
  6. 2026-08-29 17:41 UTCGHSA enrichment
  7. 2026-08-29 13:26 UTCGHSA enrichment
  8. 2026-08-29 09:06 UTCGHSA enrichment
  9. 2026-08-29 04:52 UTCGHSA enrichment
  10. 2026-08-29 00:36 UTCEG score recompute
  11. 2026-08-29 00:36 UTCGHSA enrichment
  12. 2026-08-28 21:42 UTCEPSS rescore
  13. 2026-08-28 16:29 UTCGHSA enrichment
  14. 2026-08-28 11:12 UTCGHSA enrichment
  15. 2026-08-28 06:58 UTCGHSA enrichment
  16. 2026-08-28 02:42 UTCGHSA enrichment
  17. 2026-08-27 22:29 UTCGHSA enrichment
  18. 2026-08-27 18:16 UTCEG score recompute
  19. 2026-08-27 18:16 UTCGHSA enrichment
  20. 2026-08-27 14:25 UTCEPSS rescore
  21. 2026-08-27 13:39 UTCGHSA enrichment
  22. 2026-08-27 09:26 UTCGHSA enrichment
  23. 2026-08-27 05:12 UTCGHSA enrichment
  24. 2026-08-27 00:59 UTCGHSA enrichment
  25. 2026-08-26 20:45 UTCGHSA enrichment
Show 22 more
  1. 2026-08-26 16:24 UTCEG score recompute
  2. 2026-08-26 16:24 UTCGHSA enrichment
  3. 2026-08-26 14:47 UTCEPSS rescore
  4. 2026-08-26 12:06 UTCGHSA enrichment
  5. 2026-08-26 07:52 UTCGHSA enrichment
  6. 2026-08-26 03:38 UTCGHSA enrichment
  7. 2026-08-25 23:24 UTCGHSA enrichment
  8. 2026-08-25 19:10 UTCGHSA enrichment
  9. 2026-08-25 14:57 UTCEG score recompute
  10. 2026-08-25 14:56 UTCGHSA enrichment
  11. 2026-08-25 13:49 UTCEPSS rescore
  12. 2026-08-25 10:42 UTCEG score recompute
  13. 2026-08-25 10:42 UTCGHSA enrichment
  14. 2026-08-25 06:29 UTCEG score recompute
  15. 2026-08-25 06:29 UTCGHSA enrichment
  16. 2026-08-25 05:55 UTCEG score recompute▲ 9.80
  17. 2026-08-25 05:55 UTCGHSA enrichment
  18. 2026-08-25 05:55 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
  19. 2026-08-24 14:18 UTCEPSS rescore
  20. 2026-08-22 16:24 UTCNVD update
  21. 2026-08-22 15:37 UTCEG score recompute
  22. 2026-08-22 15:35 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-74723?
CVE-2026-74723 is a critical vulnerability published on August 22, 2026. In the Linux kernel, the following vulnerability has been resolved: btrfs: lzo: reject inline extents without valid headers [BUG] For a crafted btrfs image, the following KASAN can be triggered when reading an inline lzo compressed file extent: BUG: KASAN: slab-out-of-bounds in…
When was CVE-2026-74723 disclosed?
CVE-2026-74723 was first published in the National Vulnerability Database on August 22, 2026, with the most recent update on August 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-74723 actively exploited?
CVE-2026-74723 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 69.2% of all scored CVEs.
What is the CVSS score of CVE-2026-74723?
CVE-2026-74723 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-74723?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-74723, 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-74723

Explore →

Is Your Infrastructure Affected by CVE-2026-74723?

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

Start Free Scan →Browse All CVEs