CVE-2025-39712

In the Linux kernel, the following vulnerability has been resolved: media: mt9m114: Fix deadlock in getframeinterval/setframeinterval Getting / Setting the frame interval using the V4L2 subdev pad ops getframeinterval/setframeinterval causes a deadlock, as the subdev state is locked in the 1 but...

PT-2025-46751

Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description An issue exists in the Linux kernel related to the cpufreq subsystem and intel pstate driver. Specifically, a problem with object lifecycle management within the update qos request...

cpufreq: amd-pstate: Remove unnecessary driver_lock in set_boost

...

SUSE CVE-2025-38038

In the Linux kernel, the following vulnerability has been resolved: cpufreq: amd-pstate: Remove unnecessary driverlock in setboost setboost is a per-policy function call, hence a driver wide lock is unnecessary. Also this mutexacquire can collide with the mutexacquire from the mode-switch path in...

DEBIAN-CVE-2025-38038

In the Linux kernel, the following vulnerability has been resolved: cpufreq: amd-pstate: Remove unnecessary driverlock in setboost setboost is a per-policy function call, hence a driver wide lock is unnecessary. Also this mutexacquire can collide with the mutexacquire from the mode-switch path in...

CVE-2025-38038

In the Linux kernel, the following vulnerability has been resolved: cpufreq: amd-pstate: Remove unnecessary driverlock in setboost setboost is a per-policy function call, hence a driver wide lock is unnecessary. Also this mutexacquire can collide with the mutexacquire from the mode-switch path in...

UBUNTU-CVE-2025-38038

In the Linux kernel, the following vulnerability has been resolved: cpufreq: amd-pstate: Remove unnecessary driverlock in setboost setboost is a per-policy function call, hence a driver wide lock is unnecessary. Also this mutexacquire can collide with the mutexacquire from the mode-switch path in...

CVE-2025-38038

CVE-2025-38038 affects the Linux kernel, specifically the cpufreq/amd-pstate implementation. The issue arises from an unnecessary driver-wide mutex in set_boost for per-policy calls, creating a potential deadlock with status_store mutex_acquire in the mode-switch path. SUSE’s openSUSE-SU-2025-200...

CVE-2025-38038

In the Linux kernel, the following vulnerability has been resolved: cpufreq: amd-pstate: Remove unnecessary driverlock in setboost setboost is a per-policy function call, hence a driver wide lock is unnecessary. Also this mutexacquire can collide with the mutexacquire from the mode-switch path in...

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 unnecessary driverlock in the cpufreq driver that could lead to a deadlock...

SUSE CVE-2025-37800

In the Linux kernel, the following vulnerability has been resolved: driver core: fix potential NULL pointer dereference in devuevent If userspace reads "uevent" device attribute at the same time as another threads unbinds the device from its driver, change to dev-driver from a valid pointer to NU...

DEBIAN-CVE-2025-37800

In the Linux kernel, the following vulnerability has been resolved: driver core: fix potential NULL pointer dereference in devuevent If userspace reads "uevent" device attribute at the same time as another threads unbinds the device from its driver, change to dev-driver from a valid pointer to NU...

PT-2025-29031

Name of the Vulnerable Software and Affected Versions: Linux kernel affected versions not specified Description: This issue resolves a critical lock within the iavf driver, eliminating error-prone logic associated with try locks. The resolution involves replacing the critical lock with a netdev...

kernel: isdn: mISDN: Fix sleeping function called from invalid context

In the Linux kernel, the following vulnerability has been resolved: isdn: mISDN: Fix sleeping function called from invalid context The driver can call card-isac.release function from an atomic context. Fix this by calling this function after releasing the lock. The following log reveals it:...