CVE-2021-47310: net: ti: fix UAF in tlan_remove_one
In the Linux kernel, the following vulnerability has been resolved:
net: ti: fix UAF in tlan_remove_one
priv is netdev private data and it cannot be
used after free_netdev() call. Using priv after free_netdev()
can cause UAF bug. Fix it by moving free_netdev() at the end of the
function.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel memory-safety issue in the TI network driver cleanup path. The driver could use private network-device data after it had been freed, creating a use-after-free condition. The source bundle does not provide CVSS, practical impact, or exploitation evidence.
Executive priority
Track this as a kernel hygiene and asset-exposure item until impact details are clearer. It should rise in priority where affected kernels are deployed on exposed or hard-to-patch systems, but the provided evidence does not support emergency treatment.
Technical view
CVE-2021-47310 fixes tlan_remove_one by moving free_netdev() to the end of the function. The issue is a use-after-free involving netdev private data after free_netdev(). Affected Linux versions listed include 3.10 through 5.14, with multiple stable kernel commit references.
Likely exposure
Exposure is most likely on systems running affected Linux kernel builds that include the relevant TI tlan network driver code. The bundle does not state whether the driver must be loaded, whether specific hardware is required, or whether distributions backported the fix.
Exploitation context
The source bundle marks KEV as false and provides no cited evidence of active exploitation. It also does not describe attack vector, privileges required, reliability, or post-exploitation impact. Treat exploitation status as unknown, not confirmed.
Researcher notes
The core bug is lifetime ordering: priv is netdev private data and cannot safely be used after free_netdev(). The published fix reorders cleanup so free_netdev() occurs last. The bundle lacks CVSS, CWE, exploitability analysis, and distribution-specific affected package data.
Mitigation direction
Update affected Linux kernels using vendor-supported packages or fixed stable branches.
Check distribution advisories for backported fixes tied to the referenced kernel commits.
Prioritize systems where the TI tlan driver is present or enabled.
Avoid inventing compensating controls; follow kernel or distribution guidance.
Validation and detection
Inventory Linux kernel versions across servers, appliances, and embedded systems.
Check whether kernel packages include one of the referenced stable fixes or vendor backports.
Identify systems with the tlan driver built, installed, or loaded.
Confirm remediation through package metadata, kernel changelogs, or vendor advisory mapping.
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-47310 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.