CVE-2021-47170

USB: usbfs: Don't WARN about excessively large memory allocations

MEDIUM
5.5
CVSS Score
Published: March 25, 2024 at 09:16 AM UTC
Updated: June 17, 2026 at 04:16 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: USB: usbfs: Don't WARN about excessively large memory allocations Syzbot found that the kernel generates a WARNing if the user tries to submit a bulk transfer through usbfs with a buffer that is way too large. This isn't a bug in the kernel; it's merely an invalid request from the user and the usbfs code does handle it correctly. In theory the same thing can happen with async transfers, or with the packet descriptor table for isochronous transfers. To prevent the MM subsystem from complaining about these bad allocation requests, add the __GFP_NOWARN flag to the kmalloc calls for these buffers.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 4.19.1933.3 ≤ v < 4.19.1933.3 ≤ v < 5.10.423.3 ≤ v < 5.12.93.3 ≤ v < 5.133.3 ≤ v < 5.4.1244.20 ≤ v < 5.4.1245.11 ≤ v < 5.12.95.5 ≤ v < 5.10.425.13 rc15.13 rc25.13 rc3add1aaeabe6b08ed26381a2a06e505b2f09c3ba5
Vendor states this is fixed in 2ab21d6e1411999b5fb43434f421f00bf50002eb (fixed)
Vendor states this is fixed in 2c835fede13e03f2743a333e4370b5ed2db91e83 (fixed)
Vendor states this is fixed in 4f2629ea67e7225c3fd292c7fe4f5b3c9d6392de (fixed)
Vendor states this is fixed in 8d83f109e920d2776991fa142bb904d985dca2ed (fixed)
Vendor states this is fixed in 9f7cb3f01a10d9064cf13b3d26fb7e7a5827d098 (fixed)
Vendor states this is fixed in 3.3 (unaffected)
Vendor states this is fixed in 4.19.193 (unaffected)
Vendor states this is fixed in 5.10.42 (unaffected)
Vendor states this is fixed in 5.12.9 (unaffected)
Vendor states this is fixed in 5.13 (unaffected)
Vendor states this is fixed in 5.4.124 (unaffected)

References (5)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/2ab21d6e1411999b5fb43434f421f00bf50002eb
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/2c835fede13e03f2743a333e4370b5ed2db91e83
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/4f2629ea67e7225c3fd292c7fe4f5b3c9d6392de
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/8d83f109e920d2776991fa142bb904d985dca2ed
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/9f7cb3f01a10d9064cf13b3d26fb7e7a5827d098

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-770

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card