CVE-2026-31412usb: gadget: f_mass_storage: Fix potential integer overflow in check_command_size_in_blocks()
- 5.5MediumCVSS base score
- 0.17%Exploitation in 30 daysEPSS · top 93% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: usb: gadget: f_mass_storage: Fix potential integer overflow in check_command_size_in_blocks() The `check_command_size_in_blocks()` function calculates the data size in bytes by left shifting `common->data_size_from_cmnd` by the block size (`common->curlun->blkbits`). However, it does not validate whether this shift operation will cause an integer overflow. Initially, the block size is set up in `fsg_lun_open()` , and the `common->data_size_from_cmnd` is set up in `do_scsi_command()`. During initialization, there is no integer overflow check for the interaction between two variables. So if a malicious USB host sends a SCSI READ or WRITE command requesting a large amount of data (`common->data_size_from_cmnd`), the left shift operation can wrap around. This results in a truncated data size, which can bypass boundary checks and potentially lead to memory corruption or out-of-bounds accesses. Fix this by using the check_shl_overflow() macro to safely perform the shift and catch any overflows.
Timeline
ID reserved
By Linux
- 32 days later
· 32 days later
Published
- 31 days later
· 31 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.17% · top 93% of all CVEs (17 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected 144974e7f9e32b53b02f6c8632be45d8f43d6ab5 – < 91817ad5452defe69bc7bc0e355f0ed5d01125cc
- affected 144974e7f9e32b53b02f6c8632be45d8f43d6ab5 – < ce0caaed5940162780c5c223b8ae54968a5f059b
- affected 144974e7f9e32b53b02f6c8632be45d8f43d6ab5 – < 228b37936376143f4b60cc6828663f6eaceb81b5
- affected 144974e7f9e32b53b02f6c8632be45d8f43d6ab5 – < 3428dc5520c811e66622b2f5fa43341bf9a1f8b3
- affected 144974e7f9e32b53b02f6c8632be45d8f43d6ab5 – < 387ebb0453b99d71491419a5dc4ab4bee0cacbac
- affected 144974e7f9e32b53b02f6c8632be45d8f43d6ab5 – < 8479891d1f04a8ce55366fe4ca361ccdb96f02e1
- affected 3.3
- unaffected < 3.3
- unaffected 6.1.167 – ≤ 6.1.*
- unaffected 6.6.130 – ≤ 6.6.*
- unaffected 6.12.78 – ≤ 6.12.*
- unaffected 6.18.19 – ≤ 6.18.*
- unaffected 6.19.9 – ≤ 6.19.*
- unaffected 7.0 – ≤ *
References
References6
- https://git.kernel.org/stable/c/91817ad5452defe69bc7bc0e355f0ed5d01125cc (opens in a new tab)
- https://git.kernel.org/stable/c/ce0caaed5940162780c5c223b8ae54968a5f059b (opens in a new tab)
- https://git.kernel.org/stable/c/228b37936376143f4b60cc6828663f6eaceb81b5 (opens in a new tab)
- https://git.kernel.org/stable/c/3428dc5520c811e66622b2f5fa43341bf9a1f8b3 (opens in a new tab)
- https://git.kernel.org/stable/c/387ebb0453b99d71491419a5dc4ab4bee0cacbac (opens in a new tab)
- https://git.kernel.org/stable/c/8479891d1f04a8ce55366fe4ca361ccdb96f02e1 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-21361 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-31412)Record last updated .