Local kernel memory corruption via unterminated frequency tables
Published May 1, 2024 · Updated Aug 5, 2026
Out-of-bounds write in the Linux Qualcomm MSM8974 clock driver allows local users to corrupt kernel memory during frequency-table traversal. Several arrays in drivers/clk/qcom/mmcc-msm8974.c omit the empty sentinel expected by qcom_find_freq() and qcom_find_freq_floor(), so traversal continues past their bounds. The affected driver must be present, and the public record documents only compile testing rather than a demonstrated exploit path.
Summary
What happened
Out-of-bounds write in the Linux Qualcomm MSM8974 clock driver allows local users to corrupt kernel memory during frequency-table traversal. Several arrays in drivers/clk/qcom/mmcc-msm8974.c omit the empty sentinel expected by qcom_find_freq() and qcom_find_freq_floor(), so traversal continues past their bounds. The affected driver must be present, and the public record documents only compile testing rather than a demonstrated exploit path.
The record
- CVE
- CVE-2024-26965
- Published
- May 1, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-787
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 1, 2024CVE publishedPublication date reported by the CVE source.
- Aug 5, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.14
- Affected versionversion=d8b212014e69d6b6323773ce6898f224ef4ed0d6 <3ff4a0f6a8f0ad4b4ee9e908bdfc3cacb7be4060
- Affected versionversion=d8b212014e69d6b6323773ce6898f224ef4ed0d6 <537040c257ab4cd0673fbae048f3940c8ea2e589
- Affected versionversion=d8b212014e69d6b6323773ce6898f224ef4ed0d6 <7e9926fef71e514b4a8ea9d11d5a84d52b181362
- Affected versionversion=d8b212014e69d6b6323773ce6898f224ef4ed0d6 <86bf75d9158f511db7530bc82a84b19a5134d089
- Affected versionversion=d8b212014e69d6b6323773ce6898f224ef4ed0d6 <8f562f3b25177c2055b20fd8cf000496f6fa9194
- Affected versionversion=d8b212014e69d6b6323773ce6898f224ef4ed0d6 <99740c4791dc8019b0d758c5389ca6d1c0604d95
- Affected versionversion=d8b212014e69d6b6323773ce6898f224ef4ed0d6 <ae99e199037c580b7350bfa3596f447a53bcf01f
- Affected versionversion=d8b212014e69d6b6323773ce6898f224ef4ed0d6 <ca2cf98d46748373e830a13d85d215d64a2d9bf2
- Affected versionversion=d8b212014e69d6b6323773ce6898f224ef4ed0d6 <e2c02a85bf53ae86d79b5fccf0a75ac0b78e0c96
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo