In the Linux kernel, the following vulnerability has been resolved:
io-wq: check for wq exit after adding new worker task_work
We check IO_WQ_BIT_EXIT before attempting to create a new worker, and wq exit cancels pending work if we have any. But it's possible to have a race between the two, where creation checks exit finding it not set, but we're in the process of exiting. The exit side will cancel pending creation task_work, but there's a gap where we add task_work after we've canceled existing creations at exit time.
Fix this by checking the EXIT bit post adding the creation task_work. If it's set, run the same cancelation that exit does.
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Debian | — | Upgrade linux | Jul 30, 2024 | Jun 19, 2024 |
| Suse | — | Upgrade kernel-rt-livepatchUpgrade kernel-rtUpgrade kernel-rt-develUpgrade kselftests-kmp-rtUpgrade dlm-kmp-azureUpgrade kernel-azureUpgrade kernel-azure-develUpgrade reiserfs-kmp-azureUpgrade kernel-rt-extraUpgrade kernel-rt-vdsoUpgrade kernel-devel-rtUpgrade kernel-rt_debug-vdsoUpgrade kernel-rt_debug-livepatch-develUpgrade cluster-md-kmp-rtUpgrade kernel-syms-rtUpgrade dlm-kmp-rtUpgrade kernel-azure-extraUpgrade kernel-azure-optionalUpgrade reiserfs-kmp-rtUpgrade gfs2-kmp-azureUpgrade kernel-devel-azureUpgrade kselftests-kmp-azureUpgrade kernel-rt-optionalUpgrade kernel-rt-livepatch-develUpgrade kernel-azure-vdsoUpgrade kernel-source-azureUpgrade kernel-rt_debug-develUpgrade kernel-source-rtUpgrade kernel-azure-livepatch-develUpgrade kernel-syms-azureUpgrade cluster-md-kmp-azureUpgrade kernel-rt_debugUpgrade gfs2-kmp-rtUpgrade ocfs2-kmp-azureUpgrade ocfs2-kmp-rt | Aug 9, 2024 | Jun 19, 2024 |
| Ubuntu | — | No solution existsUpgrade linux-azure-fde-5.15 | Jun 26, 2025 | Jun 19, 2024 |
With curated Threat Intelligence, you can see which vulnerabilities truly put you at risk, prioritize what matters most, and act before attackers do.
Explore Intelligence Hub