CVE-2026-68442

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

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

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

btrfs: don't propagate EXTENT_FLAG_LOGGING to split extent maps

When btrfs_drop_extent_map_range() splits an extent map, the new split maps inherit the original map's flags through a local 'flags' variable. Commit f86f7a75e2fb ("btrfs: use the flags of an extent map to identify the compression type") changed the EXTENT_FLAG_LOGGING clearing to operate on em->flags instead of that local 'flags' copy, so a split of an extent map that is currently being logged wrongly inherits EXTENT_FLAG_LOGGING.

The flag is then never cleared on the split, and when it is freed while still on the inode's modified_extents list (for example by the extent map shrinker) it trips the WARN_ON(!list_empty(&em->list)) in btrfs_free_extent_map() and leads to a use-after-free.

Clear EXTENT_FLAG_LOGGING from the local 'flags' copy used for the splits and only clear EXTENT_FLAG_PINNED from em->flags, restoring the behaviour prior to f86f7a75e2fb.

CVSS v3
7.8
EG Score
7.8(high)
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
2%
KEV
Not listed

Published

August 12, 2026

Last Modified

August 17, 2026

Advisory Details (4)

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

btrfs: don't propagate EXTENT_FLAG_LOGGING to split extent maps - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9304713b70e7e1450e3a76e758836fe5391bfa95
generic

btrfs: don't propagate EXTENT_FLAG_LOGGING to split extent maps - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5eff4d5b17fa1950e80bfd1ba43dc0699e61a644
generic

btrfs: don't propagate EXTENT_FLAG_LOGGING to split extent maps - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2a9246a424f45f33a1b8367052611ebe874868ad
generic

btrfs: don't propagate EXTENT_FLAG_LOGGING to split extent maps - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0e465c63f103a5ce6849614d6bda048d70eebec8

Vendor Advisories for CVE-2026-68442(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 33× in last 7d / 37× 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-20 06:01 UTCGHSA enrichment
  2. 2026-08-19 18:39 UTCEG score recompute
  3. 2026-08-19 18:39 UTCGHSA enrichment
  4. 2026-08-19 17:04 UTCEPSS rescore
  5. 2026-08-19 05:32 UTCGHSA enrichment
  6. 2026-08-18 18:10 UTCGHSA enrichment
  7. 2026-08-18 06:37 UTCGHSA enrichment
  8. 2026-08-17 19:15 UTCEG score recompute
  9. 2026-08-17 19:15 UTCGHSA enrichment
  10. 2026-08-17 13:47 UTCEPSS rescore
  11. 2026-08-17 06:31 UTCEG score recompute
  12. 2026-08-17 06:31 UTCGHSA enrichment
  13. 2026-08-17 05:35 UTCEG score recompute
  14. 2026-08-17 05:35 UTCGHSA enrichment
  15. 2026-08-16 19:55 UTCEG score recompute
  16. 2026-08-16 19:55 UTCGHSA enrichment
  17. 2026-08-16 14:56 UTCEPSS rescore
  18. 2026-08-16 14:56 UTCEPSS rescore
  19. 2026-08-16 08:33 UTCEG score recompute
  20. 2026-08-16 08:33 UTCGHSA enrichment
  21. 2026-08-15 21:12 UTCGHSA enrichment
  22. 2026-08-15 09:50 UTCEG score recompute
  23. 2026-08-15 09:50 UTCGHSA enrichment
  24. 2026-08-15 01:30 UTCEPSS rescore
  25. 2026-08-14 22:28 UTCGHSA enrichment
Show 12 more
  1. 2026-08-14 11:06 UTCEG score recompute
  2. 2026-08-14 11:06 UTCGHSA enrichment
  3. 2026-08-13 23:45 UTCEG score recompute
  4. 2026-08-13 23:45 UTCGHSA enrichment
  5. 2026-08-13 23:03 UTCEG score recompute▲ 7.80
  6. 2026-08-13 23:03 UTCGHSA enrichment
  7. 2026-08-13 23:03 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  8. 2026-08-13 22:00 UTCEPSS rescore
  9. 2026-08-12 13:51 UTCEPSS rescore
  10. 2026-08-12 00:19 UTCNVD update
  11. 2026-08-12 00:15 UTCEG score recompute
  12. 2026-08-12 00:15 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-68442?
CVE-2026-68442 is a high vulnerability published on August 12, 2026. In the Linux kernel, the following vulnerability has been resolved: btrfs: don't propagate EXTENTFLAGLOGGING to split extent maps When btrfsdropextentmaprange() splits an extent map, the new split maps inherit the original map's flags through a local 'flags' variable. Commit f86f7a75e2fb ("btrfs:…
When was CVE-2026-68442 disclosed?
CVE-2026-68442 was first published in the National Vulnerability Database on August 12, 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-68442 actively exploited?
CVE-2026-68442 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.1% of all scored CVEs.
What is the CVSS score of CVE-2026-68442?
CVE-2026-68442 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-68442?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68442, 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-68442

Explore →

Is Your Infrastructure Affected by CVE-2026-68442?

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

Start Free Scan →Browse All CVEs