CVE-2024-36244
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.
Predictions
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or โ if you've already worked around this in production โ publish your fix to the community-verified tier.
โ Propose a mitigation on Community โ Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
OS impact
| OS | Version | Status | Fixed in |
|---|---|---|---|
| rhel | 9 | fixed | |
| sles | affected | | |
| rocky | 9 | fixed | |
| debian | bookworm | fixed | 6.1.119-1 |
| debian | forky | fixed | 6.9.7-1 |
| debian | sid | fixed | 6.9.7-1 |
| debian | trixie | fixed | 6.9.7-1 |
| debian | bullseye | fixed | 6.1.119-1~deb11u1 |
| almalinux | 9 | fixed | kernel-64k-devel-matched-5.14.0-427.42.1.el9_4.aarch64.rpm |
References
- https://access.redhat.com/errata/RHSA-2024:8617
- https://www.suse.com/security/cve/CVE-2024-36244.html
- https://errata.rockylinux.org/RLSA-2024:8617
- https://security-tracker.debian.org/tracker/CVE-2024-36244
- https://bugzilla.redhat.com/2268118
- https://bugzilla.redhat.com/2270100
- https://bugzilla.redhat.com/2275604
- https://bugzilla.redhat.com/2277171
- https://bugzilla.redhat.com/2278176
- https://bugzilla.redhat.com/2278235
- https://bugzilla.redhat.com/2282357
- https://bugzilla.redhat.com/2293654
- https://bugzilla.redhat.com/2296067
- https://bugzilla.redhat.com/2297476
- https://bugzilla.redhat.com/2297488
- https://bugzilla.redhat.com/2297515
- https://bugzilla.redhat.com/2297544
- https://bugzilla.redhat.com/2297556
- https://bugzilla.redhat.com/2297561
- https://bugzilla.redhat.com/2297579
- https://bugzilla.redhat.com/2297582
- https://bugzilla.redhat.com/2297589
- https://bugzilla.redhat.com/2300296
- https://bugzilla.redhat.com/2300297
- https://bugzilla.redhat.com/2311715
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.