CVE-2024-49977

net: stmmac: Fix zero-division error when disabling tc cbs

MEDIUM
5.5
CVSS Score
Published: October 21, 2024 at 06:02 PM UTC
Updated: October 15, 2026 at 01:19 AM UTC
12 products affected across 2 vendorsLinux KernelSIMATIC S7-1500 TM MFPRUGGEDCOM RST2428P Firmware

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.10.221 ≤ v < 5.10.2275.15.162 ≤ v < 5.15.1686.1.96 ≤ v < 6.1.1136.10 ≤ v < 6.10.146.11 ≤ v < 6.11.36.6.36 ≤ v < 6.6.556.9.7 ≤ v < 6.102145583e5995598f50d66f8710c86bb1e910ac465.10.2215.15.162521d42a1c24d638241220d4b9fa7e7a0ed02b88e6.1.966.106.6.366.9.7a71b686418ee6bcb6d6365f7f6d838d9874d9c64b4bca4722fda928810d024350493990de39f1e40b8c43360f6e424131fa81d3ba8792ad8ff25a09ef01782804147a8c21f481b3342c83422c041d2c0
Vendor states this is fixed in 03582f4752427f60817d896f1a827aff772bd31e (fixed)
Vendor states this is fixed in 5d43e1ad4567d67af2b42d3ab7c14152ffed25c6 (fixed)
Vendor states this is fixed in 675faf5a14c14a2be0b870db30a70764df81e2df (fixed)
Vendor states this is fixed in 837d9df9c0792902710149d1a5e0991520af0f93 (fixed)
Vendor states this is fixed in b0da9504a528f05f97d926b4db74ff21917a33e9 (fixed)
Vendor states this is fixed in e297a2bf56d12fd7f91a0c209eb6ea84361f3368 (fixed)
Vendor states this is fixed in e33fe25b1efe4f2e6a5858786dbc82ae4c44ed4c (fixed)
Vendor states this is fixed in 5.10.227 (unaffected)
Vendor states this is fixed in 5.15.168 (unaffected)
Vendor states this is fixed in 6.1.113 (unaffected)
Vendor states this is fixed in 6.10 (unaffected)
Vendor states this is fixed in 6.10.14 (unaffected)
Vendor states this is fixed in 6.11.3 (unaffected)
Vendor states this is fixed in 6.12 (unaffected)
Vendor states this is fixed in 6.6.55 (unaffected)
v < V3.2
Affected range stops below V3.2, so it looks safe — our inference, not a vendor statement
v < V3.2
Affected range stops below V3.2, so it looks safe — our inference, not a vendor statement
v < V3.2
Affected range stops below V3.2, so it looks safe — our inference, not a vendor statement
v < V3.2
Affected range stops below V3.2, so it looks safe — our inference, not a vendor statement
v < V3.2
Affected range stops below V3.2, so it looks safe — our inference, not a vendor statement
v < V3.2
Affected range stops below V3.2, so it looks safe — our inference, not a vendor statement
v < V3.2
Affected range stops below V3.2, so it looks safe — our inference, not a vendor statement
v < V3.2
Affected range stops below V3.2, so it looks safe — our inference, not a vendor statement
v < V3.2
Affected range stops below V3.2, so it looks safe — our inference, not a vendor statement

References (11)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/03582f4752427f60817d896f1a827aff772bd31e
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/5d43e1ad4567d67af2b42d3ab7c14152ffed25c6
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/675faf5a14c14a2be0b870db30a70764df81e2df
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/837d9df9c0792902710149d1a5e0991520af0f93
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/b0da9504a528f05f97d926b4db74ff21917a33e9
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/e297a2bf56d12fd7f91a0c209eb6ea84361f3368
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/e33fe25b1efe4f2e6a5858786dbc82ae4c44ed4c
Source: af854a3a-2127-422b-91ae-364da2661108
https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-369

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card