64 matches found
EUVD-2025-22615
Malicious code in bioql PyPI...
SUSE CVE-2025-38388
In the Linux kernel, the following vulnerability has been resolved: firmware: armffa: Replace mutex with rwlock to avoid sleep in atomic context The current use of a mutex to protect the notifier hashtable accesses can lead to issues in the atomic context. It results in the below kernel warnings:...
DEBIAN-CVE-2025-38388
In the Linux kernel, the following vulnerability has been resolved: firmware: armffa: Replace mutex with rwlock to avoid sleep in atomic context The current use of a mutex to protect the notifier hashtable accesses can lead to issues in the atomic context. It results in the below kernel warnings:...
CVE-2025-38388
In the Linux kernel, the following vulnerability has been resolved: firmware: armffa: Replace mutex with rwlock to avoid sleep in atomic context The current use of a mutex to protect the notifier hashtable accesses can lead to issues in the atomic context. It results in the below kernel warnings:...
CVE-2025-38388
In the Linux kernel, the following vulnerability has been resolved: firmware: armffa: Replace mutex with rwlock to avoid sleep in atomic context The current use of a mutex to protect the notifier hashtable accesses can lead to issues in the atomic context. It results in the below kernel warnings:...
CVE-2025-38388 firmware: arm_ffa: Replace mutex with rwlock to avoid sleep in atomic context
In the Linux kernel, the following vulnerability has been resolved: firmware: armffa: Replace mutex with rwlock to avoid sleep in atomic context The current use of a mutex to protect the notifier hashtable accesses can lead to issues in the atomic context. It results in the below kernel warnings:...
CVE-2025-38388
CVE-2025-38388 concerns the Linux kernel’s ARM Firmware Framework for ARMv8-A (FFA). The issue stems from using a mutex to protect the notifier hashtable accesses, which could sleep in atomic context and trigger warnings like “sleeping function called from invalid context.” Connected documents co...
CVE-2025-38388
In the Linux kernel, the following vulnerability has been resolved: firmware: armffa: Replace mutex with rwlock to avoid sleep in atomic context The current use of a mutex to protect the notifier hashtable accesses can lead to issues in the atomic context. It results in the below kernel warnings:...
CVE-2025-38388 firmware: arm_ffa: Replace mutex with rwlock to avoid sleep in atomic context
In the Linux kernel, the following vulnerability has been resolved: firmware: armffa: Replace mutex with rwlock to avoid sleep in atomic context The current use of a mutex to protect the notifier hashtable accesses can lead to issues in the atomic context. It results in the below kernel warnings:...
CVE-2025-38388: Improper Locking
In the Linux kernel, the following vulnerability has been resolved: firmware: armffa: Replace mutex with rwlock to avoid sleep in atomic context The current use of a mutex to protect the notifier hashtable accesses can lead to issues in the atomic context. It results in the below kernel warnings:...
PT-2025-30788
Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description The Linux kernel contained an issue where a mutex was used to protect the notifier hashtable accesses, potentially leading to sleeping within an atomic context. This resulted in kernel...
OESA-2025-1286 kernel security update
The Linux Kernel, the operating system core itself. Security Fixes: In the Linux kernel, the following vulnerability has been resolved: IORINGOPREAD did not correctly consume the provided buffer list when read i/o returned 0 except for -EAGAIN and -EIOCBQUEUED return. This can lead to a potential...
CVE-2024-41935
In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to shrink read extent node in batches We use rwlock to protect core structure data of extent tree during its shrink, however, if there is a huge number of extent nodes in extent tree, during shrink of extent tree, it ma...
CVE-2024-41935
In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to shrink read extent node in batches We use rwlock to protect core structure data of extent tree during its shrink, however, if there is a huge number of extent nodes in extent tree, during shrink of extent tree, it ma...
CVE-2024-41935 f2fs: fix to shrink read extent node in batches
In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to shrink read extent node in batches We use rwlock to protect core structure data of extent tree during its shrink, however, if there is a huge number of extent nodes in extent tree, during shrink of extent tree, it ma...
CVE-2024-41935 f2fs: fix to shrink read extent node in batches
In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to shrink read extent node in batches We use rwlock to protect core structure data of extent tree during its shrink, however, if there is a huge number of extent nodes in extent tree, during shrink of extent tree, it ma...
CVE-2024-41935
CVE-2024-41935 (Linux kernel, f2fs) : The issue concerns the f2fs extent tree shrink operation. The patch changes the shrink process to operate on read extent nodes in batches, reducing the time a core rwlock is held and preventing potential kernel hangs when the extent tree contains a large numb...
CVE-2024-41935: Out-of-bounds Read
In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to shrink read extent node in batches We use rwlock to protect core structure data of extent tree during its shrink, however, if there is a huge number of extent nodes in extent tree, during shrink of extent tree, it ma...
PT-2025-2615
Name of the Vulnerable Software and Affected Versions Linux kernel versions prior to 6.6.74 Description The issue arises from the Linux kernel's handling of the extent tree during its shrink operation. Specifically, when there is a huge number of extent nodes in the extent tree, the kernel may ho...
CVE-2023-52699
A vulnerability was found in the Linux kernel's System V sysv filesystem and occurred when calling the sbbread function while holding the pointerslock lock. This improper handling can lead to potential deadlocks or other erratic behavior in the filesystem. Mitigation Mitigation for this issue is...