Skip to content
VulniPulse
Medium5.9Red Hat Linux

Medium [CVE-2026-68334] Linux kernel: `rxrpc` race condition causes Denial of Service

This medium-severity Red Hat Linux advisory covers CVE-2026-68334.

CVE-2026-68334 Published Aug 10, 2026Updated by vendor Aug 10, 2026
Affected products & platforms
Red Hat LinuxUnclassified
Open vendor advisory

Android app · Google Play

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

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. A race condition in the `rxrpc_wake_up_io_thread()` function could lead to a null pointer dereference.

This occurs when the `io_thread` pointer is checked and then reloaded, and if the I/O thread exits between these operations, the second load can result in a null value. This vulnerability could cause a system crash, leading to a Denial of Service (DoS).

This vulnerability has been assessed as Moderate impact. The race condition in rxrpc_wake_up_io_thread() was introduced in upstream kernel version 6.16.0.

Red Hat Enterprise Linux is not affected, as the newest RHEL kernel (6.12.x in RHEL 10) predates the introduction of the vulnerable code. Red Hat severity: Moderate — CVSS 5.9 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H).

Weakness: CWE-366.

Affected versions

No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.

Official advisory · high-confidence parse· fetched 2 hours ago·verify at source

Fixed versions

No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.

Official advisory · high-confidence parse· fetched 2 hours ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • Update to a kernel version containing the fix (6.18.42+ or 7.1.6+).

Official advisory · high-confidence parse· fetched 2 hours ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.