Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2021-47170USB: usbfs: Don't WARN about excessively large memory allocations

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 2 years 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

CVSS scores of CVE-2021-47170, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.24% · top 85% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected add1aaeabe6b08ed26381a2a06e505b2f09c3ba5 – < 2ab21d6e1411999b5fb43434f421f00bf50002eb
    • affected add1aaeabe6b08ed26381a2a06e505b2f09c3ba5 – < 2c835fede13e03f2743a333e4370b5ed2db91e83
    • affected add1aaeabe6b08ed26381a2a06e505b2f09c3ba5 – < 8d83f109e920d2776991fa142bb904d985dca2ed
    • affected add1aaeabe6b08ed26381a2a06e505b2f09c3ba5 – < 9f7cb3f01a10d9064cf13b3d26fb7e7a5827d098
    • affected add1aaeabe6b08ed26381a2a06e505b2f09c3ba5 – < 4f2629ea67e7225c3fd292c7fe4f5b3c9d6392de
  • Linux · Linux

    • affected 3.3
    • unaffected < 3.3
    • unaffected 4.19.193 – ≤ 4.19.*
    • unaffected 5.4.124 – ≤ 5.4.*
    • unaffected 5.10.42 – ≤ 5.10.*
    • unaffected 5.12.9 – ≤ 5.12.*
    • unaffected 5.13 – ≤ *

References

References5

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2021-47170 badge
[![CVE-2021-47170](https://cveledger.app/badge/CVE-2021-47170.svg)](https://cveledger.app/cve/CVE-2021-47170)

Record last updated .