CVE-2026-99179: watch_queue: Fix note pool publication race in watch_queue_set_size()
In the Linux kernel, the following vulnerability has been resolved:
watchqueue: Fix note pool publication race in watchqueuesetsize()
There is a race between watchqueuesetsize() and postonenotification(). watchqueuesetsize() publishes wqueue->notes, notesbitmap, nrpages and nrnotes with plain stores, and postonenotification() reads them with plain loads under a different lock, so nothing orders the four stores against the poster's loads: depending on the build, notes can be stored last (gcc 14 on x86-64 does this). Since keyctlwatchkey() lets a watch attach to a queue before it is sized, postonenotification() can already be running on another CPU at that moment: it reads nrnotes > 0, passes its bounds check, and then reads notes while it is still NULL, dereferencing notes[0].
An unprivileged user triggers this reliably by watching one of its own keys through a notification pipe and racing ioctl(IOCWATCHQUEUESETSIZE) on that pipe against keyctl(KEYCTLSETPERM) on the key from another CPU, triggering:
BUG: kernel NULL pointer dereference, address: 0000000000000000 RIP: 0010:postonenotification.isra.0+0xa2/0x1e0 Call Trace: postwatchnotification+0x148/0x180 keyctlsetpermkey+0x119/0x130 dosyscall64+0x108/0x4c0 entrySYSCALL64afterhwframe+0x77/0x7f Kernel panic - not syncing: Fatal exception in interrupt
Fix this by publishing nrnotes last with smpstorerelease(), and by reading it once with smploadacquire() in postonenotification() before the bitmap and the page array are touched. A poster that observes a non-zero nrnotes then also observes the pool behind it; one that observes zero drops the notification as before.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 5.10.273 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 5.15.224 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.1.191 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.6.161 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.12.115 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.18.59 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.2.13 - Upgrade
Upgrade
azurelinux/kernelto a version that resolves this vulnerability.Fixed in 6.6.161.1-1 - Upgrade
Upgrade
ubuntu/linuxto a version that resolves this vulnerability.Fixed in 7.3.0-10.10 - Upgrade
Upgrade
ubuntu/linux-awsto a version that resolves this vulnerability.Fixed in 7.3.0-1004.4 - Upgrade
Upgrade
ubuntu/linux-azureto a version that resolves this vulnerability.Fixed in 7.3.0-1004.4 - Upgrade
Upgrade
ubuntu/linux-azure-fdeto a version that resolves this vulnerability.Fixed in 7.3.0-1004.5 - Upgrade
Upgrade
ubuntu/linux-gcpto a version that resolves this vulnerability.Fixed in 7.3.0-1004.4 - Upgrade
Upgrade
ubuntu/linux-oracleto a version that resolves this vulnerability.Fixed in 7.3.0-1004.4 - Upgrade
Upgrade
ubuntu/linux-raspito a version that resolves this vulnerability.Fixed in 7.3.0-1004.4 - Upgrade
Upgrade
ubuntu/linux-realtimeto a version that resolves this vulnerability.Fixed in 7.3.0-10.10.1 - Upgrade
Upgrade
ubuntu/linux-riscvto a version that resolves this vulnerability.Fixed in 7.3.0-10.10.1 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.1.192-1 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.12.115-2 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 7.2.13-1 - Upgrade
Upgrade
debian/linux-6.12to a version that resolves this vulnerability.Fixed in 6.12.115-2~deb12u1 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.1.192-2Fixed in 6.12.117-1Fixed in 7.2.15-1Fixed in 7.3.4-1 - Upgrade
Upgrade
debian/linux-6.12to a version that resolves this vulnerability.Fixed in 6.12.117-1~deb12u1 - Compensating control
In watch_queue_set_size(), publish nr_notes last with smp_store_release(); in post_one_notification(), read nr_notes once with smp_load_acquire() before accessing the bitmap and page array.
Event History
Frequently Asked Questions
Who can trigger this issue?
An unprivileged local user can trigger it. The described reproducer uses a watch on a key owned by that user, attached through a notification pipe.
What conditions are required for exploitation?
A watch must be attached to a watch queue before that queue is sized. The attacker races IOC_WATCH_QUEUE_SET_SIZE on the notification pipe against keyctl(KEYCTL_SETPERM) on the watched key from another CPU.
What is the likely impact?
The race can cause post_one_notification() to dereference a NULL notes pointer after observing a nonzero note count. The supplied failure output shows a kernel NULL pointer dereference, indicating a kernel crash or denial of service.