CVE-2025-68261 ext4: add i_data_sem protection in ext4_destroy_inline_data_nolock()

In the Linux kernel, the following vulnerability has been resolved: ext4: add idatasem protection in ext4destroyinlinedatanolock Fix a race between inline data destruction and block mapping. The function ext4destroyinlinedatanolock changes the inode data layout by clearing EXT4INODEINLINEDATA and...

CVE-2025-68261 ext4: add i_data_sem protection in ext4_destroy_inline_data_nolock()

In the Linux kernel, the following vulnerability has been resolved: ext4: add idatasem protection in ext4destroyinlinedatanolock Fix a race between inline data destruction and block mapping. The function ext4destroyinlinedatanolock changes the inode data layout by clearing EXT4INODEINLINEDATA and...

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 ext4destroyinlinedatanolock missing idatasem protection in ext4...

CVE-2023-53795

In the Linux kernel, the following vulnerability has been resolved: iommufd: IOMMUFDDESTROY should not increase the refcount syzkaller found a race where IOMMUFDDESTROY increments the refcount: obj = iommufdgetobjectucmd-ictx, cmd-id, IOMMUFDOBJANY; if ISERRobj return PTRERRobj;...

CVE-2023-53795

In the Linux kernel, the following vulnerability has been resolved: iommufd: IOMMUFDDESTROY should not increase the refcount syzkaller found a race where IOMMUFDDESTROY increments the refcount: obj = iommufdgetobjectucmd-ictx, cmd-id, IOMMUFDOBJANY; if ISERRobj return PTRERRobj;...

UBUNTU-CVE-2023-53795

In the Linux kernel, the following vulnerability has been resolved: iommufd: IOMMUFDDESTROY should not increase the refcount syzkaller found a race where IOMMUFDDESTROY increments the refcount: obj = iommufdgetobjectucmd-ictx, cmd-id, IOMMUFDOBJANY; if ISERRobj return PTRERRobj;...

CVE-2023-53795

The CVE-2023-53795 issue in the Linux kernel concerns a race where IOMMUFD_DESTROY would incorrectly increment an object’s refcount, potentially causing spurious failures during destruction when combined with iommufd_object_destroy_user. Public advisories confirm a fix that avoids any refcount in...

PT-2025-49655

Name of the Vulnerable Software and Affected Versions Linux kernel versions prior to 6.3.0-rc1-syzkaller Description The Linux kernel contained a flaw in the iommufd subsystem where IOMMUFD DESTROY incorrectly increased the reference count. This created a race condition when combined with iommufd...

CVE-2023-53759

In the Linux kernel, the following vulnerability has been resolved: HID: hidraw: fix data race on device refcount The hidrawopen function increments the hidraw device reference counter. The counter has no dedicated synchronization mechanism, resulting in a potential data race when concurrently...

PT-2025-49489

Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description A data race exists in the hidraw open function concerning the hidraw device reference counter. This occurs because the reference counter lacks a dedicated synchronization mechanism,...

PT-2025-51674

Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description The Linux kernel contains a flaw in the ext4 filesystem implementation. Specifically, a race condition exists between inline data destruction and block mapping within the ext4 destroy...

SUSE CVE-2025-40203

In the Linux kernel, the following vulnerability has been resolved: listmount: don't call pathput under namespace semaphore Massage listmount and make sure we don't call pathput under the namespace semaphore. If we put the last reference we're fscked...

EUVD-2025-150371

In the Linux kernel, the following vulnerability has been resolved: listmount: don't call pathput under namespace semaphore Massage listmount and make sure we don't call pathput under the namespace semaphore. If we put the last reference we're fscked...

Linux Distros Unpatched Vulnerability : CVE-2025-40203

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available. - listmount: don't call pathput under namespace semaphore Massage listmount and make sure we don't call pathput under the namespace semaphore. If we put the last...

CVE-2025-40203

In the Linux kernel, the following vulnerability has been resolved: listmount: don't call pathput under namespace semaphore Massage listmount and make sure we don't call pathput under the namespace semaphore. If we put the last reference we're fscked...

DEBIAN-CVE-2025-40203

In the Linux kernel, the following vulnerability has been resolved: listmount: don't call pathput under namespace semaphore Massage listmount and make sure we don't call pathput under the namespace semaphore. If we put the last reference we're fscked...

UBUNTU-CVE-2025-40203

In the Linux kernel, the following vulnerability has been resolved: listmount: don't call pathput under namespace semaphore Massage listmount and make sure we don't call pathput under the namespace semaphore. If we put the last reference we're fscked...

CVE-2025-40203 listmount: don't call path_put() under namespace semaphore

In the Linux kernel, the following vulnerability has been resolved: listmount: don't call pathput under namespace semaphore Massage listmount and make sure we don't call pathput under the namespace semaphore. If we put the last reference we're fscked...

CVE-2025-40203

CVE-2025-40203 is a Linux kernel vulnerability: the function listmount previously called path_put() under the namespace semaphore. The issue has been resolved in the kernel (Ubuntu, SUSE, and Amazon Linux advisories reference CVE-2025-40203). Affected products are Linux kernel components; remedia...

CVE-2025-40203 listmount: don't call path_put() under namespace semaphore

In the Linux kernel, the following vulnerability has been resolved: listmount: don't call pathput under namespace semaphore Massage listmount and make sure we don't call pathput under the namespace semaphore. If we put the last reference we're fscked...