CVE-2026-46170
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.
Does this matter?
Lower severity and a low EPSS score (0.13%). Track it; it rarely justifies an emergency change on its own.
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".
- CVSS 3.1
- 5.5 MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- EPSS
- 0.13% probability · 3th percentile
- CISA KEV
- Not listed
- Affected
- linux/linux kernel
- Source
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67
References
- https://git.kernel.org/stable/c/1f26487e83e69462540bb1047139472957c913c6
- https://git.kernel.org/stable/c/531c537b8fb620beabccfb1594e8d43cbebbb87aPatch
- https://git.kernel.org/stable/c/5da972efed3dc7599da6e2b5e8d906d1b7b1a728
- https://git.kernel.org/stable/c/6a3af482188f6db4186d1605f64d911d7330abb3Patch
- https://git.kernel.org/stable/c/8143a224785ceaf2b0856e08d4498916f38228fbPatch
- https://git.kernel.org/stable/c/b74ad20198652b6b39a761c277ba65ae82b1e107Patch
- https://git.kernel.org/stable/c/b7b9a461569734d33d3259d58d2507adfac107edPatch
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.