CVE-2026-99350
What it is
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.
At a glance
- Fix
- No patch or advisory is linked yet. Look at mitigations or restrict exposure.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: not scored yet.
- Severity: not scored yet.
- Fix: none linked yet, which raises it.
Details
- Published
- Last modified
- Record status
- Received
Affected
- Linux < 35f7a69391ca0819d04ca6db3c2355848d633e16
- Linux < 965456110cf6952cc4eec80761171503e6e424df
- Linux < ec98e8bdbde85e2dd2d43570e25b52bdfac1735b
- Linux < 7801c42c3bb737cfb06194a383873fcad8daacf5
- Linux 79e2ca7aa96e80961828ab6312264633b66183cc
- Linux 2bc769b8edb158be7379d15f36e23d66cf850053
- Linux 091dc91e119fdd61432347231724f4e861c6b465
- Linux < 5.11
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-99350.md and follow it. Check whether this project is affected by CVE-2026-99350. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.