CVE-2026-99464 (GCVE-0-2026-99464)
Vulnerability from cvelistv5 – Published: 2026-11-19 14:42 – Updated: 2026-11-19 14:42| Vendor | Product | Version | CPE status | |
|---|---|---|---|---|
| Linux | Linux |
Affected:
2154be651b90ab0e6b5e9b9cf127a75429f9e90c , < d8f44a9e4820797067b8cdf1b6a4cb0c0ae3d143
(git)
Affected: 2154be651b90ab0e6b5e9b9cf127a75429f9e90c , < 98e3df13c9fd57cc4051e9ee1717cfc65ee04c7d (git) Affected: 2154be651b90ab0e6b5e9b9cf127a75429f9e90c , < e0e12b25b102e22f17ec3d0c00eb22ef7b792489 (git) Affected: 2154be651b90ab0e6b5e9b9cf127a75429f9e90c , < af452b9e01331b5338a1e5141624f17607239207 (git) |
guessed | |
| Linux | Linux |
Affected:
3.0
Unaffected: 0 , < 3.0 (semver) Unaffected: 6.12.117 , ≤ 6.12.* (semver) Unaffected: 6.18.61 , ≤ 6.18.* (semver) Unaffected: 7.3.2 , ≤ 7.3.* (semver) Unaffected: 7.4-rc1 , ≤ * (original_commit_for_fix) |
guessed |
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"drivers/media/rc/redrat3.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "d8f44a9e4820797067b8cdf1b6a4cb0c0ae3d143",
"status": "affected",
"version": "2154be651b90ab0e6b5e9b9cf127a75429f9e90c",
"versionType": "git"
},
{
"lessThan": "98e3df13c9fd57cc4051e9ee1717cfc65ee04c7d",
"status": "affected",
"version": "2154be651b90ab0e6b5e9b9cf127a75429f9e90c",
"versionType": "git"
},
{
"lessThan": "e0e12b25b102e22f17ec3d0c00eb22ef7b792489",
"status": "affected",
"version": "2154be651b90ab0e6b5e9b9cf127a75429f9e90c",
"versionType": "git"
},
{
"lessThan": "af452b9e01331b5338a1e5141624f17607239207",
"status": "affected",
"version": "2154be651b90ab0e6b5e9b9cf127a75429f9e90c",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"drivers/media/rc/redrat3.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "3.0"
},
{
"lessThan": "3.0",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.117",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.61",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.3.*",
"status": "unaffected",
"version": "7.3.2",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.4-rc1",
"versionType": "original_commit_for_fix"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.12.117",
"versionStartIncluding": "3.0",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.18.61",
"versionStartIncluding": "3.0",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.3.2",
"versionStartIncluding": "3.0",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.4-rc1",
"versionStartIncluding": "3.0",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "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\u0027s 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."
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T14:42:18.786Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/d8f44a9e4820797067b8cdf1b6a4cb0c0ae3d143"
},
{
"url": "https://git.kernel.org/stable/c/98e3df13c9fd57cc4051e9ee1717cfc65ee04c7d"
},
{
"url": "https://git.kernel.org/stable/c/e0e12b25b102e22f17ec3d0c00eb22ef7b792489"
},
{
"url": "https://git.kernel.org/stable/c/af452b9e01331b5338a1e5141624f17607239207"
}
],
"title": "media: redrat3: fix UAF in probe error path leaving rc device registered",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-99464",
"datePublished": "2026-11-19T14:42:18.786Z",
"dateReserved": "2026-09-25T10:25:14.416Z",
"dateUpdated": "2026-11-19T14:42:18.786Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"drivers/media/rc/redrat3.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "d8f44a9e4820797067b8cdf1b6a4cb0c0ae3d143",
"status": "affected",
"version": "2154be651b90ab0e6b5e9b9cf127a75429f9e90c",
"versionType": "git"
},
{
"lessThan": "98e3df13c9fd57cc4051e9ee1717cfc65ee04c7d",
"status": "affected",
"version": "2154be651b90ab0e6b5e9b9cf127a75429f9e90c",
"versionType": "git"
},
{
"lessThan": "e0e12b25b102e22f17ec3d0c00eb22ef7b792489",
"status": "affected",
"version": "2154be651b90ab0e6b5e9b9cf127a75429f9e90c",
"versionType": "git"
},
{
"lessThan": "af452b9e01331b5338a1e5141624f17607239207",
"status": "affected",
"version": "2154be651b90ab0e6b5e9b9cf127a75429f9e90c",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"drivers/media/rc/redrat3.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "3.0"
},
{
"lessThan": "3.0",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.117",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.61",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.3.*",
"status": "unaffected",
"version": "7.3.2",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.4-rc1",
"versionType": "original_commit_for_fix"
}
]
}
],
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "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\u0027s 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."
}
],
"id": "CVE-2026-99464",
"lastModified": "2026-11-19T15:18:00.610",
"metrics": {},
"published": "2026-11-19T15:18:00.610",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/98e3df13c9fd57cc4051e9ee1717cfc65ee04c7d"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/af452b9e01331b5338a1e5141624f17607239207"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/d8f44a9e4820797067b8cdf1b6a4cb0c0ae3d143"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/e0e12b25b102e22f17ec3d0c00eb22ef7b792489"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Received"
}
}
}
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.