1386 matches found
CVE-2023-53297 Bluetooth: L2CAP: fix "bad unlock balance" in l2cap_disconnect_rsp
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: fix "bad unlock balance" in l2capdisconnectrsp conn-chanlock isn't acquired before l2capgetchanbyscid, if l2capgetchanbyscid returns NULL, then 'bad unlock balance' is triggered...
CVE-2023-53297 Bluetooth: L2CAP: fix "bad unlock balance" in l2cap_disconnect_rsp
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: fix "bad unlock balance" in l2capdisconnectrsp conn-chanlock isn't acquired before l2capgetchanbyscid, if l2capgetchanbyscid returns NULL, then 'bad unlock balance' is triggered...
CVE-2023-53297
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: fix "bad unlock balance" in l2capdisconnectrsp conn-chanlock isn't acquired before l2capgetchanbyscid, if l2capgetchanbyscid returns NULL, then 'bad unlock balance' is triggered...
UBUNTU-CVE-2022-50302
In the Linux kernel, the following vulnerability has been resolved: lockd: set other missing fields when unlocking files vfslockfile expects the struct filelock to be fully initialised by the caller. Re-exported NFSv3 has been seen to Oops if the flfile field is NULL...
PT-2025-37604
Name of the Vulnerable Software and Affected Versions: Linux kernel affected versions not specified Description: A flaw exists in the Linux kernel where vfs lock file may encounter an issue if the fl file field within the struct file lock is NULL. This can occur during NFSv3 operations when...
Linux Distros Unpatched Vulnerability : CVE-2025-39744
"The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available. - rcu: Fix rcureadunlock deadloop due to IRQ work During rcureadunlockspecial, if this happens during irqexit, we can lockup if an IPI is issued. This is because...
Linux Distros Unpatched Vulnerability : CVE-2025-39749
The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available. - rcu: Protect -deferqsiwpending from data race On kernels built with CONFIGIRQWORK=y, when rcureadunlock is invoked within an interrupts-disabled region of code ...
rcu: Fix rcu_read_unlock() deadloop due to IRQ work
...
SUSE CVE-2025-39749
In the Linux kernel, the following vulnerability has been resolved: rcu: Protect -deferqsiwpending from data race On kernels built with CONFIGIRQWORK=y, when rcureadunlock is invoked within an interrupts-disabled region of code 1, it will invoke rcureadunlockspecial, which uses an irq-work handle...
CVE-2025-39749
In the Linux kernel, the following vulnerability has been resolved: rcu: Protect -deferqsiwpending from data race On kernels built with CONFIGIRQWORK=y, when rcureadunlock is invoked within an interrupts-disabled region of code 1, it will invoke rcureadunlockspecial, which uses an irq-work handle...
AZL-67166 CVE-2025-39749 affecting package kernel for versions less than 6.6.104.2-1
In the Linux kernel, the following vulnerability has been resolved: rcu: Protect -deferqsiwpending from data race On kernels built with CONFIGIRQWORK=y, when rcureadunlock is invoked within an interrupts-disabled region of code 1, it will invoke rcureadunlockspecial, which uses an irq-work handle...
DEBIAN-CVE-2025-39749
In the Linux kernel, the following vulnerability has been resolved: rcu: Protect -deferqsiwpending from data race On kernels built with CONFIGIRQWORK=y, when rcureadunlock is invoked within an interrupts-disabled region of code 1, it will invoke rcureadunlockspecial, which uses an irq-work handle...
CVE-2025-39744
In the Linux kernel, the following vulnerability has been resolved: rcu: Fix rcureadunlock deadloop due to IRQ work During rcureadunlockspecial, if this happens during irqexit, we can lockup if an IPI is issued. This is because the IPI itself triggers the irqexit path causing a recursive lock up...
DEBIAN-CVE-2025-39744
In the Linux kernel, the following vulnerability has been resolved: rcu: Fix rcureadunlock deadloop due to IRQ work During rcureadunlockspecial, if this happens during irqexit, we can lockup if an IPI is issued. This is because the IPI itself triggers the irqexit path causing a recursive lock up...
AZL-67253 CVE-2025-39744 affecting package kernel for versions less than 6.6.104.2-1
In the Linux kernel, the following vulnerability has been resolved: rcu: Fix rcureadunlock deadloop due to IRQ work During rcureadunlockspecial, if this happens during irqexit, we can lockup if an IPI is issued. This is because the IPI itself triggers the irqexit path causing a recursive lock up...
UBUNTU-CVE-2025-39744
In the Linux kernel, the following vulnerability has been resolved: rcu: Fix rcureadunlock deadloop due to IRQ work During rcureadunlockspecial, if this happens during irqexit, we can lockup if an IPI is issued. This is because the IPI itself triggers the irqexit path causing a recursive lock up...
UBUNTU-CVE-2025-39749
In the Linux kernel, the following vulnerability has been resolved: rcu: Protect -deferqsiwpending from data race On kernels built with CONFIGIRQWORK=y, when rcureadunlock is invoked within an interrupts-disabled region of code 1, it will invoke rcureadunlockspecial, which uses an irq-work handle...
CVE-2025-39749 rcu: Protect ->defer_qs_iw_pending from data race
In the Linux kernel, the following vulnerability has been resolved: rcu: Protect -deferqsiwpending from data race On kernels built with CONFIGIRQWORK=y, when rcureadunlock is invoked within an interrupts-disabled region of code 1, it will invoke rcureadunlockspecial, which uses an irq-work handle...
CVE-2025-39749 rcu: Protect ->defer_qs_iw_pending from data race
In the Linux kernel, the following vulnerability has been resolved: rcu: Protect -deferqsiwpending from data race On kernels built with CONFIGIRQWORK=y, when rcureadunlock is invoked within an interrupts-disabled region of code 1, it will invoke rcureadunlockspecial, which uses an irq-work handle...
CVE-2025-39744
The CVE-2025-39744 issue affects the Linux kernel and describes a deadlock in rcu_read_unlock() when called during irq_exit() if an IPI is issued. The root cause is an incorrect handling of irq_work state inside rcu_read_unlock_special() triggered by irq_exit(), which can cause a system hang/lock...