https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 21:42:08 +0000 https://vulnerability.circl.lu/vuln/cve-2026-64338 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>USB: misc: uss720: unregister parport on probe failure</p> <p>uss720_probe() registers a parport before reading the 1284 register used to detect unsupported Belkin F5U002 adapters. If get_1284_register() fails, the error path drops the driver private data and the USB device reference, but leaves the parport device registered.</p> <p>Leaving the port registered is more than a private allocation leak: parport_register_port() has already reserved a parport number and registered the parport bus device, while pp-&gt;private_data still points at the private data that the common error path is about to release.</p> <p>Undo the pre-announce registration in the get_1284_register() failure branch before jumping to the common private-data cleanup path. Clear priv-&gt;pp first, matching the disconnect path and avoiding a stale pointer in the private data.</p> <p>This issue was identified during our ongoing static-analysis research while reviewing kernel code.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>USB: misc: uss720: unregister parport on probe failure</p> <p>uss720_probe() registers a parport before reading the 1284 register used to detect unsupported Belkin F5U002 adapters. If get_1284_register() fails, the error path drops the driver private data and the USB device reference, but leaves the parport device registered.</p> <p>Leaving the port registered is more than a private allocation leak: parport_register_port() has already reserved a parport number and registered the parport bus device, while pp-&gt;private_data still points at the private data that the common error path is about to release.</p> <p>Undo the pre-announce registration in the get_1284_register() failure branch before jumping to the common private-data cleanup path. Clear priv-&gt;pp first, matching the disconnect path and avoiding a stale pointer in the private data.</p> <p>This issue was identified during our ongoing static-analysis research while reviewing kernel code.</p> https://vulnerability.circl.lu/vuln/cve-2026-64338