# CVE-2026-68334: rxrpc: fix io_thread race in rxrpc_wake_up_io_thread()

> A race condition in the Linux kernel's rxrpc module can cause a null pointer dereference, leading to a denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** BELL-CVE-2026-68334, DEBIAN-CVE-2026-68334, GHSA-f247-6x59-q3cw, UBUNTU-CVE-2026-68334

## What is CVE-2026-68334?

CVE-2026-68334 is a vulnerability in Linux, published on 10 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2026-68334?


## How do I fix CVE-2026-68334?

Apply the vendor's patch.

## Is CVE-2026-68334 being exploited?

There is no known exploitation of CVE-2026-68334 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-68334 and fix it if it is affected.

What it is: CVE-2026-68334 is a vulnerability in Linux, published on 10 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-68334 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-68334/ (Markdown: https://insights.sbomify.com/CVE-2026-68334/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-68334
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-68334
- OSV: https://osv.dev/vulnerability/CVE-2026-68334

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-68334/
Summaries are generated and may contain mistakes; the official description above is the record.