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

Published Jun 21, 2024
·
Updated

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 ETHZLEN 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->cycletime)" branch. This way covers both conditions and scenarios.

Add a selftest which illustrates the issue triggered by syzbot.

Other sources

In the Linux kernel, the following vulnerability has been resolved:

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

The Linux kernel CVE team has assigned CVE-2024-36244 to this issue.

Upstream advisory: https://lore.kernel.org/linux-cve-announce/2024062134-CVE-2024-36244-f88f@gregkh/T

Red Hat

Affected Software

15 affected componentsFixes available
redhat/kernel<6.6.33
6.6.33
redhat/kernel<6.9.4
6.9.4
redhat/kernel<6.10
6.10
debian/linux<=5.10.223-1, <=5.10.234-1
6.1.129-16.1.135-16.12.25-16.12.27-1
debian/linux-6.1
6.1.129-1~deb11u1
Linux Linux kernel>=5.4.68<5.5
Linux Linux kernel>=5.8.12<5.9
Linux Linux kernel>=5.9.1<6.1.119
Linux Linux kernel>=6.2<6.6.33
Linux Linux kernel>=6.7<6.9.4
Linux Linux kernel=5.9
Linux Linux kernel=5.9-rc7
Linux Linux kernel=5.9-rc8
Linux Linux kernel=6.10-rc1
Microsoft cbl2 kernel 5.15.186.1-1

Event History

Jun 21, 2024
CVE Published
via MITRE·10:18 AM
Data Sourced
via MITRE·10:18 AM
Description
Data Sourced
via NVD·11:15 AM
Description
Data Sourced
via NVD·11:15 AM
RemedySeverityAffected Software
Sep 11, 2024
Data Sourced
via Launchpad·04:24 PM
Description
Apr 27, 2025
Data Sourced
via Ubuntu·05:12 PM
RemedyDescriptionSeverityAffected Software
Oct 3, 2025
Data Sourced
via Microsoft·01:01 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·01:01 AM
Affected Software
Updated
via Microsoft·01:01 AM
DescriptionSeverity

Frequently Asked Questions

1

What is the severity of CVE-2024-36244?

CVE-2024-36244 is classified as a medium severity vulnerability affecting the Linux kernel.

2

How do I fix CVE-2024-36244?

To remediate CVE-2024-36244, you should upgrade to the patched versions of the Linux kernel provided by Red Hat or Debian.

3

What versions of the Linux kernel are affected by CVE-2024-36244?

CVE-2024-36244 affects multiple versions, including Red Hat kernel versions prior to 6.6.33, 6.9.4, and 6.10, as well as specific Debian versions.

4

Is there a known exploit for CVE-2024-36244?

As of now, there is no public information confirming an active exploit for CVE-2024-36244.

5

What components of the Linux kernel does CVE-2024-36244 impact?

CVE-2024-36244 impacts the taprio UAPI component within the Linux kernel networking stack.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203