CVSS: 5.5EPSS: %CPEs: 3EXPL: 0CVE-2025-37981 – scsi: smartpqi: Use is_kdump_kernel() to check for kdump
https://notcve.org/view.php?id=CVE-2025-37981
20 May 2025 — In the Linux kernel, the following vulnerability has been resolved: scsi: smartpqi: Use is_kdump_kernel() to check for kdump The smartpqi driver checks the reset_devices variable to determine whether special adjustments need to be made for kdump. This has the effect that after a regular kexec reboot, some driver parameters such as max_transfer_size are much lower than usual. More importantly, kexec reboot tests have revealed memory corruption caused by the driver log being written to system memory after a k... • https://git.kernel.org/stable/c/058311b72f54890de824b063feb603942269b732 •
CVSS: 5.5EPSS: %CPEs: 4EXPL: 0CVE-2025-37980 – block: fix resource leak in blk_register_queue() error path
https://notcve.org/view.php?id=CVE-2025-37980
20 May 2025 — In the Linux kernel, the following vulnerability has been resolved: block: fix resource leak in blk_register_queue() error path When registering a queue fails after blk_mq_sysfs_register() is successful but the function later encounters an error, we need to clean up the blk_mq_sysfs resources. Add the missing blk_mq_sysfs_unregister() call in the error path to properly clean up these resources and prevent a memory leak. In the Linux kernel, the following vulnerability has been resolved: block: fix resource ... • https://git.kernel.org/stable/c/320ae51feed5c2f13664aa05a76bec198967e04d •
CVSS: 7.8EPSS: %CPEs: 5EXPL: 0CVE-2025-37979 – ASoC: qcom: Fix sc7280 lpass potential buffer overflow
https://notcve.org/view.php?id=CVE-2025-37979
20 May 2025 — In the Linux kernel, the following vulnerability has been resolved: ASoC: qcom: Fix sc7280 lpass potential buffer overflow Case values introduced in commit 5f78e1fb7a3e ("ASoC: qcom: Add driver support for audioreach solution") cause out of bounds access in arrays of sc7280 driver data (e.g. in case of RX_CODEC_DMA_RX_0 in sc7280_snd_hw_params()). Redefine LPASS_MAX_PORTS to consider the maximum possible port id for q6dsp as sc7280 driver utilizes some of those values. Found by Linux Verification Center (li... • https://git.kernel.org/stable/c/77d0ffef793da818741127f4905a3e3d45d05ac7 •
CVSS: 7.1EPSS: %CPEs: 3EXPL: 0CVE-2025-37978 – block: integrity: Do not call set_page_dirty_lock()
https://notcve.org/view.php?id=CVE-2025-37978
20 May 2025 — In the Linux kernel, the following vulnerability has been resolved: block: integrity: Do not call set_page_dirty_lock() Placing multiple protection information buffers inside the same page can lead to oopses because set_page_dirty_lock() can't be called from interrupt context. Since a protection information buffer is not backed by a file there is no point in setting its page dirty, there is nothing to synchronize. Drop the call to set_page_dirty_lock() and remove the last argument to bio_integrity_unpin_bve... • https://git.kernel.org/stable/c/492c5d455969fc2e829f26ed4c83487b068f0dd7 •
CVSS: 7.1EPSS: %CPEs: 3EXPL: 0CVE-2025-37977 – scsi: ufs: exynos: Disable iocc if dma-coherent property isn't set
https://notcve.org/view.php?id=CVE-2025-37977
20 May 2025 — In the Linux kernel, the following vulnerability has been resolved: scsi: ufs: exynos: Disable iocc if dma-coherent property isn't set If dma-coherent property isn't set then descriptors are non-cacheable and the iocc shareability bits should be disabled. Without this UFS can end up in an incompatible configuration and suffer from random cache related stability issues. In the Linux kernel, the following vulnerability has been resolved: scsi: ufs: exynos: Disable iocc if dma-coherent property isn't set If dm... • https://git.kernel.org/stable/c/cc52e15397cc5dc773d3c6792b98352d3209f93f •
CVSS: 5.5EPSS: %CPEs: 1EXPL: 0CVE-2025-37976 – wifi: ath12k: Fix invalid entry fetch in ath12k_dp_mon_srng_process
https://notcve.org/view.php?id=CVE-2025-37976
20 May 2025 — In the Linux kernel, the following vulnerability has been resolved: wifi: ath12k: Fix invalid entry fetch in ath12k_dp_mon_srng_process [ Upstream commit 63fdc4509bcf483e79548de6bc08bf3c8e504bb3 ] Currently, ath12k_dp_mon_srng_process uses ath12k_hal_srng_src_get_next_entry to fetch the next entry from the destination ring. This is incorrect because ath12k_hal_srng_src_get_next_entry is intended for source rings, not destination rings. This leads to invalid entry fetches, causing potential data corruption o... • https://git.kernel.org/stable/c/0c1015493f0e3979bcbd3a12ebc0977578c87f21 •
CVSS: 7.1EPSS: %CPEs: 3EXPL: 0CVE-2025-37975 – riscv: module: Fix out-of-bounds relocation access
https://notcve.org/view.php?id=CVE-2025-37975
20 May 2025 — In the Linux kernel, the following vulnerability has been resolved: riscv: module: Fix out-of-bounds relocation access The current code allows rel[j] to access one element past the end of the relocation section. Simplify to num_relocations which is equivalent to the existing size expression. In the Linux kernel, the following vulnerability has been resolved: riscv: module: Fix out-of-bounds relocation access The current code allows rel[j] to access one element past the end of the relocation section. Simplif... • https://git.kernel.org/stable/c/080c4324fa5e81ff3780206a138223abfb57a68e •
CVSS: 6.4EPSS: %CPEs: 3EXPL: 0CVE-2025-37974 – s390/pci: Fix missing check for zpci_create_device() error return
https://notcve.org/view.php?id=CVE-2025-37974
20 May 2025 — In the Linux kernel, the following vulnerability has been resolved: s390/pci: Fix missing check for zpci_create_device() error return The zpci_create_device() function returns an error pointer that needs to be checked before dereferencing it as a struct zpci_dev pointer. Add the missing check in __clp_add() where it was missed when adding the scan_list in the fixed commit. Simply not adding the device to the scan list results in the previous behavior. In the Linux kernel, the following vulnerability has bee... • https://git.kernel.org/stable/c/1f3b309108fd0660ea8614a72328ba866ccd3378 •
CVSS: 10.0EPSS: %CPEs: 4EXPL: 0CVE-2025-37973 – wifi: cfg80211: fix out-of-bounds access during multi-link element defragmentation
https://notcve.org/view.php?id=CVE-2025-37973
20 May 2025 — In the Linux kernel, the following vulnerability has been resolved: wifi: cfg80211: fix out-of-bounds access during multi-link element defragmentation Currently during the multi-link element defragmentation process, the multi-link element length added to the total IEs length when calculating the length of remaining IEs after the multi-link element in cfg80211_defrag_mle(). This could lead to out-of-bounds access if the multi-link element or its corresponding fragment elements are the last elements in the IE... • https://git.kernel.org/stable/c/2481b5da9c6b2ee1fde55a1c29eb2ca377145a10 •
CVSS: 5.5EPSS: %CPEs: 5EXPL: 0CVE-2025-37972 – Input: mtk-pmic-keys - fix possible null pointer dereference
https://notcve.org/view.php?id=CVE-2025-37972
20 May 2025 — In the Linux kernel, the following vulnerability has been resolved: Input: mtk-pmic-keys - fix possible null pointer dereference In mtk_pmic_keys_probe, the regs parameter is only set if the button is parsed in the device tree. However, on hardware where the button is left floating, that node will most likely be removed not to enable that input. In that case the code will try to dereference a null pointer. Let's use the regs struct instead as it is defined for all supported platforms. Note that it is ok set... • https://git.kernel.org/stable/c/b581acb49aec5c3b0af9ab1c537fb73481b79069 •