CVE-2026-99466
media: microchip-csi2dc: fix async notifier leak on probe error path
What happened?
In the Linux kernel, the following vulnerability has been resolved:
media: microchip-csi2dc: fix async notifier leak on probe error path
csi2dc_of_parse() ends up calling csi2dc_prepare_notifier(), which registers the V4L2 async notifier with v4l2_async_nf_register(). The probe error label csi2dc_probe_cleanup_notifier is reached after csi2dc_of_parse() has already succeeded (e.g. when media entity init, csi2dc_power() or v4l2_async_register_subdev() fail), but it calls only v4l2_async_nf_cleanup() and never v4l2_async_nf_unregister().
The notifier therefore stays chained in the global notifier_list while the enclosing struct csi2dc_device is freed, leading to list corruption and a use-after-free when the list is next walked.
Unregister the notifier before cleaning it up on the error path, matching the teardown already done in csi2dc_remove().
Affected software and versions
| Software | Version information | Fixed version |
|---|---|---|
| LinuxLinux | affected: 2de0b3c0f678422ef2211760079a27c3cb1404b2 to < c287bcddda615b3c954cb5b1fc7e59292c878eeb; affected: 2de0b3c0f678422ef2211760079a27c3cb1404b2 to < 9fa70d75ab03f5babb072ad872a54879af4be55c; affected: 2de0b3c0f678422ef2211760079a27c3cb1404b2 to < e7dd17ce3190dd6f60e2d0153d8df15562347947; affected: 2de0b3c0f678422ef2211760079a27c3cb1404b2 to < c7528789244ce7329ca883170fb9315d739ae985 | See vendor advisory |
| LinuxLinux | affected: 5.18; unaffected: 0 to < 5.18; unaffected: 6.12.117 to ≤ 6.12.*; unaffected: 6.18.61 to ≤ 6.18.*; unaffected: 7.3.2 to ≤ 7.3.*; unaffected: 7.4-rc1 to ≤ * | See vendor advisory |
Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.
Is it being exploited?
This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.
How to respond
- Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
- Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
- Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.
Sources and remediation references
- https://www.cve.org/CVERecord?id=CVE-2026-99466
- https://git.kernel.org/stable/c/c287bcddda615b3c954cb5b1fc7e59292c878eeb
- https://git.kernel.org/stable/c/9fa70d75ab03f5babb072ad872a54879af4be55c
- https://git.kernel.org/stable/c/e7dd17ce3190dd6f60e2d0153d8df15562347947
- https://git.kernel.org/stable/c/c7528789244ce7329ca883170fb9315d739ae985