CVE-2025-68288 — usb: storage: Fix memory leak in USB bulk transport
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+1
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
version ad2518320bc440ed3db072e2444a1bb226a9cf7aversion 4.17≥ 4.16.12 and < 4.17≥ 4.14.44 and < 4.15≥ 4.9.103 and < 4.10≥ 4.4.133 and < 4.5≥ 3.18.110 and < 3.19≥ 3.16.58 and < 3.17 and 12 moreversion 39169410574503c6e901de1aa6eac5108475e017version d827bea2d18c07ba514f7d48cde49f90da9a1384≥ a45b599ad808c3c982fdcdc12b0b8611c2f92824 and < 83f0241959831586d9b6d47f6bd5d3dec8f43bf0version 93314640426ddb6af618d0802e622f6fa771792cversion 58b7ce6f9ef2367f86384b20458642945993b816version 582802e7c617cfb07cc15f280c128e6decbc57b8≥ a45b599ad808c3c982fdcdc12b0b8611c2f92824 and < 41e99fe2005182139b1058db71f0d241f8f0078c≥ a45b599ad808c3c982fdcdc12b0b8611c2f92824 and < 5b815ddb3f5560fac35b16de3a2a22d5f81c5993≥ a45b599ad808c3c982fdcdc12b0b8611c2f92824 and < 0f18eac44c5668204bf6eebb01ddb369ac56932b≥ a45b599ad808c3c982fdcdc12b0b8611c2f92824 and < cb1401b5bcc2feb5b038fc4b512e5968b016e05e≥ a45b599ad808c3c982fdcdc12b0b8611c2f92824 and < 467fec3cefbeb9e3ea80f457da9a5666a71ca0d0≥ a45b599ad808c3c982fdcdc12b0b8611c2f92824 and < 4ba515dfff7eeca369ab85cdbb3f3b231c71720c |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.21%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Deferred
- Record created in this database
- 2025
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
7 on the record
- git.kernel.org/stable/c/467fec3cefbeb9e3ea80f457da9a5666a71ca0d0
- git.kernel.org/stable/c/4ba515dfff7eeca369ab85cdbb3f3b231c71720c
- git.kernel.org/stable/c/5b815ddb3f5560fac35b16de3a2a22d5f81c5993
- git.kernel.org/stable/c/0f18eac44c5668204bf6eebb01ddb369ac56932b
- git.kernel.org/stable/c/cb1401b5bcc2feb5b038fc4b512e5968b016e05e
- git.kernel.org/stable/c/41e99fe2005182139b1058db71f0d241f8f0078c
- git.kernel.org/stable/c/83f0241959831586d9b6d47f6bd5d3dec8f43bf0
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 8h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 8h
- Unknown CVE-2026-98431 RDMA/uverbs: Fix mmap_lock/disassociation_lock circular dependency 1d
- Unknown CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 1d
- Unknown CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 1d
- Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2025-68288 is "usb: storage: Fix memory leak in USB bulk transport", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.21% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.