Answer in brief
CVE-2026-46158 records a Medium severity (CVSS 5.5) vulnerability in mptcp: pm: ADD_ADDR rtx: always decrease sk refcount. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:7.1:rc1:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:7.1:rc2:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=00cfd77b9063dcdf3628a7087faba60de85a9cc8 <e9ba34301d2e90f63f97c76ad9eb98e5250fe961 || >=00cfd77b9063dcdf3628a7087faba60de85a9cc8 <81d8142148164176385c279c7c1e1d581867423d || >=00cfd77b9063dcdf3628a7087faba60de85a9cc8 <9426265e157dd77ec237c795901ed4dea6d69b5c || >=00cfd77b9063dcdf3628a7087faba60de85a9cc8 <b41dd76f3b9735096c21d3e799a2b9fe36498d57 || >=00cfd77b9063dcdf3628a7087faba60de85a9cc8 <acd3d3562315c99f3c0db16f0fcc5f0306638982 || >=00cfd77b9063dcdf3628a7087faba60de85a9cc8 <25e37407442b8766ec2cf52fb4e31b5c3d3aeeae || >=00cfd77b9063dcdf3628a7087faba60de85a9cc8 <9634cb35af17019baec21ca648516ce376fa10e6 | e9ba34301d2e90f63f97c76ad9eb98e5250fe961, 81d8142148164176385c279c7c1e1d581867423d, 9426265e157dd77ec237c795901ed4dea6d69b5c, b41dd76f3b9735096c21d3e799a2b9fe36498d57, acd3d3562315c99f3c0db16f0fcc5f0306638982, 25e37407442b8766ec2cf52fb4e31b5c3d3aeeae, 9634cb35af17019baec21ca648516ce376fa10e6 |
| Linux/Linuxgeneric | 5.10 | Not reported |
| Linux/Linuxgeneric | >=00cfd77b9063dcdf3628a7087faba60de85a9cc8 <f5555a6d7c472849fdf2b426e3d0a85103118793 || >=00cfd77b9063dcdf3628a7087faba60de85a9cc8 <e9ba34301d2e90f63f97c76ad9eb98e5250fe961 || >=00cfd77b9063dcdf3628a7087faba60de85a9cc8 <81d8142148164176385c279c7c1e1d581867423d || >=00cfd77b9063dcdf3628a7087faba60de85a9cc8 <9426265e157dd77ec237c795901ed4dea6d69b5c || >=00cfd77b9063dcdf3628a7087faba60de85a9cc8 <b41dd76f3b9735096c21d3e799a2b9fe36498d57 || >=00cfd77b9063dcdf3628a7087faba60de85a9cc8 <acd3d3562315c99f3c0db16f0fcc5f0306638982 || >=00cfd77b9063dcdf3628a7087faba60de85a9cc8 <25e37407442b8766ec2cf52fb4e31b5c3d3aeeae || >=00cfd77b9063dcdf3628a7087faba60de85a9cc8 <9634cb35af17019baec21ca648516ce376fa10e6 | f5555a6d7c472849fdf2b426e3d0a85103118793, e9ba34301d2e90f63f97c76ad9eb98e5250fe961, 81d8142148164176385c279c7c1e1d581867423d, 9426265e157dd77ec237c795901ed4dea6d69b5c, b41dd76f3b9735096c21d3e799a2b9fe36498d57, acd3d3562315c99f3c0db16f0fcc5f0306638982, 25e37407442b8766ec2cf52fb4e31b5c3d3aeeae, 9634cb35af17019baec21ca648516ce376fa10e6 |
Published upstream
May 28, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 14, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 27, 2026
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".
Quoted source text, attributed separately from HOL analysis.