During initialization of the TI Video Processing Engine driver, a probe failure removes a required resource, causing the device registration function to succeed before the driver aborts. The error path does not trigger the driver’s remove callback, leaving the v4l2 device registered in the system. This improper cleanup can lead to a lingering device entry, potentially exhausting device table resources or causing inconsistent device state for clients that interact with the media subsystem.

The flaw resides in the Linux kernel’s media subsystem, specifically the TI VPE driver. All Linux distributions using a kernel build that includes this driver and has not yet applied the relevant patch are affected. No specific kernel version range is supplied in the data, so any kernel variant containing the buggy code before the commit can be impacted.

The CVSS score for this issue is 4.4, indicating moderate severity. The EPSS score is under 1%, suggesting a low likelihood of exploitation in the near term. It is not listed in the CISA KEV catalog. The flaw occurs during the probe phase of the TI VPE driver when the vpe_top resource is missing; v4l2_device_register() succeeds but the driver aborts without calling vpe_remove(), leaving a stale v4l2 device registration. A local attacker with privilege or the ability to cause probe failures could repeatedly trigger this path, potentially exhausting device table entries or leaving a corrupted device state that disrupts other media subsystem operations. Because the failure is local and hardware‑specific, there are no documented remote exploitation vectors, so the overall risk remains moderate with potential for localized resource exhaustion or state corruption if repeatedly exploited.