Kernel memory corruption via unchecked Radeon array index
Published Jun 18, 2025 · Updated May 11, 2026
Out-of-bounds writes in the Radeon DRM driver in Linux allow local users to corrupt kernel memory during GPU setup. In ni_set_mc_special_registers(), the final case increments j and then writes mc_reg_address[j] and mc_data[j] without a second bounds check, permitting j to equal the array size. Reachability requires local access and an affected Radeon configuration; public sources document potential memory corruption but no reliable trigger or demonstrated follow-on impact.
Summary
What happened
Out-of-bounds writes in the Radeon DRM driver in Linux allow local users to corrupt kernel memory during GPU setup. In ni_set_mc_special_registers(), the final case increments j and then writes mc_reg_address[j] and mc_data[j] without a second bounds check, permitting j to equal the array size. Reachability requires local access and an affected Radeon configuration; public sources document potential memory corruption but no reliable trigger or demonstrated follow-on impact.
The record
- CVE
- CVE-2022-50185
- Published
- Jun 18, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-787, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 18, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 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.11
- Affected versionversion=69e0b57a91adca2e3eb56ed4db39ab90f3ae1043 <136f614931a2bb73616b292cf542da3a18daefd5
- Affected versionversion=69e0b57a91adca2e3eb56ed4db39ab90f3ae1043 <1f341053852be76f82610ce47a505d930512f05c
- Affected versionversion=69e0b57a91adca2e3eb56ed4db39ab90f3ae1043 <782e413e38dffd37cc85b08b1ccb982adb4a93ce
- Affected versionversion=69e0b57a91adca2e3eb56ed4db39ab90f3ae1043 <8508d6d23a247c29792ce2fc0df3f3404d6a6a80
- Affected versionversion=69e0b57a91adca2e3eb56ed4db39ab90f3ae1043 <9faff03617afeced1c4e5daa89e79b3906374342
- Affected versionversion=69e0b57a91adca2e3eb56ed4db39ab90f3ae1043 <db1a9add3f90ff1c641974d5bb910c16b87af4ef
- Affected versionversion=69e0b57a91adca2e3eb56ed4db39ab90f3ae1043 <deb603c5928e546609c0d5798e231d0205748943
- Affected versionversion=69e0b57a91adca2e3eb56ed4db39ab90f3ae1043 <ea73869df6ef386fc0feeb28ff66742ca835b18f
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.
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