CVE-2024-26826: mptcp: fix data re-injection from stale subflow
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.65% (FIRST EPSS); higher than 51.6% of all records.
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 624902eab7abcb8731b333ec73f206d38d839cd8, 6673d9f1c2cd984390550dbdf7d5ae07b20abbf8, 6f95120f898b40d13fd441225ef511307853c9c2.
- Severity is disputed: the assigning authority (CNA) scores it 7.5, NVD 5.5.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 624902eab7abcb8731b333ec73f206d38d839cd8, 6673d9f1c2cd984390550dbdf7d5ae07b20abbf8, 6f95120f898b40d13fd441225ef511307853c9c2 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: mptcp: fix data re-injection from stale subflow When the MPTCP PM detects that a subflow is stale, all the packet scheduler must re-inject all the mptcp-level unacked data. To avoid acquiring unneeded locks, it first try to check if any unacked data is present at all in the RTX queue, but such check is currently broken, as it uses TCP-specific helper on an MPTCP socket. Funnily enough fuzzers and static checkers are happy, as the accessed memory still belongs to the mptcp_sock struct, and even from a functional perspective the recovery completed successfully, as the short-cut test always failed. A recent unrelated TCP change - commit d5fed5addb2b ("tcp: reorganize tcp_sock fast path variables") - exposed the issue, as the tcp field reorganization makes the mptcp code always skip the re-inection. Fix the issue dropping the bogus call: we are on a slow path, the early optimization proved once again to be evil.
- Published
- Apr 17, 2024
- Updated
- Aug 5, 2026
- EPSS
- 0.6% · 51th percentile
- CWE
- —
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.6%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 5.5
- CNA · Linux
- 7.5
- 2.0 point gap
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.15affected
- 1e1d9d6f119c55c05e8ea78ed3e49046690abffd and later · before 6f95120f898b40d13fd441225ef511307853c9c2affected · git
- 1e1d9d6f119c55c05e8ea78ed3e49046690abffd and later · before 6673d9f1c2cd984390550dbdf7d5ae07b20abbf8affected · git
- 1e1d9d6f119c55c05e8ea78ed3e49046690abffd and later · before b609c783c535493aa3fca22c7e40a120370b1ca5affected · git
- 1e1d9d6f119c55c05e8ea78ed3e49046690abffd and later · before 624902eab7abcb8731b333ec73f206d38d839cd8affected · git
- 1e1d9d6f119c55c05e8ea78ed3e49046690abffd and later · before b6c620dc43ccb4e802894e54b651cf81495e9598affected · git
- before 5.15not affected · semver
- 5.15.149 and later · up to and including 5.15.*not affected · semver
- 6.1.79 and later · up to and including 6.1.*not affected · semver
- 6.6.18 and later · up to and including 6.6.*not affected · semver
Affected versions · NVD (5)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.15 and later · before 5.15.149
- linux linux kernel5.16 and later · before 6.1.79
- linux linux kernel6.2 and later · before 6.6.18
- linux linux kernel6.7 and later · before 6.7.6
- linux linux kernel6.8
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:9 | bpftool | before 7.3.0-427.42.1.el9_4 | 7.3.0-427.42.1.el9_4 |
| AlmaLinux:9 | kernel | before 5.14.0-427.42.1.el9_4 | 5.14.0-427.42.1.el9_4 |
| AlmaLinux:9 | kernel-64k | before 5.14.0-427.42.1.el9_4 | 5.14.0-427.42.1.el9_4 |
| AlmaLinux:9 | kernel-64k-core | before 5.14.0-427.42.1.el9_4 | 5.14.0-427.42.1.el9_4 |
| AlmaLinux:9 | kernel-64k-debug | before 5.14.0-427.42.1.el9_4 | 5.14.0-427.42.1.el9_4 |
| AlmaLinux:9 | kernel-64k-debug-core | before 5.14.0-427.42.1.el9_4 | 5.14.0-427.42.1.el9_4 |
| AlmaLinux:9 | kernel-64k-debug-devel | before 5.14.0-427.42.1.el9_4 | 5.14.0-427.42.1.el9_4 |
| AlmaLinux:9 | kernel-64k-debug-devel-matched | before 5.14.0-427.42.1.el9_4 | 5.14.0-427.42.1.el9_4 |
| AlmaLinux:9 | kernel-64k-debug-modules | before 5.14.0-427.42.1.el9_4 | 5.14.0-427.42.1.el9_4 |
| AlmaLinux:9 | kernel-64k-debug-modules-core | before 5.14.0-427.42.1.el9_4 | 5.14.0-427.42.1.el9_4 |
| AlmaLinux:9 | kernel-64k-debug-modules-extra | before 5.14.0-427.42.1.el9_4 | 5.14.0-427.42.1.el9_4 |
| AlmaLinux:9 | kernel-64k-devel | before 5.14.0-427.42.1.el9_4 | 5.14.0-427.42.1.el9_4 |
| AlmaLinux:9 | kernel-64k-devel-matched | before 5.14.0-427.42.1.el9_4 | 5.14.0-427.42.1.el9_4 |
| AlmaLinux:9 | kernel-64k-modules | before 5.14.0-427.42.1.el9_4 | 5.14.0-427.42.1.el9_4 |
| AlmaLinux:9 | kernel-64k-modules-core | before 5.14.0-427.42.1.el9_4 | 5.14.0-427.42.1.el9_4 |
| AlmaLinux:9 | kernel-64k-modules-extra | before 5.14.0-427.42.1.el9_4 | 5.14.0-427.42.1.el9_4 |
| AlmaLinux:9 | kernel-abi-stablelists | before 5.14.0-427.42.1.el9_4 | 5.14.0-427.42.1.el9_4 |
| AlmaLinux:9 | kernel-core | before 5.14.0-427.42.1.el9_4 | 5.14.0-427.42.1.el9_4 |
| AlmaLinux:9 | kernel-cross-headers | before 5.14.0-427.42.1.el9_4 | 5.14.0-427.42.1.el9_4 |
| AlmaLinux:9 | kernel-debug | before 5.14.0-427.42.1.el9_4 | 5.14.0-427.42.1.el9_4 |
| AlmaLinux:9 | kernel-debug-core | before 5.14.0-427.42.1.el9_4 | 5.14.0-427.42.1.el9_4 |
| AlmaLinux:9 | kernel-debug-devel | before 5.14.0-427.42.1.el9_4 | 5.14.0-427.42.1.el9_4 |
| AlmaLinux:9 | kernel-debug-devel-matched | before 5.14.0-427.42.1.el9_4 | 5.14.0-427.42.1.el9_4 |
| AlmaLinux:9 | kernel-debug-modules | before 5.14.0-427.42.1.el9_4 | 5.14.0-427.42.1.el9_4 |
+96
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2024-26824Apr 17, 2024 · crypto: algif_hash - Remove bogus SGL free on zero-length error path22Monitor
- ← EarlierCVE-2024-26825Apr 17, 2024 · nfc: nci: free rx_data_reassembly skb on NCI device cleanup22Monitor
- Later →CVE-2024-26829Apr 17, 2024 · media: ir_toy: fix a memleak in irtoy_tx22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 624902eab7abcb8731b333ec73f206d38d839cd8 | Vendor (CNA) |
| Linux Linux | 6673d9f1c2cd984390550dbdf7d5ae07b20abbf8 | Vendor (CNA) |
| Linux Linux | 6f95120f898b40d13fd441225ef511307853c9c2 | Vendor (CNA) |
| Linux Linux | b609c783c535493aa3fca22c7e40a120370b1ca5 | Vendor (CNA) |
| Linux Linux | b6c620dc43ccb4e802894e54b651cf81495e9598 | Vendor (CNA) |
| almalinux:bpftool | 4.18.0-553.8.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:bpftool | 7.3.0-427.42.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel | 4.18.0-553.8.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel | 5.14.0-427.42.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k | 5.14.0-427.42.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-core | 5.14.0-427.42.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug | 5.14.0-427.42.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-core | 5.14.0-427.42.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel | 5.14.0-427.42.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel-matched | 5.14.0-427.42.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules | 5.14.0-427.42.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-core | 5.14.0-427.42.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-extra | 5.14.0-427.42.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-devel | 5.14.0-427.42.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-abi-stablelists | 4.18.0-553.8.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-core | 4.18.0-553.8.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-cross-headers | 4.18.0-553.8.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug | 4.18.0-553.8.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-core | 4.18.0-553.8.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-devel | 4.18.0-553.8.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-modules | 4.18.0-553.8.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-modules-extra | 4.18.0-553.8.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-devel | 4.18.0-553.8.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-doc | 4.18.0-553.8.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| debian:linux | 6.1.82-1 · Debian:12 | Package registry (OSV) |
+34
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-0494 · May 16, 2024(Linux Kernel Güncellemesi)
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.