CVE-2021-47344: media: zr364xx: fix memory leak in zr364xx_start_readpipe
In the Linux kernel, the following vulnerability has been resolved:
media: zr364xx: fix memory leak in zr364xx_start_readpipe
syzbot reported memory leak in zr364xx driver.
The problem was in non-freed urb in case of
usb_submit_urb() fail.
backtrace:
[<ffffffff82baedf6>] kmalloc include/linux/slab.h:561 [inline]
[<ffffffff82baedf6>] usb_alloc_urb+0x66/0xe0 drivers/usb/core/urb.c:74
[<ffffffff82f7cce8>] zr364xx_start_readpipe+0x78/0x130 drivers/media/usb/zr364xx/zr364xx.c:1022
[<ffffffff84251dfc>] zr364xx_board_init drivers/media/usb/zr364xx/zr364xx.c:1383 [inline]
[<ffffffff84251dfc>] zr364xx_probe+0x6a3/0x851 drivers/media/usb/zr364xx/zr364xx.c:1516
[<ffffffff82bb6507>] usb_probe_interface+0x177/0x370 drivers/usb/core/driver.c:396
[<ffffffff826018a9>] really_probe+0x159/0x500 drivers/base/dd.c:576
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel memory leak in the zr364xx USB media driver. If USB read-pipe setup fails, an allocated USB request block may not be freed. Business impact appears limited and mainly availability-related, but exact severity is not provided in the sources.
Executive priority
Treat as routine kernel hygiene unless your environment allows untrusted USB device access or relies on affected USB media hardware. There is no source evidence of active exploitation, but patched kernels should be adopted through normal maintenance.
Technical view
The flaw is in zr364xx_start_readpipe in drivers/media/usb/zr364xx/zr364xx.c. syzbot found that when usb_submit_urb() fails, the allocated URB is not released. Kernel stable references provide fixes across supported branches.
Likely exposure
Exposure is most relevant to Linux systems that include and load the zr364xx USB media driver, especially where matching USB camera hardware or untrusted USB devices can be connected. Server-only environments without this driver path are less likely exposed.
Exploitation context
The source bundle does not cite active exploitation, public weaponization, CVSS, or CISA KEV listing. The report comes from syzbot and describes a memory leak on an error path, not a remote attack path.
Researcher notes
The public record lacks CVSS, CWE, and exploit detail. Analysis should focus on driver reachability, kernel branch mapping, and whether vendor kernels have backported the stable patches rather than relying only on upstream version numbers.
Mitigation direction
Identify Linux systems using kernels listed as affected in the CVE source.
Check your distribution's kernel advisories for backported zr364xx fixes.
Update to a kernel package containing the referenced stable fixes.
Restrict untrusted physical USB access where vulnerable kernels cannot be updated.
Disable or avoid loading the zr364xx driver if it is unnecessary and supported by policy.
Validation and detection
Inventory kernel versions and vendor patch levels across Linux assets.
Check whether the zr364xx driver is built, installed, or loaded.
Confirm package changelogs include the CVE or referenced stable commits.
Prioritize systems with exposed USB ports or media-capture workloads.
Document exceptions where vendor fixes are unavailable or hardware requires older kernels.
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-47344 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.