Security readout for executives and security teams
Plain-English summary
This is a Linux kernel MPTCP bug. Under a specific socket-state race, a delayed worker can process a closed socket and trigger a kernel divide error. The documented impact is a crash trace, so treat it primarily as an availability risk for systems that enable or rely on Multipath TCP.
Executive priority
Schedule remediation in normal vulnerability cycles, with faster action for systems using MPTCP in production or availability-sensitive environments. Current evidence supports a kernel availability concern, not confirmed active exploitation.
Technical view
mptcp_worker can run when the associated MPTCP socket is in an unexpected CLOSED state after reset/fastclose and disconnect/listen transitions. The fault occurs during TCP window selection while sending an active reset. The upstream fix adds stricter bad-state checks before worker processing.
Likely exposure
Exposure is most relevant to Linux systems with MPTCP enabled or reachable through MPTCP paths. The bundle identifies Linux kernel versions and stable commits, but does not provide distribution-specific package names or default MPTCP enablement status.
Exploitation context
The source describes a reproducible state sequence and kernel crash trace, but provides no KEV listing, public exploitation claim, exploit maturity, or remote attack confirmation. Do not assume active exploitation from the supplied evidence.
Researcher notes
The core issue is an MPTCP worker state validation flaw after socket state transitions. The provided record lacks CVSS, CWE, exploitability analysis, and distro mapping. Validation should focus on kernel lineage, backported fixes, and MPTCP exposure.
Mitigation direction
Check vendor kernel advisories for CVE-2023-54176 package status.
Update to a kernel containing the referenced stable fixes.
Inventory systems where MPTCP is enabled or exposed.
Prioritize internet-facing or high-availability Linux hosts first.
Monitor kernel logs for MPTCP-related crashes until patched.
Validation and detection
Confirm running kernel versions against vendor CVE guidance.
Verify whether MPTCP is enabled on affected Linux systems.
Check whether installed kernels include the referenced stable commits.
Review logs for divide errors in mptcp_worker or TCP output paths.
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-2023-54176 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.
0CVSS vectors
3Timeline events
0ADP providers
5Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Dec 30, 2025, 12:08 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.