CVE-2021-47143: net/smc: remove device from smcd_dev_list after failed device_add()
In the Linux kernel, the following vulnerability has been resolved:
net/smc: remove device from smcd_dev_list after failed device_add()
If the device_add() for a smcd_dev fails, there's no cleanup step that
rolls back the earlier list_add(). The device subsequently gets freed,
and we end up with a corrupted list.
Add some error handling that removes the device from the list.
Security readout for executives and security teams
Plain-English summary
A Linux kernel bug can corrupt an internal SMC-D device list when adding a device fails. The failed device is freed but remains linked in the list. The provided sources do not state severity, exploitability, business impact, or any observed attacks.
Executive priority
Handle through kernel patch management rather than emergency response unless internal evidence shows SMC-D use on exposed or high-criticality systems. The absence of severity, CVSS, and exploitation evidence lowers confidence in urgency, not in the existence of the bug.
Technical view
In net/smc, an smcd_dev was added to smcd_dev_list before device_add(). If device_add() failed, cleanup did not remove the list entry before freeing the device, leaving a corrupted list. The referenced stable commits add error handling to remove the device from the list.
Likely exposure
Exposure appears limited to Linux systems running affected kernel versions or commits that include this net/smc SMC-D error path. The bundle lists Linux 4.19, 5.10.42, 5.12.9, and 5.13 as affected, but gives incomplete version-range detail.
Exploitation context
No active exploitation is stated. The CVE is not marked KEV, and the provided sources do not describe a public exploit, trigger conditions, required privileges, or remote reachability. Treat exploitation context as incomplete.
Researcher notes
Evidence supports a cleanup flaw causing list corruption after device_add() failure. The bundle does not identify CWE, CVSS, attacker model, crashability, privilege requirements, or affected distribution packages. Avoid claiming denial of service or code execution without additional vendor evidence.
Mitigation direction
Apply Linux stable or distribution kernel updates containing the referenced fixes.
Check vendor kernel advisories for exact affected and fixed package versions.
Prioritize systems using affected Linux kernel branches or net/smc functionality.
Use normal maintenance controls where SMC-D is not present or used.
Validation and detection
Inventory Linux kernel versions across production and edge systems.
Confirm whether kernels include one of the referenced stable fix commits.
Check distribution changelogs for CVE-2021-47143 backports.
Review whether net/smc or SMC-D support is enabled on relevant systems.
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-47143 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.