CVE-2021-47111: xen-netback: take a reference to the RX task thread
In the Linux kernel, the following vulnerability has been resolved:
xen-netback: take a reference to the RX task thread
Do this in order to prevent the task from being freed if the thread
returns (which can be triggered by the frontend) before the call to
kthread_stop done as part of the backend tear down. Not taking the
reference will lead to a use-after-free in that scenario. Such
reference was taken before but dropped as part of the rework done in
2ac061ce97f4.
Reintroduce the reference taking and add a comment this time
explaining why it's needed.
This is XSA-374 / CVE-2021-28691.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel Xen networking bug. A Xen guest frontend can trigger a timing condition where the backend RX thread is freed before teardown completes, causing a use-after-free. The provided sources do not state active exploitation, CVSS severity, or full business impact.
Executive priority
Treat this as a targeted virtualization-host risk, not a general internet-facing application issue. Prioritize patch confirmation on Xen infrastructure, especially where guests are operated by less-trusted tenants or customers.
Technical view
CVE-2021-47111 fixes xen-netback by taking a reference to the RX task thread before backend teardown. Without that reference, a frontend-triggered thread return before kthread_stop can leave teardown using freed task memory. The record identifies this as XSA-374 / CVE-2021-28691.
Likely exposure
Exposure appears limited to Linux systems using Xen netback networking, especially virtualization hosts serving Xen guest frontends. The provided affected data references Linux 5.5 and fixes around 5.10.43, 5.12.10, and 5.13, but the version range details are incomplete in the bundle.
Exploitation context
The source says the condition can be triggered by the frontend, implying guest-to-backend interaction in Xen networking. No cited source in the bundle reports public exploitation, KEV listing, weaponized exploit availability, or a confirmed attacker outcome beyond use-after-free.
Researcher notes
The strongest evidence is the kernel commit description: a frontend-triggered RX thread return can race backend teardown and cause use-after-free. The bundle lacks CVSS, CWE, exploitability details, and distribution-specific fix status, so validation should rely on kernel commit/backport checks.
Mitigation direction
Identify Xen hosts using Linux xen-netback networking.
Prioritize kernel updates to versions containing the referenced stable fixes.
Check Linux distribution advisories for backported kernel fixes.
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-47111 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.