Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-36889: mptcp: ensure snd_nxt is properly initialized on connect

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.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 39ca83ed73db9edcc6d70c0dc7a73085a4725012, 592f69b41766d366dbb8ff4ef5a67c4396527bbe, 99951b62bf20cec9247f633a3bea898338b9e5b4.

Low priority for now. Upgrade to Linux Linux 39ca83ed73db9edcc6d70c0dc7a73085a4725012, 592f69b41766d366dbb8ff4ef5a67c4396527bbe, 99951b62bf20cec9247f633a3bea898338b9e5b4 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 snd_nxt is properly initialized on connect Christoph reported a splat hinting at a corrupted snd_una: WARNING: CPU: 1 PID: 38 at net/mptcp/protocol.c:1005 __mptcp_clean_una+0x4b3/0x620 net/mptcp/protocol.c:1005 Modules linked in: CPU: 1 PID: 38 Comm: kworker/1:1 Not tainted 6.9.0-rc1-gbbeac67456c9 #59 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.11.0-2.el7 04/01/2014 Workqueue: events mptcp_worker RIP: 0010:__mptcp_clean_una+0x4b3/0x620 net/mptcp/protocol.c:1005 Code: be 06 01 00 00 bf 06 01 00 00 e8 a8 12 e7 fe e9 00 fe ff ff e8 8e 1a e7 fe 0f b7 ab 3e 02 00 00 e9 d3 fd ff ff e8 7d 1a e7 fe <0f> 0b 4c 8b bb e0 05 00 00 e9 74 fc ff ff e8 6a 1a e7 fe 0f 0b e9 RSP: 0018:ffffc9000013fd48 EFLAGS: 00010293 RAX: 0000000000000000 RBX: ffff8881029bd280 RCX: ffffffff82382fe4 RDX: ffff8881003cbd00 RSI: ffffffff823833c3 RDI: 0000000000000001 RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000000 R10: 0000000000000000 R11: fefefefefefefeff R12: ffff888138ba8000 R13: 0000000000000106 R14: ffff8881029bd908 R15: ffff888126560000 FS: 0000000000000000(0000) GS:ffff88813bd00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f604a5dae38 CR3: 0000000101dac002 CR4: 0000000000170ef0 Call Trace: <TASK> __mptcp_clean_una_wakeup net/mptcp/protocol.c:1055 [inline] mptcp_clean_una_wakeup net/mptcp/protocol.c:1062 [inline] __mptcp_retrans+0x7f/0x7e0 net/mptcp/protocol.c:2615 mptcp_worker+0x434/0x740 net/mptcp/protocol.c:2767 process_one_work+0x1e0/0x560 kernel/workqueue.c:3254 process_scheduled_works kernel/workqueue.c:3335 [inline] worker_thread+0x3c7/0x640 kernel/workqueue.c:3416 kthread+0x121/0x170 kernel/kthread.c:388 ret_from_fork+0x44/0x50 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:243 </TASK> When fallback to TCP happens early on a client socket, snd_nxt is not yet initialized and any incoming ack will copy such value into snd_una. If the mptcp worker (dumbly) tries mptcp-level re-injection after such ack, that would unconditionally trigger a send buffer cleanup using 'bad' snd_una values. We could easily disable re-injection for fallback sockets, but such dumb behavior already helped catching a few subtle issues and a very low to zero impact in practice. Instead address the issue always initializing snd_nxt (and write_seq, for consistency) at connect time.

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

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-2024-36889

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.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

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
debiandebian linux

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • debian debian linux10.0
  • linux linux kernel5.11 and later · before 5.15.159
  • linux linux kernel5.16 and later · before 6.1.91
  • linux linux kernel5.9 and later · before 5.10.218
  • linux linux kernel6.7 and later · before 6.8.10
  • linux linux kernel6.2 and later · before 6.6.31
  • linux linux kernel6.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

    • 5.9affected
    • 8fd738049ac3d67a937d36577763b47180aae1ad and later · before 99951b62bf20cec9247f633a3bea898338b9e5b4affected · git
    • 8fd738049ac3d67a937d36577763b47180aae1ad and later · before dc941fec0719d0471a5902424d6b2a17df233193affected · git
    • 8fd738049ac3d67a937d36577763b47180aae1ad and later · before 39ca83ed73db9edcc6d70c0dc7a73085a4725012affected · git
    • 8fd738049ac3d67a937d36577763b47180aae1ad and later · before aa0c07c1f20e05b30019bff083ec43665536f06faffected · git
    • 8fd738049ac3d67a937d36577763b47180aae1ad and later · before 592f69b41766d366dbb8ff4ef5a67c4396527bbeaffected · git
    • 8fd738049ac3d67a937d36577763b47180aae1ad and later · before fb7a0d334894206ae35f023a82cad5a290fd7386affected · git
    • before 5.9not affected · semver
    • 5.10.218 and later · up to and including 5.10.*not affected · semver
    • 5.15.159 and later · up to and including 5.15.*not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
AlmaLinux:9bpftoolbefore 7.3.0-427.40.1.el9_47.3.0-427.40.1.el9_4
AlmaLinux:9kernelbefore 5.14.0-427.40.1.el9_45.14.0-427.40.1.el9_4
AlmaLinux:9kernel-64kbefore 5.14.0-427.40.1.el9_45.14.0-427.40.1.el9_4
AlmaLinux:9kernel-64k-corebefore 5.14.0-427.40.1.el9_45.14.0-427.40.1.el9_4
AlmaLinux:9kernel-64k-debugbefore 5.14.0-427.40.1.el9_45.14.0-427.40.1.el9_4
AlmaLinux:9kernel-64k-debug-corebefore 5.14.0-427.40.1.el9_45.14.0-427.40.1.el9_4
AlmaLinux:9kernel-64k-debug-develbefore 5.14.0-427.40.1.el9_45.14.0-427.40.1.el9_4
AlmaLinux:9kernel-64k-debug-devel-matchedbefore 5.14.0-427.40.1.el9_45.14.0-427.40.1.el9_4
AlmaLinux:9kernel-64k-debug-modulesbefore 5.14.0-427.40.1.el9_45.14.0-427.40.1.el9_4
AlmaLinux:9kernel-64k-debug-modules-corebefore 5.14.0-427.40.1.el9_45.14.0-427.40.1.el9_4
AlmaLinux:9kernel-64k-debug-modules-extrabefore 5.14.0-427.40.1.el9_45.14.0-427.40.1.el9_4
AlmaLinux:9kernel-64k-develbefore 5.14.0-427.40.1.el9_45.14.0-427.40.1.el9_4
AlmaLinux:9kernel-64k-devel-matchedbefore 5.14.0-427.40.1.el9_45.14.0-427.40.1.el9_4
AlmaLinux:9kernel-64k-modulesbefore 5.14.0-427.40.1.el9_45.14.0-427.40.1.el9_4
AlmaLinux:9kernel-64k-modules-corebefore 5.14.0-427.40.1.el9_45.14.0-427.40.1.el9_4
AlmaLinux:9kernel-64k-modules-extrabefore 5.14.0-427.40.1.el9_45.14.0-427.40.1.el9_4
AlmaLinux:9kernel-abi-stablelistsbefore 5.14.0-427.40.1.el9_45.14.0-427.40.1.el9_4
AlmaLinux:9kernel-corebefore 5.14.0-427.40.1.el9_45.14.0-427.40.1.el9_4
AlmaLinux:9kernel-cross-headersbefore 5.14.0-427.40.1.el9_45.14.0-427.40.1.el9_4
AlmaLinux:9kernel-debugbefore 5.14.0-427.40.1.el9_45.14.0-427.40.1.el9_4
AlmaLinux:9kernel-debug-corebefore 5.14.0-427.40.1.el9_45.14.0-427.40.1.el9_4
AlmaLinux:9kernel-debug-develbefore 5.14.0-427.40.1.el9_45.14.0-427.40.1.el9_4
AlmaLinux:9kernel-debug-devel-matchedbefore 5.14.0-427.40.1.el9_45.14.0-427.40.1.el9_4
AlmaLinux:9kernel-debug-modulesbefore 5.14.0-427.40.1.el9_45.14.0-427.40.1.el9_4

+96

Same product

linux: all records

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-2024-36887May 30, 2024 · e1000e: change usleep_range to udelay in PHY mdic access
    22Monitor
  • ← EarlierCVE-2024-36888May 30, 2024 · workqueue: Fix selection of wake_cpu in kick_pool()
    24Monitor
  • Later →CVE-2024-36890May 30, 2024 · mm/slab: make __free(kfree) accept error pointers
    22Monitor

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 Linux39ca83ed73db9edcc6d70c0dc7a73085a4725012Vendor (CNA)
Linux Linux592f69b41766d366dbb8ff4ef5a67c4396527bbeVendor (CNA)
Linux Linux99951b62bf20cec9247f633a3bea898338b9e5b4Vendor (CNA)
Linux Linuxaa0c07c1f20e05b30019bff083ec43665536f06fVendor (CNA)
Linux Linuxdc941fec0719d0471a5902424d6b2a17df233193Vendor (CNA)
Linux Linuxfb7a0d334894206ae35f023a82cad5a290fd7386Vendor (CNA)
almalinux:bpftool7.3.0-427.40.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel5.14.0-427.40.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-427.40.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-427.40.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-427.40.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-427.40.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-427.40.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-427.40.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-427.40.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-427.40.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-427.40.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-427.40.1.el9_4 · AlmaLinux:9Package registry (OSV)
debian:linux6.1.94-1 · Debian:12Package registry (OSV)
debian:linux-5.105.10.218-1~deb10u1 · Debian:10Package registry (OSV)
red hat:bpftool0:4.18.0-477.81.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:bpftool-debuginfo0:4.18.0-477.81.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel0:4.18.0-477.81.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel-abi-stablelists0:4.18.0-477.81.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel-core0:4.18.0-477.81.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel-debug0:4.18.0-477.81.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel-debug-core0:4.18.0-477.81.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel-debug-debuginfo0:4.18.0-477.81.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel-debug-devel0:4.18.0-477.81.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel-debug-modules0:4.18.0-477.81.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)

+3

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 researchers

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

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 (6 more)

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

All records