Answer in brief
CVE-2026-68334 records a Unknown severity vulnerability in rxrpc: fix io_thread race in rxrpc_wake_up_io_thread(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=5800b1cf3fd8ccab752a101865be1e76dac33142 <c9165e199f56997f2f2deb5d3ec2dfab98dfa288 || >=5800b1cf3fd8ccab752a101865be1e76dac33142 <092b42cf3f6013eec43607ecbcad674723649514 || >=5800b1cf3fd8ccab752a101865be1e76dac33142 <745fb794c3e933c023af9dbb5876a5e16ad2dc71 | c9165e199f56997f2f2deb5d3ec2dfab98dfa288, 092b42cf3f6013eec43607ecbcad674723649514, 745fb794c3e933c023af9dbb5876a5e16ad2dc71 |
| Linux/Linuxgeneric | 6.16 | Not reported |
Published upstream
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 10, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-68334 records a Unknown severity vulnerability in rxrpc: fix io_thread race in rxrpc_wake_up_io_thread(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=5800b1cf3fd8ccab752a101865be1e76dac33142 <c9165e199f56997f2f2deb5d3ec2dfab98dfa288 || >=5800b1cf3fd8ccab752a101865be1e76dac33142 <092b42cf3f6013eec43607ecbcad674723649514 || >=5800b1cf3fd8ccab752a101865be1e76dac33142 <745fb794c3e933c023af9dbb5876a5e16ad2dc71 | c9165e199f56997f2f2deb5d3ec2dfab98dfa288, 092b42cf3f6013eec43607ecbcad674723649514, 745fb794c3e933c023af9dbb5876a5e16ad2dc71 |
| Linux/Linuxgeneric | 6.16 | Not reported |
Published upstream
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 10, 2026
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.
Quoted source text, attributed separately from HOL analysis.