Executive Summary

Informations
Name CVE-2024-53072 First vendor Publication 2024-11-19
Vendor Cve Last vendor Modification 2024-11-25

Security-Database Scoring CVSS v3

Cvss vector : CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Overall CVSS Score 5.5
Base Score 5.5 Environmental Score 5.5
impact SubScore 3.6 Temporal Score 5.5
Exploitabality Sub Score 1.8
 
Attack Vector Local Attack Complexity Low
Privileges Required Low User Interaction None
Scope Unchanged Confidentiality Impact None
Integrity Impact None Availability Impact High
Calculate full CVSS 3.0 Vectors scores

Security-Database Scoring CVSS v2

Cvss vector :
Cvss Base Score N/A Attack Range N/A
Cvss Impact Score N/A Attack Complexity N/A
Cvss Expoit Score N/A Authentication N/A
Calculate full CVSS 2.0 Vectors scores

Detail

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.

Original Source

Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-53072

CPE : Common Platform Enumeration

TypeDescriptionCount
Application 8
Os 3665

Sources (Detail)

https://git.kernel.org/stable/c/67ff30e24a0466bdd5be1d0b84385ec3c85fdacd
https://git.kernel.org/stable/c/7a3ed3f125292bc3398e04d10108124250892e3f
https://git.kernel.org/stable/c/a50863dd1f92d43c975ab2ecc3476617fe98a66e
https://git.kernel.org/stable/c/bceec87a73804bb4c33b9a6c96e2d27cd893a801
Source Url

Alert History

If you want to see full details history, please login or register.
0
1
2
3
4
5
6
Date Informations
2025-01-08 03:07:29
  • Multiple Updates
2025-01-07 03:07:02
  • Multiple Updates
2024-12-25 03:05:38
  • Multiple Updates
2024-12-12 03:08:32
  • Multiple Updates
2024-11-26 00:22:47
  • Multiple Updates
2024-11-20 00:20:26
  • Multiple Updates
2024-11-19 21:20:27
  • First insertion