CVE-2021-47105: ice: xsk: return xsk buffers back to pool when cleaning the ring
In the Linux kernel, the following vulnerability has been resolved:
ice: xsk: return xsk buffers back to pool when cleaning the ring
Currently we only NULL the xdp_buff pointer in the internal SW ring but
we never give it back to the xsk buffer pool. This means that buffers
can be leaked out of the buff pool and never be used again.
Add missing xsk_buff_free() call to the routine that is supposed to
clean the entries that are left in the ring so that these buffers in the
umem can be used by other sockets.
Also, only go through the space that is actually left to be cleaned
instead of a whole ring.
Security readout for executives and security teams
Plain-English summary
CVE-2021-47105 is a Linux kernel availability issue in the ice XSK buffer cleanup path. Some packet buffers are removed from the driver ring but not returned to the XSK buffer pool, so they can become unavailable for reuse. The source bundle does not provide CVSS, CWE, or evidence of active exploitation.
Executive priority
Treat as moderate operational priority when affected Linux networking workloads are present. For general Linux estates without ice/XSK usage evidence, urgency is lower but still requires normal kernel maintenance tracking.
Technical view
The ice driver cleanup routine NULLs an internal xdp_buff pointer without calling xsk_buff_free(), leaking buffers from the XSK UMEM pool. The fix returns leftover buffers to the pool and limits cleanup to entries actually remaining in the ring.
Likely exposure
Exposure is most likely on Linux systems running affected kernel builds that use the ice driver with XSK/AF_XDP buffer pools. The provided affected-version data is incomplete and should be verified against distribution kernel advisories.
Exploitation context
The bundle marks KEV as false and provides no public exploitation evidence. The practical risk appears availability-focused: repeated buffer loss could reduce usable packet buffers and disrupt workloads relying on XSK networking.
Researcher notes
Evidence is limited to the CVE description and Linux stable references. No CVSS vector, CWE, exploit status, or distribution-specific package fix is supplied, so exposure validation should focus on kernel version, driver usage, and presence of the cleanup fix.
Mitigation direction
Check vendor or distribution advisories for fixed kernel packages.
Prioritize updates on hosts using the ice driver with XSK workloads.
Track whether referenced stable commits are included in deployed kernels.
If updates are delayed, monitor affected hosts for packet processing degradation.
Validation and detection
Inventory Linux kernel versions on systems using the ice driver.
Confirm whether AF_XDP or XSK buffer pools are used in production.
Compare deployed kernel source or changelog with the referenced stable commits.
Review operational telemetry for recurring buffer exhaustion or network degradation.
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-47105 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.