Skip to content
Threat Brief

← All advisories

CVE-2026-99508

Severity unknownNo known exploitationFix available

media: ipu-bridge: Fix use-after-free in IVSC error path

Record last updated

CVSS score

None

No score published yet

EPSS, chance of exploitation in 30 days

0.2%

Higher than 10% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

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.

Patching and mitigation

Patch status
Fix available (source: CVE record (Linux))
Fix documented (source date)
Mitigation
None documented
Vendor guidance
No vendor link on record

Affected products

VendorProductAffected versionsFixed inPer
LinuxLinuxfrom c66821f381aed2c7c754d6ac8920a8665a3a01f7 before d1df2ec20a6ddac6ae553b34b39472a20c5de9c6d1df2ec20a6ddac6ae553b34b39472a20c5de9c6CVE Program
LinuxLinuxfrom c66821f381aed2c7c754d6ac8920a8665a3a01f7 before adf422b7587bff1c9069406ce7a6c5a1f0e70193adf422b7587bff1c9069406ce7a6c5a1f0e70193CVE Program
LinuxLinuxfrom c66821f381aed2c7c754d6ac8920a8665a3a01f7 before 3d42d1c82717f0853379b516a7fab54b636e09cc3d42d1c82717f0853379b516a7fab54b636e09ccCVE Program
LinuxLinuxfrom c66821f381aed2c7c754d6ac8920a8665a3a01f7 before 2af4892580167181c3181b2f0b6ffab1be0096c92af4892580167181c3181b2f0b6ffab1be0096c9CVE Program
LinuxLinux6.6Not documentedCVE Program
LinuxLinux (unaffected)from 6.12.117 up to and including 6.12.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.18.61 up to and including 6.18.*Not documentedCVE Program
LinuxLinux (unaffected)from 7.3.2 up to and including 7.3.*Not documentedCVE Program
LinuxLinux (unaffected)7.4-rc1Not documentedCVE Program
LinuxLinux (unaffected)all versions before 6.6Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by Linux

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (Linux)

    Source: CVE record (Linux) (opens in a new tab)

Vendor guidance and references