What happened
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".
Affected versions
Linux: 00cfd77b9063dcdf3628a7087faba60de85a9cc8 through before f5555a6d7c472849fdf2b426e3d0a85103118793 (git); 00cfd77b9063dcdf3628a7087faba60de85a9cc8 through before e9ba34301d2e90f63f97c76ad9eb98e5250fe961 (git); 00cfd77b9063dcdf3628a7087faba60de85a9cc8 through before 81d8142148164176385c279c7c1e1d581867423d (git); 00cfd77b9063dcdf3628a7087faba60de85a9cc8 through before 9426265e157dd77ec237c795901ed4dea6d69b5c (git); 00cfd77b9063dcdf3628a7087faba60de85a9cc8 through before b41dd76f3b9735096c21d3e799a2b9fe36498d57 (git); 00cfd77b9063dcdf3628a7087faba60de85a9cc8 through before acd3d3562315c99f3c0db16f0fcc5f0306638982 (git); 00cfd77b9063dcdf3628a7087faba60de85a9cc8 through before 25e37407442b8766ec2cf52fb4e31b5c3d3aeeae (git); 00cfd77b9063dcdf3628a7087faba60de85a9cc8 through before 9634cb35af17019baec21ca648516ce376fa10e6 (git); 5.10 Fixed: See vendor advisory.
Why it matters
Review the vendor advisory and exposure of the affected product to determine operational impact.
Detection & mitigation
- Apply vendor-provided updates or mitigations.
- Review affected product exposure and access logs.
Public PoC references
No public PoC reference has passed the current publication threshold.