Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-40931: mptcp: ensure snd_una 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.25% (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 208cd22ef5e57f82d38ec11c1a1703f9401d6dde, 7b9c7fc8600b64a86e4b47b2d190bba380267726, 8031b58c3a9b1db3ef68b3bd749fbee2e1e1aaa3.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 208cd22ef5e57f82d38ec11c1a1703f9401d6dde, 7b9c7fc8600b64a86e4b47b2d190bba380267726, 8031b58c3a9b1db3ef68b3bd749fbee2e1e1aaa3 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_una is properly initialized on connect This is strictly related to commit fb7a0d334894 ("mptcp: ensure snd_nxt is properly initialized on connect"). It turns out that syzkaller can trigger the retransmit after fallback and before processing any other incoming packet - so that snd_una is still left uninitialized. Address the issue explicitly initializing snd_una together with snd_nxt and write_seq.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Jul 12, 2024
Updated
Jun 17, 2026
EPSS
0.2% · 16th 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-2024-40931

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

Affected versions

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

  • linux linux kernel5.9 and later · before 5.10.221
  • linux linux kernel5.11 and later · before 5.15.162
  • linux linux kernel5.16 and later · before 6.1.95
  • linux linux kernel6.2 and later · before 6.6.35
  • linux linux kernel6.7 and later · before 6.9.6
  • linux linux kernel6.10

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 208cd22ef5e57f82d38ec11c1a1703f9401d6ddeaffected · git
    • 8fd738049ac3d67a937d36577763b47180aae1ad and later · before 7b9c7fc8600b64a86e4b47b2d190bba380267726affected · git
    • 8fd738049ac3d67a937d36577763b47180aae1ad and later · before f03c46eabb3a67bd2993e237ab5517f00a5f1813affected · git
    • 8fd738049ac3d67a937d36577763b47180aae1ad and later · before f1f0a46f8bb8890b90ab7194f0a0c8fe2a3fb57faffected · git
    • 8fd738049ac3d67a937d36577763b47180aae1ad and later · before ef473bf1dd7e8dd08bcc04b9e2d1bfed69a0a7ceaffected · git
    • 8fd738049ac3d67a937d36577763b47180aae1ad and later · before 8031b58c3a9b1db3ef68b3bd749fbee2e1e1aaa3affected · git
    • before 5.9not affected · semver
    • 5.10.221 and later · up to and including 5.10.*not affected · semver
    • 5.15.162 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.42.1.el9_47.3.0-427.42.1.el9_4
AlmaLinux:9kernelbefore 5.14.0-427.42.1.el9_45.14.0-427.42.1.el9_4
AlmaLinux:9kernel-64kbefore 5.14.0-427.42.1.el9_45.14.0-427.42.1.el9_4
AlmaLinux:9kernel-64k-corebefore 5.14.0-427.42.1.el9_45.14.0-427.42.1.el9_4
AlmaLinux:9kernel-64k-debugbefore 5.14.0-427.42.1.el9_45.14.0-427.42.1.el9_4
AlmaLinux:9kernel-64k-debug-corebefore 5.14.0-427.42.1.el9_45.14.0-427.42.1.el9_4
AlmaLinux:9kernel-64k-debug-develbefore 5.14.0-427.42.1.el9_45.14.0-427.42.1.el9_4
AlmaLinux:9kernel-64k-debug-devel-matchedbefore 5.14.0-427.42.1.el9_45.14.0-427.42.1.el9_4
AlmaLinux:9kernel-64k-debug-modulesbefore 5.14.0-427.42.1.el9_45.14.0-427.42.1.el9_4
AlmaLinux:9kernel-64k-debug-modules-corebefore 5.14.0-427.42.1.el9_45.14.0-427.42.1.el9_4
AlmaLinux:9kernel-64k-debug-modules-extrabefore 5.14.0-427.42.1.el9_45.14.0-427.42.1.el9_4
AlmaLinux:9kernel-64k-develbefore 5.14.0-427.42.1.el9_45.14.0-427.42.1.el9_4
AlmaLinux:9kernel-64k-devel-matchedbefore 5.14.0-427.42.1.el9_45.14.0-427.42.1.el9_4
AlmaLinux:9kernel-64k-modulesbefore 5.14.0-427.42.1.el9_45.14.0-427.42.1.el9_4
AlmaLinux:9kernel-64k-modules-corebefore 5.14.0-427.42.1.el9_45.14.0-427.42.1.el9_4
AlmaLinux:9kernel-64k-modules-extrabefore 5.14.0-427.42.1.el9_45.14.0-427.42.1.el9_4
AlmaLinux:9kernel-abi-stablelistsbefore 5.14.0-427.42.1.el9_45.14.0-427.42.1.el9_4
AlmaLinux:9kernel-corebefore 5.14.0-427.42.1.el9_45.14.0-427.42.1.el9_4
AlmaLinux:9kernel-cross-headersbefore 5.14.0-427.42.1.el9_45.14.0-427.42.1.el9_4
AlmaLinux:9kernel-debugbefore 5.14.0-427.42.1.el9_45.14.0-427.42.1.el9_4
AlmaLinux:9kernel-debug-corebefore 5.14.0-427.42.1.el9_45.14.0-427.42.1.el9_4
AlmaLinux:9kernel-debug-develbefore 5.14.0-427.42.1.el9_45.14.0-427.42.1.el9_4
AlmaLinux:9kernel-debug-devel-matchedbefore 5.14.0-427.42.1.el9_45.14.0-427.42.1.el9_4
AlmaLinux:9kernel-debug-modulesbefore 5.14.0-427.42.1.el9_45.14.0-427.42.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-40929Jul 12, 2024 · wifi: iwlwifi: mvm: check n_ssids before accessing the ssids
    28Monitor
  • ← EarlierCVE-2024-40930Jul 12, 2024 · wifi: cfg80211: validate HE operation element parsing
    22Monitor
  • Later →CVE-2024-40932Jul 12, 2024 · drm/exynos/vidi: fix memory leak in .get_modes()
    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 Linux208cd22ef5e57f82d38ec11c1a1703f9401d6ddeVendor (CNA)
Linux Linux7b9c7fc8600b64a86e4b47b2d190bba380267726Vendor (CNA)
Linux Linux8031b58c3a9b1db3ef68b3bd749fbee2e1e1aaa3Vendor (CNA)
Linux Linuxef473bf1dd7e8dd08bcc04b9e2d1bfed69a0a7ceVendor (CNA)
Linux Linuxf03c46eabb3a67bd2993e237ab5517f00a5f1813Vendor (CNA)
Linux Linuxf1f0a46f8bb8890b90ab7194f0a0c8fe2a3fb57fVendor (CNA)
almalinux:bpftool7.3.0-427.42.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel5.14.0-427.42.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-427.42.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-427.42.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-427.42.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-427.42.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-427.42.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-427.42.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-427.42.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-427.42.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-427.42.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-427.42.1.el9_4 · AlmaLinux:9Package registry (OSV)
debian:linux6.1.99-1 · Debian:12Package registry (OSV)
red hat:bpftool-debuginfo0:7.3.0-427.42.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-427.42.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-427.42.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-427.42.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-427.42.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-427.42.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-427.42.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-427.42.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-427.42.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-427.42.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo0:5.14.0-427.42.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)

+2

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.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

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.

  • CVE-2024-50302130 days apartHID: core: zero-initialize the report bufferKEV
    52Plan
  • CVE-2024-47685101 days apartnetfilter: nf_reject_ipv6: fix nf_reject_ip6_tcphdr_put()
    36Monitor
  • CVE-2024-3689843 days apartgpiolib: cdev: fix uninitialised kfifo
    31Monitor
  • CVE-2021-4755349 days apartsched/scs: Reset task stack state in bringup_cpu()
    31Monitor
  • CVE-2024-2702272 days apartfork: defer linking file vma until vma is fully initialized
    31Monitor
  • CVE-2024-50143118 days apartudf: fix uninit-value use in udf_get_fileshortad
    31Monitor

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

Weakness class (CWE)

CWE-908 · Use of Uninitialized Resource

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