CVE-2026-74630

HIGHPre-NVD 7.87.8
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-22. 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:

ipv6: prevent in6_dev_get() from resurrecting inet6_dev

in6_dev_get() reads dev->ip6_ptr under RCU and then unconditionally increments its refcount. Device teardown can clear the pointer and drop the last reference between these operations. The increment then resurrects an object whose RCU free has already been queued, so callers can use it after it is freed.

Use refcount_inc_not_zero() and return NULL when the object has already reached zero. RCU keeps the memory accessible through the attempted reference acquisition, and a successful increment pins the object for the caller.

An independent run on the exact unpatched 6f5156d7a31a (v7.2-rc3) kernel reproduced the invalid reference acquisition as UID 1000:

refcount_t: addition on 0; use-after-free. ip6_mc_source+0xef4/0x17e0

It was followed by the corresponding reference underflow in ip6_mc_source(). The supplied trace from the same unpatched revision additionally shows the access after the RCU read-side section ends:

BUG: KASAN: slab-use-after-free in mutex_lock+0x76/0xe0 Write of size 8 at addr ffff888015b50240 by task poc/1219

Bug found and triaged by OpenAI Security Research and validated by Trail of Bits.

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
3%
KEV
Not listed

Published

August 22, 2026

Last Modified

August 25, 2026

Advisory Details (8)

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

ipv6: prevent in6_dev_get() from resurrecting inet6_dev - kernel/git/stable/linux.git - Linux kernel stable tree

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

ipv6: prevent in6_dev_get() from resurrecting inet6_dev - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/14e812ab41df0cac033479da835ec9a5de633404
generic

ipv6: prevent in6_dev_get() from resurrecting inet6_dev - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/680fbd7942185448eadb990a3d10a53eb946b702
generic

ipv6: prevent in6_dev_get() from resurrecting inet6_dev - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1c206d461c680c3151daa3c89fc26eaf5bf98a7f
generic

ipv6: prevent in6_dev_get() from resurrecting inet6_dev - kernel/git/stable/linux.git - Linux kernel stable tree

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

ipv6: prevent in6_dev_get() from resurrecting inet6_dev - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/145812b678de9f3b59780173be3c0d22ed60dd93
generic

ipv6: prevent in6_dev_get() from resurrecting inet6_dev - kernel/git/stable/linux.git - Linux kernel stable tree

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

ipv6: prevent in6_dev_get() from resurrecting inet6_dev - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/785d908f8d21c8bc78b6fb2c2932ab662bf6918a

Vendor Advisories for CVE-2026-74630(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 23× in last 7d / 26× 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 01:22 UTCEPSS rescore
  2. 2026-08-29 23:18 UTCGHSA enrichment
  3. 2026-08-29 12:13 UTCGHSA enrichment
  4. 2026-08-29 00:53 UTCEG score recompute
  5. 2026-08-29 00:52 UTCGHSA enrichment
  6. 2026-08-28 21:42 UTCEPSS rescore
  7. 2026-08-28 12:34 UTCGHSA enrichment
  8. 2026-08-28 01:26 UTCEG score recompute
  9. 2026-08-28 01:26 UTCGHSA enrichment
  10. 2026-08-27 14:25 UTCEPSS rescore
  11. 2026-08-27 14:22 UTCGHSA enrichment
  12. 2026-08-27 03:18 UTCGHSA enrichment
  13. 2026-08-26 16:13 UTCGHSA enrichment
  14. 2026-08-26 04:39 UTCGHSA enrichment
  15. 2026-08-25 17:34 UTCEG score recompute
  16. 2026-08-25 17:34 UTCGHSA enrichment
  17. 2026-08-25 13:49 UTCEPSS rescore
  18. 2026-08-25 06:29 UTCEG score recompute
  19. 2026-08-25 06:29 UTCGHSA enrichment
  20. 2026-08-25 05:45 UTCEG score recompute 7.80
  21. 2026-08-25 05:45 UTCGHSA enrichment
  22. 2026-08-25 05:45 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  23. 2026-08-24 14:18 UTCEPSS rescore
  24. 2026-08-22 16:24 UTCNVD update
  25. 2026-08-22 15:42 UTCEG score recompute
Show 1 more
  1. 2026-08-22 15:35 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-74630?
CVE-2026-74630 is a high vulnerability published on August 22, 2026. In the Linux kernel, the following vulnerability has been resolved: ipv6: prevent in6devget() from resurrecting inet6_dev in6devget() reads dev->ip6_ptr under RCU and then unconditionally increments its refcount. Device teardown can clear the pointer and drop the last reference between these…
When was CVE-2026-74630 disclosed?
CVE-2026-74630 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-74630 actively exploited?
CVE-2026-74630 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 97.2% of all scored CVEs.
What is the CVSS score of CVE-2026-74630?
CVE-2026-74630 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-74630?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-74630, 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-74630

Explore →

Is Your Infrastructure Affected by CVE-2026-74630?

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