Kernel memory corruption via unchecked Radeon audio index
Published May 21, 2024 · Updated Aug 5, 2026
An out-of-bounds write in the Linux Radeon display driver allows local users to corrupt kernel memory through HDMI audio handling. In drivers/gpu/drm/radeon/evergreen.c, code writes afmt_status[afmt_idx] before checking whether afmt_idx exceeds the six-element buffer. The flaw requires local low-privileged access and the Radeon driver; public sources identify no reliable trigger or result beyond possible kernel-memory corruption.
Summary
What happened
An out-of-bounds write in the Linux Radeon display driver allows local users to corrupt kernel memory through HDMI audio handling. In drivers/gpu/drm/radeon/evergreen.c, code writes afmt_status[afmt_idx] before checking whether afmt_idx exceeds the six-element buffer. The flaw requires local low-privileged access and the Radeon driver; public sources identify no reliable trigger or result beyond possible kernel-memory corruption.
The record
- CVE
- CVE-2023-52867
- Published
- May 21, 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 21, 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.13
- Affected versionversion=5cc4e5fc293bfe2634535f544427e8c6061492a5 <112d4b02d94bf9fa4f1d3376587878400dd74783
- Affected versionversion=5cc4e5fc293bfe2634535f544427e8c6061492a5 <19534a7a225f1bf2da70a9a90d41d0215f8f6b45
- Affected versionversion=5cc4e5fc293bfe2634535f544427e8c6061492a5 <341e79f8aec6af6b0061b8171d77b085835c6a58
- Affected versionversion=5cc4e5fc293bfe2634535f544427e8c6061492a5 <347f025a02b3a5d715a0b471fc3b1439c338ad94
- Affected versionversion=5cc4e5fc293bfe2634535f544427e8c6061492a5 <7b063c93bece827fde237fae1c101bceeee4e896
- Affected versionversion=5cc4e5fc293bfe2634535f544427e8c6061492a5 <caaa74541459c4c9e2c10046cf66ad2890483d0f
- Affected versionversion=5cc4e5fc293bfe2634535f544427e8c6061492a5 <d9b4fa249deaae1145d6fc2b64dae718e5c7a855
- Affected versionversion=5cc4e5fc293bfe2634535f544427e8c6061492a5 <dd05484f99d16715a88eedfca363828ef9a4c2d4
- Affected versionversion=5cc4e5fc293bfe2634535f544427e8c6061492a5 <ddc42881f170f1f518496f5a70447501335fc783
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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