CVE-2021-47367: virtio-net: fix pages leaking when building skb in big mode
In the Linux kernel, the following vulnerability has been resolved:
virtio-net: fix pages leaking when building skb in big mode
We try to use build_skb() if we had sufficient tailroom. But we forget
to release the unused pages chained via private in big mode which will
leak pages. Fixing this by release the pages after building the skb in
big mode.
Security readout for executives and security teams
Plain-English summary
CVE-2021-47367 is a Linux kernel virtio-net flaw where unused memory pages were not released in a specific packet-building path. The source rates it medium severity with local, low-complexity access required. Business urgency is highest for Linux systems using virtio networking, especially virtualized servers or hosts running affected kernel versions.
Executive priority
Treat this as a routine but real kernel remediation item, not an emergency. Prioritize patching internet-facing, multi-user, or virtualization-heavy Linux environments during the next kernel maintenance cycle, unless vendor guidance raises severity for your distribution.
Technical view
The vulnerable virtio-net path tries build_skb() when tailroom is sufficient, but in big mode it failed to release unused pages chained through private data. The CVE source lists CWE-119 and CVSS 3.1 score 5.5 with local attack vector, low complexity, low privileges, no user interaction, and high confidentiality impact.
Likely exposure
Exposure is most likely on Linux systems using the virtio-net driver with affected kernels. The bundle identifies Linux kernel 5.13-era versions and fixed stable references around 5.14.9 and 5.15, plus specific kernel stable commits. Exact distribution package impact requires vendor mapping.
Exploitation context
The source bundle does not show CISA KEV listing or public active exploitation evidence. The CVSS vector requires local access and low privileges, with no user interaction. No exploit technique or weaponized details are provided in the cited sources.
Researcher notes
Evidence is limited to the CVE record and two Linux stable commit references. The description supports a virtio-net page-release bug in big mode; it does not provide exploit details, affected distribution packages, or operational mitigations beyond applying fixed kernels.
Mitigation direction
Check kernel vendor advisories for CVE-2021-47367 applicability.
Upgrade affected Linux kernels to versions containing the referenced stable fixes.
Prioritize virtualized Linux systems using virtio-net networking.
Apply distribution-provided kernel packages rather than hand-applying commits when possible.
Track unresolved systems through normal vulnerability management exceptions.
Validation and detection
Inventory Linux kernel versions across virtualized and cloud workloads.
Identify hosts or guests using the virtio-net driver.
Compare running kernels with vendor-fixed versions for CVE-2021-47367.
Confirm whether kernel builds include the cited stable commits.
Document systems not using virtio-net as lower exposure.
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.
cwe · low confidence lookup
CWE-119: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
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.