
CVE-2025-39734 – Revert "fs/ntfs3: Replace inode_trylock with inode_lock"
https://notcve.org/view.php?id=CVE-2025-39734
07 Sep 2025 — In the Linux kernel, the following vulnerability has been resolved: Revert "fs/ntfs3: Replace inode_trylock with inode_lock" This reverts commit 69505fe98f198ee813898cbcaf6770949636430b. • https://git.kernel.org/stable/c/e3e3b3eb54feaf6400800812c8d0f95a7213923d •

CVE-2025-39733 – team: replace team lock with rtnl lock
https://notcve.org/view.php?id=CVE-2025-39733
07 Sep 2025 — In the Linux kernel, the following vulnerability has been resolved: team: replace team lock with rtnl lock syszbot reports various ordering issues for lower instance locks and team lock. • https://git.kernel.org/stable/c/6b1d3c5f675cc794a015138b115afff172fb4c58 •

CVE-2025-39732 – wifi: ath11k: fix sleeping-in-atomic in ath11k_mac_op_set_bitrate_mask()
https://notcve.org/view.php?id=CVE-2025-39732
07 Sep 2025 — In the Linux kernel, the following vulnerability has been resolved: wifi: ath11k: fix sleeping-in-atomic in ath11k_mac_op_set_bitrate_mask() ath11k_mac_disable_peer_fixed_rate() is passed as the iterator to ieee80211_iterate_stations_atomic(). • https://git.kernel.org/stable/c/d5c65159f2895379e11ca13f62feabe93278985d •

CVE-2025-39731 – f2fs: vm_unmap_ram() may be called from an invalid context
https://notcve.org/view.php?id=CVE-2025-39731
07 Sep 2025 — In the Linux kernel, the following vulnerability has been resolved: f2fs: vm_unmap_ram() may be called from an invalid context When testing F2FS with xfstests using UFS backed virtual disks the kernel complains sometimes that f2fs_release_decomp_mem() calls vm_unmap_ram() from an invalid context. • https://git.kernel.org/stable/c/bff139b49d9f70c1ac5384aac94554846aa834de •

CVE-2025-39730 – NFS: Fix filehandle bounds checking in nfs_fh_to_dentry()
https://notcve.org/view.php?id=CVE-2025-39730
07 Sep 2025 — In the Linux kernel, the following vulnerability has been resolved: NFS: Fix filehandle bounds checking in nfs_fh_to_dentry() The function needs to check the minimal filehandle length before it can access the embedded filehandle. • https://git.kernel.org/stable/c/20fa19027286983ab2734b5910c4a687436e0c31 •

CVE-2025-39729 – crypto: ccp - Fix dereferencing uninitialized error pointer
https://notcve.org/view.php?id=CVE-2025-39729
07 Sep 2025 — In the Linux kernel, the following vulnerability has been resolved: crypto: ccp - Fix dereferencing uninitialized error pointer Fix below smatch warnings: drivers/crypto/ccp/sev-dev.c:1312 __sev_platform_init_locked() error: we previously assumed 'error' could be null • https://git.kernel.org/stable/c/9770b428b1a28360663f1f5e524ee458b4cf454b •

CVE-2025-39727 – mm: swap: fix potential buffer overflow in setup_clusters()
https://notcve.org/view.php?id=CVE-2025-39727
07 Sep 2025 — In the Linux kernel, the following vulnerability has been resolved: mm: swap: fix potential buffer overflow in setup_clusters() In setup_swap_map(), we only ensure badpages are in range (0, last_page]. • https://git.kernel.org/stable/c/b843786b0bd01ced7fcdbf3b033d68db2f7c61b2 •

CVE-2025-39726 – s390/ism: fix concurrency management in ism_cmd()
https://notcve.org/view.php?id=CVE-2025-39726
05 Sep 2025 — In the Linux kernel, the following vulnerability has been resolved: s390/ism: fix concurrency management in ism_cmd() The s390x ISM device data sheet clearly states that only one request-response sequence is allowable per ISM function at any point in time. In the Linux kernel, the following vulnerability has been resolved: s390/ism: fix concurrency management in ism_cmd() The s390x ISM device data sheet clearly states that only one request-response sequence is allowable per ISM function at any... • https://git.kernel.org/stable/c/684b89bc39ce4f204b1a2b180f39f2eb36a6b695 •

CVE-2025-39725 – mm/vmscan: fix hwpoisoned large folio handling in shrink_folio_list
https://notcve.org/view.php?id=CVE-2025-39725
05 Sep 2025 — In the Linux kernel, the following vulnerability has been resolved: mm/vmscan: fix hwpoisoned large folio handling in shrink_folio_list In shrink_folio_list(), the hwpoisoned folio may be large folio, which can't be handled by unmap_poisoned_folio(). ... The race is as follows: cpu0 cpu1 shrink_folio_list memory_failure TestSetPageHWPoison unmap_poisoned_folio --> trigger BUG_ON due to unmap_poisoned_folio couldn't handle large folio [tujinjiang@huawei.com: add comment to unmap_poisoned_folio()] In t... • https://git.kernel.org/stable/c/1c9798bf8145a92abf45aa9d38a6406d9eb8bdf0 •

CVE-2025-39724 – serial: 8250: fix panic due to PSLVERR
https://notcve.org/view.php?id=CVE-2025-39724
05 Sep 2025 — In the Linux kernel, the following vulnerability has been resolved: serial: 8250: fix panic due to PSLVERR When the PSLVERR_RESP_EN parameter is set to 1, the device generates an error response if an attempt is made to read an empty RBR (Receive Buffer Register) while the FIFO is enabled. ... Panic backtrace: [ 0.442336] Oops - unknown exception [#1] [ 0.442343] epc : dw8250_serial_in32+0x1e/0x4a [ 0.442351] ra : serial8250_do_startup+0x2c8/0x88e ... [ 0.442416] console_on_rootfs+0x26/0x70 In the ... • https://git.kernel.org/stable/c/c49436b657d0a56a6ad90d14a7c3041add7cf64d •