CVE-2026-97602

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:

inet: frags: invalidate queues before flushing them

fqdir_pre_exit() flushes the skbs from incomplete queues without changing their completion state. A fragment which found a queue before high_thresh was cleared can then acquire the queue lock and reuse stale reassembly metadata. A queue concurrently killed after fqdir->dead is set can instead become INET_FRAG_COMPLETE|INET_FRAG_HASH_DEAD while still holding its old skbs; skipping it because it is complete leaves those references behind until asynchronous fqdir teardown.

For IPv6, stale metadata can make ip6_frag_reasm() use the old nhoffset with a new skb and access memory out of bounds. The resulting heap corruption can be leveraged for local privilege escalation when unprivileged network namespaces are available. Unflushed fragments can also keep conntrack references alive after the conntrack per-net cleanup point.

Kill each incomplete queue, then flush every queue still owned by the dying rhashtable. HASH_DEAD identifies that ownership, while complete queues without it are already owned by another destroy path and must be left alone. Releasing a timer reference removed by inet_frag_kill() is deferred to inet_frag_putn(), after the queue lock is dropped.

KASAN report:

BUG: KASAN: slab-out-of-bounds in ipv6_frag_rcv (net/ipv6/reassembly.c:289 (discriminator 2) net/ipv6/reassembly.c:229 (discriminator 2) net/ipv6/reassembly.c:391 (discriminator 2)) Write of size 1 at addr ff110001039c6e00 by task poc/771 Call Trace: ? ipv6_frag_rcv (net/ipv6/reassembly.c:289 (discriminator 2) net/ipv6/reassembly.c:229 (discriminator 2) net/ipv6/reassembly.c:391 (discriminator 2)) ipv6_frag_rcv (net/ipv6/reassembly.c:289 (discriminator 2) net/ipv6/reassembly.c:229 (discriminator 2) net/ipv6/reassembly.c:391 (discriminator 2)) ip6_protocol_deliver_rcu (net/ipv6/ip6_input.c:479 (discriminator 5)) ip6_input_finish (net/ipv6/ip6_input.c:534) ipv6_rcv (include/net/dst.h:480 (discriminator 3) net/ipv6/ip6_input.c:119 (discriminator 3) net/ipv6/ip6_input.c:109 (discriminator 3) include/linux/netfilter.h:325 (discriminator 3) include/linux/netfilter.h:319 (discriminator 3) net/ipv6/ip6_input.c:351 (discriminator 3)) packet_sendmsg (net/packet/af_packet.c:3110 net/packet/af_packet.c:3142) __x64_sys_sendmmsg (net/socket.c:2883 net/socket.c:2880 net/socket.c:2880) The buggy address belongs to the object at ff110001039c6b40 which belongs to the cache skbuff_small_head of size 704 The buggy address is located 0 bytes to the right of allocated 704-byte region [ff110001039c6b40, ff110001039c6e00)

BUG: KASAN: slab-out-of-bounds in ip6_protocol_deliver_rcu (net/ipv6/ip6_input.c:423 (discriminator 1)) Read of size 1 at addr ff110001039c6e08 by task poc/771 Call Trace: ? ip6_protocol_deliver_rcu (net/ipv6/ip6_input.c:423 (discriminator 1)) ip6_protocol_deliver_rcu (net/ipv6/ip6_input.c:423 (discriminator 1)) ip6_input_finish (net/ipv6/ip6_input.c:534) ipv6_rcv (include/net/dst.h:480 (discriminator 3) net/ipv6/ip6_input.c:119 (discriminator 3) net/ipv6/ip6_input.c:109 (discriminator 3) include/linux/netfilter.h:325 (discriminator 3) include/linux/netfilter.h:319 (discriminator 3) net/ipv6/ip6_input.c:351 (discriminator 3)) packet_sendmsg (net/packet/af_packet.c:3110 net/packet/af_packet.c:3142) __x64_sys_sendmmsg (net/socket.c:2883 net/socket.c:2880 net/socket.c:2880) packet_sendmsg (net/packet/af_packet.c:2959 net/packet/af_packet.c:3053 net/packet/af_packet.c:3142) __x64_sys_sendmmsg (net/socket.c:2883 net/socket.c:2880 net/socket.c:2880) The buggy address belongs to the object at ff110001039c6b40 which belongs to the cache skbuff_small_head of size 704 The buggy address is located 8 bytes to the right of allocated 704-byte region [ff110001039c6b40, ff110001039c6e00)

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

October 3, 2026

Advisory Details (4)

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

inet: frags: invalidate queues before flushing them - kernel/git/stable/linux.git - Linux kernel stable tree

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

inet: frags: invalidate queues before flushing them - kernel/git/stable/linux.git - Linux kernel stable tree

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

inet: frags: invalidate queues before flushing them - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7cb5f4643a7fcdbfbee1fad3cdfc678add62d378
generic

inet: frags: invalidate queues before flushing them - kernel/git/stable/linux.git - Linux kernel stable tree

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

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

Frequently asked(5)

What is CVE-2026-97602?
CVE-2026-97602 is a high vulnerability published on September 25, 2026. In the Linux kernel, the following vulnerability has been resolved: inet: frags: invalidate queues before flushing them fqdirpreexit() flushes the skbs from incomplete queues without changing their completion state. A fragment which found a queue before high_thresh was cleared can then acquire the…
When was CVE-2026-97602 disclosed?
CVE-2026-97602 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-97602 actively exploited?
CVE-2026-97602 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-97602?
CVE-2026-97602 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-97602?
No fix for CVE-2026-97602 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-97602 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-97602

Explore →

Is Your Infrastructure Affected by CVE-2026-97602?

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

Book a Demo →Browse All CVEs