Linux PowerPC BPF JIT Buffer Overflow DoS

The vulnerability of the bpfjitbuildbody function in the arch/powerpc/net/bpfjitcomp64.c file, which is part of the networking support module on the PowerPC platform of the Linux operating system, involves incorrect resource locking. Exploiting this vulnerability could allow an attacker to cause ...

ROS-20250314-02

A vulnerability in the wifi component of the Linux operating system kernel is related to an incorrect lock in the function ilpciresume in drivers/net/wireless/intel/iwlegacy/common.c. Exploitation of the vulnerability could allow an an attacker to cause a denial of service A vulnerability in the...

ROS-20240919-02

Vulnerability of the reweightentity function of the sched component of the Linux operating system kernel is related to synchronization errors when using a shared resource. Exploitation of the vulnerability could allow an attacker to impact confidentiality, integrity, and availability. A...

ROS-20240830-01

Vulnerability of the rndissetresponse function in the rndis component of the Linux kernel is related to the "BufOffset + 8" operation, which can cause an integer overflow. Exploitation of the vulnerability could allow an attacker to cause a denial of service A vulnerability in the drm/vrr compone...

PT-2024-29767

Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description The vulnerability is related to the Bluetooth component in the Linux kernel and is caused by incorrect locking. This issue can lead to a denial of service. The vulnerability is resolved ...

PT-2024-9787

Name of the Vulnerable Software and Affected Versions: Linux kernel versions prior to 6.6.37 Description: A vulnerability in the Linux kernel's md component is related to incorrect locking, which can cause a softlockup when the bitmap size is less than the array size. This issue can be triggered ...

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...

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...

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...

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: Improper Locking

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...

PT-2024-7610

Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description The issue is related to the ext4 component of the Linux kernel, specifically with the function ext4 mb find by goal in fs/ext4/mballoc.c. It involves incorrect locking, which can lead to...

MediaTek chip security vulnerabilities

MediaTek chips are a variety of chips from MediaTek, a Chinese company called MediaTek. A security vulnerability exists in the vcu module of the MediaTek chips, which is caused by incorrect locking and possible out-of-bounds writes...

MediaTek chip security vulnerabilities

MediaTek chips are a variety of chips from MediaTek, a Chinese company called MediaTek. A security vulnerability exists in the vcu module of the MediaTek chips, which is caused by incorrect locking and possible out-of-bounds writes...

Google Android security vulnerabilities

Google Android is a Linux-based open source operating system from the US company Google. Google Android suffers from a security vulnerability that stems from incorrect locking that corrupts memory, which could be exploited by an attacker to cause a local privilege escalation without additional...

PT-2022-5898

Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description The issue is related to incorrect locking in the xen-netback driver of the Linux kernel, which can be exploited to cause a denial of service. Recommendations At the moment, there is no...

PT-2021-8129 · Linux +1 · Linux Kernel +1

Name of the Vulnerable Software and Affected Versions: Linux kernel affected versions not specified Description: The issue is related to the dbgfs component of the Linux kernel and is caused by incorrect locking. This can lead to a use after free bug when the monitoring targets are destroyed...