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-46986usb: dwc3: gadget: Free gadget structure only after freeing endpoints

Description

In the Linux kernel, the following vulnerability has been resolved: usb: dwc3: gadget: Free gadget structure only after freeing endpoints As part of commit e81a7018d93a ("usb: dwc3: allocate gadget structure dynamically") the dwc3_gadget_release() was added which will free the dwc->gadget structure upon the device's removal when usb_del_gadget_udc() is called in dwc3_gadget_exit(). However, simply freeing the gadget results a dangling pointer situation: the endpoints created in dwc3_gadget_init_endpoints() have their dep->endpoint.ep_list members chained off the list_head anchored at dwc->gadget->ep_list. Thus when dwc->gadget is freed, the first dwc3_ep in the list now has a dangling prev pointer and likewise for the next pointer of the dwc3_ep at the tail of the list. The dwc3_gadget_free_endpoints() that follows will result in a use-after-free when it calls list_del(). This was caught by enabling KASAN and performing a driver unbind. The recent commit 568262bf5492 ("usb: dwc3: core: Add shutdown callback for dwc3") also exposes this as a panic during shutdown. There are a few possibilities to fix this. One could be to perform a list_del() of the gadget->ep_list itself which removes it from the rest of the dwc3_ep chain. Another approach is what this patch does, by splitting up the usb_del_gadget_udc() call into its separate "del" and "put" components. This allows dwc3_gadget_free_endpoints() to be called before the gadget is finally freed with usb_put_gadget().

Timeline

  1. ID reserved

    By Linux

  2. · 1 day later

    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-46986, 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.23% · top 86% of all CVEs (18 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 e81a7018d93a7de31a3f121c9a7eecd0a5ec58b0 – < 1ea775021282d90e1d08d696b7ab54aa75d688e5
    • affected e81a7018d93a7de31a3f121c9a7eecd0a5ec58b0 – < bc0cdd72493236fb72b390ad38ce581e353c143c
    • affected e81a7018d93a7de31a3f121c9a7eecd0a5ec58b0 – < b4b8e9601d7ee8806d2687f081a42485d27674a1
    • affected e81a7018d93a7de31a3f121c9a7eecd0a5ec58b0 – < bb9c74a5bd1462499fe5ccb1e3c5ac40dcfa9139
  • Linux · Linux

    • affected 5.10
    • unaffected < 5.10
    • unaffected 5.10.38 – ≤ 5.10.*
    • unaffected 5.11.22 – ≤ 5.11.*
    • unaffected 5.12.5 – ≤ 5.12.*
    • unaffected 5.13 – ≤ *

References

References4

Sources

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

Badge for a README or a ticket

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

Record last updated .