CVE-2021-47159: net: dsa: fix a crash if ->get_sset_count() fails
In the Linux kernel, the following vulnerability has been resolved:
net: dsa: fix a crash if ->get_sset_count() fails
If ds->ops->get_sset_count() fails then it "count" is a negative error
code such as -EOPNOTSUPP. Because "i" is an unsigned int, the negative
error code is type promoted to a very high value and the loop will
corrupt memory until the system crashes.
Fix this by checking for error codes and changing the type of "i" to
just int.
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue can crash systems using the Distributed Switch Architecture network stack when a driver reports an error while counting statistic strings. The available sources describe memory corruption leading to a system crash, not confirmed data theft or remote compromise.
Executive priority
Treat this as a targeted kernel stability risk, especially for network appliances and embedded Linux systems. Prioritize patch validation where DSA hardware is present; broad emergency response is not supported by the provided evidence.
Technical view
The bug is in Linux net/dsa statistics handling. A negative get_sset_count() error can be promoted during comparison with an unsigned loop variable, creating an extremely large loop bound and corrupting memory until the kernel crashes. Stable kernel commits add error checking and change the loop index type.
Likely exposure
Exposure is most likely on Linux systems using DSA-capable networking hardware or drivers in affected kernel ranges. General Linux fleets should validate kernel backports rather than relying only on upstream version numbers.
Exploitation context
The source bundle does not show CISA KEV listing, public exploitation, exploit code, or a remote attack path. The documented impact is memory corruption and crash when the vulnerable DSA code path receives a failing get_sset_count() result.
Researcher notes
Evidence is limited to the CVE record and upstream stable commit references. There is no CVSS, CWE, KEV entry, or exploit confirmation in the bundle. Validate exact affected status through downstream kernel backports and device configuration.
Mitigation direction
Update to a vendor kernel containing the referenced upstream stable fixes.
Confirm distribution advisories or changelogs include CVE-2021-47159 or the fix commits.
Prioritize systems using DSA switch hardware or related kernel drivers.
If patching is delayed, check vendor guidance for supported operational mitigations.
Validation and detection
Inventory Linux kernel versions and vendor backport status across affected hosts.
Identify hosts with DSA networking support, switch drivers, or embedded network appliances.
Verify installed kernel source or package changelog contains the referenced fix commits.
Review crash logs for kernel faults around net/dsa statistics paths.
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-47159 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.