CVE-2026-99508: Linux kernel · media: ipu-bridge: Fix use-after-free in IVSC error path
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in d1df2ec20a6ddac6ae553b34b39472a20c5de9c6 : update Linux kernel when convenient.
Data as of 19 Nov 2026, 14:49 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in d1df2ec20a6ddac6ae553b34b39472a20c5de9c6, adf422b7587bff1c9069406ce7a6c5a1f0e70193, 3d42d1c82717f0853379b516a7fab54b636e09cc +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 d1df2ec20a6ddac6ae553b34b39472a20c5de9c6, adf422b7587bff1c9069406ce7a6c5a1f0e70193, 3d42d1c82717f0853379b516a7fab54b636e09cc or 2af4892580167181c3181b2f0b6ffab1be0096c9.
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– |
Description
In the Linux kernel, the following vulnerability has been resolved: media: ipu-bridge: Fix use-after-free in IVSC error path ipu_bridge_get_ivsc_acpi_dev() returns an ACPI device with a reference held. If no matching CSI device is found, ipu_bridge_check_ivsc_dev() drops that reference before passing the device to dev_err(). Concurrent CSI device and ACPI namespace removal can drop the other references, making this the final put. dev_err() then reads the freed struct acpi_device and its kobject name. This was reproduced without kprobes by racing normal CSI platform-device unregistration and ACPI configfs table removal against the production ipu_bridge_init() entry. KASAN reported the final free through device_release(), followed by invalid reads through _dev_err(). Emit the error message while the lookup reference is still held, then drop the reference as before. Source reproducers and vulnerable/fixed serial logs, with only the build hostname redacted, are available at: https://github.com/kimaiden1984-boop/linux-ipu-bridge-acpi-uaf-reproducer The fixed target builds with W=1 on x86-64. This was not tested on physical IPU hardware. The tests establish runtime reachability but do not measure occurrence frequency on shipping systems or establish exploitability.
References
- git.kernel.org/stable/c/2af4892580167181c3181b2f0b6ffab1be0096c9 (opens in a new tab)
- git.kernel.org/stable/c/d1df2ec20a6ddac6ae553b34b39472a20c5de9c6 (opens in a new tab)
- git.kernel.org/stable/c/adf422b7587bff1c9069406ce7a6c5a1f0e70193 (opens in a new tab)
- git.kernel.org/stable/c/3d42d1c82717f0853379b516a7fab54b636e09cc (opens in a new tab)