VulnerabilityPublished 28 May 2026Updated 6 Nov 2026

CVE-2026-46158: Linux kernel · mptcp: pm: ADD_ADDR rtx: always decrease sk refcount

Affects Linux kernelSource CVE Database V5

Compare

Not known to be exploited · fixed in f5555a6d7c472849fdf2b426e3d0a85103118793 : 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 f5555a6d7c472849fdf2b426e3d0a85103118793, e9ba34301d2e90f63f97c76ad9eb98e5250fe961, b41dd76f3b9735096c21d3e799a2b9fe36498d57 +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, < f5555a6d7c472849fdf2b426e3d0a85103118793	Fixed in f5555a6d7c472849fdf2b426e3d0a85103118793
LinuxLinux	Affected ≥ 00cfd77b9063dcdf3628a7087faba60de85a9cc8, < e9ba34301d2e90f63f97c76ad9eb98e5250fe961	Fixed in e9ba34301d2e90f63f97c76ad9eb98e5250fe961
LinuxLinux	Affected ≥ 00cfd77b9063dcdf3628a7087faba60de85a9cc8, < b41dd76f3b9735096c21d3e799a2b9fe36498d57	Fixed in b41dd76f3b9735096c21d3e799a2b9fe36498d57
LinuxLinux	Affected ≥ 00cfd77b9063dcdf3628a7087faba60de85a9cc8, < acd3d3562315c99f3c0db16f0fcc5f0306638982	Fixed in acd3d3562315c99f3c0db16f0fcc5f0306638982
LinuxLinux	Affected ≥ 00cfd77b9063dcdf3628a7087faba60de85a9cc8, < 9426265e157dd77ec237c795901ed4dea6d69b5c	Fixed in 9426265e157dd77ec237c795901ed4dea6d69b5c
LinuxLinux	Affected ≥ 00cfd77b9063dcdf3628a7087faba60de85a9cc8, < 9634cb35af17019baec21ca648516ce376fa10e6	Fixed in 9634cb35af17019baec21ca648516ce376fa10e6

Description

In the Linux kernel, the following vulnerability has been resolved: mptcp: pm: ADD_ADDR rtx: always decrease sk refcount When an ADD_ADDR is retransmitted, the sk is held in sk_reset_timer(). It should then be released in all cases at the end. Some (unlikely) checks were returning directly instead of calling sock_put() to decrease the refcount. Jump to a new 'exit' label to call __sock_put() (which will become sock_put() in the next commit) to fix this potential leak. While at it, drop the '!msk' check which cannot happen because it is never reset, and explicitly mark the remaining one as "unlikely".

References

Community reviews

Loading reviews…