CVE-2023-52883 json
drm/amdgpu: Fix possible null pointer dereference
published 2024-06-20 2 y ago modified 2026-06-17 4 mo ago also EUVD-2023-59596
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 46%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
drm/amdgpu: Fix possible null pointer dereference
abo->tbo.resource may be NULL in amdgpu_vm_bo_update.
Patch / fix
- Linux Linux 6.5.9, 6.6
- linux linux_kernel 51b79f338175, fefac8c4686f
- linux Debian 14, Debian 13 6.5.10-1
debian advisories DEBIAN-CVE-2023-52883
- linux-nvidia-6.5 Ubuntu 22.04 LTS 6.5.0-1014.14
ubuntu advisories UBUNTU-CVE-2023-52883
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel RHEL 8.8 EUS 4.18.0-477.70.1.el8_8
- perf RHEL 8.8 EUS 4.18.0-477.70.1.el8_8
- bpftool RHEL 8.8 EUS 4.18.0-477.70.1.el8_8
- kernel-core RHEL 8.8 EUS 4.18.0-477.70.1.el8_8
- kernel-tools RHEL 8.8 EUS 4.18.0-477.70.1.el8_8
- python3-perf RHEL 8.8 EUS 4.18.0-477.70.1.el8_8
- kernel-modules RHEL 8.8 EUS 4.18.0-477.70.1.el8_8
- kernel-zfcpdump RHEL 8.8 EUS 4.18.0-477.70.1.el8_8
red hat advisories RHSA-2024:6206
- kernel-rt Linux Micro 6.0 6.4.0-9.1
- kernel-source-rt Linux Micro 6.0 6.4.0-9.1
- kernel-source Linux Micro 6.0 6.4.0-18.1
- kernel-default Linux Micro 6.0 6.4.0-18.1
- kernel-kvmsmall Linux Micro 6.0 6.4.0-18.1
- kernel-default-base Linux Micro 6.0 6.4.0-17.1.1.51
- kernel-rt Real Time Module 15 SP6, openSUSE Leap 15.6 6.4.0-150600.10.5.1
- kernel-syms-rt Real Time Module 15 SP6, openSUSE Leap 15.6 6.4.0-150600.10.5.1
suse advisories SUSE-SU-2025:20028-1SUSE-SU-2025:20008-1SUSE-SU-2024:2973-1SUSE-SU-2024:2896-1SUSE-SU-2024:2571-1
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2023-52883 updated cvss 5.5
kernel: drm/amdgpu: Fix possible null pointer dereference
-
Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 moreaffected: no fix planned “Out of support scope”
-
Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 moreaffected: no fix available “Fix deferred”
-
Red Hat CodeReady Linux Builder EUS (v.8.8) kernel-debuginfo-common-x86_64 4.18.0-477.70.1.el8_8, kernel-debuginfo-common-aarch64 4.18.0-477.70.1.el8_8, kernel-debuginfo-common-ppc64le 4.18.0-477.70.1.el8_8 Red Hat Enterprise Linux BaseOS EUS (v.8.8) perf 4.18.0-477.70.1.el8_8, kernel 4.18.0-477.70.1.el8_8, bpftool 4.18.0-477.70.1.el8_8, kernel-core 4.18.0-477.70.1.el8_8, kernel-tools 4.18.0-477.70.1.el8_8, python3-perf 4.18.0-477.70.1.el8_8, +15 morefixed: vendor fix RHSA-2024:6206
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
0.56% chance of exploitation in the next 30 days, higher than 46% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Linux Linux
- linux linux_kernel
Classification
- Weakness
-
- CWE-476 NULL Pointer Dereference
- Technology feeds
References
Sources
- CVE List CVE-2023-52883
- NVD CVE-2023-52883
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.