4821 matches found
CVE-2023-52516
In the Linux kernel, the following vulnerability has been resolved: dma-debug: don't call dmaentryalloccheckleak under freeentrieslock dmaentryalloccheckleak calls into printk - serial console output qcom geni and grabs port-lock under freeentrieslock spin lock, which is a reverse locking...
SUSE CVE-2021-47055
In the Linux kernel, the following vulnerability has been resolved: mtd: require write permissions for locking and badblock ioctls MEMLOCK, MEMUNLOCK and OTPLOCK modify protection bits. Thus require write permission. Depending on the hardware MEMLOCK might even be write-once, e.g. for SPI-NOR...
Linux kernel security vulnerabilities
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 the need for the device list to hold an associated lock when modified, otherwise the list may become corrupt...
CVE-2021-47055
In the Linux kernel, the following vulnerability has been resolved: mtd: require write permissions for locking and badblock ioctls MEMLOCK, MEMUNLOCK and OTPLOCK modify protection bits. Thus require write permission. Depending on the hardware MEMLOCK might even be write-once, e.g. for SPI-NOR...
DEBIAN-CVE-2021-47055
In the Linux kernel, the following vulnerability has been resolved: mtd: require write permissions for locking and badblock ioctls MEMLOCK, MEMUNLOCK and OTPLOCK modify protection bits. Thus require write permission. Depending on the hardware MEMLOCK might even be write-once, e.g. for SPI-NOR...
UBUNTU-CVE-2021-47055
In the Linux kernel, the following vulnerability has been resolved: mtd: require write permissions for locking and badblock ioctls MEMLOCK, MEMUNLOCK and OTPLOCK modify protection bits. Thus require write permission. Depending on the hardware MEMLOCK might even be write-once, e.g. for SPI-NOR...
CVE-2021-47055
In the Linux kernel, the following vulnerability has been resolved: mtd: require write permissions for locking and badblock ioctls MEMLOCK, MEMUNLOCK and OTPLOCK modify protection bits. Thus require write permission. Depending on the hardware MEMLOCK might even be write-once, e.g. for SPI-NOR...
CVE-2021-47067 soc/tegra: regulators: Fix locking up when voltage-spread is out of range
In the Linux kernel, the following vulnerability has been resolved: soc/tegra: regulators: Fix locking up when voltage-spread is out of range Fix voltage coupler lockup which happens when voltage-spread is out of range due to a bug in the code. The max-spread requirement shall be accounted when C...
CVE-2021-47055 mtd: require write permissions for locking and badblock ioctls
In the Linux kernel, the following vulnerability has been resolved: mtd: require write permissions for locking and badblock ioctls MEMLOCK, MEMUNLOCK and OTPLOCK modify protection bits. Thus require write permission. Depending on the hardware MEMLOCK might even be write-once, e.g. for SPI-NOR...
CVE-2021-47041
A flaw was found in the Linux Kernel, potentially allowing for a deadlock when running nvmet-tcp and nvme-tcp on the same system. This may lead to compromised Availability...
CVE-2021-47041
In the Linux kernel, the following vulnerability has been resolved: nvmet-tcp: fix incorrect locking in statechange sk callback We are not changing anything in the TCP connection state so we should not take a writelock but rather a read lock. This caused a deadlock when running nvmet-tcp and...
DEBIAN-CVE-2021-47041
In the Linux kernel, the following vulnerability has been resolved: nvmet-tcp: fix incorrect locking in statechange sk callback We are not changing anything in the TCP connection state so we should not take a writelock but rather a read lock. This caused a deadlock when running nvmet-tcp and...
CVE-2021-47041
In the Linux kernel, the following vulnerability has been resolved: nvmet-tcp: fix incorrect locking in statechange sk callback We are not changing anything in the TCP connection state so we should not take a writelock but rather a read lock. This caused a deadlock when running nvmet-tcp and...
DEBIAN-CVE-2021-47038
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: avoid deadlock between hcidev-lock and socket lock Commit eab2404ba798 "Bluetooth: Add BTPHY socket option" added a dependency between socket lock and hcidev-lock that could lead to deadlock. It turns out that...
CVE-2021-47041
In the Linux kernel, the following vulnerability has been resolved: nvmet-tcp: fix incorrect locking in statechange sk callback We are not changing anything in the TCP connection state so we should not take a writelock but rather a read lock. This caused a deadlock when running nvmet-tcp and...
Race condition
In the Linux kernel, the following vulnerability has been resolved: hfsplus: prevent corruption in shrinking truncate I believe there are some issues introduced by commit 31651c607151 "hfsplus: avoid deadlock on file truncation" HFS+ has extent records which always contains 8 extents. In case the...
CVE-2021-47038
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: avoid deadlock between hcidev-lock and socket lock Commit eab2404ba798 "Bluetooth: Add BTPHY socket option" added a dependency between socket lock and hcidev-lock that could lead to deadlock. It turns out that...
UBUNTU-CVE-2021-47041
In the Linux kernel, the following vulnerability has been resolved: nvmet-tcp: fix incorrect locking in statechange sk callback We are not changing anything in the TCP connection state so we should not take a writelock but rather a read lock. This caused a deadlock when running nvmet-tcp and...
Design/Logic Flaw
In the Linux kernel, the following vulnerability has been resolved: nvmet-tcp: fix incorrect locking in statechange sk callback We are not changing anything in the TCP connection state so we should not take a writelock but rather a read lock. This caused a deadlock when running nvmet-tcp and...
CVE-2021-47041 nvmet-tcp: fix incorrect locking in state_change sk callback
In the Linux kernel, the following vulnerability has been resolved: nvmet-tcp: fix incorrect locking in statechange sk callback We are not changing anything in the TCP connection state so we should not take a writelock but rather a read lock. This caused a deadlock when running nvmet-tcp and...