CVSS: -EPSS: %CPEs: 6EXPL: 0CVE-2025-37875 – igc: fix PTM cycle trigger logic
https://notcve.org/view.php?id=CVE-2025-37875
09 May 2025 — In the Linux kernel, the following vulnerability has been resolved: igc: fix PTM cycle trigger logic Writing to clear the PTM status 'valid' bit while the PTM cycle is triggered results in unreliable PTM operation. To fix this, clear the PTM 'trigger' and status after each PTM transaction. The issue can be reproduced with the following: $ sudo phc2sys -R 1000 -O 0 -i tsn0 -m Note: 1000 Hz (-R 1000) is unrealistically large, but provides a way to quickly reproduce the issue. PHC2SYS exits with: "ioctl PTP_OF... • https://git.kernel.org/stable/c/a90ec84837325df4b9a6798c2cc0df202b5680bd •
CVSS: -EPSS: %CPEs: 8EXPL: 0CVE-2025-37871 – nfsd: decrease sc_count directly if fail to queue dl_recall
https://notcve.org/view.php?id=CVE-2025-37871
09 May 2025 — In the Linux kernel, the following vulnerability has been resolved: nfsd: decrease sc_count directly if fail to queue dl_recall A deadlock warning occurred when invoking nfs4_put_stid following a failed dl_recall queue operation: T1 T2 nfs4_laundromat nfs4_get_client_reaplist nfs4_anylock_blockers __break_lease spin_lock // ctx->flc_lock spin_lock // clp->cl_lock nfs4_lockowner_has_blockers locks_owner_has_blockers spin_lock // flctx->flc_lock nfsd_break_deleg_cb nfsd_break_one_deleg nfs4_put_stid refcount_... • https://git.kernel.org/stable/c/b874cdef4e67e5150e07eff0eae1cbb21fb92da1 •
CVSS: -EPSS: %CPEs: 3EXPL: 0CVE-2025-37870 – drm/amd/display: prevent hang on link training fail
https://notcve.org/view.php?id=CVE-2025-37870
09 May 2025 — In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: prevent hang on link training fail [Why] When link training fails, the phy clock will be disabled. However, in enable_streams, it is assumed that link training succeeded and the mux selects the phy clock, causing a hang when a register write is made. [How] When enable_stream is hit, check if link training failed. If it did, fall back to the ref clock to avoid a hang and keep the system in a recoverable state. • https://git.kernel.org/stable/c/0363c03672cd3191f037905bf981eb523a3b71b1 •
CVSS: -EPSS: %CPEs: 7EXPL: 0CVE-2025-37867 – RDMA/core: Silence oversized kvmalloc() warning
https://notcve.org/view.php?id=CVE-2025-37867
09 May 2025 — In the Linux kernel, the following vulnerability has been resolved: RDMA/core: Silence oversized kvmalloc() warning syzkaller triggered an oversized kvmalloc() warning. Silence it by adding __GFP_NOWARN. syzkaller log: WARNING: CPU: 7 PID: 518 at mm/util.c:665 __kvmalloc_node_noprof+0x175/0x180 CPU: 7 UID: 0 PID: 518 Comm: c_repro Not tainted 6.11.0-rc6+ #6 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 RIP: 0010:__kvmalloc_node_noprof+0x1... • https://git.kernel.org/stable/c/37824952dc8fcd96e5c5a1ce9abf3f0ba09b1e5e •
CVSS: -EPSS: %CPEs: 9EXPL: 0CVE-2025-37862 – HID: pidff: Fix null pointer dereference in pidff_find_fields
https://notcve.org/view.php?id=CVE-2025-37862
09 May 2025 — In the Linux kernel, the following vulnerability has been resolved: HID: pidff: Fix null pointer dereference in pidff_find_fields This function triggered a null pointer dereference if used to search for a report that isn't implemented on the device. This happened both for optional and required reports alike. The same logic was applied to pidff_find_special_field and although pidff_init_fields should return an error earlier if one of the required reports is missing, future modifications could change this log... • https://git.kernel.org/stable/c/44a1b8b2027afbb37e418993fb23561bdb9efb38 •
CVSS: -EPSS: %CPEs: 4EXPL: 0CVE-2025-37861 – scsi: mpi3mr: Synchronous access b/w reset and tm thread for reply queue
https://notcve.org/view.php?id=CVE-2025-37861
09 May 2025 — In the Linux kernel, the following vulnerability has been resolved: scsi: mpi3mr: Synchronous access b/w reset and tm thread for reply queue When the task management thread processes reply queues while the reset thread resets them, the task management thread accesses an invalid queue ID (0xFFFF), set by the reset thread, which points to unallocated memory, causing a crash. Add flag 'io_admin_reset_sync' to synchronize access between the reset, I/O, and admin threads. Before a reset, the reset handler sets t... • https://git.kernel.org/stable/c/65ba18c84dbd03afe9b38c06c151239d97a09834 •
CVSS: -EPSS: %CPEs: 9EXPL: 0CVE-2025-37859 – page_pool: avoid infinite loop to schedule delayed worker
https://notcve.org/view.php?id=CVE-2025-37859
09 May 2025 — In the Linux kernel, the following vulnerability has been resolved: page_pool: avoid infinite loop to schedule delayed worker We noticed the kworker in page_pool_release_retry() was waken up repeatedly and infinitely in production because of the buggy driver causing the inflight less than 0 and warning us in page_pool_inflight()[1]. Since the inflight value goes negative, it means we should not expect the whole page_pool to get back to work normally. This patch mitigates the adverse effect by not rescheduli... • https://git.kernel.org/stable/c/c3c7c57017ce1d4b2d3788c1fc59e7e39026e158 •
CVSS: -EPSS: %CPEs: 9EXPL: 0CVE-2025-37858 – fs/jfs: Prevent integer overflow in AG size calculation
https://notcve.org/view.php?id=CVE-2025-37858
09 May 2025 — In the Linux kernel, the following vulnerability has been resolved: fs/jfs: Prevent integer overflow in AG size calculation The JFS filesystem calculates allocation group (AG) size using 1 << l2agsize in dbExtendFS(). When l2agsize exceeds 31 (possible with >2TB aggregates on 32-bit systems), this 32-bit shift operation causes undefined behavior and improper AG sizing. On 32-bit architectures: - Left-shifting 1 by 32+ bits results in 0 due to integer overflow - This creates invalid AG sizes (0 or garbage va... • https://git.kernel.org/stable/c/dd07a985e2ded47b6c7d69fc93c1fe02977c8454 •
CVSS: -EPSS: %CPEs: 9EXPL: 0CVE-2025-37857 – scsi: st: Fix array overflow in st_setup()
https://notcve.org/view.php?id=CVE-2025-37857
09 May 2025 — In the Linux kernel, the following vulnerability has been resolved: scsi: st: Fix array overflow in st_setup() Change the array size to follow parms size instead of a fixed value. • https://git.kernel.org/stable/c/736ae988bfb5932c05625baff70fba224d547c08 •
CVSS: -EPSS: %CPEs: 4EXPL: 0CVE-2025-37856 – btrfs: harden block_group::bg_list against list_del() races
https://notcve.org/view.php?id=CVE-2025-37856
09 May 2025 — In the Linux kernel, the following vulnerability has been resolved: btrfs: harden block_group::bg_list against list_del() races As far as I can tell, these calls of list_del_init() on bg_list cannot run concurrently with btrfs_mark_bg_unused() or btrfs_mark_bg_to_reclaim(), as they are in transaction error paths and situations where the block group is readonly. However, if there is any chance at all of racing with mark_bg_unused(), or a different future user of bg_list, better to be safe than sorry. Otherwi... • https://git.kernel.org/stable/c/bf089c4d1141b27332c092b1dcca5022c415a3b6 •