LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50185: drm/radeon: fix potential buffer overflow in ni_set_mc_special_registers()

In the Linux kernel, the following vulnerability has been resolved: drm/radeon: fix potential buffer overflow in ni_set_mc_special_registers() The last case label can write two buffers 'mc_reg_address[j]' and 'mc_data[j]' with 'j' offset equal to SMC_NISLANDS_MC_REGISTER_ARRAY_SIZE since there are no checks for this value in both case labels after the last 'j++'. Instead of changing '>' to '>=' there, add the bounds check at the start of the second 'case' (the first one already has it). Also, remove redundant last checks for 'j' index bigger than array size. The expression is always false. Moreover, before or after the patch 'table->last' can be equal to SMC_NISLANDS_MC_REGISTER_ARRAY_SIZE and it seems it can be a valid value. Detected using the static analysis tool - Svace.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2022-50185 is a Linux kernel Radeon graphics driver flaw where a bounds check was missing in one code path. Sources describe a potential buffer overflow, fixed in stable kernel commits. No CVSS score, CWE, or active exploitation evidence is provided.

Executive priority

Treat this as a kernel maintenance item until vendor severity data improves. There is no cited active exploitation, but kernel memory safety bugs deserve timely patch tracking, especially on Radeon-enabled Linux endpoints.

Technical view

The issue is in drm/radeon ni_set_mc_special_registers(). The final case path could write mc_reg_address[j] and mc_data[j] when j equals SMC_NISLANDS_MC_REGISTER_ARRAY_SIZE. The fix adds a bounds check in the second case and removes redundant impossible checks.

Likely exposure

Exposure appears limited to Linux systems using affected kernel versions with the Radeon DRM driver code present or enabled. The source bundle lists Linux kernel versions and stable commits but does not map distribution package versions or runtime prerequisites.

Exploitation context

The source bundle says the issue was detected by Svace static analysis and is not in CISA KEV. No public exploitation, proof-of-concept, attacker requirements, or demonstrated impact is cited in the provided sources.

Researcher notes

Evidence is narrow: a kernel commit description, affected version metadata, and no CVSS. The bug is a missing bounds check in a Radeon memory-controller register table path. Impact beyond potential overflow is not established by the sources.

Mitigation direction

  • Update to a vendor kernel that includes the referenced stable Radeon fix.
  • Check Linux distribution advisories for backported packages and exact fixed versions.
  • Prioritize systems using AMD Radeon GPUs or loading the radeon DRM driver.
  • If patching is delayed, review vendor guidance for driver-specific risk reduction.
  • Keep kernel updates inside the normal tested maintenance process.

Validation and detection

  • Inventory Linux kernel versions across servers, workstations, and appliances.
  • Confirm whether the radeon DRM driver is present, enabled, or loaded.
  • Compare installed packages with distribution advisories for CVE-2022-50185.
  • Verify vendor changelogs reference the kernel stable fix or equivalent backport.
  • Document systems where Radeon hardware or driver use cannot be confirmed.
Prepared
Confidence
medium
Sources
10

Public sources used

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-2022-50185 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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
0ADP providers
9Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux69e0b57a91adca2e3eb56ed4db39ab90f3ae1043, 69e0b57a91adca2e3eb56ed4db39ab90f3ae1043, 69e0b57a91adca2e3eb56ed4db39ab90f3ae1043, 69e0b57a91adca2e3eb56ed4db39ab90f3ae1043, 69e0b57a91adca2e3eb56ed4db39ab90f3ae1043, 69e0b57a91adca2e3eb56ed4db39ab90f3ae1043, 69e0b57a91adca2e3eb56ed4db39ab90f3ae1043, 69e0b57a91adca2e3eb56ed4db39ab90f3ae1043unaffected
LinuxLinux3.11, 0, 4.14.291, 4.19.256, 5.4.211, 5.10.137, 5.15.61, 5.18.18, 5.19.2, 6.0affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.