1217 matches found
CVE-2025-40012
CVE-2025-40012 is a Linux kernel vulnerability in net/smc where smc_lo_register_dmb() allocates DMB buffers with kzalloc() and smc_rx_splice() calls get_page() on them; since kzalloc memory isn’t page-backed this triggers WARN_ON_ONCE() and can lead to a use-after-free if memory is released befor...
CVE-2025-40012 net/smc: fix warning in smc_rx_splice() when calling get_page()
In the Linux kernel, the following vulnerability has been resolved: net/smc: fix warning in smcrxsplice when calling getpage smcloregisterdmb allocates DMB buffers with kzalloc, which are later passed to getpage in smcrxsplice. Since kmalloc memory is not page-backed, this triggers WARNONONCE in...
CVE-2025-40006 mm/hugetlb: fix folio is still mapped when deleted
In the Linux kernel, the following vulnerability has been resolved: mm/hugetlb: fix folio is still mapped when deleted Migration may be raced with fallocating hole. removeinodesinglefolio will unmap the folio if the folio is still mapped. However, it's called without folio lock. If the folio is...
CVE-2025-40006
CVE-2025-40006 pertains to the Linux kernel mm/hugetlb subsystem. The issue arises when a folio becomes unmapped during a race between migration and hole allocation, where remove_inode_single_folio can unmap a folio only if the folio lock is held; if the folio migrates and the mapped PTE converts...
CVE-2025-40006
In the Linux kernel, the following vulnerability has been resolved: mm/hugetlb: fix folio is still mapped when deleted Migration may be raced with fallocating hole. removeinodesinglefolio will unmap the folio if the folio is still mapped. However, it's called without folio lock. If the folio is...
CVE-2025-40006 mm/hugetlb: fix folio is still mapped when deleted
In the Linux kernel, the following vulnerability has been resolved: mm/hugetlb: fix folio is still mapped when deleted Migration may be raced with fallocating hole. removeinodesinglefolio will unmap the folio if the folio is still mapped. However, it's called without folio lock. If the folio is...
Linux kernel 安全漏洞
Linux kernel is the kernel used by Linux, the open source operating system of the Linux Foundation in the United States. A security vulnerability exists in the Linux kernel that stems from a migration operation competing with a fallocating hole that could cause folio to remain mapped without bein...
s390/uv: Don't call folio_wait_writeback() without a folio reference
...
Linux Distros Unpatched Vulnerability : CVE-2023-53593
The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available. - cifs: Release folio lock on fscache read hit. Under the current code, when cifsreadpageworker is called, the call contract is that the callee should unlock the...
CLSA-2025-1759866837 kernel: Fix of 44 CVEs
mm: zswap: fix missing folio cleanup in writeback race path CVE-2024-26832 - mm: fix zswap writeback race condition CVE-2023-53178 - dm array: fix releasing a faulty array block twice in dmarraycursorend CVE-2024-57929 - drm/dpmst: Fix MST sideband message body length check CVE-2024-56616 - gpio:...
SUSE CVE-2023-53593
In the Linux kernel, the following vulnerability has been resolved: cifs: Release folio lock on fscache read hit. Under the current code, when cifsreadpageworker is called, the call contract is that the callee should unlock the page. This is documented in the readfolio section of...
CVE-2023-53593
In the Linux kernel, the following vulnerability has been resolved: cifs: Release folio lock on fscache read hit. Under the current code, when cifsreadpageworker is called, the call contract is that the callee should unlock the page. This is documented in the readfolio section of...
UBUNTU-CVE-2023-53593
In the Linux kernel, the following vulnerability has been resolved: cifs: Release folio lock on fscache read hit. Under the current code, when cifsreadpageworker is called, the call contract is that the callee should unlock the page. This is documented in the readfolio section of...
CVE-2023-53593
CVE-2023-53593 – Linux kernel (CIFS): The issue arises in the CIFS readpath when fscache cache hits occur, leaking a folio lock. The fix releases the folio lock after read completion in cifs_readpage_worker. The problem occurred because the callee was expected to unlock the folio, but in certain ...
CVE-2023-53593 cifs: Release folio lock on fscache read hit.
In the Linux kernel, the following vulnerability has been resolved: cifs: Release folio lock on fscache read hit. Under the current code, when cifsreadpageworker is called, the call contract is that the callee should unlock the page. This is documented in the readfolio section of...
CVE-2023-53593 cifs: Release folio lock on fscache read hit.
In the Linux kernel, the following vulnerability has been resolved: cifs: Release folio lock on fscache read hit. Under the current code, when cifsreadpageworker is called, the call contract is that the callee should unlock the page. This is documented in the readfolio section of...
PT-2025-40756
Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description The Linux kernel contains an issue where a folio lock is leaked when fscache is in use and a cache hit occurs during a read operation. This occurs because the cifs readpage worker functi...
EUVD-2024-0816
Malicious code in bioql PyPI...