CVE-2026-99350: rxrpc: Fix update of call->tx_pending without holding lock

Published Nov 19, 2026
·
Updated

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

6 affected componentsFixes available
linux/kernel>=5.10.140<5.11
5.11
linux/kernel>=5.15.64<5.16
5.16
linux/kernel>=5.19.6<5.20
5.20
linux/kernel>=6.0.0<6.12.118
6.12.118
linux/kernel>=6.13.0<6.18.61
6.18.61
linux/kernel>=6.19.0<7.3.2
7.3.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 5.11
  2. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 5.16
  3. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 5.20
  4. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.12.118
  5. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.18.61
  6. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 7.3.2

Event History

Nov 19, 2026
CVE Published
via MITRE·02:22 PM
Data Sourced
via MITRE·02:22 PM
Description
Data Sourced
via OSV·02:22 PM
DescriptionAffected Software
Data Sourced
via NVD·03:17 PM
Description

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203