CVE-2026-31669

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-04-24. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.8Exploit: NoneExposed: 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:

mptcp: fix slab-use-after-free in __inet_lookup_established

The ehash table lookups are lockless and rely on SLAB_TYPESAFE_BY_RCU to guarantee socket memory stability during RCU read-side critical sections. Both tcp_prot and tcpv6_prot have their slab caches created with this flag via proto_register().

However, MPTCP's mptcp_subflow_init() copies tcpv6_prot into tcpv6_prot_override during inet_init() (fs_initcall, level 5), before inet6_init() (module_init/device_initcall, level 6) has called proto_register(&tcpv6_prot). At that point, tcpv6_prot.slab is still NULL, so tcpv6_prot_override.slab remains NULL permanently.

This causes MPTCP v6 subflow child sockets to be allocated via kmalloc (falling into kmalloc-4k) instead of the TCPv6 slab cache. The kmalloc-4k cache lacks SLAB_TYPESAFE_BY_RCU, so when these sockets are freed without SOCK_RCU_FREE (which is cleared for child sockets by design), the memory can be immediately reused. Concurrent ehash lookups under rcu_read_lock can then access freed memory, triggering a slab-use-after-free in __inet_lookup_established.

Fix this by splitting the IPv6-specific initialization out of mptcp_subflow_init() into a new mptcp_subflow_v6_init(), called from mptcp_proto_v6_init() before protocol registration. This ensures tcpv6_prot_override.slab correctly inherits the SLAB_TYPESAFE_BY_RCU slab cache.

CVSS v3
9.8
EG Score
9.8(medium)
EPSS
37.3%
KEV
Not listed

Published

April 24, 2026

Last Modified

July 14, 2026

Advisory Details (9)

Auto-updated Jul 17, 2026
⚠️ Active exploitation confirmed. No patch confirmed yet.
generic

mptcp: fix slab-use-after-free in __inet_lookup_established - kernel/git/stable/linux.git - Linux kernel stable tree

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

mptcp: fix slab-use-after-free in __inet_lookup_established - kernel/git/stable/linux.git - Linux kernel stable tree

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

mptcp: fix slab-use-after-free in __inet_lookup_established - kernel/git/stable/linux.git - Linux kernel stable tree

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

mptcp: fix slab-use-after-free in __inet_lookup_established - kernel/git/stable/linux.git - Linux kernel stable tree

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

mptcp: fix slab-use-after-free in __inet_lookup_established - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9b55b253907e7431210483519c5ad711a37dafa1
generic

mptcp: fix slab-use-after-free in __inet_lookup_established - kernel/git/stable/linux.git - Linux kernel stable tree

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

mptcp: fix slab-use-after-free in __inet_lookup_established - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/15fa9ead4d5e6b6b9c794e84144146c917f2cb62

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 5.15.203osv

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.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 14× 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 251 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-31669?
CVE-2026-31669 is a critical vulnerability published on April 24, 2026. In the Linux kernel, the following vulnerability has been resolved: mptcp: fix slab-use-after-free in inetlookupestablished The ehash table lookups are lockless and rely on SLABTYPESAFEBY_RCU to guarantee socket memory stability during RCU read-side critical sections. Both tcp_prot and tcpv6_prot…
When was CVE-2026-31669 disclosed?
CVE-2026-31669 was first published in the National Vulnerability Database on April 24, 2026, with the most recent update on July 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31669 actively exploited?
CVE-2026-31669 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 37.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-31669?
CVE-2026-31669 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-31669?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31669, 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-31669

Explore →

Is Your Infrastructure Affected by CVE-2026-31669?

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