CVE-2025-68288: usb: storage: Fix memory leak in USB bulk transport
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.20% (FIRST EPSS).
- Fixed version: Linux Linux 0f18eac44c5668204bf6eebb01ddb369ac56932b, 3.17, 3.19.
Low priority for now. Upgrade to Linux Linux 0f18eac44c5668204bf6eebb01ddb369ac56932b, 3.17, 3.19 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Dec 16, 2025
- Updated
- Oct 13, 2026
- EPSS
- 0.2% · 10th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 582802e7c617cfb07cc15f280c128e6decbc57b8, 58b7ce6f9ef2367f86384b20458642945993b816, 93314640426ddb6af618d0802e622f6fa771792c, ad2518320bc440ed3db072e2444a1bb226a9cf7a, d827bea2d18c07ba514f7d48cde49f90da9a1384, 39169410574503c6e901de1aa6eac5108475e017, 4.17affected
- a45b599ad808c3c982fdcdc12b0b8611c2f92824 and later · before 83f0241959831586d9b6d47f6bd5d3dec8f43bf0affected · git
- a45b599ad808c3c982fdcdc12b0b8611c2f92824 and later · before 4ba515dfff7eeca369ab85cdbb3f3b231c71720caffected · git
- a45b599ad808c3c982fdcdc12b0b8611c2f92824 and later · before 467fec3cefbeb9e3ea80f457da9a5666a71ca0d0affected · git
- a45b599ad808c3c982fdcdc12b0b8611c2f92824 and later · before cb1401b5bcc2feb5b038fc4b512e5968b016e05eaffected · git
- a45b599ad808c3c982fdcdc12b0b8611c2f92824 and later · before 0f18eac44c5668204bf6eebb01ddb369ac56932baffected · git
- a45b599ad808c3c982fdcdc12b0b8611c2f92824 and later · before 5b815ddb3f5560fac35b16de3a2a22d5f81c5993affected · git
- a45b599ad808c3c982fdcdc12b0b8611c2f92824 and later · before 41e99fe2005182139b1058db71f0d241f8f0078caffected · git
- 3.16.58 and later · before 3.17affected · semver
- 3.18.110 and later · before 3.19affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.159-1 | 6.1.159-1 |
| Debian:13 | linux | before 6.12.63-1 | 6.12.63-1 |
| Debian:14 | linux | before 6.17.11-1 | 6.17.11-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2025-68286Dec 16, 2025 · drm/amd/display: Check NULL before accessing31Monitor
- ← EarlierCVE-2025-68287Dec 16, 2025 · usb: dwc3: Fix race condition between concurrent dwc3_remove_requests() call paths0Monitor
- Later →CVE-2025-68289Dec 16, 2025 · usb: gadget: f_eem: Fix memory leak in eem_unwrap0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 0f18eac44c5668204bf6eebb01ddb369ac56932b | Vendor (CNA) |
| Linux Linux | 3.17 | Vendor (CNA) |
| Linux Linux | 3.19 | Vendor (CNA) |
| Linux Linux | 4.10 | Vendor (CNA) |
| Linux Linux | 4.15 | Vendor (CNA) |
| Linux Linux | 4.17 | Vendor (CNA) |
| Linux Linux | 4.5 | Vendor (CNA) |
| Linux Linux | 41e99fe2005182139b1058db71f0d241f8f0078c | Vendor (CNA) |
| Linux Linux | 467fec3cefbeb9e3ea80f457da9a5666a71ca0d0 | Vendor (CNA) |
| Linux Linux | 4ba515dfff7eeca369ab85cdbb3f3b231c71720c | Vendor (CNA) |
| Linux Linux | 5b815ddb3f5560fac35b16de3a2a22d5f81c5993 | Vendor (CNA) |
| Linux Linux | 83f0241959831586d9b6d47f6bd5d3dec8f43bf0 | Vendor (CNA) |
| Linux Linux | cb1401b5bcc2feb5b038fc4b512e5968b016e05e | Vendor (CNA) |
| debian:linux | 6.1.159-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/41e99fe2005182139b1058db71f0d241f8f0078c
- git.kernel.org/stable/c/467fec3cefbeb9e3ea80f457da9a5666a71ca0d0
- git.kernel.org/stable/c/4ba515dfff7eeca369ab85cdbb3f3b231c71720c
- git.kernel.org/stable/c/5b815ddb3f5560fac35b16de3a2a22d5f81c5993
- git.kernel.org/stable/c/83f0241959831586d9b6d47f6bd5d3dec8f43bf0
- git.kernel.org/stable/c/cb1401b5bcc2feb5b038fc4b512e5968b016e05e
Vendor advisories and official records. Exploit/PoC links are deliberately left out.