CVE-2026-64338
CVE CVE-2026-64338EUVD EUVD-2026-48882Published 2026-07-25T08:50:02.000Z
What the advisory describes
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->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->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.
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux 3295f1b866bfbcabd625511968e8a5c541f9ab32 <729b68a5bad71220ae0914c8bdab9488ad5be6c8; 02d13616ca30014ed96302e51a5b0e17664e58bc; patch: 5.10.261; 6.9.7 <6.10; 10132ccf99f49b43aeb7470df50d72344a601ad6 <0b3073f40cc9f95d5ff0037eb0a06f5c1725a7ea; 4.19.317 <4.20; dff3b01e91a3df93063b03d0f8dd5c40546687ec; patch: 6.1.178; 6.6.36 <6.6.145; patch: 6.18.39; 489d77fbd66375972a380d207f7eb39b00c4a67b; patch: 6.6.145; 3295f1b866bfbcabd625511968e8a5c541f9ab32 <b4ecbdc4f8830f5586c4a5cfc384c00f20f8f8b3; patch: 7.1.4; patch: 0; 6.1.96 <6.1.178; 3295f1b866bfbcabd625511968e8a5c541f9ab32 <5e62d7857fd51b908b8371062ee839739a086bbe; patch: 6.12.96; 4eaf2331a77996bbbaf2b824d452ac8ebda7e6e7 <93563243377f8e9b46cc94d9c4f06533dd31b141; 5.10.221 <5.10.261; 5.4.279 <5.5; 8fc246a8a456679993df565d3c9e3da28030ee43 <1712fd71a5aaf81e47c747f180535fa963ad7830; 5.15.162 <5.15.212; patch: 7.2-rc3; patch: 5.15.212; 3295f1b866bfbcabd625511968e8a5c541f9ab32 <48dd0b2ec9f2e97c486eb68cd0a64b25c1c3df3e; 6.10; 04736c1bc32197f7d859e01a96ae80a16659931d <6bbb98bec71b577fda4f4b48f7aea5874b04a576
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.