CVSS: -EPSS: %CPEs: 2EXPL: 0CVE-2025-37855 – drm/amd/display: Guard Possible Null Pointer Dereference
https://notcve.org/view.php?id=CVE-2025-37855
09 May 2025 — In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Guard Possible Null Pointer Dereference [WHY] In some situations, dc->res_pool may be null. [HOW] Check if pointer is null before dereference. • https://git.kernel.org/stable/c/dc2de1ac7145f882f3c03d2d6f84583ae7e35d41 •
CVSS: -EPSS: %CPEs: 6EXPL: 0CVE-2025-37854 – drm/amdkfd: Fix mode1 reset crash issue
https://notcve.org/view.php?id=CVE-2025-37854
09 May 2025 — In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: Fix mode1 reset crash issue If HW scheduler hangs and mode1 reset is used to recover GPU, KFD signal user space to abort the processes. After process abort exit, user queues still use the GPU to access system memory before h/w is reset while KFD cleanup worker free system memory and free VRAM. There is use-after-free race bug that KFD allocate and reuse the freed system memory, and user queue write to the same system memory to c... • https://git.kernel.org/stable/c/57c9dabda80ac167de8cd71231baae37cc2f442d •
CVSS: -EPSS: %CPEs: 5EXPL: 0CVE-2025-37853 – drm/amdkfd: debugfs hang_hws skip GPU with MES
https://notcve.org/view.php?id=CVE-2025-37853
09 May 2025 — In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: debugfs hang_hws skip GPU with MES debugfs hang_hws is used by GPU reset test with HWS, for MES this crash the kernel with NULL pointer access because dqm->packet_mgr is not setup for MES path. Skip GPU with MES for now, MES hang_hws debugfs interface will be supported later. • https://git.kernel.org/stable/c/a36f8d544522a19ef06ed9e84667d154dcb6be52 •
CVSS: -EPSS: %CPEs: 6EXPL: 0CVE-2025-37852 – drm/amdgpu: handle amdgpu_cgs_create_device() errors in amd_powerplay_create()
https://notcve.org/view.php?id=CVE-2025-37852
09 May 2025 — In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: handle amdgpu_cgs_create_device() errors in amd_powerplay_create() Add error handling to propagate amdgpu_cgs_create_device() failures to the caller. When amdgpu_cgs_create_device() fails, release hwmgr and return -ENOMEM to prevent null pointer dereference. [v1]->[v2]: Change error code from -EINVAL to -ENOMEM. Free hwmgr. • https://git.kernel.org/stable/c/55ef52c30c3e747f145a64de96192e37a8fed670 •
CVSS: -EPSS: %CPEs: 9EXPL: 0CVE-2025-37851 – fbdev: omapfb: Add 'plane' value check
https://notcve.org/view.php?id=CVE-2025-37851
09 May 2025 — In the Linux kernel, the following vulnerability has been resolved: fbdev: omapfb: Add 'plane' value check Function dispc_ovl_setup is not intended to work with the value OMAP_DSS_WB of the enum parameter plane. The value of this parameter is initialized in dss_init_overlays and in the current state of the code it cannot take this value so it's not a real problem. For the purposes of defensive coding it wouldn't be superfluous to check the parameter value, because some functions down the call stack process ... • https://git.kernel.org/stable/c/a570efb4d877adbf3db2dc95487f2ba6bfdd148a •
CVSS: -EPSS: %CPEs: 9EXPL: 0CVE-2025-37850 – pwm: mediatek: Prevent divide-by-zero in pwm_mediatek_config()
https://notcve.org/view.php?id=CVE-2025-37850
09 May 2025 — In the Linux kernel, the following vulnerability has been resolved: pwm: mediatek: Prevent divide-by-zero in pwm_mediatek_config() With CONFIG_COMPILE_TEST && !CONFIG_HAVE_CLK, pwm_mediatek_config() has a divide-by-zero in the following line: do_div(resolution, clk_get_rate(pc->clk_pwms[pwm->hwpwm])); due to the fact that the !CONFIG_HAVE_CLK version of clk_get_rate() returns zero. This is presumably just a theoretical problem: COMPILE_TEST overrides the dependency on RALINK which would select COMMON_CLK. R... • https://git.kernel.org/stable/c/caf065f8fd583b43a3f95d84c8a0a0d07597963b •
CVSS: -EPSS: %CPEs: 6EXPL: 0CVE-2025-37849 – KVM: arm64: Tear down vGIC on failed vCPU creation
https://notcve.org/view.php?id=CVE-2025-37849
09 May 2025 — In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Tear down vGIC on failed vCPU creation If kvm_arch_vcpu_create() fails to share the vCPU page with the hypervisor, we propagate the error back to the ioctl but leave the vGIC vCPU data initialised. Note only does this leak the corresponding memory when the vCPU is destroyed but it can also lead to use-after-free if the redistributor device handling tries to walk into the vCPU. Add the missing cleanup to kvm_arch_vcpu_create(), e... • https://git.kernel.org/stable/c/07476e0d932afc53c05468076393ac35d0b4999e •
CVSS: -EPSS: %CPEs: 4EXPL: 0CVE-2025-37846 – arm64: mops: Do not dereference src reg for a set operation
https://notcve.org/view.php?id=CVE-2025-37846
09 May 2025 — In the Linux kernel, the following vulnerability has been resolved: arm64: mops: Do not dereference src reg for a set operation The source register is not used for SET* and reading it can result in a UBSAN out-of-bounds array access error, specifically when the MOPS exception is taken from a SET* sequence with XZR (reg 31) as the source. Architecturally this is the only case where a src/dst/size field in the ESR can be reported as 31. Prior to 2de451a329cf662b the code in do_el0_mops() was benign as the use... • https://git.kernel.org/stable/c/2de451a329cf662beeba71f63c7f83ee24ca6642 •
CVSS: -EPSS: %CPEs: 9EXPL: 0CVE-2025-37844 – cifs: avoid NULL pointer dereference in dbg call
https://notcve.org/view.php?id=CVE-2025-37844
09 May 2025 — In the Linux kernel, the following vulnerability has been resolved: cifs: avoid NULL pointer dereference in dbg call cifs_server_dbg() implies server to be non-NULL so move call under condition to avoid NULL pointer dereference. Found by Linux Verification Center (linuxtesting.org) with SVACE. • https://git.kernel.org/stable/c/e79b0332ae06b4895dcecddf4bbc5d3917e9383c •
CVSS: -EPSS: %CPEs: 3EXPL: 0CVE-2025-37842 – spi: fsl-qspi: use devm function instead of driver remove
https://notcve.org/view.php?id=CVE-2025-37842
09 May 2025 — In the Linux kernel, the following vulnerability has been resolved: spi: fsl-qspi: use devm function instead of driver remove Driver use devm APIs to manage clk/irq/resources and register the spi controller, but the legacy remove function will be called first during device detach and trigger kernel panic. Drop the remove function and use devm_add_action_or_reset() for driver cleanup to ensure the release sequence. Trigger kernel panic on i.MX8MQ by echo 30bb0000.spi >/sys/bus/platform/drivers/fsl-quadspi/un... • https://git.kernel.org/stable/c/8fcb830a00f0980ffe38d223cdd9a4d2d24da476 •