# CVE-2024-36244: net/sched: taprio: extend minimum interval restriction to entire cycle too

> A flaw in the Linux kernel's taprio scheduler allows a local attacker to cause a denial of service by configuring invalid cycle times.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Jun 2024
- **Updated:** 23 May 2026
- **Also known as:** AZL-68057, BELL-CVE-2024-36244, DEBIAN-CVE-2024-36244, GHSA-35qp-2m3w-q656, ROOT-OS-DEBIAN-11-CVE-2024-36244, ROOT-OS-UBUNTU-2204-CVE-2024-36244, UBUNTU-CVE-2024-36244

## What is CVE-2024-36244?

CVE-2024-36244 is a medium-severity denial of service vulnerability in Linux kernel, published on 21 Jun 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2024-36244?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2024-36244?

Apply the vendor's patch.

## Is CVE-2024-36244 being exploited?

There is no known exploitation of CVE-2024-36244 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-36244 and fix it if it is affected.

What it is: CVE-2024-36244 is a medium-severity denial of service vulnerability in Linux kernel, published on 21 Jun 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-36244 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-36244/ (Markdown: https://insights.sbomify.com/CVE-2024-36244/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-36244
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-36244
- OSV: https://osv.dev/vulnerability/CVE-2024-36244

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-36244/
Summaries are generated and may contain mistakes; the official description above is the record.