Skip to content
statance
MenuClose
unknown

CVE-2026-99466

media: microchip-csi2dc: fix async notifier leak on probe error path

Published 19 Nov 2026 · Source updated 19 Nov 2026 · Retrieved 2026-11-19 15:23 UTC

Monitor this CVE ↗Full CVE monitoring on Pro and Business

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().

Description supplied by CVE Program. Formatting is simplified; follow the original advisory for full details.

Affected software and versions

Source-provided software and version information
SoftwareVersion informationFixed version
LinuxLinuxaffected: 2de0b3c0f678422ef2211760079a27c3cb1404b2 to < c287bcddda615b3c954cb5b1fc7e59292c878eeb; affected: 2de0b3c0f678422ef2211760079a27c3cb1404b2 to < 9fa70d75ab03f5babb072ad872a54879af4be55c; affected: 2de0b3c0f678422ef2211760079a27c3cb1404b2 to < e7dd17ce3190dd6f60e2d0153d8df15562347947; affected: 2de0b3c0f678422ef2211760079a27c3cb1404b2 to < c7528789244ce7329ca883170fb9315d739ae985See vendor advisory
LinuxLinuxaffected: 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.

CISA data retrieved 2026-11-19 21:16 UTC. Check CISA ↗

How to respond

  1. Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
  2. 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.
  3. Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.

Sources and remediation references

This public advisory does not determine whether a particular server is affected. Records are refreshed as sources change; verify urgent decisions against the original advisory.

← Browse the public CVE feed