CVSS: 5.5EPSS: 0%CPEs: 7EXPL: 0CVE-2024-57946 – virtio-blk: don't keep queue frozen during system suspend
https://notcve.org/view.php?id=CVE-2024-57946
21 Jan 2025 — In the Linux kernel, the following vulnerability has been resolved: virtio-blk: don't keep queue frozen during system suspend Commit 4ce6e2db00de ("virtio-blk: Ensure no requests in virtqueues before deleting vqs.") replaces queue quiesce with queue freeze in virtio-blk's PM callbacks. And the motivation is to drain inflight IOs before suspending. block layer's queue freeze looks very handy, but it is also easy to cause deadlock, such as, any attempt to call into bio_queue_enter() may run into deadlock if t... • https://git.kernel.org/stable/c/d738f3215bb4f88911ff4579780a44960c8e0ca5 •
CVSS: 5.5EPSS: 0%CPEs: 4EXPL: 0CVE-2025-21664 – dm thin: make get_first_thin use rcu-safe list first function
https://notcve.org/view.php?id=CVE-2025-21664
21 Jan 2025 — In the Linux kernel, the following vulnerability has been resolved: dm thin: make get_first_thin use rcu-safe list first function The documentation in rculist.h explains the absence of list_empty_rcu() and cautions programmers against relying on a list_empty() -> list_first() sequence in RCU safe code. This is because each of these functions performs its own READ_ONCE() of the list head. This can lead to a situation where the list_empty() sees a valid list entry, but the subsequent list_first() sees a diffe... • https://git.kernel.org/stable/c/b10ebd34cccae1b431caf1be54919aede2be7cbe •
CVSS: 7.2EPSS: 0%CPEs: 3EXPL: 0CVE-2025-21663 – net: stmmac: dwmac-tegra: Read iommu stream id from device tree
https://notcve.org/view.php?id=CVE-2025-21663
21 Jan 2025 — In the Linux kernel, the following vulnerability has been resolved: net: stmmac: dwmac-tegra: Read iommu stream id from device tree Nvidia's Tegra MGBE controllers require the IOMMU "Stream ID" (SID) to be written to the MGBE_WRAP_AXI_ASID0_CTRL register. The current driver is hard coded to use MGBE0's SID for all controllers. This causes softirq time outs and kernel panics when using controllers other than MGBE0. Example dmesg errors when an ethernet cable is connected to MGBE1: [ 116.133290] tegra-mgbe 69... • https://git.kernel.org/stable/c/d8ca113724e79b324f553914cefa9dd6961de152 •
CVSS: 5.5EPSS: 0%CPEs: 6EXPL: 0CVE-2025-21662 – net/mlx5: Fix variable not being completed when function returns
https://notcve.org/view.php?id=CVE-2025-21662
21 Jan 2025 — In the Linux kernel, the following vulnerability has been resolved: net/mlx5: Fix variable not being completed when function returns When cmd_alloc_index(), fails cmd_work_handler() needs to complete ent->slotted before returning early. Otherwise the task which issued the command may hang: mlx5_core 0000:01:00.0: cmd_work_handler:877:(pid 3880418): failed to allocate command entry INFO: task kworker/13:2:4055883 blocked for more than 120 seconds. Not tainted 4.19.90-25.44.v2101.ky10.aarch64 #1 "echo 0 > /pr... • https://git.kernel.org/stable/c/4baae687a20ef2b82fde12de3c04461e6f2521d6 •
CVSS: 7.1EPSS: 0%CPEs: 6EXPL: 0CVE-2025-21660 – ksmbd: fix unexpectedly changed path in ksmbd_vfs_kern_path_locked
https://notcve.org/view.php?id=CVE-2025-21660
21 Jan 2025 — In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix unexpectedly changed path in ksmbd_vfs_kern_path_locked When `ksmbd_vfs_kern_path_locked` met an error and it is not the last entry, it will exit without restoring changed path buffer. But later this buffer may be used as the filename for creation. In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix unexpectedly changed path in ksmbd_vfs_kern_path_locked When `ksmbd_vfs_kern_path_locked` met an error an... • https://git.kernel.org/stable/c/d1b2d2a9c912fc7b788985fbaf944e80f4b3f2af •
CVSS: 5.5EPSS: 0%CPEs: 3EXPL: 0CVE-2025-21658 – btrfs: avoid NULL pointer dereference if no valid extent tree
https://notcve.org/view.php?id=CVE-2025-21658
21 Jan 2025 — In the Linux kernel, the following vulnerability has been resolved: btrfs: avoid NULL pointer dereference if no valid extent tree [BUG] Syzbot reported a crash with the following call trace: BTRFS info (device loop0): scrub: started on devid 1 BUG: kernel NULL pointer dereference, address: 0000000000000208 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 106e70067 P4D 106e70067 PUD 107143067 PMD 0 Oops: Oops: 0000 [#1] PREEMPT SMP NOPTI CPU: 1 UID: 0 PID: 689 Comm: r... • https://git.kernel.org/stable/c/42437a6386ffeaaf200731e73d723ea491f3fe7d •
CVSS: 5.5EPSS: 0%CPEs: 3EXPL: 0CVE-2025-21656 – hwmon: (drivetemp) Fix driver producing garbage data when SCSI errors occur
https://notcve.org/view.php?id=CVE-2025-21656
21 Jan 2025 — In the Linux kernel, the following vulnerability has been resolved: hwmon: (drivetemp) Fix driver producing garbage data when SCSI errors occur scsi_execute_cmd() function can return both negative (linux codes) and positive (scsi_cmnd result field) error codes. Currently the driver just passes error codes of scsi_execute_cmd() to hwmon core, which is incorrect because hwmon only checks for negative error codes. This leads to hwmon reporting uninitialized data to userspace in case of SCSI errors (for example... • https://git.kernel.org/stable/c/5b46903d8bf372e563bf2150d46b87fff197a109 •
CVSS: 7.1EPSS: 0%CPEs: 7EXPL: 0CVE-2024-57945 – riscv: mm: Fix the out of bound issue of vmemmap address
https://notcve.org/view.php?id=CVE-2024-57945
21 Jan 2025 — In the Linux kernel, the following vulnerability has been resolved: riscv: mm: Fix the out of bound issue of vmemmap address In sparse vmemmap model, the virtual address of vmemmap is calculated as: ((struct page *)VMEMMAP_START - (phys_ram_base >> PAGE_SHIFT)). And the struct page's va can be calculated with an offset: (vmemmap + (pfn)). However, when initializing struct pages, kernel actually starts from the first page from the same section that phys_ram_base belongs to. If the first page's physical addre... • https://git.kernel.org/stable/c/a278d5c60f21aa15d540abb2f2da6e6d795c3e6e •
CVSS: 7.8EPSS: 0%CPEs: 4EXPL: 0CVE-2024-57940 – exfat: fix the infinite loop in exfat_readdir()
https://notcve.org/view.php?id=CVE-2024-57940
21 Jan 2025 — In the Linux kernel, the following vulnerability has been resolved: exfat: fix the infinite loop in exfat_readdir() If the file system is corrupted so that a cluster is linked to itself in the cluster chain, and there is an unused directory entry in the cluster, 'dentry' will not be incremented, causing condition 'dentry < max_dentries' unable to prevent an infinite loop. This infinite loop causes s_lock not to be released, and other tasks will hang, such as exfat_sync_fs(). This commit stops traversing the... • https://git.kernel.org/stable/c/ca06197382bde0a3bc20215595d1c9ce20c6e341 •
CVSS: 5.5EPSS: 0%CPEs: 4EXPL: 0CVE-2024-57939 – riscv: Fix sleeping in invalid context in die()
https://notcve.org/view.php?id=CVE-2024-57939
21 Jan 2025 — In the Linux kernel, the following vulnerability has been resolved: riscv: Fix sleeping in invalid context in die() die() can be called in exception handler, and therefore cannot sleep. However, die() takes spinlock_t which can sleep with PREEMPT_RT enabled. That causes the following warning: BUG: sleeping function called from invalid context at kernel/locking/spinlock_rt.c:48 in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 285, name: mutex preempt_count: 110001, expected: 0 RCU nest depth: 0, expect... • https://git.kernel.org/stable/c/76d2a0493a17d4c8ecc781366850c3c4f8e1a446 •