| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <2025121639-CVE-2025-68288-c606@gregkh> Date: Tue, 16 Dec 2025 16:06:42 +0100 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: linux-cve-announce@...r.kernel.org Cc: Greg Kroah-Hartman <gregkh@...nel.org> Subject: CVE-2025-68288: usb: storage: Fix memory leak in USB bulk transport From: Greg Kroah-Hartman <gregkh@...nel.org> Description =========== In the Linux kernel, the following vulnerability has been resolved: usb: storage: Fix memory leak in USB bulk transport A kernel memory leak was identified by the 'ioctl_sg01' test from Linux Test Project (LTP). The following bytes were mainly observed: 0x53425355. When USB storage devices incorrectly skip the data phase with status data, the code extracts/validates the CSW from the sg buffer, but fails to clear it afterwards. This leaves status protocol data in srb's transfer buffer, such as the US_BULK_CS_SIGN 'USBS' signature observed here. Thus, this can lead to USB protocols leaks to user space through SCSI generic (/dev/sg*) interfaces, such as the one seen here when the LTP test requested 512 KiB. Fix the leak by zeroing the CSW data in srb's transfer buffer immediately after the validation of devices that skip data phase. Note: Differently from CVE-2018-1000204, which fixed a big leak by zero- ing pages at allocation time, this leak occurs after allocation, when USB protocol data is written to already-allocated sg pages. The Linux kernel CVE team has assigned CVE-2025-68288 to this issue. Affected and fixed versions =========================== Issue introduced in 4.17 with commit a45b599ad808c3c982fdcdc12b0b8611c2f92824 and fixed in 5.10.247 with commit 83f0241959831586d9b6d47f6bd5d3dec8f43bf0 Issue introduced in 4.17 with commit a45b599ad808c3c982fdcdc12b0b8611c2f92824 and fixed in 5.15.197 with commit 4ba515dfff7eeca369ab85cdbb3f3b231c71720c Issue introduced in 4.17 with commit a45b599ad808c3c982fdcdc12b0b8611c2f92824 and fixed in 6.1.159 with commit 467fec3cefbeb9e3ea80f457da9a5666a71ca0d0 Issue introduced in 4.17 with commit a45b599ad808c3c982fdcdc12b0b8611c2f92824 and fixed in 6.6.119 with commit cb1401b5bcc2feb5b038fc4b512e5968b016e05e Issue introduced in 4.17 with commit a45b599ad808c3c982fdcdc12b0b8611c2f92824 and fixed in 6.12.61 with commit 0f18eac44c5668204bf6eebb01ddb369ac56932b Issue introduced in 4.17 with commit a45b599ad808c3c982fdcdc12b0b8611c2f92824 and fixed in 6.17.11 with commit 5b815ddb3f5560fac35b16de3a2a22d5f81c5993 Issue introduced in 4.17 with commit a45b599ad808c3c982fdcdc12b0b8611c2f92824 and fixed in 6.18 with commit 41e99fe2005182139b1058db71f0d241f8f0078c Issue introduced in 3.16.58 with commit 582802e7c617cfb07cc15f280c128e6decbc57b8 Issue introduced in 3.18.110 with commit 58b7ce6f9ef2367f86384b20458642945993b816 Issue introduced in 4.4.133 with commit 93314640426ddb6af618d0802e622f6fa771792c Issue introduced in 4.9.103 with commit ad2518320bc440ed3db072e2444a1bb226a9cf7a Issue introduced in 4.14.44 with commit d827bea2d18c07ba514f7d48cde49f90da9a1384 Issue introduced in 4.16.12 with commit 39169410574503c6e901de1aa6eac5108475e017 Please see https://www.kernel.org for a full list of currently supported kernel versions by the kernel community. Unaffected versions might change over time as fixes are backported to older supported kernel versions. The official CVE entry at https://cve.org/CVERecord/?id=CVE-2025-68288 will be updated if fixes are backported, please check that for the most up to date information about this issue. Affected files ============== The file(s) affected by this issue are: drivers/usb/storage/transport.c Mitigation ========== The Linux kernel CVE team recommends that you update to the latest stable kernel version for this, and many other bugfixes. Individual changes are never tested alone, but rather are part of a larger kernel release. Cherry-picking individual commits is not recommended or supported by the Linux kernel community at all. If however, updating to the latest release is impossible, the individual changes to resolve this issue can be found at these commits: https://git.kernel.org/stable/c/83f0241959831586d9b6d47f6bd5d3dec8f43bf0 https://git.kernel.org/stable/c/4ba515dfff7eeca369ab85cdbb3f3b231c71720c https://git.kernel.org/stable/c/467fec3cefbeb9e3ea80f457da9a5666a71ca0d0 https://git.kernel.org/stable/c/cb1401b5bcc2feb5b038fc4b512e5968b016e05e https://git.kernel.org/stable/c/0f18eac44c5668204bf6eebb01ddb369ac56932b https://git.kernel.org/stable/c/5b815ddb3f5560fac35b16de3a2a22d5f81c5993 https://git.kernel.org/stable/c/41e99fe2005182139b1058db71f0d241f8f0078c
Powered by blists - more mailing lists