Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 24 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-49977, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.25% · top 84% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected b4bca4722fda928810d024350493990de39f1e40 – < e33fe25b1efe4f2e6a5858786dbc82ae4c44ed4c
    • affected 2145583e5995598f50d66f8710c86bb1e910ac46 – < b0da9504a528f05f97d926b4db74ff21917a33e9
    • affected 521d42a1c24d638241220d4b9fa7e7a0ed02b88e – < 5d43e1ad4567d67af2b42d3ab7c14152ffed25c6
    • affected a71b686418ee6bcb6d6365f7f6d838d9874d9c64 – < 03582f4752427f60817d896f1a827aff772bd31e
    • affected b8c43360f6e424131fa81d3ba8792ad8ff25a09e – < e297a2bf56d12fd7f91a0c209eb6ea84361f3368
    • affected b8c43360f6e424131fa81d3ba8792ad8ff25a09e – < 837d9df9c0792902710149d1a5e0991520af0f93
    • affected b8c43360f6e424131fa81d3ba8792ad8ff25a09e – < 675faf5a14c14a2be0b870db30a70764df81e2df
    • affected f01782804147a8c21f481b3342c83422c041d2c0
    • affected 5.10.221 – < 5.10.227
    • affected 5.15.162 – < 5.15.168
    • affected 6.1.96 – < 6.1.113
    • affected 6.6.36 – < 6.6.55
    • affected 6.9.7 – < 6.10
  • Linux · Linux

    • affected 6.10
    • unaffected < 6.10
    • unaffected 5.10.227 – ≤ 5.10.*
    • unaffected 5.15.168 – ≤ 5.15.*
    • unaffected 6.1.113 – ≤ 6.1.*
    • unaffected 6.6.55 – ≤ 6.6.*
    • unaffected 6.10.14 – ≤ 6.10.*
    • unaffected 6.11.3 – ≤ 6.11.*
    • unaffected 6.12 – ≤ *

References

References11

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-49977 badge
[![CVE-2024-49977](https://cveledger.app/badge/CVE-2024-49977.svg)](https://cveledger.app/cve/CVE-2024-49977)

Record last updated .