VulnerabilityPublished 28 May 2026Updated 6 Nov 2026

CVE-2026-46170: Linux kernel · mptcp: pm: ADD_ADDR rtx: free sk if last

Affects Linux kernelSource CVE Database V5

Compare

Not known to be exploited · fixed in b74ad20198652b6b39a761c277ba65ae82b1e107 : update Linux kernel when convenient.

Data as of 6 Nov 2026, 16:34 UTC

Severity

Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none

Exploitation: No evidence of active exploitation and no public proof of concept
Automatable: Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact: Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch

Available – fixed in b74ad20198652b6b39a761c277ba65ae82b1e107, b7b9a461569734d33d3259d58d2507adfac107ed, aa8cabde7e83bf96269ee47427dc9b59e3ed8e60 +5

Exploitation evidence

Disclosed: evidence found.
CVE published 28 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 6 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 00cfd77b9063dcdf3628a7087faba60de85a9cc8, < b74ad20198652b6b39a761c277ba65ae82b1e107	Fixed in b74ad20198652b6b39a761c277ba65ae82b1e107
LinuxLinux	Affected ≥ 00cfd77b9063dcdf3628a7087faba60de85a9cc8, < b7b9a461569734d33d3259d58d2507adfac107ed	Fixed in b7b9a461569734d33d3259d58d2507adfac107ed
LinuxLinux	Affected ≥ 00cfd77b9063dcdf3628a7087faba60de85a9cc8, < aa8cabde7e83bf96269ee47427dc9b59e3ed8e60	Fixed in aa8cabde7e83bf96269ee47427dc9b59e3ed8e60
LinuxLinux	Affected ≥ 00cfd77b9063dcdf3628a7087faba60de85a9cc8, < 8143a224785ceaf2b0856e08d4498916f38228fb	Fixed in 8143a224785ceaf2b0856e08d4498916f38228fb
LinuxLinux	Affected ≥ 00cfd77b9063dcdf3628a7087faba60de85a9cc8, < 531c537b8fb620beabccfb1594e8d43cbebbb87a	Fixed in 531c537b8fb620beabccfb1594e8d43cbebbb87a
LinuxLinux	Affected ≥ 00cfd77b9063dcdf3628a7087faba60de85a9cc8, < 6a3af482188f6db4186d1605f64d911d7330abb3	Fixed in 6a3af482188f6db4186d1605f64d911d7330abb3

Description

In the Linux kernel, the following vulnerability has been resolved: mptcp: pm: ADD_ADDR rtx: free sk if last When an ADD_ADDR is retransmitted, the sk is held in sk_reset_timer(), and released at the end. If at that moment, it was the last reference being held, the sk would not be freed. sock_put() should then be called instead of __sock_put(). But that's not enough: if it is the last reference, sock_put() will call sk_free(), which will end up calling sk_stop_timer_sync() on the same timer, and waiting indefinitely to finish. So it is needed to mark that the timer is done at the end of the timer handler when it has not been rescheduled, not to call sk_stop_timer_sync() on "itself".

References

Community reviews

Loading reviews…