# drm/amdgpu: Fix a null pointer access when the smc_rreg pointer is NULL

CVE record · `CVE-2023-52817`

- **Identifiers:** `CVE-2023-52817`
- **State:** Confirmed
- **Severity:** CVSS 5.5 Medium
- **Critical:** No
- **CNA:** Linux
- **Weakness (CWE):** [CWE-476](https://cwe.mitre.org/data/definitions/476.html)
- **Tags:** [Memory corruption](https://agentprime.io/advisories/tag/memory-corruption.md)
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 21 May 2024
- **Updated:** 11 May 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 21 May 2024, 15:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `d38ceaf99ed015f2a0b9af3499791bd3a3daae21 to before bf2d51eedf03bd61e3556e35d74d49e2e6112398` (git)
  - affected: `d38ceaf99ed015f2a0b9af3499791bd3a3daae21 to before 437e0fa907ba39b4d7eda863c03ea9cf48bd93a9` (git)
  - affected: `d38ceaf99ed015f2a0b9af3499791bd3a3daae21 to before f475d5502f33a6c5b149b0afe96316ad1962a64a` (git)
  - affected: `d38ceaf99ed015f2a0b9af3499791bd3a3daae21 to before 174f62a0aa15c211e60208b41ee9e7cdfb73d455` (git)
  - affected: `d38ceaf99ed015f2a0b9af3499791bd3a3daae21 to before 6c1b3d89a2dda79881726bb6e37af19c0936d736` (git)
  - affected: `d38ceaf99ed015f2a0b9af3499791bd3a3daae21 to before 820daf9ffe2b0afb804567b10983fb38bc5ae288` (git)
  - affected: `d38ceaf99ed015f2a0b9af3499791bd3a3daae21 to before ba3c0796d292de84f2932cc5bbb0f771fc720996` (git)
  - affected: `d38ceaf99ed015f2a0b9af3499791bd3a3daae21 to before 5104fdf50d326db2c1a994f8b35dcd46e63ae4ad` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `4.2`
  - unaffected: `before 4.2` (semver)
  - unaffected: `4.19.300 to 4.19.*, inclusive` (semver)
  - unaffected: `5.4.262 to 5.4.*, inclusive` (semver)
  - unaffected: `5.10.202 to 5.10.*, inclusive` (semver)
  - unaffected: `5.15.140 to 5.15.*, inclusive` (semver)
  - unaffected: `6.1.64 to 6.1.*, inclusive` (semver)
  - unaffected: `6.5.13 to 6.5.*, inclusive` (semver)
  - unaffected: `6.6.3 to 6.6.*, inclusive` (semver)
  - unaffected: `6.7 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

- 5.5 Medium, CVSS 3.1: `CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`, from ADP (CISA-ADP)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0024, the 15th percentile, on 21 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the CVE Program, published 21 May 2024. New records show when each source confirmed them.

## Sources

- [CVE List: CVE-2023-52817](https://www.cve.org/CVERecord?id=CVE-2023-52817)
- [NVD: CVE-2023-52817](https://nvd.nist.gov/vuln/detail/CVE-2023-52817)

### References from the CNA

- <https://git.kernel.org/stable/c/bf2d51eedf03bd61e3556e35d74d49e2e6112398>
- <https://git.kernel.org/stable/c/437e0fa907ba39b4d7eda863c03ea9cf48bd93a9>
- <https://git.kernel.org/stable/c/f475d5502f33a6c5b149b0afe96316ad1962a64a>
- <https://git.kernel.org/stable/c/174f62a0aa15c211e60208b41ee9e7cdfb73d455>
- <https://git.kernel.org/stable/c/6c1b3d89a2dda79881726bb6e37af19c0936d736>
- <https://git.kernel.org/stable/c/820daf9ffe2b0afb804567b10983fb38bc5ae288>
- <https://git.kernel.org/stable/c/ba3c0796d292de84f2932cc5bbb0f771fc720996>
- <https://git.kernel.org/stable/c/5104fdf50d326db2c1a994f8b35dcd46e63ae4ad>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2023-52817>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2023-52817/>. Everything for agents: <https://agentprime.io/llms.txt>.
