Loading vulnerability…
CVE-2024-36244 is an input-validation flaw in the Linux kernel Time-Aware Priority Scheduler (taprio) qdisc. taprio enforced a minimum duration for individual schedule entries, but a caller could supply an explicit cycle time that differed from, and was shorter than, the sum of those entry intervals. The validation did not consistently enforce that the cycle time was at least N times the Ethernet minimum-frame transmission duration, where N is the number of schedule entries. The fix applies the cycle-time validation regardless of whether the cycle time is explicitly supplied or automatically calculated.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
12 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Linux kernel traffic-scheduling TAPRIO minimum-interval validation issue.
Linux kernel TAPRIO traffic-scheduling minimum-interval restriction vulnerability.
A Linux kernel net/sched taprio vulnerability addressed by extending the minimum-interval restriction to the full cycle.
A Linux kernel net/sched taprio vulnerability addressed by extending the minimum interval restriction across the entire cycle.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.