85 matches found
Important: kernel6.12
Issue Overview: In the Linux kernel, the following vulnerability has been resolved: eth: bnxt: fix out-of-range access of vnicinfo array CVE-2025-22112 In the Linux kernel, the following vulnerability has been resolved: wifi: cfg80211: init wiphywork before allocating rfkill fails CVE-2025-22119 ...
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...
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...
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 cpufreq: amd-pstate: Remove unnecessary driver_lock in set_boost
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...
Astra Linux – Vulnerability in Linux 6.12
In the Linux kernel, the following vulnerability has been resolved: cpufreq: amd-pstate: Unnecessary driverlock has been removed from the setboost function. setboost is a function call per policy; therefore, a driver-wide lock is unnecessary. Additionally, this mutexacquire operation may conflict...
kernel: cpufreq: amd-pstate: add check for cpufreq_cpu_get's return value
In the Linux kernel, the following vulnerability has been resolved: cpufreq: amd-pstate: add check for cpufreqcpuget's return value cpufreqcpuget may return NULL. To avoid NULL-dereference check it and return in case of error. Found by Linux Verification Center linuxtesting.org with SVACE...
SUSE CVE-2025-23137
In the Linux kernel, the following vulnerability has been resolved: cpufreq/amd-pstate: Add missing NULL ptr check in amdpstateupdate Check if policy is NULL before dereferencing it in amdpstateupdate...
DEBIAN-CVE-2025-23137
In the Linux kernel, the following vulnerability has been resolved: cpufreq/amd-pstate: Add missing NULL ptr check in amdpstateupdate Check if policy is NULL before dereferencing it in amdpstateupdate...
UBUNTU-CVE-2025-23137
In the Linux kernel, the following vulnerability has been resolved: cpufreq/amd-pstate: Add missing NULL ptr check in amdpstateupdate Check if policy is NULL before dereferencing it in amdpstateupdate...
CVE-2025-23137
In the Linux kernel, the following vulnerability has been resolved: cpufreq/amd-pstate: Add missing NULL ptr check in amdpstateupdate Check if policy is NULL before dereferencing it in amdpstateupdate...
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 policy pointer checking in the amd-pstate driver, which could lead to null pointer dereferencing...
PT-2025-16777 · Linux +2 · Linux Kernel +2
Name of the Vulnerable Software and Affected Versions: Linux kernel affected versions not specified Description: A vulnerability in the Linux kernel has been resolved. The issue was related to a missing NULL pointer check in the amd pstate update function. This function is part of the...
The vulnerability of the amd_pstate_epp_cpu_exit() function in the drivers/cpufreq/amd-pstate.c module of the Linux operating system allows a hacker to trigger a service failure.
The vulnerability of the amdpstateeppcpuexit function in the drivers/cpufreq/amd-pstate.c module of the Linux operating system is related to improper memory release before deleting the last reference „memory leak“. Exploiting this vulnerability can allow an attacker to cause a service failure...
SUSE CVE-2025-21841
In the Linux kernel, the following vulnerability has been resolved: cpufreq/amd-pstate: Fix cpufreqpolicy ref counting amdpstateupdatelimits takes a cpufreqpolicy reference but doesn't decrement the refcount in one of the exit paths, fix that...
DEBIAN-CVE-2025-21841
In the Linux kernel, the following vulnerability has been resolved: cpufreq/amd-pstate: Fix cpufreqpolicy ref counting amdpstateupdatelimits takes a cpufreqpolicy reference but doesn't decrement the refcount in one of the exit paths, fix that...
UBUNTU-CVE-2025-21841
In the Linux kernel, the following vulnerability has been resolved: cpufreq/amd-pstate: Fix cpufreqpolicy ref counting amdpstateupdatelimits takes a cpufreqpolicy reference but doesn't decrement the refcount in one of the exit paths, fix that...
PT-2025-25813
Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description The issue concerns the Linux kernel, specifically the cpufreq amd-pstate driver. It involves the removal of an unnecessary driver lock in the set boost function. This lock was unnecessar...