LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23169: mptcp: fix race in mptcp_pm_nl_flush_addrs_doit()

In the Linux kernel, the following vulnerability has been resolved: mptcp: fix race in mptcp_pm_nl_flush_addrs_doit() syzbot and Eulgyu Kim reported crashes in mptcp_pm_nl_get_local_id() and/or mptcp_pm_nl_is_backup() Root cause is list_splice_init() in mptcp_pm_nl_flush_addrs_doit() which is not RCU ready. list_splice_init_rcu() can not be called here while holding pernet->lock spinlock. Many thanks to Eulgyu Kim for providing a repro and testing our patches.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A race condition in the Linux kernel's Multipath TCP address-management code can cause kernel crashes. The supplied CVSS score is 7.8 and requires local, low-privileged access, so this is primarily a host-compromise and availability concern rather than a remotely exploitable internet threat.

Executive priority

Treat as a high-priority kernel update for multi-user, container-hosting, and other locally exposed systems. Internet-only servers without untrusted local access have lower immediate exploitability, but kernel crashes can still create operational disruption. Use vendor package guidance because the bundle does not map every affected release to a corrected version.

Technical view

The flaw occurs in mptcp_pm_nl_flush_addrs_doit(), where list_splice_init() is not safe for RCU readers. Concurrent access can trigger crashes in mptcp_pm_nl_get_local_id() or mptcp_pm_nl_is_backup(). The CVSS vector reports local access, low complexity, low privileges, no user interaction, unchanged scope, and high confidentiality, integrity, and availability impacts.

Likely exposure

Potential exposure includes systems running the listed affected Linux kernel versions from 5.11 through 6.19. Practical reachability likely depends on access to the affected MPTCP network-management path. The bundle does not establish whether MPTCP configuration, namespace permissions, or specific capabilities are required, so administrators should confirm exposure with their distribution.

Exploitation context

The issue was found through syzbot crash testing, and a reproducer was provided to kernel developers. The supplied record says it is not in KEV and contains no evidence of active exploitation. Although the CVSS vector claims high confidentiality, integrity, and availability impacts, the technical description specifically documents crashes and does not describe demonstrated privilege escalation.

Researcher notes

The root cause is an RCU-unsafe list splice during address flushing while concurrent readers inspect MPTCP address state. Multiple stable-tree commits are supplied, indicating branch-specific backports. Exact triggering permissions, affected configuration prerequisites, and exploitation beyond crashes are not established in the bundle and should not be assumed.

Mitigation direction

  • Install a vendor-supported kernel containing the applicable stable fix commit.
  • Consult the Linux distribution's advisory for exact affected and corrected package versions.
  • Prioritize shared or multi-user hosts where untrusted local users can access kernel networking features.
  • If patching is delayed, review vendor guidance for safely restricting unnecessary MPTCP functionality.

Validation and detection

  • Inventory running kernel versions and compare them with distribution-specific advisories.
  • Confirm whether MPTCP is enabled or used on affected systems.
  • Verify the installed kernel includes the applicable stable fix or vendor backport.
  • Review kernel logs and crash reports for faults involving the named MPTCP functions.
Prepared
Confidence
medium
Sources
8

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2026-23169 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
0ADP providers
7Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2026-23169Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux141694df6573b49aa4143c92556544b4b0bbda72, 141694df6573b49aa4143c92556544b4b0bbda72, 141694df6573b49aa4143c92556544b4b0bbda72, 141694df6573b49aa4143c92556544b4b0bbda72, 141694df6573b49aa4143c92556544b4b0bbda72, 141694df6573b49aa4143c92556544b4b0bbda72unaffected
LinuxLinux5.11, 0, 5.15.201, 6.1.164, 6.6.125, 6.12.72, 6.18.9, 6.19affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.