CVE-2026-74398

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-15. 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.8%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

ipv6: addrconf: bail out of dad_failure when state is no longer POSTDAD

addrconf_dad_failure() transitions ifp->state from DAD to POSTDAD via addrconf_dad_end(), which drops ifp->lock on return. The lock is re-acquired after net_info_ratelimited(). A concurrent ipv6_del_addr() can take the lock in that window, set ifp->state to DEAD and run list_del_rcu(&ifp->if_list).

addrconf_dad_failure() then overwrites DEAD with ERRDAD at errdad: and schedules a new dad_work. The work calls ipv6_del_addr() again, hitting the already-poisoned list entry:

general protection fault: 0000 [#1] SMP NOPTI CPU: 4 PID: 217 Comm: kworker/4:1 Workqueue: ipv6_addrconf addrconf_dad_work RIP: 0010:ipv6_del_addr+0xe9/0x280 RAX: dead000000000122 Call Trace: addrconf_dad_stop+0x113/0x140 addrconf_dad_work+0x28c/0x430 process_one_work+0x1eb/0x3b0 worker_thread+0x4d/0x400 kthread+0x104/0x140 ret_from_fork+0x35/0x40

Fold the addrconf_dad_end() logic into addrconf_dad_failure() under a single ifp->lock critical section. The STABLE_PRIVACY branch temporarily drops ifp->lock around address regeneration, so at lock_errdad: verify the state is still POSTDAD before transitioning to ERRDAD; bail out otherwise to avoid overwriting a state set by another path while the lock was released.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
49
EG Risk 49/100CISA SSVC

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%
Exploitation1% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track* or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.8%
EPSS %ILE
53rd
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact total (CVSS ≥ 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 15, 2026

Last Modified

August 17, 2026

Advisory Details (8)

Auto-updated Oct 5, 2026
Patch available.
generic

ipv6: addrconf: bail out of dad_failure when state is no longer POSTDAD - kernel/git/stable/linux.git - Linux kernel stable tree

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

ipv6: addrconf: bail out of dad_failure when state is no longer POSTDAD - kernel/git/stable/linux.git - Linux kernel stable tree

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

ipv6: addrconf: bail out of dad_failure when state is no longer POSTDAD - kernel/git/stable/linux.git - Linux kernel stable tree

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

ipv6: addrconf: bail out of dad_failure when state is no longer POSTDAD - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8ed0ce9ea58d677d1bac92614ee5f60f8ea57363
generic

ipv6: addrconf: bail out of dad_failure when state is no longer POSTDAD - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/875c284c0f98b042bb97abad460f63a24c977f88
generic

ipv6: addrconf: bail out of dad_failure when state is no longer POSTDAD - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/627ac78f2741e2ebd2225e2e953b6964a8a9182f
generic

ipv6: addrconf: bail out of dad_failure when state is no longer POSTDAD - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/47b05836705b63dab93d9ac7c69a3a507375ef80
generic

ipv6: addrconf: bail out of dad_failure when state is no longer POSTDAD - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3bdc86d89fd6c6523753fa6f42fcfaf30ee699cb

Vendor Advisories for CVE-2026-74398(1)

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

Patch Availability(5)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-34.34) @ resolute2026-10-05ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1014.14) @ resolute2026-10-05ubuntu
ubuntulinux-tools-oracle-edge (7.0.0-1012.12~24.04.1) @ noble2026-10-05ubuntu
ubuntulinux-tools-gke-hwe-26.04 (7.0.0-1007.8) @ resolute2026-10-05ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1035.38) @ noble2026-10-05ubuntu

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

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (55 versions)
  • every version up to 6.1.180-1: fixed in 6.1.180-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.96-1 (31 versions)
  • every version up to 6.12.100-1: fixed in 6.12.100-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (160 versions)
  • every version up to 7.1.5-1: fixed in 7.1.5-1
—

All Vendor Advisories

(5)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

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

Showing the most recent 100 of 383 total refreshes for this CVE.

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2026-74398?
CVE-2026-74398 is a critical vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: ipv6: addrconf: bail out of dad_failure when state is no longer POSTDAD addrconfdadfailure() transitions ifp->state from DAD to POSTDAD via addrconfdadend(), which drops ifp->lock on return. The lock is re-acquired after…
When was CVE-2026-74398 disclosed?
CVE-2026-74398 was first published 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-74398 actively exploited?
CVE-2026-74398 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (53rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-74398?
CVE-2026-74398 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-74398?
A fix for CVE-2026-74398 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-74398 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-74398

Explore →

Is Your Infrastructure Affected by CVE-2026-74398?

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

Book a Demo →Browse All CVEs