LiveActive security incident?Get immediate response
CVE Record

CVE-2024-36978: net: sched: sch_multiq: fix possible OOB write in multiq_tune()

In the Linux kernel, the following vulnerability has been resolved: net: sched: sch_multiq: fix possible OOB write in multiq_tune() q->bands will be assigned to qopt->bands to execute subsequent code logic after kmalloc. So the old q->bands should not be used in kmalloc. Otherwise, an out-of-bounds write will occur.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2024-36978 is a Linux kernel networking bug in the multiq traffic scheduler. The flaw can cause an out-of-bounds write during scheduler tuning. Kernel memory corruption issues can matter operationally, but the provided sources do not include CVSS, exploitability detail, or active exploitation evidence.

Executive priority

Track and remediate through the kernel patch program. Escalate above routine priority only for internet-exposed, multi-tenant, or vendor-appliance environments where kernel updates are delayed or operational impact is high.

Technical view

The issue is in net/sched/sch_multiq.c, where multiq_tune() could allocate using the old q->bands value after q->bands is reassigned from qopt->bands, enabling an out-of-bounds write. The Linux stable tree contains fixes across supported kernel branches.

Likely exposure

Exposure is most likely on Linux systems or embedded products running affected kernel branches with the multiq queuing discipline available. The bundle lists Linux as affected and includes Debian LTS and Siemens advisories, but does not provide CPEs or complete product-level coverage.

Exploitation context

The source bundle does not show CISA KEV listing, public exploitation, proof-of-concept status, or required privileges. Treat exploitation status as unconfirmed. Because this is kernel memory corruption in networking scheduler code, validation should focus on affected kernel lineage and vendor patch state.

Researcher notes

Evidence supports a resolved kernel out-of-bounds write, but not a severity score, exploit path, or product-specific impact beyond referenced vendors. Avoid assuming remote exploitability. Use commit presence and vendor advisories as the primary validation anchors.

Mitigation direction

  • Update Linux kernels to vendor releases containing the stable multiq fix.
  • Check Debian LTS guidance if running Debian-packaged kernels.
  • Check Siemens advisories for affected Siemens-managed products.
  • Prioritize normal kernel patch rollout for systems with traffic control enabled.
  • Use vendor guidance where appliance patching differs from standard Linux updates.

Validation and detection

  • Inventory Linux kernel versions across servers, containers hosts, and appliances.
  • Check whether the vendor kernel includes the referenced stable fix commit.
  • Review use of the multiq queuing discipline on exposed systems.
  • Confirm Debian or Siemens advisory applicability where those vendors are present.
  • Document systems awaiting vendor patches or maintenance windows.
Prepared
Confidence
medium
Sources
12

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-36978 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
3ADP providers
12Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container
siemens-SADPADP container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxc2999f7fb05b87da4060e38150c70fa46794d82b, c2999f7fb05b87da4060e38150c70fa46794d82b, c2999f7fb05b87da4060e38150c70fa46794d82b, c2999f7fb05b87da4060e38150c70fa46794d82b, c2999f7fb05b87da4060e38150c70fa46794d82b, c2999f7fb05b87da4060e38150c70fa46794d82b, c2999f7fb05b87da4060e38150c70fa46794d82bunaffected
LinuxLinux5.4, 0, 5.4.279, 5.10.221, 5.15.162, 6.1.95, 6.6.35, 6.9.6, 6.10affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.