Security readout for executives and security teams
Plain-English summary
A Linux MPTCP server can mishandle shared socket metadata when accepting a connection. During socket cleanup, the kernel may free the same memory twice, potentially causing a kernel crash or other memory corruption. The supplied severity is critical, but the sources do not demonstrate data theft, code execution, or active exploitation.
Executive priority
Treat this as an accelerated kernel-remediation item, especially on MPTCP-serving systems. The critical score warrants prompt inventory and patching, while the absence of supplied exploitation evidence argues against declaring an active incident solely from this CVE.
Technical view
An accepted MPTCP socket inherits its listener's inet_opt pointer instead of receiving independent ownership. Destruction of the subflow and original socket can therefore free the same allocation twice in inet_sock_destruct. KASAN observed the fault during socket dismantling. Linux stable commits provide branch-specific corrections.
Likely exposure
Exposure concerns Linux systems running affected kernel builds where MPTCP server connections are accepted and later dismantled. The supplied version list is ambiguous about introduced and fixed boundaries, so vulnerability managers should map each running distribution kernel to its vendor advisory or the corresponding stable commit.
Exploitation context
The supplied CVSS is 9.8 with an unauthenticated network vector. However, the bundle marks this CVE as absent from KEV and provides no evidence of active exploitation, public weaponization, or demonstrated confidentiality and integrity impact. The documented result is a KASAN-detected double-free during cleanup.
Researcher notes
The evidence establishes a shared-pointer ownership error and reproducible double-free. It does not establish practical remote code execution or the CVSS confidentiality and integrity consequences. The flattened affected-version data cannot reliably distinguish introduction and correction boundaries; use the six branch-specific stable commits and distribution advisories for exact applicability.
Mitigation direction
- Identify the running kernel branch and apply the corresponding Linux stable fix or distribution security update.
- Prioritize systems that provide or rely upon MPTCP server functionality.
- Reboot into the updated kernel and confirm the vulnerable build is no longer running.
- If updating is delayed, consult the Linux distribution for supported mitigations and compensating controls.
Validation and detection
- Inventory each host's running kernel version and compare it with the applicable distribution advisory and stable fix.
- Confirm the running kernel contains the branch-specific correction referenced by the Linux stable commits.
- Review kernel logs for double-free or KASAN reports involving inet_sock_destruct during MPTCP socket teardown.
- Verify updated systems booted the remediated kernel, rather than merely installing its package.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-2024-26782 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9LinuxVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/f74362a004225df935863dea6eb7d82daaa5b16eCVE reference, Linux
- https://git.kernel.org/stable/c/4a4eeb6912538c2d0b158e8d11b62d96c1dada4eCVE reference, Linux
- https://git.kernel.org/stable/c/d93fd40c62397326046902a2c5cb75af50882a85CVE reference, Linux
- https://git.kernel.org/stable/c/ce0809ada38dca8d6d41bb57ab40494855c30582CVE reference, Linux
- https://git.kernel.org/stable/c/85933e80d077c9ae2227226beb86c22f464059ccCVE reference, Linux
- https://git.kernel.org/stable/c/10048689def7e40a4405acda16fdc6477d4ecc5cCVE reference, Linux
- https://lists.debian.org/debian-lts-announce/2024/06/msg00017.htmlCVE reference, CVE · x_transferred
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.