Skip to content
Threat Brief

← All advisories

CVE-2026-99350

Severity unknownNo known exploitationFix available

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

Record last updated

CVSS score

None

No score published yet

EPSS, chance of exploitation in 30 days

0.2%

Higher than 10% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

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

VendorProductAffected versionsFixed inPer
LinuxLinuxfrom 5.10.140 before 5.115.11CVE Program
LinuxLinuxfrom 5.15.64 before 5.165.16CVE Program
LinuxLinuxfrom 5.19.6 before 5.205.20CVE Program
LinuxLinuxfrom b0f571ecd7943423c25947439045f0d352ca3dbf before 7801c42c3bb737cfb06194a383873fcad8daacf57801c42c3bb737cfb06194a383873fcad8daacf5CVE Program
LinuxLinuxfrom b0f571ecd7943423c25947439045f0d352ca3dbf before 35f7a69391ca0819d04ca6db3c2355848d633e1635f7a69391ca0819d04ca6db3c2355848d633e16CVE Program
LinuxLinuxfrom b0f571ecd7943423c25947439045f0d352ca3dbf before 965456110cf6952cc4eec80761171503e6e424df965456110cf6952cc4eec80761171503e6e424dfCVE Program
LinuxLinuxfrom b0f571ecd7943423c25947439045f0d352ca3dbf before ec98e8bdbde85e2dd2d43570e25b52bdfac1735bec98e8bdbde85e2dd2d43570e25b52bdfac1735bCVE Program
LinuxLinux091dc91e119fdd61432347231724f4e861c6b465Not documentedCVE Program
LinuxLinux2bc769b8edb158be7379d15f36e23d66cf850053Not documentedCVE Program
LinuxLinux6.0Not documentedCVE Program
LinuxLinux79e2ca7aa96e80961828ab6312264633b66183ccNot documentedCVE Program
LinuxLinux (unaffected)from 6.12.118 up to and including 6.12.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.18.61 up to and including 6.18.*Not documentedCVE Program
LinuxLinux (unaffected)from 7.3.2 up to and including 7.3.*Not documentedCVE Program
LinuxLinux (unaffected)7.4-rc1Not documentedCVE Program
LinuxLinux (unaffected)all versions before 6.0Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by Linux

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (Linux)

    Source: CVE record (Linux) (opens in a new tab)

Vendor guidance and references