CVE-2026-99464: Linux kernel · media: redrat3: fix UAF in probe error path leaving rc device registered
Source GCVE Database
Not known to be exploited · fixed in e0e12b25b102e22f17ec3d0c00eb22ef7b792489 : patch Linux kernel soon.
Data as of 19 Nov 2026, 17:20 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in e0e12b25b102e22f17ec3d0c00eb22ef7b792489, d8f44a9e4820797067b8cdf1b6a4cb0c0ae3d143, af452b9e01331b5338a1e5141624f17607239207 +1
Exploitation evidence
Disclosed: evidence found.
CVE published 19 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.
What to do
Upgrade Linux kernel to e0e12b25b102e22f17ec3d0c00eb22ef7b792489, d8f44a9e4820797067b8cdf1b6a4cb0c0ae3d143, af452b9e01331b5338a1e5141624f17607239207 or 98e3df13c9fd57cc4051e9ee1717cfc65ee04c7d.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix has been implemented in the Linux kernel to ensure the RC device is unregistered in the probe error path before freeing the associated memory, preventing the use-after-free condition. Users should update to the fixed kernel version once available. No additional mitigations are specified or required beyond applying the official fix.
Description
A use-after-free (UAF) vulnerability was identified and fixed in the Linux kernel's redrat3 media driver. The flaw occurs in the probe error path where the RC device remains registered after its backing structure is freed, leading to a dangling pointer dereference when the device name is later accessed via sysfs. This issue arises if the detector enable fails after the RC device registration, causing the error path to skip unregistering the RC device before freeing memory.
References
- nvd.nist.gov/vuln/detail/CVE-2026-99464 (opens in a new tab)
- git.kernel.org/stable/c/98e3df13c9fd57cc4051e9ee1717cfc65ee04c7d (opens in a new tab)
- git.kernel.org/stable/c/af452b9e01331b5338a1e5141624f17607239207 (opens in a new tab)
- git.kernel.org/stable/c/d8f44a9e4820797067b8cdf1b6a4cb0c0ae3d143 (opens in a new tab)
- git.kernel.org/stable/c/e0e12b25b102e22f17ec3d0c00eb22ef7b792489 (opens in a new tab)