Loading vulnerability…
CVE-2024-36978 is an out-of-bounds write vulnerability in the Linux kernel network scheduler's sch_multiq queuing discipline. In multiq_tune(), the queue's band count is updated from the supplied configuration after allocation logic. The vulnerable logic used the prior band-count value when determining allocation requirements, then operated using the new value, permitting writes beyond the allocated bounds when the values differ. The issue was fixed upstream in Linux kernel 6.10-rc3.
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.
17 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A specific vulnerability referenced in connection with a kernelCTF mitigation and reproduction/stabilization work. The content does not describe the flaw type, impact, affected component, or exploitation details.
Possible out-of-bounds write in Linux kernel sch_multiq traffic scheduler tuning.
Possible out-of-bounds write in the Linux kernel sch_multiq traffic scheduler.
Possible out-of-bounds write in the Linux sch_multiq traffic-control scheduler.
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.