https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 00:37:32 +0000 https://vulnerability.circl.lu/vuln/bell-cve-2026-64338 <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> https://vulnerability.circl.lu/vuln/bell-cve-2026-64338 https://vulnerability.circl.lu/vuln/certfr-2026-avi-0982 certfr-2026-avi-0982 https://vulnerability.circl.lu/vuln/certfr-2026-avi-0982 https://vulnerability.circl.lu/vuln/fkie_cve-2026-64338 <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>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/fkie_cve-2026-64338 https://vulnerability.circl.lu/vuln/ghsa-pghr-8xhx-xv5x <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>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/ghsa-pghr-8xhx-xv5x https://vulnerability.circl.lu/vuln/msrc_cve-2026-64338 msrc_CVE-2026-64338 https://vulnerability.circl.lu/vuln/msrc_cve-2026-64338 https://vulnerability.circl.lu/vuln/opensuse-su-2026:11476-1 <p>kernel-devel-7.1.7-1.1 on GA media</p> <p>kernel-devel-7.1.7-1.1 on GA media</p> https://vulnerability.circl.lu/vuln/opensuse-su-2026:11476-1 https://vulnerability.circl.lu/vuln/suse-su-2026:23477-1 <p>Security update for the Linux Kernel</p> <p>Security update for the Linux Kernel</p> https://vulnerability.circl.lu/vuln/suse-su-2026:23477-1 https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-64338 <p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 211 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: USB: misc: uss720: unregister parport on probe failure 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. 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. 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. This issue was identified during our ongoing static-analysis research while reviewing kernel code.</p> <p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 211 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: USB: misc: uss720: unregister parport on probe failure 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. 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. 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. This issue was identified during our ongoing static-analysis research while reviewing kernel code.</p> https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-64338 https://vulnerability.circl.lu/vuln/wid-sec-w-2026-2527 <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, dazu können DoS-Angriffe, die Offenlegung von Informationen, die Beschädigung des Speichers oder die Umgehung von Sicherheitsmaßnahmen gehören.</p> <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, dazu können DoS-Angriffe, die Offenlegung von Informationen, die Beschädigung des Speichers oder die Umgehung von Sicherheitsmaßnahmen gehören.</p> https://vulnerability.circl.lu/vuln/wid-sec-w-2026-2527