CVE-2026-23321

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2026-15272 (ENISA EUVD) · GHSA-cp65-xq47-m66j (GitHub Security Advisories)Source: ENISA EUVD

5.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

mptcp: pm: in-kernel: always mark signal+subflow endp as used

Syzkaller managed to find a combination of actions that was generating this warning:

msk->pm.local_addr_used == 0 WARNING: net/mptcp/pm_kernel.c:1071 at __mark_subflow_endp_available net/mptcp/pm_kernel.c:1071 [inline], CPU#1: syz.2.17/961 WARNING: net/mptcp/pm_kernel.c:1071 at mptcp_nl_remove_subflow_and_signal_addr net/mptcp/pm_kernel.c:1103 [inline], CPU#1: syz.2.17/961 WARNING: net/mptcp/pm_kernel.c:1071 at mptcp_pm_nl_del_addr_doit+0x81d/0x8f0 net/mptcp/pm_kernel.c:1210, CPU#1: syz.2.17/961 Modules linked in: CPU: 1 UID: 0 PID: 961 Comm: syz.2.17 Not tainted 6.19.0-08368-gfafda3b4b06b #22 PREEMPT(full) Hardware name: QEMU Ubuntu 25.10 PC v2 (i440FX + PIIX, + 10.1 machine, 1996), BIOS 1.17.0-debian-1.17.0-1build1 04/01/2014 RIP: 0010:__mark_subflow_endp_available net/mptcp/pm_kernel.c:1071 [inline] RIP: 0010:mptcp_nl_remove_subflow_and_signal_addr net/mptcp/pm_kernel.c:1103 [inline] RIP: 0010:mptcp_pm_nl_del_addr_doit+0x81d/0x8f0 net/mptcp/pm_kernel.c:1210 Code: 89 c5 e8 46 30 6f fe e9 21 fd ff ff 49 83 ed 80 e8 38 30 6f fe 4c 89 ef be 03 00 00 00 e8 db 49 df fe eb ac e8 24 30 6f fe 90 <0f> 0b 90 e9 1d ff ff ff e8 16 30 6f fe eb 05 e8 0f 30 6f fe e8 9a RSP: 0018:ffffc90001663880 EFLAGS: 00010293 RAX: ffffffff82de1a6c RBX: 0000000000000000 RCX: ffff88800722b500 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 RBP: ffff8880158b22d0 R08: 0000000000010425 R09: ffffffffffffffff R10: ffffffff82de18ba R11: 0000000000000000 R12: ffff88800641a640 R13: ffff8880158b1880 R14: ffff88801ec3c900 R15: ffff88800641a650 FS: 00005555722c3500(0000) GS:ffff8880f909d000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f66346e0f60 CR3: 000000001607c000 CR4: 0000000000350ef0 Call Trace: genl_family_rcv_msg_doit+0x117/0x180 net/netlink/genetlink.c:1115 genl_family_rcv_msg net/netlink/genetlink.c:1195 [inline] genl_rcv_msg+0x3a8/0x3f0 net/netlink/genetlink.c:1210 netlink_rcv_skb+0x16d/0x240 net/netlink/af_netlink.c:2550 genl_rcv+0x28/0x40 net/netlink/genetlink.c:1219 netlink_unicast_kernel net/netlink/af_netlink.c:1318 [inline] netlink_unicast+0x3e9/0x4c0 net/netlink/af_netlink.c:1344 netlink_sendmsg+0x4aa/0x5b0 net/netlink/af_netlink.c:1894 sock_sendmsg_nosec net/socket.c:727 [inline] __sock_sendmsg+0xc9/0xf0 net/socket.c:742 ____sys_sendmsg+0x272/0x3b0 net/socket.c:2592 ___sys_sendmsg+0x2de/0x320 net/socket.c:2646 __sys_sendmsg net/socket.c:2678 [inline] __do_sys_sendmsg net/socket.c:2683 [inline] __se_sys_sendmsg net/socket.c:2681 [inline] __x64_sys_sendmsg+0x110/0x1a0 net/socket.c:2681 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0x143/0x440 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f66346f826d Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 e8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007ffc83d8bdc8 EFLAGS: 00000246 ORIG_RAX: 000000000000002e RAX: ffffffffffffffda RBX: 00007f6634985fa0 RCX: 00007f66346f826d RDX: 00000000040000b0 RSI: 0000200000000740 RDI: 0000000000000007 RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 00007f6634985fa8 R13: 00007f6634985fac R14: 0000000000000000 R15: 0000000000001770

The actions that caused that seem to be:

  • Set the MPTCP subflows limit to 0
  • Create an MPTCP endpoint with both the 'signal' and 'subflow' flags
  • Create a new MPTCP connection from a different address: an ADD_ADDR
linked to the MPTCP endpoint will be sent ('signal' flag), but no subflows is initiated ('subflow' flag)
  • Remove the MPTCP endpoint

---truncated---

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.1%
EPSS %ILE
2nd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

March 25, 2026

Last Modified

October 15, 2026

Advisory Details (8)

Auto-updated Jul 19, 2026
Patch available.
Web page

mptcp: pm: in-kernel: always mark signal+subflow endp as used - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c5c877e140e5f46023a74a51e577ce5edd0a4be7
Web page

mptcp: pm: in-kernel: always mark signal+subflow endp as used - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a64aa7db39392add5be09dffaedbf1f0ce5554df
Web page

mptcp: pm: in-kernel: always mark signal+subflow endp as used - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/67f34ab318807989b57dfdb0f79e2d4e57018290
Web page

mptcp: pm: in-kernel: always mark signal+subflow endp as used - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/579a752464a64cb5f9139102f0e6b90a1f595ceb
Web page

mptcp: pm: in-kernel: always mark signal+subflow endp as used - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/198824ccfa64ffebd918bf99c939bd8170a4a4d8
Web page

mptcp: pm: in-kernel: always mark signal+subflow endp as used - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/05799c2f1ca5eb13d65764dda688d02021b65e06

Vendor Advisories for CVE-2026-23321(1)

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

Patch Availability(15)

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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux-6.16.1.106-3~deb11u1 ... 6.1.164-1~deb11u1 (16 versions)
  • every version up to 6.1.170-1~deb11u1: fixed in 6.1.170-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (48 versions)
  • every version up to 6.1.170-1: fixed in 6.1.170-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)
  • every version up to 6.12.85-1: fixed in 6.12.85-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (121 versions)
  • every version up to 6.19.8-1: fixed in 6.19.8-1
—

All Vendor Advisories

(14)

Data Freshness Timeline

(refreshed 6× in last 7d / 40× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 99 of 264 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 165 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-23321?
CVE-2026-23321 is a medium-severity vulnerability; its CVE record was published on March 25, 2026. In the Linux kernel, the following vulnerability has been resolved: mptcp: pm: in-kernel: always mark signal+subflow endp as used Syzkaller managed to find a combination of actions that was generating this warning: msk->pm.local_addr_used == 0 WARNING: net/mptcp/pm_kernel.c:1071 at…
When was the CVE record for CVE-2026-23321 published?
The CVE record for CVE-2026-23321 was published on March 25, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 15, 2026; the record at its source may have been updated since.
Is CVE-2026-23321 actively exploited?
CVE-2026-23321 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (2nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-23321?
CVE-2026-23321 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-23321?
A fix for CVE-2026-23321 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-23321 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-23321

Explore →

Is Your Infrastructure Affected by CVE-2026-23321?

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