drm/amd/pp: Fix potential NULL pointer dereference in atomctrl_initialize_mc_reg_table
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ b3892e2bb519fe18225d0628f0dd255761f16502 · < 820116a39f96bdc7d426c33a804b52f53700a919| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s AMD graphics power-management code does not check whether smu_atom_get_data_table() returned NULL. If retrieval of vram_info fails, the code later dereferences that NULL pointer, potentially causing a crash. The input does not specify an attack path, authentication requirements, or user interaction.
Engineers running Linux kernels with the affected AMD graphics code should check their installations; affected versions are not specified.