LiveActive security incident?Get immediate response
CVE Record

CVE-2021-46930: usb: mtu3: fix list_head check warning

In the Linux kernel, the following vulnerability has been resolved: usb: mtu3: fix list_head check warning This is caused by uninitialization of list_head. BUG: KASAN: use-after-free in __list_del_entry_valid+0x34/0xe4 Call trace: dump_backtrace+0x0/0x298 show_stack+0x24/0x34 dump_stack+0x130/0x1a8 print_address_description+0x88/0x56c __kasan_report+0x1b8/0x2a0 kasan_report+0x14/0x20 __asan_load8+0x9c/0xa0 __list_del_entry_valid+0x34/0xe4 mtu3_req_complete+0x4c/0x300 [mtu3] mtu3_gadget_stop+0x168/0x448 [mtu3] usb_gadget_unregister_driver+0x204/0x3a0 unregister_gadget_item+0x44/0xa4

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2021-46930 is a Linux kernel issue in the mtu3 USB gadget driver. The bug can trigger a use-after-free warning because a list_head was not initialized correctly. The sources do not provide CVSS, real-world impact, or active exploitation evidence, so business urgency depends on whether exposed systems use this driver and affected kernel versions.

Executive priority

Handle through normal kernel patch governance, with higher priority for appliances, embedded systems, or USB gadget deployments using mtu3. There is insufficient source evidence to justify emergency response solely for exploitation risk.

Technical view

The source describes an uninitialized list_head leading to a KASAN-reported use-after-free in __list_del_entry_valid during mtu3_req_complete, reached while stopping/unregistering the mtu3 USB gadget driver. The issue is marked resolved in Linux stable commits, but the bundle does not include a CVSS score, CWE, or detailed exploitability analysis.

Likely exposure

Exposure appears limited to Linux systems running affected kernels with the mtu3 USB gadget driver present or enabled. The provided version data identifies Linux kernel 5.2 and related stable lines through listed affected versions, but exact downstream distribution exposure requires vendor kernel mapping.

Exploitation context

The bundle shows no KEV listing and provides no cited evidence of active exploitation. The available evidence is a kernel bug report and stable fix references, not public exploitation details. Treat exploitability and attack preconditions as unconfirmed from the supplied sources.

Researcher notes

Useful follow-up is code and distribution mapping: determine which kernel branches include the stable commits and whether downstream kernels backported them. The source bundle does not define attacker control, privilege requirements, or reachable configurations.

Mitigation direction

  • Map systems to Linux kernel versions and enabled mtu3 USB gadget support.
  • Apply vendor or upstream Linux stable updates containing the referenced fixes.
  • Check distribution advisories for backported kernel fixes before relying on version numbers alone.
  • Prioritize embedded or USB gadget-capable Linux devices where mtu3 is enabled.

Validation and detection

  • Confirm whether the running kernel includes or loads the mtu3 driver.
  • Compare installed kernel packages against vendor advisories for CVE-2021-46930.
  • Review kernel logs for KASAN or list corruption reports involving mtu3.
  • Verify patched kernels include the referenced stable commits or downstream equivalents.
Prepared
Confidence
medium
Sources
6

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2021-46930 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
2ADP providers
5Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux83374e035b6286731c5aa617844c7b724294c2a7, 83374e035b6286731c5aa617844c7b724294c2a7, 83374e035b6286731c5aa617844c7b724294c2a7, 83374e035b6286731c5aa617844c7b724294c2a7unaffected
LinuxLinux5.2, 0, 5.4.170, 5.10.90, 5.15.13, 5.16affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.