CVE-2026-31669

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.8Exploit: None knownExposed: 0

A fix is available — apply it.

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)
EG Risk
49(Track)
EG Risk 49/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
Severity98% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
38%
KEV
Not listed

Published

April 24, 2026

Last Modified

August 5, 2026

Advisory Details (9)

Auto-updated Aug 26, 2026
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/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/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/15fa9ead4d5e6b6b9c794e84144146c917f2cb62
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/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/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

Patch Availability(13)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-0:4.18.0-305.197.1.el8_42026-07-06redhat
redhatkernel-0:4.18.0-372.199.1.el8_62026-07-06redhat
redhatkernel-0:4.18.0-477.150.1.el8_82026-07-06redhat
redhatkernel-0:5.14.0-570.125.1.el9_62026-07-01redhat
redhatkernel-0:5.14.0-284.178.1.el9_22026-07-01redhat
redhatkernel-rt-0:5.14.0-284.178.1.rt14.463.el9_22026-07-01redhat
redhatkernel-0:6.12.0-55.84.1.el10_02026-06-29redhat
redhatkernel-0:5.14.0-687.17.1.el9_82026-06-22redhat
redhatkernel-0:5.14.0-427.134.1.el9_42026-06-22redhat
redhatkernel-0:6.12.0-211.26.1.el10_22026-06-20redhat
redhatkernel-rt-0:4.18.0-553.134.1.rt7.475.el8_102026-06-16redhat
redhatkernel-0:4.18.0-553.134.1.el8_102026-06-16redhat
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.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux-6.16.1.106-3~deb11u1 ... 6.1.164-1~deb11u1 (16 versions)6.1.170-1~deb11u1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (48 versions)6.1.170-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (124 versions)6.19.13-1

Weakness Classification(1)

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

Additional Vendor Advisories

(12)

Data Freshness Timeline

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

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

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 August 5, 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 0% probability of exploitation in the next 30 days, which ranks it in the top 61.9% of all scored CVEs.
What is the CVSS score of CVE-2026-31669?
CVE-2026-31669 has a CVSS v4.0 base score of 9.8 (CNA self-assessment; NVD's own analysis pending).
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

See which npm, PyPI, Go, and Maven packages are affected by 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.