CVE-2021-47514: devlink: fix netns refcount leak in devlink_nl_cmd_reload()
In the Linux kernel, the following vulnerability has been resolved:
devlink: fix netns refcount leak in devlink_nl_cmd_reload()
While preparing my patch series adding netns refcount tracking,
I spotted bugs in devlink_nl_cmd_reload()
Some error paths forgot to release a refcount on a netns.
To fix this, we can reduce the scope of get_net()/put_net()
section around the call to devlink_reload().
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel resource-management bug. Failed devlink reload handling could leave network namespace references unreleased, potentially causing resource retention or stability issues. The source bundle provides no CVSS score, exploitation evidence, or business-impact detail.
Executive priority
Treat as a kernel maintenance item unless local exposure analysis shows critical systems remain on affected builds. There is no sourced evidence of active exploitation, but kernel resource leaks can affect reliability.
Technical view
devlink_nl_cmd_reload() acquired a network namespace reference with get_net(), but some error paths failed to release it with put_net(). The referenced stable fixes reduce the get_net()/put_net() scope around devlink_reload() to prevent the refcount leak.
Likely exposure
Exposure is limited to Linux systems running affected kernel builds listed in the source bundle, including 5.10, 5.10.85, 5.15.8, and 5.16. Distribution backports may change practical exposure.
Exploitation context
No active exploitation is supported by the bundle. KEV is false, and the provided sources do not include exploit reports, prerequisites, proof-of-concept details, or attack-path information.
Researcher notes
The available record is sparse: no CVSS, CWE, privilege model, or trigger conditions are provided. Analysis should focus on kernel provenance, stable-branch patch inclusion, and whether local builds contain the vulnerable devlink code path.
Mitigation direction
Update affected Linux kernels to vendor builds containing the referenced stable fixes.
Check Linux distribution advisories for backported fixes covering CVE-2021-47514.
Prioritize systems running affected kernel versions until package status is confirmed.
If patching is delayed, follow vendor guidance; no specific workaround is provided.
Validation and detection
Inventory Linux kernel versions across servers, appliances, and container hosts.
Confirm whether installed kernels include the referenced devlink refcount fix commits.
Review distribution changelogs for CVE-2021-47514 or equivalent stable backports.
Track unresolved systems until they are patched or proven unaffected.
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-47514 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.