Skip to main content
Menu
CVEs

Linux kernel race condition in rxrpc transmit path

CVE-2026-99350Published November 19, 2026, updated

Exploited
No known exploitation
Fix
Fixed in 5.11, 5.16, 5.20
Who is exposed
Not reported

Summary

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.

What to do

Upgrade to a fixed version: 5.11, 5.16, 5.20.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-99350 (rxrpc: Fix update of call->tx_pending without holding lock), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-99350 (entry last updated 2026-11-19):
Affected:
- Linux Linux: from 5.10.140, fixed in 5.11; from 5.15.64, fixed in 5.16; from 5.19.6, fixed in 5.20
- Linux Linux: versions 6.0
Fixed versions: 5.11, 5.16, 5.20.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-99350 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-99350 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://git.kernel.org/stable/c/35f7a69391ca0819d04ca6db3c2355848d633e16
- https://git.kernel.org/stable/c/965456110cf6952cc4eec80761171503e6e424df
- https://git.kernel.org/stable/c/ec98e8bdbde85e2dd2d43570e25b52bdfac1735b
- https://git.kernel.org/stable/c/7801c42c3bb737cfb06194a383873fcad8daacf5
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-99350
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-99350"}.

Affected versions

cve.now Index

20Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure?/25Unknown. No advisory context yet
  • Reach20/20Affects Linux kernel (software on nearly every server, desktop or phone)
  • Severity?/10Unknown. No CVSS score or vendor rating
  • No patch0/5No signal

What would change the score

  • Would score about 75 if added to CISA KEV
  • Would score about 70 if CISA's SSVC rates exploitation active
  • Would score about 42 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Record last updated

Evidence 6

Questions about CVE-2026-99350

Is CVE-2026-99350 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-99350?

Linux: from 5.10.140 before 5.11; from 5.15.64 before 5.16; from 5.19.6 before 5.20. Linux: version 6.0.

Source: cve.now feed data

How do I fix CVE-2026-99350?

Upgrade to a fixed version: 5.11, 5.16, 5.20.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.