Skip to content
CVE Tracker
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2022-50185

drm/radeon: fix potential buffer overflow in ni_set_mc_special_registers()

High7.8EPSS 0.29%
Published
Updated
Reserved
Assigned by
Linux

Description

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.

Scores

CVSS scores of CVE-2022-50185, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.29% · top 78% of all CVEs (6 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Weakness

Affected products

  • Linux · Linux

    • affected 69e0b57a91adca2e3eb56ed4db39ab90f3ae1043 – < ea73869df6ef386fc0feeb28ff66742ca835b18f
    • affected 69e0b57a91adca2e3eb56ed4db39ab90f3ae1043 – < 1f341053852be76f82610ce47a505d930512f05c
    • affected 69e0b57a91adca2e3eb56ed4db39ab90f3ae1043 – < db1a9add3f90ff1c641974d5bb910c16b87af4ef
    • affected 69e0b57a91adca2e3eb56ed4db39ab90f3ae1043 – < 8508d6d23a247c29792ce2fc0df3f3404d6a6a80
    • affected 69e0b57a91adca2e3eb56ed4db39ab90f3ae1043 – < deb603c5928e546609c0d5798e231d0205748943
    • affected 69e0b57a91adca2e3eb56ed4db39ab90f3ae1043 – < 782e413e38dffd37cc85b08b1ccb982adb4a93ce
    • affected 69e0b57a91adca2e3eb56ed4db39ab90f3ae1043 – < 9faff03617afeced1c4e5daa89e79b3906374342
    • affected 69e0b57a91adca2e3eb56ed4db39ab90f3ae1043 – < 136f614931a2bb73616b292cf542da3a18daefd5
  • Linux · Linux

    • affected 3.11
    • unaffected < 3.11
    • unaffected 4.14.291 – ≤ 4.14.*
    • unaffected 4.19.256 – ≤ 4.19.*
    • unaffected 5.4.211 – ≤ 5.4.*
    • unaffected 5.10.137 – ≤ 5.10.*
    • unaffected 5.15.61 – ≤ 5.15.*
    • unaffected 5.18.18 – ≤ 5.18.*
    • unaffected 5.19.2 – ≤ 5.19.*
    • unaffected 6.0 – ≤ *

References (8)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2022-50185 badge
[![CVE-2022-50185](https://trackcve.app/badge/CVE-2022-50185.svg)](https://trackcve.app/cve/CVE-2022-50185)

Record last updated .