CVE-2026-23016

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-01-31. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: 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:

inet: frags: drop fraglist conntrack references

Jakub added a warning in nf_conntrack_cleanup_net_list() to make debugging leaked skbs/conntrack references more obvious.

syzbot reports this as triggering, and I can also reproduce this via ip_defrag.sh selftest:

conntrack cleanup blocked for 60s WARNING: net/netfilter/nf_conntrack_core.c:2512 [..]

conntrack clenups gets stuck because there are skbs with still hold nf_conn references via their frag_list.

net.core.skb_defer_max=0 makes the hang disappear.

Eric Dumazet points out that skb_release_head_state() doesn't follow the fraglist.

ip_defrag.sh can only reproduce this problem since commit 6471658dc66c ("udp: use skb_attempt_defer_free()"), but AFAICS this problem could happen with TCP as well if pmtu discovery is off.

The relevant problem path for udp is:

  • netns emits fragmented packets
  • nf_defrag_v6_hook reassembles them (in output hook)
  • reassembled skb is tracked (skb owns nf_conn reference)
  • ip6_output refragments
  • refragmented packets also own nf_conn reference (ip6_fragment
calls ip6_copy_metadata())
  • on input path, nf_defrag_v6_hook skips defragmentation: the
fragments already have skb->nf_conn attached
  • skbs are reassembled via ipv6_frag_rcv()
  • skb_consume_udp -> skb_attempt_defer_free() -> skb ends up
in pcpu freelist, but still has nf_conn reference.

Possible solutions: 1 let defrag engine drop nf_conn entry, OR 2 export kick_defer_list_purge() and call it from the conntrack netns exit callback, OR 3 add skb_has_frag_list() check to skb_attempt_defer_free()

2 & 3 also solve ip_defrag.sh hang but share same drawback:

Such reassembled skbs, queued to socket, can prevent conntrack module removal until userspace has consumed the packet. While both tcp and udp stack do call nf_reset_ct() before placing skb on socket queue, that function doesn't iterate frag_list skbs.

Therefore drop nf_conn entries when they are placed in defrag queue. Keep the nf_conn entry of the first (offset 0) skb so that reassembled skb retains nf_conn entry for sake of TX path.

Note that fixes tag is incorrect; it points to the commit introducing the 'ip_defrag.sh reproducible problem': no need to backport this patch to every stable kernel.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/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
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

January 31, 2026

Last Modified

June 17, 2026

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 6.18.6osv

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.

Data Freshness Timeline

(refreshed 8× in last 7d / 46× 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 110 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-23016?
CVE-2026-23016 is a medium vulnerability published on January 31, 2026. In the Linux kernel, the following vulnerability has been resolved: inet: frags: drop fraglist conntrack references Jakub added a warning in nfconntrackcleanupnetlist() to make debugging leaked skbs/conntrack references more obvious. syzbot reports this as triggering, and I can also reproduce this…
When was CVE-2026-23016 disclosed?
CVE-2026-23016 was first published in the National Vulnerability Database on January 31, 2026, with the most recent update on June 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-23016 actively exploited?
CVE-2026-23016 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.1% of all scored CVEs.
What is the CVSS score of CVE-2026-23016?
CVE-2026-23016 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-23016?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-23016, 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-23016

Explore →

Is Your Infrastructure Affected by CVE-2026-23016?

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