CVE-2022-50070: mptcp: do not queue data on closed subflows
Noroxi assessment
Priority: Monitor (action score 31/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.26% (FIRST EPSS).
- 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 8caf5c15b5288d52d9c89374d6c10fa32ee84ec5, c886d70286bf3ad411eb3d689328a67f7102c6ae, fb9c73ef2ac2ec816efdc8b9267bc04e1369c20b.
Low priority for now. Upgrade to Linux Linux 8caf5c15b5288d52d9c89374d6c10fa32ee84ec5, c886d70286bf3ad411eb3d689328a67f7102c6ae, fb9c73ef2ac2ec816efdc8b9267bc04e1369c20b 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: do not queue data on closed subflows Dipanjan reported a syzbot splat at close time: WARNING: CPU: 1 PID: 10818 at net/ipv4/af_inet.c:153 inet_sock_destruct+0x6d0/0x8e0 net/ipv4/af_inet.c:153 Modules linked in: uio_ivshmem(OE) uio(E) CPU: 1 PID: 10818 Comm: kworker/1:16 Tainted: G OE 5.19.0-rc6-g2eae0556bb9d #2 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1.1 04/01/2014 Workqueue: events mptcp_worker RIP: 0010:inet_sock_destruct+0x6d0/0x8e0 net/ipv4/af_inet.c:153 Code: 21 02 00 00 41 8b 9c 24 28 02 00 00 e9 07 ff ff ff e8 34 4d 91 f9 89 ee 4c 89 e7 e8 4a 47 60 ff e9 a6 fc ff ff e8 20 4d 91 f9 <0f> 0b e9 84 fe ff ff e8 14 4d 91 f9 0f 0b e9 d4 fd ff ff e8 08 4d RSP: 0018:ffffc9001b35fa78 EFLAGS: 00010246 RAX: 0000000000000000 RBX: 00000000002879d0 RCX: ffff8881326f3b00 RDX: 0000000000000000 RSI: ffff8881326f3b00 RDI: 0000000000000002 RBP: ffff888179662674 R08: ffffffff87e983a0 R09: 0000000000000000 R10: 0000000000000005 R11: 00000000000004ea R12: ffff888179662400 R13: ffff888179662428 R14: 0000000000000001 R15: ffff88817e38e258 FS: 0000000000000000(0000) GS:ffff8881f5f00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000020007bc0 CR3: 0000000179592000 CR4: 0000000000150ee0 Call Trace: <TASK> __sk_destruct+0x4f/0x8e0 net/core/sock.c:2067 sk_destruct+0xbd/0xe0 net/core/sock.c:2112 __sk_free+0xef/0x3d0 net/core/sock.c:2123 sk_free+0x78/0xa0 net/core/sock.c:2134 sock_put include/net/sock.h:1927 [inline] __mptcp_close_ssk+0x50f/0x780 net/mptcp/protocol.c:2351 __mptcp_destroy_sock+0x332/0x760 net/mptcp/protocol.c:2828 mptcp_worker+0x5d2/0xc90 net/mptcp/protocol.c:2586 process_one_work+0x9cc/0x1650 kernel/workqueue.c:2289 worker_thread+0x623/0x1070 kernel/workqueue.c:2436 kthread+0x2e9/0x3a0 kernel/kthread.c:376 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:302 </TASK> The root cause of the problem is that an mptcp-level (re)transmit can race with mptcp_close() and the packet scheduler checks the subflow state before acquiring the socket lock: we can try to (re)transmit on an already closed ssk. Fix the issue checking again the subflow socket status under the subflow socket lock protection. Additionally add the missing check for the fallback-to-tcp case.
- Published
- Jun 18, 2025
- Updated
- Aug 5, 2026
- EPSS
- 0.2% · 18th percentile
- CWE
- —
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CNA vs NVD score
- NVD
- 7.8
- CNA · Linux
- 7.8
- agree
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.
Running WordPress? Scan your site free with WP Lens
Noroxi 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 |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.10 and later · before 5.15.190
- linux linux kernel5.16 and later · before 5.19.4
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.10affected
- d5f49190def61c47b2faff170ba8fbc48bac4371 and later · before fb9c73ef2ac2ec816efdc8b9267bc04e1369c20baffected · git
- d5f49190def61c47b2faff170ba8fbc48bac4371 and later · before 8caf5c15b5288d52d9c89374d6c10fa32ee84ec5affected · git
- d5f49190def61c47b2faff170ba8fbc48bac4371 and later · before c886d70286bf3ad411eb3d689328a67f7102c6aeaffected · git
- before 5.10not affected · semver
- 5.15.190 and later · up to and including 5.15.*not affected · semver
- 5.19.4 and later · up to and including 5.19.*not affected · semver
- 6.0 and laternot affected · original_commit_for_fix
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 5.19.6-1 | 5.19.6-1 |
| Red Hat:rhel_aus:8.4::baseos | bpftool | before 0:4.18.0-305.179.1.el8_4 | 0:4.18.0-305.179.1.el8_4 |
| Red Hat:rhel_aus:8.4::baseos | bpftool-debuginfo | before 0:4.18.0-305.179.1.el8_4 | 0:4.18.0-305.179.1.el8_4 |
| Red Hat:rhel_aus:8.4::baseos | kernel | before 0:4.18.0-305.179.1.el8_4 | 0:4.18.0-305.179.1.el8_4 |
| Red Hat:rhel_aus:8.4::baseos | kernel-abi-stablelists | before 0:4.18.0-305.179.1.el8_4 | 0:4.18.0-305.179.1.el8_4 |
| Red Hat:rhel_aus:8.4::baseos | kernel-core | before 0:4.18.0-305.179.1.el8_4 | 0:4.18.0-305.179.1.el8_4 |
| Red Hat:rhel_aus:8.4::baseos | kernel-debug | before 0:4.18.0-305.179.1.el8_4 | 0:4.18.0-305.179.1.el8_4 |
| Red Hat:rhel_aus:8.4::baseos | kernel-debug-core | before 0:4.18.0-305.179.1.el8_4 | 0:4.18.0-305.179.1.el8_4 |
| Red Hat:rhel_aus:8.4::baseos | kernel-debug-debuginfo | before 0:4.18.0-305.179.1.el8_4 | 0:4.18.0-305.179.1.el8_4 |
| Red Hat:rhel_aus:8.4::baseos | kernel-debug-devel | before 0:4.18.0-305.179.1.el8_4 | 0:4.18.0-305.179.1.el8_4 |
| Red Hat:rhel_aus:8.4::baseos | kernel-debug-modules | before 0:4.18.0-305.179.1.el8_4 | 0:4.18.0-305.179.1.el8_4 |
| Red Hat:rhel_aus:8.4::baseos | kernel-debug-modules-extra | before 0:4.18.0-305.179.1.el8_4 | 0:4.18.0-305.179.1.el8_4 |
| Red Hat:rhel_aus:8.4::baseos | kernel-debuginfo | before 0:4.18.0-305.179.1.el8_4 | 0:4.18.0-305.179.1.el8_4 |
| Red Hat:rhel_aus:8.4::baseos | kernel-debuginfo-common-x86_64 | before 0:4.18.0-305.179.1.el8_4 | 0:4.18.0-305.179.1.el8_4 |
| Red Hat:rhel_aus:8.4::baseos | kernel-devel | before 0:4.18.0-305.179.1.el8_4 | 0:4.18.0-305.179.1.el8_4 |
| Red Hat:rhel_aus:8.4::baseos | kernel-doc | before 0:4.18.0-305.179.1.el8_4 | 0:4.18.0-305.179.1.el8_4 |
| Red Hat:rhel_aus:8.4::baseos | kernel-modules | before 0:4.18.0-305.179.1.el8_4 | 0:4.18.0-305.179.1.el8_4 |
| Red Hat:rhel_aus:8.4::baseos | kernel-modules-extra | before 0:4.18.0-305.179.1.el8_4 | 0:4.18.0-305.179.1.el8_4 |
| Red Hat:rhel_aus:8.4::baseos | kernel-tools | before 0:4.18.0-305.179.1.el8_4 | 0:4.18.0-305.179.1.el8_4 |
| Red Hat:rhel_aus:8.4::baseos | kernel-tools-debuginfo | before 0:4.18.0-305.179.1.el8_4 | 0:4.18.0-305.179.1.el8_4 |
| Red Hat:rhel_aus:8.4::baseos | kernel-tools-libs | before 0:4.18.0-305.179.1.el8_4 | 0:4.18.0-305.179.1.el8_4 |
| Red Hat:rhel_aus:8.4::baseos | perf | before 0:4.18.0-305.179.1.el8_4 | 0:4.18.0-305.179.1.el8_4 |
| Red Hat:rhel_aus:8.4::baseos | perf-debuginfo | before 0:4.18.0-305.179.1.el8_4 | 0:4.18.0-305.179.1.el8_4 |
| Red Hat:rhel_aus:8.4::baseos | python3-perf | before 0:4.18.0-305.179.1.el8_4 | 0:4.18.0-305.179.1.el8_4 |
+85
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-2022-50068Jun 18, 2025 · drm/ttm: Fix dummy res NULL ptr deref bug22Monitor
- ← EarlierCVE-2022-50069Jun 18, 2025 · BPF: Fix potential bad pointer dereference in bpf_sys_bpf()22Monitor
- Later →CVE-2022-50072Jun 18, 2025 · NFSv4/pnfs: Fix a use-after-free bug in open31Monitor
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 | 8caf5c15b5288d52d9c89374d6c10fa32ee84ec5 | Vendor (CNA) |
| Linux Linux | c886d70286bf3ad411eb3d689328a67f7102c6ae | Vendor (CNA) |
| Linux Linux | fb9c73ef2ac2ec816efdc8b9267bc04e1369c20b | Vendor (CNA) |
| debian:linux | 5.19.6-1 · Debian:12 | Package registry (OSV) |
| red hat:bpftool | 0:4.18.0-372.166.1.el8_6 · Red Hat:rhel_aus:8.6::baseos | Package registry (OSV) |
| red hat:bpftool-debuginfo | 0:4.18.0-372.166.1.el8_6 · Red Hat:rhel_aus:8.6::baseos | Package registry (OSV) |
| red hat:kernel | 0:4.18.0-372.166.1.el8_6 · Red Hat:rhel_aus:8.6::baseos | Package registry (OSV) |
| red hat:kernel-abi-stablelists | 0:4.18.0-372.166.1.el8_6 · Red Hat:rhel_aus:8.6::baseos | Package registry (OSV) |
| red hat:kernel-core | 0:4.18.0-372.166.1.el8_6 · Red Hat:rhel_aus:8.6::baseos | Package registry (OSV) |
| red hat:kernel-debug | 0:4.18.0-372.166.1.el8_6 · Red Hat:rhel_aus:8.6::baseos | Package registry (OSV) |
| red hat:kernel-debug-core | 0:4.18.0-372.166.1.el8_6 · Red Hat:rhel_aus:8.6::baseos | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:4.18.0-372.166.1.el8_6 · Red Hat:rhel_aus:8.6::baseos | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:4.18.0-372.166.1.el8_6 · Red Hat:rhel_aus:8.6::baseos | Package registry (OSV) |
| red hat:kernel-debug-modules | 0:4.18.0-372.166.1.el8_6 · Red Hat:rhel_aus:8.6::baseos | Package registry (OSV) |
| red hat:kernel-debug-modules-extra | 0:4.18.0-372.166.1.el8_6 · Red Hat:rhel_aus:8.6::baseos | Package registry (OSV) |
| red hat:kernel-debuginfo | 0:4.18.0-372.166.1.el8_6 · Red Hat:rhel_aus:8.6::baseos | Package registry (OSV) |
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.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
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
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.