CVE-2026-74321

HIGHPre-NVD 7.57.5
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: 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: fix invalid pointer dereference in __btrfs_run_delayed_refs()

In the beginning of the loop, we try to obtain a locked delayed ref head, if 'locked_ref' is currently NULL, by calling btrfs_select_ref_head(), which can return an error pointer. If the error pointer is -EAGAIN we do a continue and go back to the beginning of the loop, which will not try again to call btrfs_select_ref_head() since 'locked_ref' is no longer NULL but it's ERR_PTR(-EAGAIN), and then we do:

spin_lock(&locked_ref->lock);

against a ERR_PTR(-EAGAIN) value, generating an invalid pointer dereference.

Fix this by ensuring that 'locked_ref' is set to NULL when btrfs_select_ref_head() returns ERR_PTR(-EAGAIN) and incrementing 'count' as well, to prevent infinite looping. We do this by doing a goto to the bottom of the loop that already sets 'locked_ref' to NULL and does a cond_resched(), with an increment to 'count' right before the goto. These measures were in place before the refactoring in commit 0110a4c43451 ("btrfs: refactor __btrfs_run_delayed_refs loop") but were unintentionally lost afterwards.

CVSS v3
7.5
EG Score
7.5(high)
EG Risk
38(Track)
EG Risk 38/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
Severity75% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
41%
KEV
Not listed

Published

August 15, 2026

Last Modified

August 17, 2026

Advisory Details (8)

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

btrfs: fix invalid pointer dereference in __btrfs_run_delayed_refs() - kernel/git/stable/linux.git - Linux kernel stable tree

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

btrfs: fix invalid pointer dereference in __btrfs_run_delayed_refs() - kernel/git/stable/linux.git - Linux kernel stable tree

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

btrfs: fix invalid pointer dereference in __btrfs_run_delayed_refs() - kernel/git/stable/linux.git - Linux kernel stable tree

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

btrfs: fix invalid pointer dereference in __btrfs_run_delayed_refs() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9faa6b69ad73f03c7bde53e07d75a28822dc9a1a
generic

btrfs: fix invalid pointer dereference in __btrfs_run_delayed_refs() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/65770111a2d47c2b15e20b2ba92bb12198f289d4
generic

btrfs: fix invalid pointer dereference in __btrfs_run_delayed_refs() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/486f8298b6188ff11ef1f4be7f1d5d2e4d1b1fae
generic

btrfs: fix invalid pointer dereference in __btrfs_run_delayed_refs() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3b15d02be05e74321adb1e0ae0cb4ccfba7c6cb1
generic

btrfs: fix invalid pointer dereference in __btrfs_run_delayed_refs() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/015dc4a1e0c2cba551d4620eba13d26d5081dc34

Vendor Advisories for CVE-2026-74321(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 31× in last 7d / 31× 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-21 01:15 UTCEG score recompute
  2. 2026-08-21 01:15 UTCGHSA enrichment
  3. 2026-08-20 22:56 UTCEPSS rescore
  4. 2026-08-20 14:02 UTCGHSA enrichment
  5. 2026-08-20 02:49 UTCEG score recompute
  6. 2026-08-20 02:49 UTCGHSA enrichment
  7. 2026-08-19 17:04 UTCEPSS rescore
  8. 2026-08-19 15:33 UTCGHSA enrichment
  9. 2026-08-19 04:13 UTCGHSA enrichment
  10. 2026-08-18 17:00 UTCEG score recompute
  11. 2026-08-18 17:00 UTCGHSA enrichment
  12. 2026-08-18 13:49 UTCEPSS rescore
  13. 2026-08-18 13:49 UTCEPSS rescore
  14. 2026-08-18 04:56 UTCGHSA enrichment
  15. 2026-08-17 17:44 UTCEG score recompute
  16. 2026-08-17 17:43 UTCGHSA enrichment
  17. 2026-08-17 13:47 UTCEPSS rescore
  18. 2026-08-17 06:27 UTCEG score recompute
  19. 2026-08-17 06:27 UTCGHSA enrichment
  20. 2026-08-17 05:56 UTCEG score recompute 7.50
  21. 2026-08-17 05:56 UTCGHSA enrichment
  22. 2026-08-17 05:54 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
  23. 2026-08-17 05:27 UTCEG score recompute
  24. 2026-08-17 05:27 UTCGHSA enrichment
  25. 2026-08-17 05:25 UTCMITRE cvelistV5
Show 6 more
  1. 2026-08-16 14:56 UTCEPSS rescore
  2. 2026-08-16 14:56 UTCEPSS rescore
  3. 2026-08-16 02:15 UTCEPSS rescore
  4. 2026-08-15 06:23 UTCNVD update
  5. 2026-08-15 06:16 UTCEG score recompute
  6. 2026-08-15 06:12 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-74321?
CVE-2026-74321 is a high vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: btrfs: fix invalid pointer dereference in btrfsrundelayed_refs() In the beginning of the loop, we try to obtain a locked delayed ref head, if 'lockedref' is currently NULL, by calling btrfsselectrefhead(), which can return an error…
When was CVE-2026-74321 disclosed?
CVE-2026-74321 was first published in the National Vulnerability Database on August 15, 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-74321 actively exploited?
CVE-2026-74321 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 58.8% of all scored CVEs.
What is the CVSS score of CVE-2026-74321?
CVE-2026-74321 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-74321?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-74321, 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-74321

Explore →

Is Your Infrastructure Affected by CVE-2026-74321?

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