NULL Pointer Dereference Affecting kernel-azure-devel package, versions <6.4.0-150600.8.20.1


Severity

Recommended
0.0
medium
0
10

Based on SUSE Linux Enterprise Server security rating.

Threat Intelligence

EPSS
0.04% (6th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-SLES156-KERNELAZUREDEVEL-8504415
  • published14 Dec 2024
  • disclosed13 Dec 2024

Introduced: 13 Dec 2024

CVE-2024-50156  (opens in a new tab)
CWE-476  (opens in a new tab)

How to fix?

Upgrade SLES:15.6 kernel-azure-devel to version 6.4.0-150600.8.20.1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream kernel-azure-devel package and not the kernel-azure-devel package as distributed by SLES. See How to fix? for SLES:15.6 relevant fixed versions and status.

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

drm/msm: Avoid NULL dereference in msm_disp_state_print_regs()

If the allocation in msm_disp_state_dump_regs() failed then block-&gt;state can be NULL. The msm_disp_state_print_regs() function does have code to try to handle it with:

if (*reg) dump_addr = *reg;

...but since "dump_addr" is initialized to NULL the above is actually a noop. The code then goes on to dereference dump_addr.

Make the function print "Registers not stored" when it sees a NULL to solve this. Since we're touching the code, fix msm_disp_state_print_regs() not to pointlessly take a double-pointer and properly mark the pointer as const.

Patchwork: https://patchwork.freedesktop.org/patch/619657/

CVSS Scores

version 3.1