Skip to main content
VulnerabilityPublished

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

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-99350· Medium

Not known to be exploited · fixed in ec98e8bdbde85e2dd2d43570e25b52bdfac1735b : update Linux kernel when convenient.

Data as of 19 Nov 2026, 16:20 UTC

Severity
Medium

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in ec98e8bdbde85e2dd2d43570e25b52bdfac1735b, 965456110cf6952cc4eec80761171503e6e424df, 7801c42c3bb737cfb06194a383873fcad8daacf5 +4

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • >=5.10.140 <5.11
  • >=5.15.64 <5.16
  • >=5.19.6 <5.20
Fixed in
  • ec98e8bdbde85e2dd2d43570e25b52bdfac1735b
  • 965456110cf6952cc4eec80761171503e6e424df
  • 7801c42c3bb737cfb06194a383873fcad8daacf5
  • 35f7a69391ca0819d04ca6db3c2355848d633e16
  • 5.20
  • 5.16
  • 5.11
LinuxLinuxAffected
  • =6.0
Fixed in–

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.

References

Community reviews

Loading reviews…