CVE-2026-99443: pps: generators: don't use the driver's info after unregister
In the Linux kernel, the following vulnerability has been resolved:
pps: generators: don't use the driver's info after unregister
A file that was opened before ppsgenunregistersource() keeps ppsgen, and with it the pointer to the driver's ppsgensourceinfo. PPSGENSETENABLE and PPSGENUSESYSTEMCLOCK keep using that pointer after the driver has gone:
- ppsgentio allocates its info with devmkzalloc(), so after an unbind both ioctls read freed memory, and SETENABLE calls the driver's enable() with its freed private data.
- ppsgen-dummy does not set info->owner, so it can be unloaded while the file is open, and the ioctls then read the unloaded module's data and call its code.
TIO can't probe in a VM, as it needs ART. A test driver that registers its info in devm memory like TIO does, unbound while /dev/pps-gen0 is open, gives:
BUG: KASAN: slab-use-after-free in ppsgencdevioctl+0x4c1/0x580 Read of size 1 at addr ffff88800e647f38 by task ppsgen64/145 ... Freed by task 146: kfree+0x25a/0x6d0 releasenodes+0xd1/0x140 devresreleaseall+0x10e/0x1a0 deviceunbindcleanup+0x71/0x250 devicereleasedriverinternal+0x41b/0x570 unbindstore+0xd9/0x100
and unloading ppsgen-dummy while its file is open oopses:
BUG: unable to handle page fault for address: ffffffffa0203040 Oops: Oops: 0000 [#1] SMP KASAN NOPTI RIP: 0010:ppsgencdevioctl+0x372/0x580
Protect info in the ioctl handler with a mutex, and clear it under the mutex on unregister, so that unregister waits for the ioctls using it and later ones fail with -ENODEV. PPSKCBIND does the same for a removed PPS device since commit 3649f9a6b897 ("pps: don't allow PPSKCBIND on removed devices"). The sysfs attributes need nothing new: they are removed, and their callbacks drained, before info is cleared.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.18.63 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.3.2 - Compensating control
Protect info in the ioctl handler with a mutex, and clear it under the mutex during unregister so unregister waits for ioctls using it.