{"metadata": {"vulnerability": "CVE-2026-99464", "count": 10, "kinds": {"milestone": 4, "sighting": 1, "kev": 0, "other": 5}, "linked_omitted": 0}, "data": [{"timestamp": "2026-09-25T10:25:14.416Z", "date_only": false, "value": "2026-09-25T10:25:14.416Z", "kind": "milestone", "label": "Reserved", "source": "cvelistv5", "record": "CVE-2026-99464", "field": "cveMetadata.dateReserved"}, {"timestamp": "2026-11-19T14:42:18.786Z", "date_only": false, "value": "2026-11-19T14:42:18.786Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-99464", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, {"timestamp": "2026-11-19T14:42:18.786Z", "date_only": false, "value": "2026-11-19T14:42:18.786Z", "kind": "other", "label": "Updated", "source": "cvelistv5", "record": "CVE-2026-99464", "field": "cveMetadata.dateUpdated"}, {"timestamp": "2026-11-19T14:42:18.786Z", "date_only": false, "value": "2026-11-19T14:42:18.786Z", "kind": "other", "label": "Updated", "source": "cvelistv5 / Linux", "record": "CVE-2026-99464", "field": "containers.cna.providerMetadata.dateUpdated"}, {"timestamp": "2026-11-19T15:18:00Z", "date_only": false, "value": "2026-11-19T15:18:00Z", "kind": "other", "label": "Nvd published at", "source": "github \u00b7 GHSA-P7M8-9V2J-43PJ", "record": "GHSA-P7M8-9V2J-43PJ", "field": "database_specific.nvd_published_at", "linked_record": true}, {"timestamp": "2026-11-19T15:18:00.610Z", "date_only": false, "value": "2026-11-19T15:18:00.610", "kind": "milestone", "label": "Published", "source": "fkie_nvd \u00b7 FKIE_CVE-2026-99464", "record": "FKIE_CVE-2026-99464", "field": "published", "metric_role": "disclosure", "metric_basis": "recorded_event", "linked_record": true}, {"timestamp": "2026-11-19T15:18:00.610Z", "date_only": false, "value": "2026-11-19T15:18:00.610", "kind": "other", "label": "Updated", "source": "fkie_nvd \u00b7 FKIE_CVE-2026-99464", "record": "FKIE_CVE-2026-99464", "field": "lastModified", "linked_record": true}, {"timestamp": "2026-11-19T15:31:25Z", "date_only": false, "value": "2026-11-19T15:31:25Z", "kind": "milestone", "label": "Published", "source": "github \u00b7 GHSA-P7M8-9V2J-43PJ", "record": "GHSA-P7M8-9V2J-43PJ", "field": "published", "metric_role": "disclosure", "metric_basis": "recorded_event", "linked_record": true}, {"timestamp": "2026-11-19T15:31:25Z", "date_only": false, "value": "2026-11-19T15:31:25Z", "kind": "other", "label": "Updated", "source": "github \u00b7 GHSA-P7M8-9V2J-43PJ", "record": "GHSA-P7M8-9V2J-43PJ", "field": "modified", "linked_record": true}, {"timestamp": "2026-11-19T16:30:16.127Z", "date_only": false, "value": "2026-11-19T16:30:16.127246Z", "kind": "sighting", "label": "Seen", "source": "https://infosec.exchange/users/cve/statuses/117644054714510129", "record": "CVE-2026-99464", "field": "creation_timestamp", "uuid": "4ebf1133-ad1f-428d-a5ee-e00d387ef0a0", "content": "CVE-2026-99464 media: redrat3: fix UAF in probe error path leaving rc device registered In the Linux kernel, the following vulnerability has been resolved:\nmedia: redrat3: fix UAF in probe error path leaving rc device registered\nredrat3 stores its device name and phys path inside the main rr3structure, and the rc device's device_name and input_phys point intorr3. When the RC device is registered, it keeps those pointers.\n  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\n  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\nSyzkaller triggers this via usb probing. It probes the RedRat3 USBinterface, which calls redrat3_dev_probe() in redrat3.c. That functionallocates rr3, then builds an rc device whose name points into rr3 viaredrat3_init_rc_dev() in redrat3.c, and registers it withrc_register_device().\nWhen the detector enable fails after the RC device is registered, theprobe jumps to the led_free path. That path unregisters the LED but doesnot unregister the RC device before freeing rr3 via redrat3_delete() inredrat3.c. The RC device still holds device_name = rr3-&gt;name which is nowfreed.\nLater udevd reads /sys/.../input device name via sysfs_emit() in file.c,which calls input_dev_show_name() in input.c, which emits dev-&gt;name whichis the freed rr3-&gt;name.\nWhen the detector enable fails after the RC device is registered, theerror path must not leave the RC device registered. Make the probe errorpath clean up the same way redrat3_dev_disconnect() does.\nThis change should be safe because the RC device is fully registered atthis point and its teardown via rc_unregister_device() is protected bythe input device mutex, and rr3 is still alive during unregister sodevice_name remains valid until after unregister. The URBs are killedbefore rc_free, so no completion can run after rc is freed. No new lockordering is introduced.\nhttps://www.cve.org/CVERecord?id=CVE-2026-99464https://git.kernel.org/stable/c/d8f44a9e4820797067b8cdf1b6a4cb0c0ae3d143https://git.kernel.org/stable/c/98e3df13c9fd57cc4051e9ee1717cfc65ee04c7dhttps://git.kernel.org/stable/c/e0e12b25b102e22f17ec3d0c00eb22ef7b792489https://git.kernel.org/stable/c/af452b9e01331b5338a1e5141624f17607239207#kernel #Linux#CVE_2026_99464#bot", "url": "https://infosec.exchange/users/cve/statuses/117644054714510129"}], "metrics": {"as_of": "2026-11-19T18:37:59.961Z", "anchors": {"origin": {"timestamp": "2026-11-19T14:42:18.786Z", "date_only": false, "value": "2026-11-19T14:42:18.786Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-99464", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, "discovery": null, "report": null, "acknowledgement": null, "disclosure": {"timestamp": "2026-11-19T14:42:18.786Z", "date_only": false, "value": "2026-11-19T14:42:18.786Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-99464", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, "exploit_publication": null, "exploitation": null, "patch": null}, "vendor_response_time": {"available": false, "missing": ["start", "end"]}, "time_to_exploit": {"available": false, "missing": ["end"]}, "disclosure_to_exploit": {"available": false, "missing": ["end"]}, "disclosure_to_exploit_publication": {"available": false, "missing": ["end"]}, "time_to_patch": {"available": false, "missing": ["start", "end"]}, "total_time_to_patch": {"available": false, "missing": ["start", "end"]}, "disclosure_to_patch": {"available": false, "missing": ["end"]}, "time_unpatched": {"available": true, "seconds": 14141.175547, "hours": 3.9281043186111115, "days": 0.16367101327546296, "min_seconds": 14141.175547, "max_seconds": 14141.175547, "approximate": false, "ongoing": true, "order_known": true, "batch_listing": false, "end_before_start": false, "start": {"timestamp": "2026-11-19T14:42:18.786Z", "date_only": false, "value": "2026-11-19T14:42:18.786Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-99464", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, "end": {"timestamp": "2026-11-19T18:37:59.961Z", "date_only": false, "label": "As of", "source": "Calculation clock"}}, "exploitation_to_patch": {"available": false, "missing": ["start"]}, "exploit_publication_to_patch": {"available": false, "missing": ["start"]}}}
