Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%
Buy Us a Coffee

CVE-2026-99103— workqueue: Fix unbound pool lifetime for pending pwqs

Quick assessment

Affected
Linux Linux
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

在 Linux 内核中，以下漏洞已得到修复： workqueue：修复待处理 pwq 中无绑定工作池（unbound pool）生命周期不受限的问题 KASAN 报告在 函数中存在对无绑定 的释放后使用（use-after-free）问题： 问题根源： 当取消最后一个非活跃的工作项时，会跳过 调用，导致一个引用计数（refcnt）已降为零的空 （per-workqueue queue）仍保留在 链表中。 而当前的 实现会在从链表中移除该 之前，先对所属的无绑定工作池（unbound pool）执行 操作。如果此次

AI Predicted 7.8 Difficulty: Moderate

Affected Version Matrix 16

VendorProduct Version RangeStatus
Linux Linux 5a70baec2294e8a7d0fcc4558741c23e752dad5c< 6741dd3fd38e47c08bc39d11ef5fa141fa6d0441 affected
843288afd3cc6f3342659c6cf81fc47684d25563< 9f5d5aef3072a33c6f9bfb954bb0cba1c2541849 affected
5797b1c18919cd9c289ded7954383e499f729ce0< f320b85c90fe5fc9d4d06badd450518323a94a7f affected
5797b1c18919cd9c289ded7954383e499f729ce0< 3d2ef2b9f4c084ab498494d26495a82f7e15407b affected
5797b1c18919cd9c289ded7954383e499f729ce0< cf9c8aaea0d47410df8708bec195889f3a85cd3c affected
fc67aebe34f22632ccb22faea48cc4d3134620a2 affected
6.6.23< 6.6.25 affected
6.8.2< 6.8.4 affected
… +8 more rows
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-99103

Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
workqueue: Fix unbound pool lifetime for pending pwqs
Source: CVE Program / CVE List V5
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved: workqueue: Fix unbound pool lifetime for pending pwqs KASAN reports a use-after-free of an unbound worker_pool in node_activate_pending_pwq(): BUG: KASAN: slab-use-after-free in _raw_spin_trylock+0x6d/0x120 Read of size 4 at addr ffff8880089ce000 by task kworker/u22:0/318 CPU: 1 UID: 0 PID: 318 Comm: kworker/u22:0 Not tainted 7.2.0 #1 PREEMPT(lazy) Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014 Workqueue: 0x0 (flush-8:0) Call Trace: <TASK> dump_stack_lvl+0x53/0x70 print_report+0xce/0x610 kasan_report+0xce/0x100 _raw_spin_trylock+0x6d/0x120 pwq_dec_nr_in_flight+0x4b4/0xcb0 process_one_work+0x921/0x11a0 worker_thread+0x4d0/0xd20 kthread+0x2de/0x3c0 ret_from_fork+0x3aa/0x620 ret_from_fork_asm+0x1a/0x30 </TASK> Allocated by task 311: alloc_pwq+0x439/0xca0 apply_wqattrs_prepare+0x75e/0xd10 apply_workqueue_attrs_locked+0x44/0xa0 wq_nice_store+0x350/0x450 Freed by task 0: kfree+0x127/0x3b0 rcu_core+0x523/0x1780 handle_softirqs+0x1b3/0x610 Last potentially related work creation: put_unbound_pool+0x3f3/0x7d0 pwq_release_workfn+0x494/0x8e0 kthread_worker_fn+0x1ff/0x790 Canceling the last inactive work skips pwq_dec_nr_active(), so an empty pwq can remain on pending_pwqs when its refcnt reaches zero. pwq_release_workfn() currently puts the pool before removing that pwq. If this drops the last pool reference, the pool can be RCU-freed while the pwq remains reachable, and node_activate_pending_pwq() may trylock the freed pool->lock. Remove the pwq from pending_pwqs before putting the pool.
Source: CVE Program / CVE List V5
CVSS Information
N/A
Source: CVE Program / CVE List V5
Vulnerability Type
N/A
Source: CVE Program / CVE List V5

Affected Products

Vendor Product Affected Versions CPE Subscribe
Linux Linux 5a70baec2294e8a7d0fcc4558741c23e752dad5c ~ 6741dd3fd38e47c08bc39d11ef5fa141fa6d0441 -
Linux Linux 6.9 -

II. Public POCs for CVE-2026-99103

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-99103

请登录查看更多情报信息。

Patches & Fixes for CVE-2026-99103 (5)

Same Patch Batch · Linux · 2026-10-28 · 117 CVEs total

CVE-2026-99144 sched_ext: Fix use-after-free of a destroyed user DSQ by a deferred reenqueue
CVE-2026-99130 io_uring/cancel: don't spin on local work the task can't run
CVE-2026-99131 xfs: fix capability check in xfs
CVE-2026-99133 net/iucv: fix the recvmsg window update
CVE-2026-99132 xfs: don't hold buffer locks across sync transaction commit in xfs_sync_sb_buf
CVE-2026-99134 mac802154: fix data race and NULL deref on local->assoc_dev
CVE-2026-99135 dm-integrity: fix infinite loop on discard with large tag size
CVE-2026-99137 cifs: don't update i_size in cifs_do_truncate without a cached handle
CVE-2026-99136 dm-crypt: fix a tiny race condition in crypt_dec_pending
CVE-2026-99138 tcp: fix use-after-free in do_tcp_getsockopt(TCP_CC_INFO)
CVE-2026-99140 tracing: Fix hist trigger timestamps for buffered events
CVE-2026-99139 tcp: fix use-after-free in do_tcp_getsockopt(TCP_CONGESTION)
CVE-2026-99141 tracing: Fix crash in print_graph_function_event()
CVE-2026-99142 tracing: Check operator stack capacity before pushing
CVE-2026-99143 tracing: Keep the predicate limit separate from program capacity
CVE-2026-99156 scsi: st: Fix use-after-free race between st_remove() and st_open()
CVE-2026-99153 scsi: libiscsi: Validate the ITT reflected in a Reject PDU
CVE-2026-99152 scsi: libiscsi: Validate the task named by a management response
CVE-2026-99154 scsi: libiscsi: Reject a negative task index from parse_pdu_itt
CVE-2026-99151 drm/amd/display: Fix NULL sink dereference in USB4 bandwidth functions

Showing top 20 of 117 CVEs. View all on vendor page &rarr; →

IV. Related Vulnerabilities

Same product: Linux
Same vendor: Linux