CoreCVE
Back

MEDIUM

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

Published Jun 21, 2024

Description

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.

Affected products

Remediation

No remediation recorded yet.

Metrics

Weaknesses (1)

CWE-20

Improper Input Validation

References (10)

Change history (0)

No recorded changes yet.

Sources
CVE.org / MITRE
Status PUBLISHED
Assigner Linux
Published Jun 21, 2024
Updated May 23, 2026
Reserved Jun 21, 2024
Link CVE-2024-36244
CISA Vulnrichment
Updated Sep 10, 2024
NVD
Status Modified
Modified Jun 17, 2026
Link CVE-2024-36244
Red Hat
Severity Moderate
Public date Jun 21, 2024
Links CVE-2024-36244 - Bugzilla