CVE-2024-57998: OPP: add index check to assert to avoid buffer overflow in _read_freq()
In the Linux kernel, the following vulnerability has been resolved:
OPP: add index check to assert to avoid buffer overflow in _read_freq()
Pass the freq index to the assert function to make sure
we do not read a freq out of the opp->rates[] table when called
from the indexed variants:
dev_pm_opp_find_freq_exact_indexed() or
dev_pm_opp_find_freq_ceil/floor_indexed().
Add a secondary parameter to the assert function, unused
for assert_single_clk() then add assert_clk_index() which
will check for the clock index when called from the _indexed()
find functions.
Security readout for executives and security teams
Plain-English summary
CVE-2024-57998 is a Linux kernel bug in the OPP power-management code. A missing index check could let the kernel read past a frequency table. Public sources show kernel fixes, but no CVSS score, CWE, or active exploitation evidence.
Executive priority
Treat as a normal kernel patching priority, elevated for Linux appliances or embedded devices with slower update cycles. There is no public evidence of exploitation in the provided sources, but kernel memory-safety bugs should not be deferred indefinitely.
Technical view
The OPP _read_freq() path could read outside opp->rates[] when called through dev_pm_opp_find_freq_exact_indexed(), ceil_indexed(), or floor_indexed(). The fix passes the frequency index into assertions and adds assert_clk_index() to validate indexed clock access before reading the table.
Likely exposure
Exposure is limited to systems running affected Linux kernel versions where platform or driver code uses indexed OPP frequency lookup paths. The source bundle lists Linux as affected and references multiple stable kernel fixes; exact fleet exposure requires kernel-version and vendor-advisory validation.
Exploitation context
No cited source reports active exploitation, and this CVE is not in KEV. Public information does not describe a remote attack path. Practical impact likely depends on reachable kernel code paths, device configuration, and whether indexed OPP APIs are used.
Researcher notes
Evidence is incomplete: no CVSS, CWE, CPEs, or exploitability analysis is provided. The affected-version data is not sufficient by itself to derive all vulnerable ranges. Use upstream commits and vendor advisories as authoritative patch references.
Mitigation direction
Apply Linux stable kernel updates containing the referenced fixes.
For Debian LTS systems, review and apply the cited Debian security update.
Check your distribution or device vendor guidance for backported fixes.
Prioritize vendor kernels used in appliances, embedded systems, and managed endpoints.
Validation and detection
Inventory running kernel versions across Linux assets.
Map kernels to vendor advisories or the referenced stable commits.
Confirm patched kernels include the OPP index-check change.
Review platform drivers for use of indexed OPP frequency lookup APIs.
Document exceptions where vendor status is still unclear.
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-57998 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.
0CVSS vectors
3Timeline events
1ADP providers
7Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Feb 27, 2025, 02:07 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.