cbcvebase.
CVE-2026-43402
published 2026-05-08

CVE-2026-43402: In the Linux kernel, the following vulnerability has been resolved: kthread: consolidate kthread exit paths to prevent use-after-free Guillaume reported…

PriorityP349critical9.8CVSS 3.1
AVNACLPRNUINSUCHIHAH
EPSS
0.46%
36.8th percentile
In the Linux kernel, the following vulnerability has been resolved: kthread: consolidate kthread exit paths to prevent use-after-free Guillaume reported crashes via corrupted RCU callback function pointers during KUnit testing. The crash was traced back to the pidfs rhashtable conversion which replaced the 24-byte rb_node with an 8-byte rhash_head in struct pid, shrinking it from 160 to 144 bytes. struct kthread (without CONFIG_BLK_CGROUP) is also 144 bytes. With CONFIG_SLAB_MERGE_DEFAULT and SLAB_HWCACHE_ALIGN both round up to 192 bytes and share the same slab cache. struct pid.rcu.func and struct kthread.affinity_node both sit at offset 0x78. When a kthread exits via make_task_dead() it bypasses kthread_exit() and misses the affinity_node cleanup. free_kthread_struct() frees the memory while the node is still linked into the global kthread_affinity_list. A subsequent list_del() by another kthread writes through dangling list pointers into the freed and reused memory, corrupting the pid's rcu.func pointer. Instead of patching free_kthread_struct() to handle the missed cleanup, consolidate all kthread exit paths. Turn kthread_exit() into a macro that calls do_exit() and add kthread_do_exit() which is called from do_exit() for any task with PF_KTHREAD set. This guarantees that kthread-specific cleanup always happens regardless of the exit path - make_task_dead(), direct do_exit(), or kthread_exit(). Replace __to_kthread() with a new tsk_is_kthread() accessor in the public header. Export do_exit() since module code using the kthread_exit() macro now needs it directly.

Affected

13 ranges
VendorProductVersion rangeFixed in
linuxlinux
linuxlinux>= 4d13f4304fa43471bfea101658a11feec7b28ac0 < 4729c7b00a347fd37d0cbc265b85f2884c3e06b64729c7b00a347fd37d0cbc265b85f2884c3e06b6
linuxlinux>= 4d13f4304fa43471bfea101658a11feec7b28ac0 < 5a591d7a5e48d30100943940a30a6ab41b15c6725a591d7a5e48d30100943940a30a6ab41b15c672
linuxlinux>= 4d13f4304fa43471bfea101658a11feec7b28ac0 < 28aaa9c39945b7925a1cc1d513c8f21ed38f5e4f28aaa9c39945b7925a1cc1d513c8f21ed38f5e4f
linuxlinux_kernel
linuxlinux_kernel
linuxlinux_kernel>= 6.14 < 6.18.196.18.19
linuxlinux_kernel>= 6.19 < 6.19.96.19.9
ubuntulinux
ubuntulinux-hwe-6.17
ubuntulinux-nvidia-6.17
ubuntulinux-oem-6.17
ubuntulinux-raspi

CVSS provenance

nvdv3.19.8CRITICALCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
vendor_ubuntu7.1HIGH
vendor_redhat7.0MEDIUM
Stop checking back — get the weekly exploitation signal.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.