PT-2026-151531

CVE-2026-99350

·

Published

2026-11-19

·

Updated

2026-11-19

Description by

Score
N/A
Not available

No severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.

In the Linux kernel, the following vulnerability has been resolved:
rxrpc: Fix update of call->tx pending without holding lock
Currently, rxrpc send data() updates call->tx pending just before it returns - but it won't be holding the call->user mutex 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 rxrpc send data() 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->user mutex down into rxrpc send data() 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 out unlock
(3) Restricting the txb variable to inside the buffering loop and leaving ->tx pending set until we've queued the buffer.
Note that there's a slight change in behaviour in that wait for space failure now doesn't check for completion because it doesn't hold the call user mutex. The caller, however, should re-issue the send and pick up any error at a second attempt.
Vendors
Affected products
Related identifiers
Found an issue in the description? Have something to add? Feel free to write us 👾