CVE-2025-68304

The CVE-2025-68304 entries describe a Linux kernel Bluetooth subsystem use-after-free risk in hci_core: lookup of hci_conn on the RX path. The root cause is a hdev lock/lookup/unlock/use pattern in RX that can allow concurrent deletion of hci_conn* while protocol RX processing uses it, prior to/b...

CVE-2025-68304 Bluetooth: hci_core: lookup hci_conn on RX path on protocol side

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hcicore: lookup hciconn on RX path on protocol side The hdev lock/lookup/unlock/use pattern in the packet RX path doesn't ensure hciconn is not concurrently modified/deleted. This locking appears to be leftover from...

CVE-2025-68285 libceph: fix potential use-after-free in have_mon_and_osd_map()

In the Linux kernel, the following vulnerability has been resolved: libceph: fix potential use-after-free in havemonandosdmap The wait loop in cephopensession can race with the client receiving a new monmap or osdmap shortly after the initial map is received. Both cephmonchandlemap and handleonem...

CVE-2025-68185

In the Linux kernel, the following vulnerability has been resolved: nfs4setupreaddir: insufficient locking for -dparent-dinode dereferencing Theoretically it's an oopsable race, but I don't believe one can manage to hit it on real hardware; might become doable on a KVM, but it still won't be easy...

UBUNTU-CVE-2025-68185

In the Linux kernel, the following vulnerability has been resolved: nfs4setupreaddir: insufficient locking for -dparent-dinode dereferencing Theoretically it's an oopsable race, but I don't believe one can manage to hit it on real hardware; might become doable on a KVM, but it still won't be easy...

CVE-2025-68202

In the Linux kernel, the following vulnerability has been resolved: schedext: Fix unsafe locking in the scxdumpstate For built with CONFIGPREEMPTRT=y kernels, the dumplock will be converted sleepable spinlock and not disable-irq, so the following scenarios occur: inconsistent IN-HARDIRQ-W -...

UBUNTU-CVE-2025-68202

In the Linux kernel, the following vulnerability has been resolved: schedext: Fix unsafe locking in the scxdumpstate For built with CONFIGPREEMPTRT=y kernels, the dumplock will be converted sleepable spinlock and not disable-irq, so the following scenarios occur: inconsistent IN-HARDIRQ-W -...

CVE-2025-68202 sched_ext: Fix unsafe locking in the scx_dump_state()

In the Linux kernel, the following vulnerability has been resolved: schedext: Fix unsafe locking in the scxdumpstate For built with CONFIGPREEMPTRT=y kernels, the dumplock will be converted sleepable spinlock and not disable-irq, so the following scenarios occur: inconsistent IN-HARDIRQ-W -...

CVE-2025-68185

The CVE-2025-68185 entry concerns the Linux kernel vulnerability nfs4_setup_readdir() with insufficient locking when dereferencing ->d_parent->d_inode. The issue is described as a theoretically oopsable race that is unlikely to be exploitable on real hardware, though may be possible under K...

CVE-2025-68185 nfs4_setup_readdir(): insufficient locking for ->d_parent->d_inode dereferencing

In the Linux kernel, the following vulnerability has been resolved: nfs4setupreaddir: insufficient locking for -dparent-dinode dereferencing Theoretically it's an oopsable race, but I don't believe one can manage to hit it on real hardware; might become doable on a KVM, but it still won't be easy...

Linux Distros Unpatched Vulnerability : CVE-2025-68185

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available. - nfs4setupreaddir: insufficient locking for -dparent-dinode dereferencing Theoretically it's an oopsable race, but I don't believe one can manage to hit it on re...

Linux Distros Unpatched Vulnerability : CVE-2025-68202

"The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available. - schedext: Fix unsafe locking in the scxdumpstate For built with CONFIGPREEMPTRT=y kernels, the dumplock will be converted sleepable spinlock and not disable-ir...

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 lack of locking of dparent-dinode access in nfs4setupreaddir, which could lead to a race condition...

PT-2025-51708

Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description A flaw exists in the Bluetooth implementation within the Linux kernel, specifically in the hci core component. The issue relates to improper locking mechanisms when handling Bluetooth...

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 an improper locking order of the CHV/BXT+VTD platform GGTT, which could lead to a deadlock...

编号撤回

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 scsihostbusy trigger regression, which could lead to SRCU locking issues...

编号撤回

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 an inconsistent locking state that could lead to a deadlock...

ROS-20251215-7301

Vulnerability in mongodb-org related to incorrect resource locking. Exploitation of the vulnerability could allow an attacker to cause a denial of service...

CVE-2025-40219

In the Linux kernel, the following vulnerability has been resolved: PCI/IOV: Add PCI rescan-remove locking when enabling/disabling SR-IOV Before disabling SR-IOV via config space accesses to the parent PF, sriovdisable first removes the PCI devices representing the VFs. Since commit 9d16947b7583...

CVE-2025-36919

In aoccread of aocchanneldev.c, there is a possible double free due to improper locking. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation...