Security readout for executives and security teams
Plain-English summary
This is a Linux kernel memory-safety bug in packet fragmentation handling for the traffic-control conntrack action. In the reported case, it caused a kernel crash during fragment cleanup. Business urgency depends on whether affected kernels use act_ct with fragmented traffic; the bundle provides no CVSS score or active exploitation evidence.
Executive priority
Handle as a targeted kernel stability risk, not a broad emergency based on current evidence. Prioritize internet-facing or high-throughput network nodes using act_ct, and fold remediation into kernel maintenance unless local exposure is confirmed.
Technical view
When tcf_ct_handle_fragments() temporarily stores an IP fragment and returns -EINPROGRESS, act_ct could restore skb qdisc control-block data and corrupt FRAG_CB(). Later inet_frag_rbtree_purge could dereference invalid memory, producing KASAN wild-memory-access and crash evidence.
Likely exposure
Exposure is most likely on Linux systems running affected kernel versions that use net/sched act_ct for connection tracking and process IP fragments. Systems not using this kernel path are less likely exposed. The source bundle does not identify distributions, configurations, or cloud products.
Exploitation context
The bundle says KEV is false and gives no evidence of active exploitation. The only demonstrated context is testing of reassembly and refragmentation using act_ct that produced a crash. Treat exploitability beyond denial of service as unproven from these sources.
Researcher notes
Key condition is act_ct fragment handling returning -EINPROGRESS, followed by qdisc skb control-block restoration corrupting fragment metadata. The source data lacks CVSS, CWE, exploit details, and distribution-specific affected ranges, so validation should be configuration-led.
Mitigation direction
Update to a vendor-supported Linux kernel containing the referenced stable fixes.
Prioritize systems using traffic-control conntrack actions with fragmented traffic exposure.
Check distribution advisories for backported fixes before relying on upstream version numbers.
Reduce unnecessary exposure of fragment-heavy traffic paths where operationally feasible.
Validation and detection
Inventory Linux kernel versions across affected hosts.
Confirm whether traffic-control rules use act_ct on those hosts.
Verify vendor kernel changelogs include the referenced upstream stable commits.
Review crash telemetry for inet_frag_rbtree_purge or related KASAN reports.
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-47014 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.