Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2021-47370: mptcp: ensure tx skbs always have the MPTCP ext

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.20% (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 5.14.9, 977d293e23b48a1129830d7968605f61c4af71a0, f8ff625a8082db8c2b58dcb5229b27928943b94b.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 5.14.9, 977d293e23b48a1129830d7968605f61c4af71a0, f8ff625a8082db8c2b58dcb5229b27928943b94b 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: ensure tx skbs always have the MPTCP ext Due to signed/unsigned comparison, the expression: info->size_goal - skb->len > 0 evaluates to true when the size goal is smaller than the skb size. That results in lack of tx cache refill, so that the skb allocated by the core TCP code lacks the required MPTCP skb extensions. Due to the above, syzbot is able to trigger the following WARN_ON(): WARNING: CPU: 1 PID: 810 at net/mptcp/protocol.c:1366 mptcp_sendmsg_frag+0x1362/0x1bc0 net/mptcp/protocol.c:1366 Modules linked in: CPU: 1 PID: 810 Comm: syz-executor.4 Not tainted 5.14.0-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 RIP: 0010:mptcp_sendmsg_frag+0x1362/0x1bc0 net/mptcp/protocol.c:1366 Code: ff 4c 8b 74 24 50 48 8b 5c 24 58 e9 0f fb ff ff e8 13 44 8b f8 4c 89 e7 45 31 ed e8 98 57 2e fe e9 81 f4 ff ff e8 fe 43 8b f8 <0f> 0b 41 bd ea ff ff ff e9 6f f4 ff ff 4c 89 e7 e8 b9 8e d2 f8 e9 RSP: 0018:ffffc9000531f6a0 EFLAGS: 00010216 RAX: 000000000000697f RBX: 0000000000000000 RCX: ffffc90012107000 RDX: 0000000000040000 RSI: ffffffff88eac9e2 RDI: 0000000000000003 RBP: ffff888078b15780 R08: 0000000000000000 R09: 0000000000000000 R10: ffffffff88eac017 R11: 0000000000000000 R12: ffff88801de0a280 R13: 0000000000006b58 R14: ffff888066278280 R15: ffff88803c2fe9c0 FS: 00007fd9f866e700(0000) GS:ffff8880b9d00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007faebcb2f718 CR3: 00000000267cb000 CR4: 00000000001506e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: __mptcp_push_pending+0x1fb/0x6b0 net/mptcp/protocol.c:1547 mptcp_release_cb+0xfe/0x210 net/mptcp/protocol.c:3003 release_sock+0xb4/0x1b0 net/core/sock.c:3206 sk_stream_wait_memory+0x604/0xed0 net/core/stream.c:145 mptcp_sendmsg+0xc39/0x1bc0 net/mptcp/protocol.c:1749 inet6_sendmsg+0x99/0xe0 net/ipv6/af_inet6.c:643 sock_sendmsg_nosec net/socket.c:704 [inline] sock_sendmsg+0xcf/0x120 net/socket.c:724 sock_write_iter+0x2a0/0x3e0 net/socket.c:1057 call_write_iter include/linux/fs.h:2163 [inline] new_sync_write+0x40b/0x640 fs/read_write.c:507 vfs_write+0x7cf/0xae0 fs/read_write.c:594 ksys_write+0x1ee/0x250 fs/read_write.c:647 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x4665f9 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 bc ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007fd9f866e188 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 RAX: ffffffffffffffda RBX: 000000000056c038 RCX: 00000000004665f9 RDX: 00000000000e7b78 RSI: 0000000020000000 RDI: 0000000000000003 RBP: 00000000004bfcc4 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 000000000056c038 R13: 0000000000a9fb1f R14: 00007fd9f866e300 R15: 0000000000022000 Fix the issue rewriting the relevant expression to avoid sign-related problems - note: size_goal is always >= 0. Additionally, ensure that the skb in the tx cache always carries the relevant extension.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
May 21, 2024
Updated
Jun 17, 2026
EPSS
0.2% · 10th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

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.

Follow CVE-2021-47370

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

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 help

Affected 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.

VendorProduct
linuxlinux 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.14.7 and later · before 5.14.9

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

    • e35820fb56415be6924bf552ec223ed5f347b4be and later · before f8ff625a8082db8c2b58dcb5229b27928943b94baffected · git
    • 1094c6fe7280e17e0e87934add5ad2585e990def and later · before 977d293e23b48a1129830d7968605f61c4af71a0affected · git
    • 5.14.7 and later · before 5.14.9affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 5.14.9-15.14.9-1
openSUSE:Leap 15.5dtb-aarch64before 5.14.21-150500.55.68.15.14.21-150500.55.68.1
openSUSE:Leap 15.5kernel-64kbbefore 5.14.21-150500.55.68.15.14.21-150500.55.68.1
openSUSE:Leap 15.5kernel-azurebefore 5.14.21-150500.33.57.15.14.21-150500.33.57.1
openSUSE:Leap 15.5kernel-debugbefore 5.14.21-150500.55.68.15.14.21-150500.55.68.1
openSUSE:Leap 15.5kernel-defaultbefore 5.14.21-150500.55.68.15.14.21-150500.55.68.1
openSUSE:Leap 15.5kernel-default-basebefore 5.14.21-150500.55.68.1.150500.6.31.15.14.21-150500.55.68.1.150500.6.31.1
openSUSE:Leap 15.5kernel-docsbefore 5.14.21-150500.55.68.15.14.21-150500.55.68.1
openSUSE:Leap 15.5kernel-kvmsmallbefore 5.14.21-150500.55.68.15.14.21-150500.55.68.1
openSUSE:Leap 15.5kernel-obs-buildbefore 5.14.21-150500.55.68.15.14.21-150500.55.68.1
openSUSE:Leap 15.5kernel-obs-qabefore 5.14.21-150500.55.68.15.14.21-150500.55.68.1
openSUSE:Leap 15.5kernel-rtbefore 5.14.21-150500.13.58.15.14.21-150500.13.58.1
openSUSE:Leap 15.5kernel-rt_debugbefore 5.14.21-150500.13.58.15.14.21-150500.13.58.1
openSUSE:Leap 15.5kernel-sourcebefore 5.14.21-150500.55.68.15.14.21-150500.55.68.1
openSUSE:Leap 15.5kernel-source-azurebefore 5.14.21-150500.33.57.15.14.21-150500.33.57.1
openSUSE:Leap 15.5kernel-source-rtbefore 5.14.21-150500.13.58.15.14.21-150500.13.58.1
openSUSE:Leap 15.5kernel-symsbefore 5.14.21-150500.55.68.15.14.21-150500.55.68.1
openSUSE:Leap 15.5kernel-syms-azurebefore 5.14.21-150500.33.57.15.14.21-150500.33.57.1
openSUSE:Leap 15.5kernel-syms-rtbefore 5.14.21-150500.13.58.15.14.21-150500.13.58.1
openSUSE:Leap 15.5kernel-zfcpdumpbefore 5.14.21-150500.55.68.15.14.21-150500.55.68.1
openSUSE:Leap Micro 5.3kernel-defaultbefore 5.14.21-150400.24.122.25.14.21-150400.24.122.2
openSUSE:Leap Micro 5.3kernel-default-basebefore 5.14.21-150400.24.122.2.150400.24.58.25.14.21-150400.24.122.2.150400.24.58.2
openSUSE:Leap Micro 5.3kernel-rtbefore 5.14.21-150400.15.82.15.14.21-150400.15.82.1
SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOSkernel-64kbbefore 5.14.21-150400.24.122.25.14.21-150400.24.122.2

+27

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • 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 KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2021-47368May 21, 2024 · enetc: Fix illegal access when reading affinity_hint
    28Monitor
  • ← EarlierCVE-2021-47369May 21, 2024 · s390/qeth: fix NULL deref in qeth_clear_working_pool_list()
    22Monitor
  • Later →CVE-2021-47371May 21, 2024 · nexthop: Fix memory leaks in nexthop notification chain listeners
    28Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux5.14.9Vendor (CNA)
Linux Linux977d293e23b48a1129830d7968605f61c4af71a0Vendor (CNA)
Linux Linuxf8ff625a8082db8c2b58dcb5229b27928943b94bVendor (CNA)
debian:linux5.14.9-1 · Debian:12Package registry (OSV)
opensuse:dtb-aarch645.14.21-150500.55.68.1 · openSUSE:Leap 15.5Package registry (OSV)
opensuse:kernel-64kb5.14.21-150500.55.68.1 · openSUSE:Leap 15.5Package registry (OSV)
opensuse:kernel-azure5.14.21-150500.33.57.1 · openSUSE:Leap 15.5Package registry (OSV)
opensuse:kernel-debug5.14.21-150500.55.68.1 · openSUSE:Leap 15.5Package registry (OSV)
opensuse:kernel-default5.14.21-150400.24.122.2 · openSUSE:Leap Micro 5.3Package registry (OSV)
opensuse:kernel-default-base5.14.21-150400.24.122.2.150400.24.58.2 · openSUSE:Leap Micro 5.3Package registry (OSV)
opensuse:kernel-rt5.14.21-150500.13.58.1 · openSUSE:Leap 15.5Package registry (OSV)
opensuse:kernel-rt_debug5.14.21-150500.13.58.1 · openSUSE:Leap 15.5Package registry (OSV)
opensuse:kernel-source-azure5.14.21-150500.33.57.1 · openSUSE:Leap 15.5Package registry (OSV)
opensuse:kernel-source-rt5.14.21-150500.13.58.1 · openSUSE:Leap 15.5Package registry (OSV)
opensuse:kernel-syms-azure5.14.21-150500.33.57.1 · openSUSE:Leap 15.5Package registry (OSV)
opensuse:kernel-syms-rt5.14.21-150500.13.58.1 · openSUSE:Leap 15.5Package registry (OSV)
suse:kernel-64kb5.14.21-150400.24.122.2 · SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOSPackage registry (OSV)
suse:kernel-azure5.14.21-150500.33.57.1 · SUSE:Linux Enterprise Module for Public Cloud 15 SP5Package registry (OSV)
suse:kernel-default5.14.21-150400.24.122.2 · SUSE:Linux Enterprise Micro 5.3Package registry (OSV)
suse:kernel-default-base5.14.21-150400.24.122.2.150400.24.58.2 · SUSE:Linux Enterprise Micro 5.3Package registry (OSV)
suse:kernel-livepatch-SLE15-SP4_Update_271-150400.9.3.2 · SUSE:Linux Enterprise Live Patching 15 SP4Package registry (OSV)
suse:kernel-livepatch-SLE15-SP5-RT_Update_161-150500.11.3.1 · SUSE:Linux Enterprise Live Patching 15 SP5Package registry (OSV)
suse:kernel-rt5.14.21-150500.13.58.1 · SUSE:Linux Enterprise Micro 5.5Package registry (OSV)
suse:kernel-rt_debug5.14.21-150500.13.58.1 · SUSE:Real Time Module 15 SP5Package registry (OSV)
suse:kernel-source-azure5.14.21-150500.33.57.1 · SUSE:Linux Enterprise Module for Public Cloud 15 SP5Package registry (OSV)
suse:kernel-source-rt5.14.21-150500.13.58.1 · SUSE:Linux Enterprise Micro 5.5Package registry (OSV)
suse:kernel-syms-azure5.14.21-150500.33.57.1 · SUSE:Linux Enterprise Module for Public Cloud 15 SP5Package registry (OSV)
suse:kernel-syms-rt5.14.21-150500.13.58.1 · SUSE:Real Time Module 15 SP5Package 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.

Finders, 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).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

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

CVSS vector

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

nvd-primary

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (1 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records