CVE-2025-38319

drm/amd/pp: Fix potential NULL pointer dereference in atomctrl_initialize_mc_reg_table

MEDIUM

5.5

CVSS Score

Published: July 10, 2025 at 07:42 AM UTC

Updated: June 17, 2026 at 09:16 AM UTC

2 products affected across 2 vendorsLinux KernelDebian Linux

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM5.5

Exploit prediction

EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: drm/amd/pp: Fix potential NULL pointer dereference in atomctrl_initialize_mc_reg_table The function atomctrl_initialize_mc_reg_table() and atomctrl_initialize_mc_reg_table_v2_2() does not check the return value of smu_atom_get_data_table(). If smu_atom_get_data_table() fails to retrieve vram_info, it returns NULL which is later dereferenced.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Debian Linux · Debiandrupal

95%

11.0

Linux Kernel · Linux

95%

4.18 ≤ v < 5.15.1864.18 ≤ v < 6.1.1424.18 ≤ v < 6.12.344.18 ≤ v < 6.15.34.18 ≤ v < 6.164.18 ≤ v < 6.6.945.16 ≤ v < 6.1.1426.13 ≤ v < 6.15.36.2 ≤ v < 6.6.946.7 ≤ v < 6.12.344.18b3892e2bb519fe18225d0628f0dd255761f16502

Vendor states this is fixed in 64f3acc8c7e6809631457b75638601b36dea3129 (fixed)

Vendor states this is fixed in 7080c20a9139842033ed4af604dc1fa4028593ad (fixed)

Vendor states this is fixed in 820116a39f96bdc7d426c33a804b52f53700a919 (fixed)

Vendor states this is fixed in 85cdcb834fb490731ff2d123f87ca799c57dacf2 (fixed)

Vendor states this is fixed in a4ff7391c8b75b1541900bd9d0c238e558c11fb3 (fixed)

Vendor states this is fixed in cdf7e1ff99ab06ef15d0b5d1aca5258a4fb62b85 (fixed)

Vendor states this is fixed in 4.18 (unaffected)

Vendor states this is fixed in 5.15.186 (unaffected)

Vendor states this is fixed in 6.1.142 (unaffected)

Vendor states this is fixed in 6.12.34 (unaffected)

Vendor states this is fixed in 6.15.3 (unaffected)

Vendor states this is fixed in 6.16 (unaffected)