CVE-2021-47070: uio_hv_generic: Fix another memory leak in error handling paths
In the Linux kernel, the following vulnerability has been resolved:
uio_hv_generic: Fix another memory leak in error handling paths
Memory allocated by 'vmbus_alloc_ring()' at the beginning of the probe
function is never freed in the error handling path.
Add the missing 'vmbus_free_ring()' call.
Note that it is already freed in the .remove function.
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue is a memory leak in an error path of the uio_hv_generic driver. If probing the device fails, memory allocated for a VMBus ring was not released. The CVE is rated medium and requires local low-privilege access, so it is mainly a host hardening and patch management concern.
Executive priority
Treat this as routine but necessary kernel maintenance, not an emergency. Prioritize systems with shared local users, virtualization exposure, or strict data isolation requirements. There is no source-provided evidence of active exploitation, but kernel flaws should be closed during the next controlled patch cycle.
Technical view
The vulnerable probe path allocates memory with vmbus_alloc_ring() but omits vmbus_free_ring() when later error handling runs. Upstream stable fixes add the missing free call. The source bundle lists Linux kernel versions/commits as affected and references stable kernel commits plus a Debian LTS announcement.
Likely exposure
Exposure is most likely on Linux systems running affected kernel builds where the uio_hv_generic driver and VMBus-related probing are relevant. The bundle does not prove broad internet exposure or remote reachability. Confirm exposure through kernel version, distribution advisory status, and whether this driver can load or is present.
Exploitation context
The CVSS vector indicates local access, low attack complexity, low privileges, no user interaction, unchanged scope, and high confidentiality impact. The source bundle marks CISA KEV as false and provides no cited evidence of active exploitation or public exploit availability.
Researcher notes
The key evidence is the upstream description: an error-handling leak after vmbus_alloc_ring() in uio_hv_generic probe, fixed by adding vmbus_free_ring(). The CVSS confidentiality impact appears high, but the provided description does not explain the data exposure path. Avoid overclaiming beyond local, low-privilege prerequisites.
Mitigation direction
Update affected Linux kernels through vendor-supported packages or stable kernel fixes.
Review Debian LTS or your distribution advisory for package-specific fixed versions.
Restrict unnecessary local user access on affected systems until updates are applied.
Disable or avoid loading unneeded drivers only if supported by vendor guidance.
Track kernel advisories for any revised impact or backport information.
Validation and detection
Inventory Linux kernel versions across servers, guests, and images.
Check whether uio_hv_generic is present, loadable, or in use.
Compare installed kernel packages against vendor fixed-version advisories.
Confirm updates include one of the referenced stable fixes or downstream backports.
Reboot into the updated kernel and verify the running version.
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-47070 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.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.