CVE-2026-99350: rxrpc: Fix update of call->tx_pending without holding lock
In the Linux kernel, the following vulnerability has been resolved:
rxrpc: Fix update of call->txpending without holding lock
Currently, rxrpcsenddata() updates call->txpending just before it returns - but it won't be holding the call->usermutex when it does this if a wait was interrupted by a signal. This would allow a parallel sendmsg() to race.
Further, both the callers of rxrpcsenddata() call it with the lock held, and then it returns an indication through the parameter list to say whether it has dropped the lock or not - after which the callers both just drop the lock if it's still held.
Fix this by:
(1) Moving the release of call->usermutex down into rxrpcsenddata() and get rid of the indicator parameter. This makes it easier to see where the lock is held.
(2) After waiting, if the attempt to reacquire the mutex is interrupted, just return directly there rather than going to outunlock
(3) Restricting the txb variable to inside the buffering loop and leaving ->txpending set until we've queued the buffer.
Note that there's a slight change in behaviour in that waitforspace failure now doesn't check for completion because it doesn't hold the call usermutex. The caller, however, should re-issue the send and pick up any error at a second attempt.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 5.11 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 5.16 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 5.20 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.12.118 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.18.61 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.3.2