Skip to content
Noroxi
CVE-2025-40258· NVD / CVE Program· CNA Linux

mptcp: fix race condition in mptcp_schedule_work()

Noroxi assessment

Priority: Monitor (action score 39/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.46% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 035bca3f017ee9dea3a5a756e77a6f7138cc6eea, 3fc7723ed01d1130d4bf7063c50e0af60ecccbb4, 8f9ba1a99a89feef9b5867c15a0141a97e893309.

Low priority for now. Upgrade to Linux Linux 035bca3f017ee9dea3a5a756e77a6f7138cc6eea, 3fc7723ed01d1130d4bf7063c50e0af60ecccbb4, 8f9ba1a99a89feef9b5867c15a0141a97e893309 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 race condition in mptcp_schedule_work() syzbot reported use-after-free in mptcp_schedule_work() [1] Issue here is that mptcp_schedule_work() schedules a work, then gets a refcount on sk->sk_refcnt if the work was scheduled. This refcount will be released by mptcp_worker(). [A] if (schedule_work(...)) { [B] sock_hold(sk); return true; } Problem is that mptcp_worker() can run immediately and complete before [B] We need instead : sock_hold(sk); if (schedule_work(...)) return true; sock_put(sk); [1] refcount_t: addition on 0; use-after-free. WARNING: CPU: 1 PID: 29 at lib/refcount.c:25 refcount_warn_saturate+0xfa/0x1d0 lib/refcount.c:25 Call Trace: <TASK> __refcount_add include/linux/refcount.h:-1 [inline] __refcount_inc include/linux/refcount.h:366 [inline] refcount_inc include/linux/refcount.h:383 [inline] sock_hold include/net/sock.h:816 [inline] mptcp_schedule_work+0x164/0x1a0 net/mptcp/protocol.c:943 mptcp_tout_timer+0x21/0xa0 net/mptcp/protocol.c:2316 call_timer_fn+0x17e/0x5f0 kernel/time/timer.c:1747 expire_timers kernel/time/timer.c:1798 [inline] __run_timers kernel/time/timer.c:2372 [inline] __run_timer_base+0x648/0x970 kernel/time/timer.c:2384 run_timer_base kernel/time/timer.c:2393 [inline] run_timer_softirq+0xb7/0x180 kernel/time/timer.c:2403 handle_softirqs+0x22f/0x710 kernel/softirq.c:622 __do_softirq kernel/softirq.c:656 [inline] run_ktimerd+0xcf/0x190 kernel/softirq.c:1138 smpboot_thread_fn+0x542/0xa60 kernel/smpboot.c:160 kthread+0x711/0x8a0 kernel/kthread.c:463 ret_from_fork+0x4bc/0x870 arch/x86/kernel/process.c:158 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245

CriticalCVSS 9.8 · v3.1—No exploit Fix available
Published
Dec 4, 2025
Updated
Oct 19, 2026
EPSS
0.4% · 39th percentile
CWE
—

Report tools

JSON

Action score

39

Monitor

Low priority for now.

CVSS
39 / 40 · 9.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.4%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Linux
9.8
NVD has not scored this yet; the score shown is the CNA’s.

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.

Follow CVE-2025-40258

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.

—

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.7affected
    • 3b1d6210a9577369103330b0d802b0bf74b65e7f and later · before f865e6595acf33083168db76921e66ace8bf0e5baffected · git
    • 3b1d6210a9577369103330b0d802b0bf74b65e7f and later · before 99908e2d601236842d705d5fd04fb349577316f5affected · git
    • 3b1d6210a9577369103330b0d802b0bf74b65e7f and later · before db4f7968a75250ca6c4ed70d0a78beabb2dcee18affected · git
    • 3b1d6210a9577369103330b0d802b0bf74b65e7f and later · before 8f9ba1a99a89feef9b5867c15a0141a97e893309affected · git
    • 3b1d6210a9577369103330b0d802b0bf74b65e7f and later · before ac28dfddedf6f209190950fc71bcff65ec4ab47baffected · git
    • 3b1d6210a9577369103330b0d802b0bf74b65e7f and later · before 3fc7723ed01d1130d4bf7063c50e0af60ecccbb4affected · git
    • 3b1d6210a9577369103330b0d802b0bf74b65e7f and later · before 035bca3f017ee9dea3a5a756e77a6f7138cc6eeaaffected · git
    • before 5.7not affected · semver
    • 5.10.247 and later · up to and including 5.10.*not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-124.31.1.el10_16.12.0-124.31.1.el10_1
AlmaLinux:10kernel-docbefore 6.12.0-124.31.1.el10_16.12.0-124.31.1.el10_1
AlmaLinux:8bpftoolbefore 4.18.0-553.100.1.el8_104.18.0-553.100.1.el8_10
AlmaLinux:8kernelbefore 4.18.0-553.100.1.el8_104.18.0-553.100.1.el8_10
AlmaLinux:8kernel-abi-stablelistsbefore 4.18.0-553.100.1.el8_104.18.0-553.100.1.el8_10
AlmaLinux:8kernel-corebefore 4.18.0-553.100.1.el8_104.18.0-553.100.1.el8_10
AlmaLinux:8kernel-cross-headersbefore 4.18.0-553.100.1.el8_104.18.0-553.100.1.el8_10
AlmaLinux:8kernel-debugbefore 4.18.0-553.100.1.el8_104.18.0-553.100.1.el8_10
AlmaLinux:8kernel-debug-corebefore 4.18.0-553.100.1.el8_104.18.0-553.100.1.el8_10
AlmaLinux:8kernel-debug-develbefore 4.18.0-553.100.1.el8_104.18.0-553.100.1.el8_10
AlmaLinux:8kernel-debug-modulesbefore 4.18.0-553.100.1.el8_104.18.0-553.100.1.el8_10
AlmaLinux:8kernel-debug-modules-extrabefore 4.18.0-553.100.1.el8_104.18.0-553.100.1.el8_10
AlmaLinux:8kernel-develbefore 4.18.0-553.100.1.el8_104.18.0-553.100.1.el8_10
AlmaLinux:8kernel-docbefore 4.18.0-553.100.1.el8_104.18.0-553.100.1.el8_10
AlmaLinux:8kernel-headersbefore 4.18.0-553.100.1.el8_104.18.0-553.100.1.el8_10
AlmaLinux:8kernel-modulesbefore 4.18.0-553.100.1.el8_104.18.0-553.100.1.el8_10
AlmaLinux:8kernel-modules-extrabefore 4.18.0-553.100.1.el8_104.18.0-553.100.1.el8_10
AlmaLinux:8kernel-rtbefore 4.18.0-553.100.1.rt7.441.el8_104.18.0-553.100.1.rt7.441.el8_10
AlmaLinux:8kernel-rt-corebefore 4.18.0-553.100.1.rt7.441.el8_104.18.0-553.100.1.rt7.441.el8_10
AlmaLinux:8kernel-rt-debugbefore 4.18.0-553.100.1.rt7.441.el8_104.18.0-553.100.1.rt7.441.el8_10
AlmaLinux:8kernel-rt-debug-corebefore 4.18.0-553.100.1.rt7.441.el8_104.18.0-553.100.1.rt7.441.el8_10
AlmaLinux:8kernel-rt-debug-develbefore 4.18.0-553.100.1.rt7.441.el8_104.18.0-553.100.1.rt7.441.el8_10
AlmaLinux:8kernel-rt-debug-modulesbefore 4.18.0-553.100.1.rt7.441.el8_104.18.0-553.100.1.rt7.441.el8_10
AlmaLinux:8kernel-rt-debug-modules-extrabefore 4.18.0-553.100.1.rt7.441.el8_104.18.0-553.100.1.rt7.441.el8_10

+96

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2025-40256Dec 4, 2025 · xfrm: also call xfrm_state_delete_tunnel at destroy time for states that were never added
    0Monitor
  • ← EarlierCVE-2025-40257Dec 4, 2025 · mptcp: fix a race in mptcp_pm_del_add_timer()
    39Monitor
  • Later →CVE-2025-40259Dec 4, 2025 · scsi: sg: Do not sleep in atomic context
    0Monitor

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 Linux035bca3f017ee9dea3a5a756e77a6f7138cc6eeaVendor (CNA)
Linux Linux3fc7723ed01d1130d4bf7063c50e0af60ecccbb4Vendor (CNA)
Linux Linux8f9ba1a99a89feef9b5867c15a0141a97e893309Vendor (CNA)
Linux Linux99908e2d601236842d705d5fd04fb349577316f5Vendor (CNA)
Linux Linuxac28dfddedf6f209190950fc71bcff65ec4ab47bVendor (CNA)
Linux Linuxdb4f7968a75250ca6c4ed70d0a78beabb2dcee18Vendor (CNA)
Linux Linuxf865e6595acf33083168db76921e66ace8bf0e5bVendor (CNA)
almalinux:kernel5.14.0-611.26.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-611.26.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-611.26.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-611.26.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-611.26.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-611.26.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-611.26.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-611.26.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-611.26.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-611.26.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-611.26.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel-matched5.14.0-611.26.1.el9_7 · AlmaLinux:9Package registry (OSV)
debian:linux6.1.159-1 · Debian:12Package registry (OSV)
debian:linux-6.16.1.159-1~deb11u1 · Debian:11Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-611.26.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-611.26.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-611.26.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-611.26.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-611.26.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-611.26.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-611.26.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-611.26.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-611.26.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)

+17

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.

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

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • 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
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

—

CVSS vector

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

nvd-secondary

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

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

All records