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-36244

net/sched: taprio: extend minimum interval restriction to entire cycle too

Description

In the Linux kernel, the following vulnerability has been resolved: net/sched: taprio: extend minimum interval restriction to entire cycle too It is possible for syzbot to side-step the restriction imposed by the blamed commit in the Fixes: tag, because the taprio UAPI permits a cycle-time different from (and potentially shorter than) the sum of entry intervals. We need one more restriction, which is that the cycle time itself must be larger than N * ETH_ZLEN bit times, where N is the number of schedule entries. This restriction needs to apply regardless of whether the cycle time came from the user or was the implicit, auto-calculated value, so we move the existing "cycle == 0" check outside the "if "(!new->cycle_time)" branch. This way covers both conditions and scenarios. Add a selftest which illustrates the issue triggered by syzbot.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 23 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-36244, 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 (11 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 b5b73b26b3ca34574124ed7ae9c5ba8391a7f176 – < 34d83c3e6e97867ae061d14eb52123404aab1cbc
    • affected b5b73b26b3ca34574124ed7ae9c5ba8391a7f176 – < b939d1e04a90248b4cdf417b0969c270ceb992b2
    • affected b5b73b26b3ca34574124ed7ae9c5ba8391a7f176 – < 91f249b01fe490fce11fbb4307952ca8cce78724
    • affected b5b73b26b3ca34574124ed7ae9c5ba8391a7f176 – < fb66df20a7201e60f2b13d7f95d031b31a8831d3
    • affected 83bd58952b2b8543d8c48d1453975ab47a0a7504
    • affected 817ff50796c5e364c879596509f83fcba194bb6f
    • affected 5.4.68 – < 5.5
    • affected 5.8.12 – < 5.9
  • Linux · Linux

    • affected 5.9
    • unaffected < 5.9
    • unaffected 6.1.119 – ≤ 6.1.*
    • unaffected 6.6.33 – ≤ 6.6.*
    • unaffected 6.9.4 – ≤ 6.9.*
    • unaffected 6.10 – ≤ *

References

References5

Sources

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

Badge for a README or a ticket

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

Record last updated .