149 matches found
CVE-2023-53563 cpufreq: amd-pstate-ut: Fix kernel panic when loading the driver
In the Linux kernel, the following vulnerability has been resolved: cpufreq: amd-pstate-ut: Fix kernel panic when loading the driver After loading the amd-pstate-ut driver, amdpstateutcheckperf and amdpstateutcheckfreq use cpufreqcpuget to get the policy of the CPU and mark it as busy. In these...
CVE-2023-53563 cpufreq: amd-pstate-ut: Fix kernel panic when loading the driver
In the Linux kernel, the following vulnerability has been resolved: cpufreq: amd-pstate-ut: Fix kernel panic when loading the driver After loading the amd-pstate-ut driver, amdpstateutcheckperf and amdpstateutcheckfreq use cpufreqcpuget to get the policy of the CPU and mark it as busy. In these...
CVE-2023-53550
Technical details about CVE-2023-53550 are not provided in the connected documents. The SUSE advisories listed reference this CVE but do not include affected versions, root cause, nor remediation specifics. Monitor for updates.
CVE-2023-53550 cpufreq: amd-pstate: fix global sysfs attribute type
In the Linux kernel, the following vulnerability has been resolved: cpufreq: amd-pstate: fix global sysfs attribute type In commit 3666062b87ec "cpufreq: amd-pstate: move to use busgetdevroot" the "amdpstate" attributes where moved from a dedicated kobject to the cpu root kobject. While the...
CVE-2023-53550 cpufreq: amd-pstate: fix global sysfs attribute type
In the Linux kernel, the following vulnerability has been resolved: cpufreq: amd-pstate: fix global sysfs attribute type In commit 3666062b87ec "cpufreq: amd-pstate: move to use busgetdevroot" the "amdpstate" attributes where moved from a dedicated kobject to the cpu root kobject. While the...
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 mis-typed amd-pstate global sysfs attribute, which could lead to a failure of control-flow integrity...
EUVD-2025-18614
Malicious code in bioql PyPI...
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
...
Linux Distros Unpatched Vulnerability : CVE-2025-21841
The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available. - In the Linux kernel, the following vulnerability has been resolved: cpufreq/amd-pstate: Fix cpufreqpolicy ref counting amdpstateupdatelimits takes a cpufreqpoli...
Linux Distros Unpatched Vulnerability : CVE-2025-38038
The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available. - cpufreq: amd-pstate: Remove unnecessary driverlock in setboost setboost is a per-policy function call, hence a driver wide lock is unnecessary. Also this...
Linux Distros Unpatched Vulnerability : CVE-2025-23137
The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available. - 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...
The vulnerability of the set_boost() function in the drivers/cpufreq/amd-pstate.c kernel module of Linux operating systems allows a hacker to cause a system failure.
The vulnerability of the setboost function in the drivers/cpufreq/amd-pstate.c kernel module of Linux operating systems is related to insufficient resource locking. Exploiting this vulnerability could allow an attacker to cause a service failure...
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 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...
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...