A potential memory leak exists in the Linux kernel’s ti_fpc202 driver when the probe function does not correctly release device node references. The kernel patch replaces manual handling with for_each_child_of_node_scoped(), automatically freeing references at the end of the loop. If this flaw remains, repeated device scans could consume kernel memory, leading to kernel instability, crashes, or a denial‑of‑service scenario. The vulnerability does not provide a direct path to gaining code execution, but the loss of kernel memory can degrade overall system reliability.

All Linux kernel installations that include the ti_fpc202 driver are affected, as the issue targets the generic kernel code rather than a specific distribution version. Since the driver is part of the default kernel tree, any system running a kernel build that predates the patch is potentially vulnerable. The vendor is the Linux community, and the fix is delivered through the upstream kernel release process.

The CVSS score is not listed, and no EPSS data is available, so the exploitation likelihood based on public data is low. The flaw requires local privilege or kernel execution to repeatedly invoke the probe function. The likely attack vector is a locally privileged user or a user running code that can trigger the driver’s probe routine. If the flaw is exercised, the resulting memory exhaustion could lead to kernel instability, crashes, or a denial‑of‑service scenario. It is not listed in CISA’s KEV catalog and no publicly available exploits are known.