usb: gadget: f_mass_storage: Fix potential integer overflow in check_command_size_in_blocks()
Summary
| CVE | CVE-2026-31412 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-04-10 11:16:22 UTC |
| Updated | 2026-04-13 15:02:06 UTC |
| 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. |
Risk And Classification
EPSS: 0.000100000 probability, percentile 0.011210000 (date 2026-04-15)
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected 144974e7f9e32b53b02f6c8632be45d8f43d6ab5 91817ad5452defe69bc7bc0e355f0ed5d01125cc git | Not specified |
| CNA | Linux | Linux | affected 144974e7f9e32b53b02f6c8632be45d8f43d6ab5 ce0caaed5940162780c5c223b8ae54968a5f059b git | Not specified |
| CNA | Linux | Linux | affected 144974e7f9e32b53b02f6c8632be45d8f43d6ab5 228b37936376143f4b60cc6828663f6eaceb81b5 git | Not specified |
| CNA | Linux | Linux | affected 144974e7f9e32b53b02f6c8632be45d8f43d6ab5 3428dc5520c811e66622b2f5fa43341bf9a1f8b3 git | Not specified |
| CNA | Linux | Linux | affected 144974e7f9e32b53b02f6c8632be45d8f43d6ab5 387ebb0453b99d71491419a5dc4ab4bee0cacbac git | Not specified |
| CNA | Linux | Linux | affected 144974e7f9e32b53b02f6c8632be45d8f43d6ab5 8479891d1f04a8ce55366fe4ca361ccdb96f02e1 git | Not specified |
| CNA | Linux | Linux | affected 3.3 | Not specified |
| CNA | Linux | Linux | unaffected 3.3 semver | Not specified |
| CNA | Linux | Linux | unaffected 6.1.167 6.1.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.6.130 6.6.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.78 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.18.19 6.18.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.19.9 6.19.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.0 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/8479891d1f04a8ce55366fe4ca361ccdb96f02e1 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/228b37936376143f4b60cc6828663f6eaceb81b5 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/387ebb0453b99d71491419a5dc4ab4bee0cacbac | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/3428dc5520c811e66622b2f5fa43341bf9a1f8b3 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/91817ad5452defe69bc7bc0e355f0ed5d01125cc | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/ce0caaed5940162780c5c223b8ae54968a5f059b | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.