CVE-2024-49977: net: stmmac: Fix zero-division error when disabling tc cbs
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 03582f4752427f60817d896f1a827aff772bd31e, 5.10.227, 5.15.168; azl3 kernel 6.6.51.1-5 on Azure Linux 3.0 6.6.57.1-2; azl3 kernel 6.6.57.1-2 on Azure Linux 3.0 6.6.57.1-2.
Low priority for now. Upgrade to Linux Linux 03582f4752427f60817d896f1a827aff772bd31e, 5.10.227, 5.15.168; azl3 kernel 6.6.51.1-5 on Azure Linux 3.0 6.6.57.1-2; azl3 kernel 6.6.57.1-2 on Azure Linux 3.0 6.6.57.1-2 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: stmmac: Fix zero-division error when disabling tc cbs The commit b8c43360f6e4 ("net: stmmac: No need to calculate speed divider when offload is disabled") allows the "port_transmit_rate_kbps" to be set to a value of 0, which is then passed to the "div_s64" function when tc-cbs is disabled. This leads to a zero-division error. When tc-cbs is disabled, the idleslope, sendslope, and credit values the credit values are not required to be configured. Therefore, adding a return statement after setting the txQ mode to DCB when tc-cbs is disabled would prevent a zero-division error.
- Published
- Oct 21, 2024
- Updated
- Oct 15, 2026
- EPSS
- 0.2% · 16th percentile
- CWE
- CWE-369
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.
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 kernel5.10.221 and later · before 5.10.227
- linux linux kernel5.15.162 and later · before 5.15.168
- linux linux kernel6.1.96 and later · before 6.1.113
- linux linux kernel6.6.36 and later · before 6.6.55
- linux linux kernel6.9.7 and later · before 6.10
- linux linux kernel6.10 and later · before 6.10.14
- linux linux kernel6.11 and later · before 6.11.3
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
- f01782804147a8c21f481b3342c83422c041d2c0, 6.10affected
- b4bca4722fda928810d024350493990de39f1e40 and later · before e33fe25b1efe4f2e6a5858786dbc82ae4c44ed4caffected · git
- 2145583e5995598f50d66f8710c86bb1e910ac46 and later · before b0da9504a528f05f97d926b4db74ff21917a33e9affected · git
- 521d42a1c24d638241220d4b9fa7e7a0ed02b88e and later · before 5d43e1ad4567d67af2b42d3ab7c14152ffed25c6affected · git
- a71b686418ee6bcb6d6365f7f6d838d9874d9c64 and later · before 03582f4752427f60817d896f1a827aff772bd31eaffected · git
- b8c43360f6e424131fa81d3ba8792ad8ff25a09e and later · before e297a2bf56d12fd7f91a0c209eb6ea84361f3368affected · git
- b8c43360f6e424131fa81d3ba8792ad8ff25a09e and later · before 837d9df9c0792902710149d1a5e0991520af0f93affected · git
- b8c43360f6e424131fa81d3ba8792ad8ff25a09e and later · before 675faf5a14c14a2be0b870db30a70764df81e2dfaffected · git
- 5.10.221 and later · before 5.10.227affected · semver
- 5.15.162 and later · before 5.15.168affected · 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 6.1.115-1 | 6.1.115-1 |
| Debian:13 | linux | before 6.11.4-1 | 6.11.4-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-2024-49970Oct 21, 2024 · drm/amd/display: Implement bounds check for stream encoder creation in DCN40122Monitor
- ← EarlierCVE-2024-49973Oct 21, 2024 · r8169: add tally counter fields added with RTL812522Monitor
- Later →CVE-2024-49982Oct 21, 2024 · aoe: fix the potential use-after-free problem in more places31Monitor
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 | 03582f4752427f60817d896f1a827aff772bd31e | Vendor (CNA) |
| Linux Linux | 5.10.227 | Vendor (CNA) |
| Linux Linux | 5.15.168 | Vendor (CNA) |
| Linux Linux | 5d43e1ad4567d67af2b42d3ab7c14152ffed25c6 | Vendor (CNA) |
| Linux Linux | 6.1.113 | Vendor (CNA) |
| Linux Linux | 6.10 | Vendor (CNA) |
| Linux Linux | 6.6.55 | Vendor (CNA) |
| Linux Linux | 675faf5a14c14a2be0b870db30a70764df81e2df | Vendor (CNA) |
| Linux Linux | 837d9df9c0792902710149d1a5e0991520af0f93 | Vendor (CNA) |
| Linux Linux | b0da9504a528f05f97d926b4db74ff21917a33e9 | Vendor (CNA) |
| Linux Linux | e297a2bf56d12fd7f91a0c209eb6ea84361f3368 | Vendor (CNA) |
| Linux Linux | e33fe25b1efe4f2e6a5858786dbc82ae4c44ed4c | Vendor (CNA) |
| azl3 kernel 6.6.51.1-5 on Azure Linux 3.0 | 6.6.57.1-2 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 kernel 6.6.57.1-2 on Azure Linux 3.0 | 6.6.57.1-2 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.167.1-2 on CBL Mariner 2.0 | 5.15.173.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.167.1-2 on CBL-Mariner 2.0 | 5.15.173.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.173.1-1 on CBL Mariner 2.0 | 5.15.173.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.115-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-26945173 days apartcrypto: iaa - Fix nr_cpus < nr_iaa case33Monitor
- CVE-2024-477000 days apartext4: check stripe size compatibility on remount as well22Monitor
- CVE-2024-498920 days apartdrm/amd/display: Initialize get_bytes_per_element's default to 122Monitor
- CVE-2024-498990 days apartdrm/amd/display: Initialize denominators' default to 122Monitor
- CVE-2024-4766312 days apartstaging: iio: frequency: ad9834: Validate frequency parameter value22Monitor
- CVE-2024-4766412 days apartspi: hisi-kunpeng: Add verification for the max_frequency provided by the firmware22Monitor
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-369 · Divide By ZeroCVSS 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 (10 more)Show less
- git.kernel.org/stable/c/5d43e1ad4567d67af2b42d3ab7c14152ffed25c6
- git.kernel.org/stable/c/675faf5a14c14a2be0b870db30a70764df81e2df
- git.kernel.org/stable/c/837d9df9c0792902710149d1a5e0991520af0f93
- git.kernel.org/stable/c/b0da9504a528f05f97d926b4db74ff21917a33e9
- git.kernel.org/stable/c/e297a2bf56d12fd7f91a0c209eb6ea84361f3368
- git.kernel.org/stable/c/e33fe25b1efe4f2e6a5858786dbc82ae4c44ed4c
- lists.debian.org/debian-lts-announce/2025/01/msg00001.html
- lists.debian.org/debian-lts-announce/2025/03/msg00002.html
- cert-portal.siemens.com/productcert/html/ssa-265688.html
- cert-portal.siemens.com/productcert/html/ssa-355557.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.