PT-2026-151675

CVE-2026-99464

·

Published

2026-11-19

·

Updated

2026-11-19

Description by

Score
N/A
Not available

No severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.

In the Linux kernel, the following vulnerability has been resolved:
media: redrat3: fix UAF in probe error path leaving rc device registered
redrat3 stores its device name and phys path inside the main rr3 structure, and the rc device's device name and input phys point into rr3. When the RC device is registered, it keeps those pointers.
KASAN: slab-use-after-free in string nocheck lib/vsprintf.c:648 Read of size 1 at addr ffff888051fda758 by task udevd/7464 Call Trace: string nocheck lib/vsprintf.c:648 [inline] string+0x216/0x2d0 lib/vsprintf.c:730 vsnprintf+0x74a/0xef0 lib/vsprintf.c:2945 vscnprintf+0x41/0x90 lib/vsprintf.c:3014 sysfs emit+0x10e/0x180 fs/sysfs/file.c:761 input dev show name+0x58/0x70 drivers/input/input.c:1282
Allocated by task 10: redrat3 dev probe+0x477/0x2570 drivers/media/rc/redrat3.c:1023 Freed by task 10: redrat3 delete drivers/media/rc/redrat3.c:466 [inline] redrat3 dev probe+0x1bf4/0x2570 drivers/media/rc/redrat3.c:1124
Syzkaller triggers this via usb probing. It probes the RedRat3 USB interface, which calls redrat3 dev probe() in redrat3.c. That function allocates rr3, then builds an rc device whose name points into rr3 via redrat3 init rc dev() in redrat3.c, and registers it with rc register device().
When the detector enable fails after the RC device is registered, the probe jumps to the led free path. That path unregisters the LED but does not unregister the RC device before freeing rr3 via redrat3 delete() in redrat3.c. The RC device still holds device name = rr3->name which is now freed.
Later udevd reads /sys/.../input device name via sysfs emit() in file.c, which calls input dev show name() in input.c, which emits dev->name which is the freed rr3->name.
When the detector enable fails after the RC device is registered, the error path must not leave the RC device registered. Make the probe error path clean up the same way redrat3 dev disconnect() does.
This change should be safe because the RC device is fully registered at this point and its teardown via rc unregister device() is protected by the input device mutex, and rr3 is still alive during unregister so device name remains valid until after unregister. The URBs are killed before rc free, so no completion can run after rc is freed. No new lock ordering is introduced.
Vendors
Affected products
Related identifiers
Found an issue in the description? Have something to add? Feel free to write us 👾