{"id":"AZL-114920","summary":"CVE-2026-99464 affecting package kernel 6.6.161.1-1","details":"In the Linux kernel, the following vulnerability has been resolved:\n\nmedia: redrat3: fix UAF in probe error path leaving rc device registered\n\nredrat3 stores its device name and phys path inside the main rr3\nstructure, and the rc device's device_name and input_phys point into\nrr3. When the RC device is registered, it keeps those pointers.\n\n  KASAN: slab-use-after-free in string_nocheck lib/vsprintf.c:648\n  Read of size 1 at addr ffff888051fda758 by task udevd/7464\n  Call Trace:\n   string_nocheck lib/vsprintf.c:648 [inline]\n   string+0x216/0x2d0 lib/vsprintf.c:730\n   vsnprintf+0x74a/0xef0 lib/vsprintf.c:2945\n   vscnprintf+0x41/0x90 lib/vsprintf.c:3014\n   sysfs_emit+0x10e/0x180 fs/sysfs/file.c:761\n   input_dev_show_name+0x58/0x70 drivers/input/input.c:1282\n\n  Allocated by task 10:\n   redrat3_dev_probe+0x477/0x2570 drivers/media/rc/redrat3.c:1023\n  Freed by task 10:\n   redrat3_delete drivers/media/rc/redrat3.c:466 [inline]\n   redrat3_dev_probe+0x1bf4/0x2570 drivers/media/rc/redrat3.c:1124\n\nSyzkaller triggers this via usb probing. It probes the RedRat3 USB\ninterface, which calls redrat3_dev_probe() in redrat3.c. That function\nallocates rr3, then builds an rc device whose name points into rr3 via\nredrat3_init_rc_dev() in redrat3.c, and registers it with\nrc_register_device().\n\nWhen the detector enable fails after the RC device is registered, the\nprobe jumps to the led_free path. That path unregisters the LED but does\nnot unregister the RC device before freeing rr3 via redrat3_delete() in\nredrat3.c. The RC device still holds device_name = rr3-\u003ename which is now\nfreed.\n\nLater udevd reads /sys/.../input device name via sysfs_emit() in file.c,\nwhich calls input_dev_show_name() in input.c, which emits dev-\u003ename which\nis the freed rr3-\u003ename.\n\nWhen the detector enable fails after the RC device is registered, the\nerror path must not leave the RC device registered. Make the probe error\npath clean up the same way redrat3_dev_disconnect() does.\n\nThis change should be safe because the RC device is fully registered at\nthis point and its teardown via rc_unregister_device() is protected by\nthe input device mutex, and rr3 is still alive during unregister so\ndevice_name remains valid until after unregister. The URBs are killed\nbefore rc_free, so no completion can run after rc is freed. No new lock\nordering is introduced.","modified":"2026-11-20T14:17:19.285308608Z","published":"2026-11-19T15:18:00Z","upstream":["CVE-2026-99464"],"references":[{"type":"WEB","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-99464"}],"affected":[{"package":{"name":"kernel","ecosystem":"Azure Linux:3","purl":"pkg:rpm/azure-linux/kernel"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"6.6.161.1-1"}]}],"database_specific":{"source":"https://github.com/microsoft/AzureLinuxVulnerabilityData/blob/main/osv/AZL-114920.json"}}],"schema_version":"1.9.2"}