mptcp: pm: ADD_ADDR rtx: always decrease sk refcount
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 00cfd77b9063dcdf3628a7087faba60de85a9cc8 · < acd3d3562315c99f3c0db16f0fcc5f0306638982| No fix yet |
| Linux Linux |
|
|
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".
From the CVE record · Linux
The Linux kernel's MPTCP ADD_ADDR retransmission path can fail to release a socket reference when certain checks return early, potentially leaking references. The input does not describe an attacker action or specify whether exploitation requires network access, authentication, or user interaction.
Engineers running the Linux kernel should check their deployments; affected versions were not provided.