CVE-2021-47294: netrom: Decrease sock refcount when sock timers expire
In the Linux kernel, the following vulnerability has been resolved:
netrom: Decrease sock refcount when sock timers expire
Commit 63346650c1a9 ("netrom: switch to sock timer API") switched to use
sock timer API. It replaces mod_timer() by sk_reset_timer(), and
del_timer() by sk_stop_timer().
Function sk_reset_timer() will increase the refcount of sock if it is
called on an inactive timer, hence, in case the timer expires, we need to
decrease the refcount ourselves in the handler, otherwise, the sock
refcount will be unbalanced and the sock will never be freed.
Security readout for executives and security teams
Plain-English summary
CVE-2021-47294 is a Linux kernel NET/ROM socket lifecycle bug. When certain socket timers expire, the kernel can fail to drop a reference count, so affected sockets are never freed. The source does not provide CVSS, impact scoring, or confirmed attack conditions.
Executive priority
Handle through normal kernel patch governance unless NET/ROM is used in production or kernel provenance is uncertain. The business concern is resource leakage and potential availability impact, but severity and exploitation details are not established in the source.
Technical view
A prior change moved NET/ROM to the sock timer API. sk_reset_timer() can increment a socket reference when called on an inactive timer. The timer handler did not decrement that reference on expiry, creating an unbalanced refcount and preventing socket cleanup.
Likely exposure
Exposure appears limited to Linux systems running affected kernel versions with the NET/ROM code path in use. The source lists affected Linux versions and stable fixes, but does not state whether exploitation is local, remote, authenticated, or default-enabled.
Exploitation context
No active exploitation is cited, and the CVE is not marked KEV. The public source describes a kernel resource cleanup defect, not an exploit technique. Treat exploitability and attacker preconditions as unconfirmed from the provided evidence.
Researcher notes
The key condition is refcount imbalance after sk_reset_timer() on inactive NET/ROM socket timers. The provided data supports a kernel memory/resource leak conclusion, but does not establish reachability, privilege requirements, crash behavior, or practical denial-of-service impact.
Mitigation direction
Update to a vendor kernel containing the referenced stable NET/ROM fixes.
Check Linux distribution advisories for backported fixed package versions.
Prioritize hosts using NET/ROM or custom kernels with NET/ROM enabled.
Track this as unresolved where kernel provenance or backport status is unclear.
Validation and detection
Inventory Linux kernel versions across exposed and internally managed systems.
Confirm whether kernels include the referenced stable commits or distro backports.
Identify systems with NET/ROM support enabled or operationally required.
Review vendor advisories for affected package names and fixed release numbers.
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-47294 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.