Memory corruption via negative watermark-set array index
Published Sep 27, 2024 · Updated Aug 5, 2026
Out-of-bounds access in the AMD display driver in Linux allows local users to trigger a kernel-memory overrun through display state handling. The watermark calculation indexes reader_wm_sets[num_valid_sets - 1] without first rejecting a zero num_valid_sets value, producing a negative array index. Reachability requires the AMD display path and a state with no valid watermark set; public sources document no specific crash or code-execution outcome.
Summary
What happened
Out-of-bounds access in the AMD display driver in Linux allows local users to trigger a kernel-memory overrun through display state handling. The watermark calculation indexes reader_wm_sets[num_valid_sets - 1] without first rejecting a zero num_valid_sets value, producing a negative array index. Reachability requires the AMD display path and a state with no valid watermark set; public sources document no specific crash or code-execution outcome.
The record
- CVE
- CVE-2024-46815
- Published
- Sep 27, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 27, 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=4.15
- Affected versionversion=4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c <21f9cb44f8c60bf6c26487d428b1a09ad3e8aebf
- Affected versionversion=4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c <6a4a08e45e614cfa7a56498cdfaeb7fae2f07fa0
- Affected versionversion=4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c <7c47dd2e92341f2989ab73dbed07f8894593ad7b
- Affected versionversion=4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c <a72d4996409569027b4609414a14a87679b12267
- Affected versionversion=4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c <b36e9b3104c4ba0f2f5dd083dcf6159cb316c996
- Affected versionversion=4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c <b38a4815f79b87efb196cd5121579fc51e29a7fb
- Affected versionversion=4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c <c4a7f7c0062fe2c73f70bb7e335199e25bd71492
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
No sourced classifications are available.
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