Tools
Log in
English

Learn to codeSecurity check

CVE-2026-99627

HighCVSS 7.1

CVE-2026-99627 High 7.1 · Linux kernel · Linux · details and fixes

Severity
High
Score
7.1 · CVSS 3.1CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
Product
Linux kernel · Linux
Published
2026-11-20
Last modified
2026-11-22
Exploitation
Not on the exploited list

Description

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

drm/amdgpu/gfx12: disallow GFXOFF while updating the SPM VMID

gfx_v12_0_update_spm_vmid() does a read-modify-write of RLC_SPM_MC_CNTL
over MMIO without keeping GFX powered, unlike gfx11. When GFX is in
GFXOFF at that point the update doesn't stick, and with the SPM VMID
programmed on submission again, the job of a process with a reserved
VMID can still run with the SPM writing through VMID 0.

On navi48, after a few other submissions and a VM fault on the same VM,
a COPY_DATA of RLC_SPM_MC_CNTL from such a job reads 0 although the
update was called for it:

$ amd_uapi_regression --run-subtest cs-secure-ib-compute,gem-mapping-info-high-va,gpuvm-fault-high-va,reserved-vmid-spm-vmid
amdgpu 0000:03:00.0: [gfxhub] page fault (src_id:0 ring:40 vmid:7 pasid:185)
amdgpu 0000:03:00.0: Faulty UTCL2 client ID: SDMA1 (0xe)
RLC_SPM_MC_CNTL in the job: 0x00000000

With GFXOFF disallowed around the update it reads the reserved VMID 15.

(cherry picked from commit 907aebc5578ae09fa5c0e2f0784201295837e60b)

Related fix guides

L04Pending security updatesL05New kernel installed, no reboot

Back to the CVE list