CVE-2026-99350
Severity unknownNo known exploitationFix availablerxrpc: Fix update of call->tx_pending without holding lock
Record last updated
CVSS score
No score published yet
EPSS, chance of exploitation in 30 days
Higher than 10% of scored CVEs. A prediction, not evidence.
CISA remediation deadline
Not in the KEV catalog
Description
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.
Patching and mitigation
- Patch status
- Fix available (source: CVE record (Linux))
- Fix documented (source date)
- Mitigation
- None documented
- Vendor guidance
- No vendor link on record
Affected products
| Vendor | Product | Affected versions | Fixed in | Per |
|---|---|---|---|---|
| Linux | Linux | from 5.10.140 before 5.11 | 5.11 | CVE Program |
| Linux | Linux | from 5.15.64 before 5.16 | 5.16 | CVE Program |
| Linux | Linux | from 5.19.6 before 5.20 | 5.20 | CVE Program |
| Linux | Linux | from b0f571ecd7943423c25947439045f0d352ca3dbf before 7801c42c3bb737cfb06194a383873fcad8daacf5 | 7801c42c3bb737cfb06194a383873fcad8daacf5 | CVE Program |
| Linux | Linux | from b0f571ecd7943423c25947439045f0d352ca3dbf before 35f7a69391ca0819d04ca6db3c2355848d633e16 | 35f7a69391ca0819d04ca6db3c2355848d633e16 | CVE Program |
| Linux | Linux | from b0f571ecd7943423c25947439045f0d352ca3dbf before 965456110cf6952cc4eec80761171503e6e424df | 965456110cf6952cc4eec80761171503e6e424df | CVE Program |
| Linux | Linux | from b0f571ecd7943423c25947439045f0d352ca3dbf before ec98e8bdbde85e2dd2d43570e25b52bdfac1735b | ec98e8bdbde85e2dd2d43570e25b52bdfac1735b | CVE Program |
| Linux | Linux | 091dc91e119fdd61432347231724f4e861c6b465 | Not documented | CVE Program |
| Linux | Linux | 2bc769b8edb158be7379d15f36e23d66cf850053 | Not documented | CVE Program |
| Linux | Linux | 6.0 | Not documented | CVE Program |
| Linux | Linux | 79e2ca7aa96e80961828ab6312264633b66183cc | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 6.12.118 up to and including 6.12.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 6.18.61 up to and including 6.18.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 7.3.2 up to and including 7.3.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | 7.4-rc1 | Not documented | CVE Program |
| Linux | Linux (unaffected) | all versions before 6.0 | Not documented | CVE Program |
Timeline
Disclosure
CVE record published by Linux
Source: CVE Program (opens in a new tab)
Patch
Fix documented by CVE record (Linux)
Vendor guidance and references
- https://git.kernel.org/stable/c/35f7a69391ca0819d04ca6db3c2355848d633e16 (opens in a new tab)
- https://git.kernel.org/stable/c/7801c42c3bb737cfb06194a383873fcad8daacf5 (opens in a new tab)
- https://git.kernel.org/stable/c/965456110cf6952cc4eec80761171503e6e424df (opens in a new tab)
- https://git.kernel.org/stable/c/ec98e8bdbde85e2dd2d43570e25b52bdfac1735b (opens in a new tab)