CVE-2023-52738

Source
https://cve.org/CVERecord?id=CVE-2023-52738
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2023-52738.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2023-52738
Downstream
BELL (1)
CLSA (1)
DEBIAN (1)
SUSE (5)
UBUNTU (1)
Related
Published
2024-05-21T15:23:01Z
Modified
2026-11-17T07:00:39Z
Severity
  • 5.3 (Medium) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L CVSS Calculator
Summary
drm/amdgpu/fence: Fix oops due to non-matching drm_sched init/fini
Details

In the Linux kernel, the following vulnerability has been resolved:

drm/amdgpu/fence: Fix oops due to non-matching drm_sched init/fini

Currently amdgpu calls drm_sched_fini() from the fence driver sw fini routine - such function is expected to be called only after the respective init function - drm_sched_init() - was executed successfully.

Happens that we faced a driver probe failure in the Steam Deck recently, and the function drm_sched_fini() was called even without its counter-part had been previously called, causing the following oops:

amdgpu: probe of 0000:04:00.0 failed with error -110 BUG: kernel NULL pointer dereference, address: 0000000000000090 PGD 0 P4D 0 Oops: 0002 [#1] PREEMPT SMP NOPTI CPU: 0 PID: 609 Comm: systemd-udevd Not tainted 6.2.0-rc3-gpiccoli #338 Hardware name: Valve Jupiter/Jupiter, BIOS F7A0113 11/04/2022 RIP: 0010:drm_sched_fini+0x84/0xa0 [gpu_sched] [...] Call Trace: amdgpu_fence_driver_sw_fini+0xc8/0xd0 [amdgpu] amdgpu_device_fini_sw+0x2b/0x3b0 [amdgpu] amdgpu_driver_release_kms+0x16/0x30 [amdgpu] devm_drm_dev_init_release+0x49/0x70 [...]

To prevent that, check if the drm_sched was properly initialized for a given ring before calling its fini counter-part.

Notice ideally we'd use sched.ready for that; such field is set as the latest thing on drm_sched_init(). But amdgpu seems to "override" the meaning of such field - in the above oops for example, it was a GFX ring causing the crash, and the sched.ready field was set to true in the ring init routine, regardless of the state of the DRM scheduler. Hence, we ended-up using sched.ops as per Christian's suggestion [0], and also removed the no_scheduler check [1].

[0] https://lore.kernel.org/amd-gfx/984ee981-2906-0eaf-ccec-9f80975cb136@amd.com/ [1] https://lore.kernel.org/amd-gfx/cd0e2994-f85f-d837-609f-7056d5fb7231@amd.com/

Database specific
{
    "cna_assigner":  "Linux",
    "osv_generated_from":  "https://github.com/CVEProject/cvelistV5/tree/main/cves/2023/52xxx/CVE-2023-52738.json"
}
References

Affected packages

Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

Affected ranges

Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
067f44c8b4590c3f24d21a037578a478590f2175
Fixed
2e557c8ca2c585bdef591b8503ba83b85f5d0afd
Fixed
2bcbbef9cace772f5b7128b11401c515982de34b
Fixed
5ad7bbf3dba5c4a684338df1f285080f2588b535
Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
8ba968ae672b3075794c8086aa164595b0175abe

Affected versions

v5.*
v5.14.10
v5.14.11
v5.14.12
v5.14.13
v5.14.14
v5.14.15
v5.14.16
v5.14.17
v5.14.18
v5.14.19
v5.14.20
v5.14.21

Database specific

source
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2023-52738.json"

Linux / Kernel

Package

Name
Kernel

Affected ranges

Type
ECOSYSTEM
Events
Introduced
5.14.10
Fixed
5.15
Type
ECOSYSTEM
Events
Introduced
5.15.0
Fixed
5.15.94
Type
ECOSYSTEM
Events
Introduced
5.16.0
Fixed
6.1.12

Database specific

source
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2023-52738.json"