CVE-2026-97595

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.5EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.5Exploit: 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:

mac802154: fix use-after-free of sdata via queued RX frames

The RX softirq producer ieee802154_subif_frame() queues received beacon and MAC-command frames onto local->rx_beacon_list / rx_mac_cmd_list and schedules a process-context worker, storing a raw mac_pkt->sdata (and skb->dev == sdata->dev) with neither a reference nor any locking:

  • the lists have no lock: the softirq producer list_add_tail()s while the
mac_wq worker list_del()s, so sibling interfaces on the same phy corrupt the list;
  • the workers dereference the interface after it may have been freed.
mac802154_rx_mac_cmd_worker() touches mac_pkt->sdata directly, and mac802154_rx_beacon_worker() -> mac802154_process_beacon() dereferences skb->dev (== sdata->dev). Removing an interface frees its sdata (netdev_priv) while a queued frame still points at it, so a later worker run is a use-after-free.

Reproduced under KASAN by flooding a victim interface with MAC command frames and removing it (the beacon path is the same class via skb->dev):

BUG: KASAN: slab-use-after-free in mac802154_rx_mac_cmd_worker+0x463/0x630 [mac802154] Read of size 4 at addr ffff888002f9ea18 by task kworker/u8:1/31 Workqueue: phy0-mac-cmds mac802154_rx_mac_cmd_worker [mac802154] Call Trace: mac802154_rx_mac_cmd_worker+0x463/0x630 [mac802154] process_one_work+0x611/0xe80 worker_thread+0x52e/0xdc0 kthread+0x30c/0x630 ret_from_fork+0x2fd/0x3e0

Fix both lists together:

  • add local->rx_lock and take it around every list access: the softirq
producer (plain spin_lock, softirq context) and the workers and flush (spin_lock_bh, process context);
  • pin the interface for the lifetime of a queued frame with
netdev_hold()/netdev_put(), so the worker can safely dereference sdata / skb->dev even while the interface is being removed;
  • dequeue under the lock at the head and loop-drain the whole list in the
workers (they previously processed one frame per run and relied on a later enqueue to drain the rest);
  • drop not-yet-started frames of an interface before it is unregistered,
from ieee802154_if_remove() (after the RCU grace period) and from the ieee802154_remove_interfaces() loop -- the latter is the whole-phy teardown path, which does not go through ieee802154_if_remove().

An in-flight worker that already dequeued a frame keeps its own netdev reference; unregister_netdevice() then waits it out in netdev_run_todo(), which runs at rtnl_unlock() (rtnl released) and after the interface has been closed, so it does not pin rtnl. A worker blocked in an association TX only delays that one interface's unregister (the usual "waiting for %s to become free"), it does not hold rtnl. netdev_hold() is used for this reason instead of a cancel_work_sync() under rtnl, which would block on the worker's unbounded MLME TX wait via ieee802154_sync_queue().

The mac-command worker additionally skips processing for a stopped interface (ieee802154_sdata_running()), avoiding a needless association response during teardown.

CVSS v3
7.5
EG Score
7.5HIGHhigh confidence
EG Risk
38
EG Risk 38/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
Severity75% × 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.3%
EPSS %ILE
18th
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

October 3, 2026

Advisory Details (4)

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

mac802154: fix use-after-free of sdata via queued RX frames - kernel/git/stable/linux.git - Linux kernel stable tree

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

mac802154: fix use-after-free of sdata via queued RX frames - kernel/git/stable/linux.git - Linux kernel stable tree

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

mac802154: fix use-after-free of sdata via queued RX frames - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/07f0214018d7241e3610c1be984c8abfce16c099
generic

mac802154: fix use-after-free of sdata via queued RX frames - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4740ef0518c5e3bf31ebfb2288a6ac3b462ead06

Vendor Advisories for CVE-2026-97595(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
linux-6.126.12.100-1~deb12u1, 6.12.101-1~deb12u1, 6.12.107-1~deb12u1
  • every version up to 6.12.111-1~deb12u1: fixed in 6.12.111-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (35 versions)
  • every version up to 6.12.111-1: fixed in 6.12.111-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (180 versions)
  • every version up to 7.2.7-1: fixed in 7.2.7-1
—

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-97595?
CVE-2026-97595 is a high vulnerability published on September 25, 2026. In the Linux kernel, the following vulnerability has been resolved: mac802154: fix use-after-free of sdata via queued RX frames The RX softirq producer ieee802154subifframe() queues received beacon and MAC-command frames onto local->rxbeaconlist / rxmaccmd_list and schedules a process-context…
When was CVE-2026-97595 disclosed?
CVE-2026-97595 was first published on September 25, 2026, with the most recent update on October 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-97595 actively exploited?
CVE-2026-97595 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (18th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-97595?
CVE-2026-97595 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-97595?
No fix for CVE-2026-97595 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-97595 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-97595

Explore →

Is Your Infrastructure Affected by CVE-2026-97595?

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