Skip to main content
VulnerabilityPublished Updated

CVE-2025-40258: Linux kernel · mptcp: fix race condition in mptcp_schedule_work()

Source GCVE Database

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Dec 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

AI-suggested

A fix for this vulnerability has been implemented in the Linux kernel source code by correcting the order of reference count increment and work scheduling in mptcp_schedule_work(). Users and administrators should apply the official Linux kernel updates that include this fix. Since this is not a cloud service, remediation depends on deploying patched kernel versions. Patch status is not explicitly confirmed in the provided data; therefore, check the Linux kernel vendor advisory for the latest remediation guidance and apply updates accordingly.

Description

A critical use-after-free vulnerability in the Linux kernel's mptcp_schedule_work() function has been resolved. The issue arises from a race condition where a reference count on a socket can be released prematurely, leading to potential memory corruption. This flaw was reported by syzbot and involves improper ordering of reference count increment and work scheduling. The vulnerability allows for potential complete compromise of confidentiality, integrity, and availability of the affected system.

References

Community reviews

Loading reviews…