mptcp: pm: ADD_ADDR rtx: free sk if last

Answer in brief

CVE-2026-46170 records a Unknown severity vulnerability in mptcp: pm: ADD_ADDR rtx: free sk if last. The current sources do not mark it as known exploited. The current feed maps 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.

Published May 28, 2026Updated Aug 27, 2026Source checked Aug 27, 2026First seen by HOL Aug 27, 2026Material review Aug 27, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. 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.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Linux/Linuxgeneric	>=00cfd77b9063dcdf3628a7087faba60de85a9cc8 <1f26487e83e69462540bb1047139472957c913c6 \|\| >=00cfd77b9063dcdf3628a7087faba60de85a9cc8 <5da972efed3dc7599da6e2b5e8d906d1b7b1a728 \|\| >=00cfd77b9063dcdf3628a7087faba60de85a9cc8 <6a3af482188f6db4186d1605f64d911d7330abb3 \|\| >=00cfd77b9063dcdf3628a7087faba60de85a9cc8 <531c537b8fb620beabccfb1594e8d43cbebbb87a \|\| >=00cfd77b9063dcdf3628a7087faba60de85a9cc8 <b74ad20198652b6b39a761c277ba65ae82b1e107 \|\| >=00cfd77b9063dcdf3628a7087faba60de85a9cc8 <8143a224785ceaf2b0856e08d4498916f38228fb \|\| >=00cfd77b9063dcdf3628a7087faba60de85a9cc8 <b7b9a461569734d33d3259d58d2507adfac107ed	1f26487e83e69462540bb1047139472957c913c6, 5da972efed3dc7599da6e2b5e8d906d1b7b1a728, 6a3af482188f6db4186d1605f64d911d7330abb3, 531c537b8fb620beabccfb1594e8d43cbebbb87a, b74ad20198652b6b39a761c277ba65ae82b1e107, 8143a224785ceaf2b0856e08d4498916f38228fb, b7b9a461569734d33d3259d58d2507adfac107ed
Linux/Linuxgeneric	5.10	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux.
Review the reported fix. Update Linux/Linux to 1f26487e83e69462540bb1047139472957c913c6 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
May 28, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Aug 27, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Aug 27, 2026

Sources and claim methodology

Upstream source 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".

Quoted source text, attributed separately from HOL analysis.