In the Linux kernel, the following vulnerability has been resolved: io_uring/io-wq: re-check IO_WQ_BIT_EXIT for each linked work item commit… (CVE-2026-64425)
A vulnerability in the Linux kernel's io_uring/io-wq subsystem related to the handling of the IO_WQ_BIT_EXIT flag for linked work items has been resolved. The issue involved improper re-checking of the exit bit during processing of linked work items, potentially allowing some work items to continue running after exit had begun. The fix moves the exit bit check further inside the processing loop to cover all linked items properly.
AI Analysis
Technical Summary
The Linux kernel io_uring/io-wq subsystem had a flaw where io_worker_handle_work() took a snapshot of the IO_WQ_BIT_EXIT flag before processing a chain of linked work items but did not re-check this flag for each linked item. If the exit bit was set after the first linked item started, subsequent linked items could incorrectly continue execution by reusing stale state, skipping cancellation logic. The patch moves the exit bit check deeper inside the work processing loop to ensure all linked work items respect the exit condition. This vulnerability was identified through syzbot testing on devices with slow linked work items.
Potential Impact
The vulnerability could allow linked work items to continue running after the kernel has initiated exit procedures for the io_uring work queue. This could potentially lead to unexpected behavior or resource usage during shutdown sequences. No known exploits are reported in the wild. The impact is limited to the internal kernel work queue processing and does not indicate direct privilege escalation or remote code execution based on the provided data.
Mitigation Recommendations
A fix has been committed to the Linux kernel source code addressing this issue by improving the exit bit checking logic for linked work items. Users should apply the official kernel update containing commit 10dc95939817 or later to remediate this vulnerability. Since this is a kernel-level fix, updating the kernel to a patched version is the recommended mitigation.
In the Linux kernel, the following vulnerability has been resolved: io_uring/io-wq: re-check IO_WQ_BIT_EXIT for each linked work item commit… (CVE-2026-64425)
Description
A vulnerability in the Linux kernel's io_uring/io-wq subsystem related to the handling of the IO_WQ_BIT_EXIT flag for linked work items has been resolved. The issue involved improper re-checking of the exit bit during processing of linked work items, potentially allowing some work items to continue running after exit had begun. The fix moves the exit bit check further inside the processing loop to cover all linked items properly.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel io_uring/io-wq subsystem had a flaw where io_worker_handle_work() took a snapshot of the IO_WQ_BIT_EXIT flag before processing a chain of linked work items but did not re-check this flag for each linked item. If the exit bit was set after the first linked item started, subsequent linked items could incorrectly continue execution by reusing stale state, skipping cancellation logic. The patch moves the exit bit check deeper inside the work processing loop to ensure all linked work items respect the exit condition. This vulnerability was identified through syzbot testing on devices with slow linked work items.
Potential Impact
The vulnerability could allow linked work items to continue running after the kernel has initiated exit procedures for the io_uring work queue. This could potentially lead to unexpected behavior or resource usage during shutdown sequences. No known exploits are reported in the wild. The impact is limited to the internal kernel work queue processing and does not indicate direct privilege escalation or remote code execution based on the provided data.
Mitigation Recommendations
A fix has been committed to the Linux kernel source code addressing this issue by improving the exit bit checking logic for linked work items. Users should apply the official kernel update containing commit 10dc95939817 or later to remediate this vulnerability. Since this is a kernel-level fix, updating the kernel to a patched version is the recommended mitigation.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-rmw8-w7cg-rwfm
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-64425"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a6542099c2644c7f80832f7
Added to database: 07/25/2026, 23:08:57 UTC
Last enriched: 07/25/2026, 23:22:39 UTC
Last updated: 07/26/2026, 03:59:35 UTC
Views: 5
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.