CVE-2024-56684: mailbox: mtk-cmdq: fix wrong use of sizeof in cmdq_get_clocks()
In the Linux kernel, the following vulnerability has been resolved:
mailbox: mtk-cmdq: fix wrong use of sizeof in cmdq_get_clocks()
It should be size of the struct clk_bulk_data, not data pointer pass to
devm_kcalloc().
Security readout for executives and security teams
Plain-English summary
A Linux MediaTek command-queue mailbox driver allocates too little memory because it measures a pointer instead of the intended clock-data structure. This may corrupt kernel memory, potentially compromising confidentiality, integrity, and availability. Exposure appears limited to systems using the affected driver and code path, but the supplied sources do not define all required runtime conditions.
Executive priority
High priority for exposed MediaTek-based systems because kernel memory corruption could produce complete security impact. Expedite exposure confirmation and patching there. Other Linux systems should verify applicability before emergency action; the sources do not establish universal Linux exposure or active exploitation.
Technical view
In cmdq_get_clocks(), devm_kcalloc() receives the size of a data pointer rather than sizeof(struct clk_bulk_data). The resulting undersized allocation can permit out-of-bounds memory access when clock records are populated. CVSS 3.1 is 8.4: local, low complexity, no privileges or user interaction, with high confidentiality, integrity, and availability impacts.
Likely exposure
Prioritize Linux systems in the listed affected versions that include and use the MediaTek CMDQ mailbox driver. The bundle identifies 6.11, 6.11.11, 6.12.2, and 6.13 as affected, but also contains an ambiguous "0" entry. Confirm precise affected ranges with kernel or distribution guidance.
Exploitation context
The supplied CVSS vector describes local attack access without required privileges or user interaction. However, CISA KEV status is false, and the bundle provides no evidence of active exploitation, public proof-of-concept availability, or confirmed attack prerequisites. Treat practical exploitability as unconfirmed.
Researcher notes
The source bundle assigns no CWE and does not document a crash trace, reachable allocation count, affected hardware matrix, exploit primitive, or complete version boundaries. The size mismatch supports an under-allocation and possible memory-corruption assessment, but reliable exploitation is not demonstrated. Review the three stable-kernel commits and downstream backports for branch-specific applicability.
Mitigation direction
Upgrade to a vendor-supported kernel containing the referenced allocation-size correction.
Check Linux distribution advisories for exact fixed package versions and backport status.
Prioritize systems that actively use the MediaTek CMDQ mailbox driver.
Apply normal isolation and local-access restrictions while updates are pending.
Validation and detection
Inventory kernel versions and compare them with vendor-confirmed affected and fixed releases.
Determine whether the MediaTek CMDQ mailbox driver is present and used.
Verify the referenced correction exists in deployed kernel source or vendor backports.
After updating, confirm the running kernel matches the installed fixed package.
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-56684 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.
1CVSS vectors
3Timeline events
0ADP providers
4Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.