CVE-2026-98073

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-09-25. 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 mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

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

net: Remove conflicting altnames for dying netns in __dev_change_net_namespace().

syzbot reported the warning in cfg80211_pernet_exit(). [0]

The repro does the following:

  • create two device in root netns and non-root netns
  • assign the same altname for the two devices
  • remove the non-root netns

Since commit 7663d522099e ("net: check for altname conflicts when changing netdev's netns"), cfg80211_switch_netns() and cfg802154_switch_netns() fail if init_net has a device with the conflicting altname.

default_device_exit_net() had the same issue and commit d09486a04f5d ("net: fix removing a namespace with conflicting altnames") fixed it.

cfg80211_pernet_exit() and cfg802154_pernet_exit() need the same fix.

Let's generalise the fix by removing conflicting altnames for dying netns in __dev_change_net_namespace().

[0]: cfg80211_switch_netns(rdev, &init_net) WARNING: net/wireless/core.c:1871 at cfg80211_pernet_exit+0xd5/0x120 net/wireless/core.c:1871, CPU#1: kworker/u8:9/1160 Modules linked in: CPU: 1 UID: 0 PID: 1160 Comm: kworker/u8:9 Not tainted syzkaller #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026 Workqueue: netns cleanup_net RIP: 0010:cfg80211_pernet_exit+0xd5/0x120 net/wireless/core.c:1871 Code: e8 03 42 80 3c 20 00 74 08 4c 89 f7 e8 b4 ef 0e f7 4d 8b 36 49 81 fe 20 10 4a 90 74 12 e8 03 3d 9f f6 eb 85 e8 fc 3c 9f f6 90 <0f> 0b 90 eb cc e8 f1 3c 9f f6 eb 05 e8 ea 3c 9f f6 5b 41 5c 41 5e RSP: 0018:ffffc900057a78f0 EFLAGS: 00010293 RAX: ffffffff8b287154 RBX: ffff88807ba72780 RCX: ffff8880213e8000 RDX: 0000000000000000 RSI: 00000000ffffffef RDI: 0000000000000000 RBP: 00000000ffffffef R08: ffffffff9024cc67 R09: 0000000000000000 R10: fffff52000af4eb0 R11: fffffbfff204998d R12: dffffc0000000000 R13: ffffffff904a1080 R14: ffff888144ed0008 R15: ffff888144ed0e20 FS: 0000000000000000(0000) GS:ffff888124de6000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00005642de0a8a70 CR3: 000000007a40c000 CR4: 00000000003526f0 Call Trace: ops_exit_list net/core/net_namespace.c:200 [inline] ops_undo_list+0x43d/0x8d0 net/core/net_namespace.c:253 cleanup_net+0x572/0x810 net/core/net_namespace.c:706 process_one_work kernel/workqueue.c:3387 [inline] process_scheduled_works+0xc3d/0x1630 kernel/workqueue.c:3470 worker_thread+0xa47/0xfb0 kernel/workqueue.c:3551 kthread+0x38b/0x480 kernel/kthread.c:436 ret_from_fork+0x514/0xb70 arch/x86/kernel/process.c:158 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245

CVSS v3
7.8
EG Score
7.8HIGHhigh confidence
EG Risk
40
EG Risk 40/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
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.2%
EPSS %ILE
4th
KEV
Not listed

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

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 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

September 25, 2026

Last Modified

September 30, 2026

Advisory Details (3)

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

net: Remove conflicting altnames for dying netns in __dev_change_net_namespace(). - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: Remove conflicting altnames for dying netns in __dev_change_net_namespace(). - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: Remove conflicting altnames for dying netns in __dev_change_net_namespace(). - kernel/git/stable/linux.git - Linux kernel stable tree

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

Vendor Advisories for CVE-2026-98073(2)

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

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (358 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (181 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (179 versions)
  • every version up to 7.2.7-1: fixed in 7.2.7-1
—

Data Freshness Timeline

(refreshed 40× in last 7d / 59× 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-10-04 23:47 UTCEG score recompute
  2. 2026-10-04 23:47 UTCVendor advisory
  3. 2026-10-04 23:47 UTCGHSA enrichment
  4. 2026-10-04 23:23 UTCEPSS rescore
  5. 2026-10-04 10:41 UTCVendor advisory
  6. 2026-10-04 10:41 UTCGHSA enrichment
  7. 2026-10-03 21:34 UTCEG score recompute
  8. 2026-10-03 21:34 UTCVendor advisory
  9. 2026-10-03 21:34 UTCGHSA enrichment
  10. 2026-10-03 14:26 UTCEPSS rescore
  11. 2026-10-03 08:27 UTCVendor advisory
  12. 2026-10-03 08:26 UTCGHSA enrichment
  13. 2026-10-02 19:16 UTCEG score recompute
  14. 2026-10-02 19:16 UTCVendor advisory
  15. 2026-10-02 19:15 UTCGHSA enrichment
  16. 2026-10-02 17:57 UTCEPSS rescore
  17. 2026-10-02 06:08 UTCEG score recompute
  18. 2026-10-02 06:08 UTCVendor advisory
  19. 2026-10-02 06:08 UTCGHSA enrichment
  20. 2026-10-01 19:51 UTCEPSS rescore
  21. 2026-10-01 17:01 UTCVendor advisory
  22. 2026-10-01 17:01 UTCGHSA enrichment
  23. 2026-10-01 03:41 UTCEG score recompute
  24. 2026-10-01 03:41 UTCVendor advisory
  25. 2026-10-01 03:41 UTCGHSA enrichment
Show 34 more
  1. 2026-09-30 15:04 UTCEPSS rescore
  2. 2026-09-30 14:35 UTCVendor advisory
  3. 2026-09-30 14:35 UTCGHSA enrichment
  4. 2026-09-30 13:41 UTCVendor advisory
  5. 2026-09-30 13:41 UTCGHSA enrichment
  6. 2026-09-30 00:35 UTCEG score recompute
  7. 2026-09-30 00:35 UTCVendor advisory
  8. 2026-09-30 00:34 UTCGHSA enrichment
  9. 2026-09-29 11:22 UTCVendor advisory
  10. 2026-09-29 11:22 UTCGHSA enrichment
  11. 2026-09-28 22:14 UTCEG score recompute
  12. 2026-09-28 22:14 UTCVendor advisory
  13. 2026-09-28 22:13 UTCGHSA enrichment
  14. 2026-09-28 13:52 UTCEPSS rescore
  15. 2026-09-28 13:52 UTCEPSS rescore
  16. 2026-09-28 09:05 UTCVendor advisory
  17. 2026-09-28 09:05 UTCGHSA enrichment
  18. 2026-09-27 19:58 UTCEG score recompute
  19. 2026-09-27 19:58 UTCGHSA enrichment
  20. 2026-09-27 13:49 UTCEPSS rescore
  21. 2026-09-27 06:51 UTCGHSA enrichment
  22. 2026-09-26 17:44 UTCEG score recompute
  23. 2026-09-26 17:43 UTCGHSA enrichment
  24. 2026-09-26 15:59 UTCEPSS rescore
  25. 2026-09-26 04:34 UTCEG score recompute
  26. 2026-09-26 04:34 UTCGHSA enrichment
  27. 2026-09-25 15:23 UTCEG score recompute
  28. 2026-09-25 15:23 UTCGHSA enrichment
  29. 2026-09-25 14:51 UTCEG score recompute▲ 7.80
  30. 2026-09-25 14:51 UTCGHSA enrichment
  31. 2026-09-25 14:49 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  32. 2026-09-25 11:30 UTCNVD update
  33. 2026-09-25 10:27 UTCEG score recompute
  34. 2026-09-25 10:27 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-98073?
CVE-2026-98073 is a high vulnerability published on September 25, 2026. In the Linux kernel, the following vulnerability has been resolved: net: Remove conflicting altnames for dying netns in devchangenet_namespace(). syzbot reported the warning in cfg80211pernetexit(). [0] The repro does the following: 1. create two device in root netns and non-root netns 2. assign…
When was CVE-2026-98073 disclosed?
CVE-2026-98073 was first published on September 25, 2026, with the most recent update on September 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-98073 actively exploited?
CVE-2026-98073 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (4th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-98073?
CVE-2026-98073 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-98073?
No fix for CVE-2026-98073 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-98073 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-98073

Explore →

Is Your Infrastructure Affected by CVE-2026-98073?

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

Book a Demo →Browse All CVEs