CVE-2021-47201: iavf: free q_vectors before queues in iavf_disable_vf
In the Linux kernel, the following vulnerability has been resolved:
iavf: free q_vectors before queues in iavf_disable_vf
iavf_free_queues() clears adapter->num_active_queues, which
iavf_free_q_vectors() relies on, so swap the order of these two function
calls in iavf_disable_vf(). This resolves a panic encountered when the
interface is disabled and then later brought up again after PF
communication is restored.
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue can cause a panic when an iavf network interface is disabled and later brought back after PF communication is restored. The business impact is likely availability disruption on systems using this driver, not confirmed data theft or privilege escalation.
Executive priority
Treat this as a targeted availability risk. Prioritize patching where iavf-backed networking supports production workloads, but there is no sourced evidence of active exploitation or broad remote compromise.
Technical view
The bug is an ordering error in iavf_disable_vf(): iavf_free_queues() clears adapter->num_active_queues before iavf_free_q_vectors() uses it. The resolved change frees q_vectors before queues, preventing a panic during the disable and later re-enable path after PF communication returns.
Likely exposure
Exposure is most relevant to Linux systems using the iavf driver and affected kernel builds, especially virtualized or SR-IOV environments where VF interfaces may be disabled, reset, or recover PF communication.
Exploitation context
The provided sources do not show active exploitation, and the CVE is not listed as KEV. Evidence points to a reliability-triggered kernel panic condition under specific network driver state transitions.
Researcher notes
The source data provides no CVSS, CWE, exploit evidence, or detailed attacker model. Analysis should stay scoped to the documented kernel panic caused by cleanup order in iavf_disable_vf().
Mitigation direction
Apply kernel or distribution updates containing the referenced stable fixes.
Confirm whether your vendor backported the iavf ordering fix.
Prioritize systems using iavf virtual functions or affected kernel versions.
Monitor vendor advisories for exact fixed package versions.
Test network interface disable, reset, and recovery workflows after updating.
Validation and detection
Inventory Linux hosts for affected kernel versions and iavf driver usage.
Review crash logs for iavf-related panics during VF disable or recovery.
Confirm updated source or package includes the q_vectors-before-queues fix.
Validate that PF communication recovery no longer triggers host panic.
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-47201 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.