CVE-2024-53072

platform/x86/amd/pmc: Detect when STB is not available

5.5 MediumFix available

In the Linux kernel, the following vulnerability has been resolved:

platform/x86/amd/pmc: Detect when STB is not available

Loading the amd_pmc module as:

amd_pmc enable_stb=1

...can result in the following messages in the kernel ring buffer:

amd_pmc AMDI0009:00: SMU cmd failed. err: 0xff
ioremap on RAM at 0x0000000000000000 - 0x0000000000ffffff
WARNING: CPU: 10 PID: 2151 at arch/x86/mm/ioremap.c:217 __ioremap_caller+0x2cd/0x340

Further debugging reveals that this occurs when the requests for S2D_PHYS_ADDR_LOW and S2D_PHYS_ADDR_HIGH return a value of 0, indicating that the STB is inaccessible. To prevent the ioremap warning and provide clarity to the user, handle the invalid address and display an error message.

Attack profile

How easy it is to exploit

Attack vector: Local
Complexity: Low
Privileges needed: Low
User interaction: None

What an attacker can affect

Confidentiality: None
Integrity: None
Availability: High

Exploit likelihood

0.24%Up 0.2 points since Nov 20, 2024

What each source reports

NVD Score used 5.5

In the Linux kernel, the following vulnerability has been resolved:

platform/x86/amd/pmc: Detect when STB is not available

Loading the amd_pmc module as:

amd_pmc enable_stb=1

...can result in the following messages in the kernel ring buffer:

amd_pmc AMDI0009:00: SMU cmd failed. err: 0xff
ioremap on RAM at 0x0000000000000000 - 0x0000000000ffffff
WARNING: CPU: 10 PID: 2151 at arch/x86/mm/ioremap.c:217 __ioremap_caller+0x2cd/0x340

Record: CVE-2024-53072
CVSS 3.1: 5.5 MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Updated: 2026-11-02

CVE List 5.5

platform/x86/amd/pmc: Detect when STB is not available

In the Linux kernel, the following vulnerability has been resolved:

platform/x86/amd/pmc: Detect when STB is not available

Loading the amd_pmc module as:

amd_pmc enable_stb=1

...can result in the following messages in the kernel ring buffer:

amd_pmc AMDI0009:00: SMU cmd failed. err: 0xff
ioremap on RAM at 0x0000000000000000 - 0x0000000000ffffff
WARNING: CPU: 10 PID: 2151 at arch/x86/mm/ioremap.c:217 __ioremap_caller+0x2cd/0x340

Record: CVE-2024-53072
CVSS 3.1: 5.5 MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Updated: 2026-11-02

EUVDEUVD-2024-50488 5.5

In the Linux kernel, the following vulnerability has been resolved:

platform/x86/amd/pmc: Detect when STB is not available

Loading the amd_pmc module as:

amd_pmc enable_stb=1

...can result in the following messages in the kernel ring buffer:

amd_pmc AMDI0009:00: SMU cmd failed. err: 0xff
ioremap on RAM at 0x0000000000000000 - 0x0000000000ffffff
WARNING: CPU: 10 PID: 2151 at arch/x86/mm/ioremap.c:217 __ioremap_caller+0x2cd/0x340

Record: EUVD-2024-50488
CVSS 3.1: 5.5 MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Updated: 2026-11-02

GitHub AdvisoriesGHSA-cgh6-mrm3-hqpj 5.5

In the Linux kernel, the following vulnerability has been resolved: platform/x86/amd/pmc: Detect...

In the Linux kernel, the following vulnerability has been resolved:

platform/x86/amd/pmc: Detect when STB is not available

Loading the amd_pmc module as:

amd_pmc enable_stb=1

...can result in the following messages in the kernel ring buffer:

amd_pmc AMDI0009:00: SMU cmd failed. err: 0xff
ioremap on RAM at 0x0000000000000000 - 0x0000000000ffffff
WARNING: CPU: 10 PID: 2151 at arch/x86/mm/ioremap.c:217 __ioremap_caller+0x2cd/0x340

Record: GHSA-cgh6-mrm3-hqpj
CVSS 3.1: 5.5 MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Updated: 2026-11-02

OSVAZL-53903 5.5

CVE-2024-53072 affecting package kernel for versions less than 6.6.64.2-1

In the Linux kernel, the following vulnerability has been resolved:

platform/x86/amd/pmc: Detect when STB is not available

Loading the amd_pmc module as:

amd_pmc enable_stb=1

...can result in the following messages in the kernel ring buffer:

amd_pmc AMDI0009:00: SMU cmd failed. err: 0xff
ioremap on RAM at 0x0000000000000000 - 0x0000000000ffffff
WARNING: CPU: 10 PID: 2151 at arch/x86/mm/ioremap.c:217 __ioremap_caller+0x2cd/0x340

Record: AZL-53903
CVSS 3.1: 5.5 MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Updated: 2026-11-02

OSVBELL-CVE-2024-53072 5.5

Record: BELL-CVE-2024-53072
CVSS 3.1: 5.5 MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Updated: 2026-11-02

Show 27 moreShow less

OSV 5.5

platform/x86/amd/pmc: Detect when STB is not available

In the Linux kernel, the following vulnerability has been resolved:

platform/x86/amd/pmc: Detect when STB is not available

Loading the amd_pmc module as:

amd_pmc enable_stb=1

...can result in the following messages in the kernel ring buffer:

amd_pmc AMDI0009:00: SMU cmd failed. err: 0xff
ioremap on RAM at 0x0000000000000000 - 0x0000000000ffffff
WARNING: CPU: 10 PID: 2151 at arch/x86/mm/ioremap.c:217 __ioremap_caller+0x2cd/0x340

Record: CVE-2024-53072
CVSS 3.1: 5.5 MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Updated: 2026-11-02

OSVDEBIAN-CVE-2024-53072 5.5

In the Linux kernel, the following vulnerability has been resolved: platform/x86/amd/pmc: Detect when STB is not available Loading the amd_pmc module as: amd_pmc enable_stb=1 ...can result in the following messages in the kernel ring buffer: amd_pmc AMDI0009:00: SMU cmd failed. err: 0xff ioremap on RAM at 0x0000000000000000 - 0x0000000000ffffff WARNING: CPU: 10 PID: 2151 at arch/x86/mm/ioremap.c:217 __ioremap_caller+0x2cd/0x340 Further debugging reveals that this occurs when the requests for S2D_PHYS_ADDR_LOW and S2D_PHYS_ADDR_HIGH return a value of 0, indicating that the STB is inaccessible. To prevent the ioremap warning and provide clarity to the user, handle the invalid address and display an error message.

Record: DEBIAN-CVE-2024-53072
CVSS 3.1: 5.5 MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Updated: 2026-11-02

OSVOESA-2024-2537 7.8

kernel security update

The Linux Kernel, the operating system core itself.

Security Fix(es):

In the Linux kernel, the following vulnerability has been resolved: xhci: Handle TD clearing for multiple streams case When multiple streams are in use, multiple TDs might be in flight when an endpoint is stopped. We need to issue a Set TR Dequeue Pointer for each, to ensure everything is reset properly and the caches cleared. Change the logic so that any N>1 TDs found active for different streams are deferred until after the first one is processed, calling xhci_invalidate_cancelled_tds() again from xhci_handle_cmd_set_deq() to queue another command until we are done with all of them. Also change the error/"should never happen" paths to ensure we at least clear any affected TDs, even if we can't issue a command to clear the hardware cache, and complain loudly with an xhci_warn() if this ever happens. This problem case dates back to commit e9df17eb1408 ("USB: xhci: Correct assumptions about number of rings per endpoint.") early on in the XHCI driver's life, when stream support was first added. It was then identified but not fixed nor made into a warning in commit 674f8438c121 ("xhci: split handling halted endpoints into two steps"), which added a FIXME comment for the problem case (without materially changing the behavior as far as I can tell, though the new logic made the problem more obvious). Then later, in commit 94f339147fc3 ("xhci: Fix failure to give back some cached cancelled URBs."), it was acknowledged again. [Mathias: commit 94f339147fc3 ("xhci: Fix failure to give back some cached cancelled URBs.") was a targeted regression fix to the previously mentioned patch. Users reported issues with usb stuck after unmounting/disconnecting UAS devices. This rolled back the TD clearing of multiple streams to its original state.] Apparently the commit author was aware of the problem (yet still chose to submit it): It was still mentioned as a FIXME, an xhci_dbg() was added to log the problem condition, and the remaining issue was mentioned in the commit description. The choice of making the log type xhci_dbg() for what is, at this point, a completely unhandled and known broken condition is puzzling and unfortunate, as it guarantees that no actual users would see the log in production, thereby making it nigh undebuggable (indeed, even if you turn on DEBUG, the message doesn't really hint at there being a problem at all). It took me months of random xHC crashes to finally find a reliable repro and be able to do a deep dive debug session, which could all have been avoided had this unhandled, broken condition been actually reported with a warning, as it should have been as a bug intentionally left in unfixed (never mind that it shouldn't have been left in at all). > Another fix to solve clearing the caches of all stream rings with > cancelled TDs is needed, but not as urgent. 3 years after that statement and 14 years after the original bug was introduced, I think it's finally time to fix it. And maybe next time let's not leave bugs unfixed (that are actually worse than the original bug), and let's actually get people to review kernel commits please. Fixes xHC crashes and IOMMU faults with UAS devices when handling errors/faults. Easiest repro is to use hdparm to mark an early sector (e.g. 1024) on a disk as bad, then cat /dev/sdX > /dev/null in a loop. At least in the case of JMicron controllers, the read errors end up having to cancel two TDs (for two queued requests to different streams) and the one that didn't get cleared properly ends up faulting the xHC entirely when it tries to access DMA pages that have since been unmapped, referred to by the stale TDs. This normally happens quickly (after two or three loops). After this fix, I left the cat in a loop running overnight and experienced no xHC failures, with all read errors recovered…

Record: OESA-2024-2537
CVSS 3.1: 7.8 HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Updated: 2026-11-02

OSVRHSA-2025:6966 7.8

Red Hat Security Advisory: kernel security update

Record: RHSA-2025:6966
CVSS 3.1: 7.8 HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Updated: 2026-11-02

OSVUBUNTU-CVE-2024-53072 5.5

Record: UBUNTU-CVE-2024-53072
CVSS 3.1: 5.5 MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Updated: 2026-11-02

OSVCLSA-2026-1783355084 No score

kernel: Fix of 60 CVEs

net/sched: fix pedit partial COW leading to page cache corruption {CVE-2026-46331}
unshare: fix unshare_fs() handling {CVE-2026-43472}
net/sched: sch_hfsc: fix divide-by-zero in rtsc_min() {CVE-2026-31423}
net/sched: cls_flow: fix NULL pointer dereference on shared blocks {CVE-2026-31422}
net/sched: cls_fw: fix NULL pointer dereference on shared blocks {CVE-2026-31421}
dm: fix queue start/stop imbalance under suspend/load/resume races {CVE-2025-40134}
ext4: avoid allocating blocks from corrupted group in ext4_mb_try_best_found() {CVE-2024-26773}
ext4: fix i_data_sem unlock order in ext4_ind_migrate() {CVE-2024-50006}
xen: Fix the issue of resource not being properly released in xenbus_dev_probe() {CVE-2024-53198}
HID: pidff: Fix null pointer dereference in pidff_find_fields {CVE-2025-37862}
crypto: af_alg - Set merge to zero early in af_alg_sendmsg {CVE-2025-39931}
x86/cpu/hygon: Add missing resctrl_cpu_detect() in bsp_init helper {CVE-2025-39681}
can: kvaser_usb: kvaser_usb_read_bulk_callback(): fix URB memory leak {CVE-2026-23061}
bonding: restore IFF_MASTER/SLAVE flags on bond enslave ether type change {CVE-2023-53103}
NFS: Fix a potential data corruption {CVE-2023-53711}
NFS: Fix a use after free in nfs_direct_join_group() {CVE-2023-53711}
hwmon: (w83791d) Fix NULL pointer dereference by removing unnecessary structure field {CVE-2021-47386}
scsi: bnx2fc: Remove spin_lock_bh while releasing resources after upload {CVE-2024-36919}
x86/mm: Ensure input to pfn_to_kaddr() is treated as a 64-bit type {CVE-2023-52659}
Input: uinput - reject requests with unreasonable number of slots {CVE-2024-46745}
afs: Fix the maximum cell name length {CVE-2025-21646}
drm/i915: Avoid potential vm use-after-free {CVE-2023-52931}
interconnect: fix mem leak when freeing nodes {CVE-2023-53096}
drm/vkms: Fix memory leak in vkms_init() {CVE-2022-50269}
USB: dwc3: fix memory leak with using debugfs_lookup() {CVE-2023-53415}
mm/uffd: fix pte marker when fork() without fork event {CVE-2022-49744}
scsi: qla2xxx: Fix memory leak in qla2x00_probe_one() {CVE-2023-53696}
ipmi_si: fix a memleak in try_smi_init() {CVE-2023-53611}
KVM: Explicitly verify target vCPU is online in kvm_get_vcpu() {CVE-2024-58083}
scsi: lpfc: Release hbalock before calling lpfc_worker_wake_up() {CVE-2024-36924}
firmware: cs_dsp: Validate payload length before processing block {CVE-2024-42237}
hwmon: (w83792d) Fix NULL pointer dereference by removing unnecessary structure field {CVE-2021-47385}
ftrace: Avoid potential division by zero in function_stat_show() {CVE-2025-21898}
IB/core: Implement a limit on UMAD receive List {CVE-2024-42145}
vfio/pci: Disable auto-enable of exclusive INTx IRQ {CVE-2024-27437}
netfilter: nf_tables: reject duplicate device on updates {CVE-2025-38678}
PCI: vmd: Make vmd_dev::cfg_lock a raw_spinlock_t type {CVE-2025-23161}
net: nexthop: Initialize all fields in dumped nexthops {CVE-2024-42283}
tracing: Make sure trace_printk() can output as soon as it can be used {CVE-2023-53007}
net: tls: explicitly disallow disconnect {CVE-2025-37756}
KVM: x86: Reject Hyper-V's SEND_IPI hypercalls if local APIC isn't in-kernel {CVE-2025-21779}
ext4: turn quotas off if mount failed after enabling quotas {CVE-2023-54153}
NFC: digital: Bounds check NFC-A cascade depth in SDD response handler {CVE-2026-31622}
block: fix overflow in blk_ioctl_discard() {CVE-2024-36917}
usb: xhci: Check endpoint is valid before dereferencing it {CVE-2023-52901}
iio: core: fix memleak in iio_device_register_sysfs {CVE-2023-52643}
platform/x86/amd/pmc: Detect when STB is not available {CVE-2024-53072}
mm: memcg: fix NULL pointer in mem_cgroup_track_foreign_dirty_slowpath() {CVE-2023-52939}
dm thin: make get_first_thin use rcu-safe list first function {CVE-2025-21664}
bus: mhi: host: pci_generic: Use pci_try_reset_function() to avoid deadlock {CVE-2025-21951}
bonding: provide a net pointer to…

Record: CLSA-2026-1783355084
Updated: 2026-11-02

OSVSUSE-SU-2024:4314-1 No score