CVE-2021-47159: net: dsa: fix a crash if ->get_sset_count() fails
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.24% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 0f2cb08c57edefb0e7b5045e0e3e9980a3d3aa37, 7b22466648a4f8e3e94f57ca428d1531866d1373, a269333fa5c0c8e53c92b5a28a6076a28cde3e83.
- Severity is disputed: the assigning authority (CNA) scores it 7.8, NVD 5.5.
Low priority for now. Upgrade to Linux Linux 0f2cb08c57edefb0e7b5045e0e3e9980a3d3aa37, 7b22466648a4f8e3e94f57ca428d1531866d1373, a269333fa5c0c8e53c92b5a28a6076a28cde3e83 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Mar 25, 2024
- Updated
- Aug 5, 2026
- EPSS
- 0.2% · 16th percentile
- CWE
- CWE-835
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 5.5
- CNA · Linux
- 7.8
- 2.3 point gap
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel4.7 and later · before 4.19.193
- linux linux kernel4.20 and later · before 5.4.124
- linux linux kernel5.5 and later · before 5.10.42
- linux linux kernel5.11 and later · before 5.12.9
- linux linux kernel5.13
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.7affected
- badf3ada60ab8f76f9488dc8f5c0c57f70682f5a and later · before 0f2cb08c57edefb0e7b5045e0e3e9980a3d3aa37affected · git
- badf3ada60ab8f76f9488dc8f5c0c57f70682f5a and later · before ce5355f140a7987011388c7e30c4f8fbe180d3e8affected · git
- badf3ada60ab8f76f9488dc8f5c0c57f70682f5a and later · before caff86f85512b8e0d9830e8b8b0dfe13c68ce5b6affected · git
- badf3ada60ab8f76f9488dc8f5c0c57f70682f5a and later · before 7b22466648a4f8e3e94f57ca428d1531866d1373affected · git
- badf3ada60ab8f76f9488dc8f5c0c57f70682f5a and later · before a269333fa5c0c8e53c92b5a28a6076a28cde3e83affected · git
- before 4.7not affected · semver
- 4.19.193 and later · up to and including 4.19.*not affected · semver
- 5.4.124 and later · up to and including 5.4.*not affected · semver
- 5.10.42 and later · up to and including 5.10.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 5.14.6-1 | 5.14.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2021-47153Mar 25, 2024 · i2c: i801: Don't generate an interrupt on bus reset28Monitor
- ← EarlierCVE-2021-47158Mar 25, 2024 · net: dsa: sja1105: add error handling in sja1105_setup()22Monitor
- Later →CVE-2021-47160Mar 25, 2024 · net: dsa: mt7530: fix VLAN traffic leaks28Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 0f2cb08c57edefb0e7b5045e0e3e9980a3d3aa37 | Vendor (CNA) |
| Linux Linux | 7b22466648a4f8e3e94f57ca428d1531866d1373 | Vendor (CNA) |
| Linux Linux | a269333fa5c0c8e53c92b5a28a6076a28cde3e83 | Vendor (CNA) |
| Linux Linux | caff86f85512b8e0d9830e8b8b0dfe13c68ce5b6 | Vendor (CNA) |
| Linux Linux | ce5355f140a7987011388c7e30c4f8fbe180d3e8 | Vendor (CNA) |
| debian:linux | 5.14.6-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2024-2703237 days apartf2fs: fix to avoid potential panic during recovery25Monitor
- CVE-2022-4863534 days apartfsdax: Fix infinite loop in dax_iomap_rw()24Monitor
- CVE-2023-526358 days apartPM / devfreq: Synchronize devfreq_monitor_[start/stop]22Monitor
- CVE-2024-266818 days apartnetdevsim: avoid potential loop in nsim_dev_trap_report_work()22Monitor
- CVE-2024-2678010 days apartaf_unix: Fix task hung while purging oob_skb in GC.22Monitor
- CVE-2022-4863020 days apartcrypto: qcom-rng - fix infinite loop on requests not multiple of WORD_SZ22Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-835 · Loop with Unreachable Exit Condition ('Infinite Loop')CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.