Security readout for executives and security teams
Plain-English summary
CVE-2024-58052 is a Linux kernel AMDGPU driver flaw that could crash affected systems if a missing firmware data table is dereferenced. It is availability-only: the sources do not indicate data theft or privilege escalation. Kernel maintainers note the problematic condition should not normally occur on the relevant Polaris GPU path.
Executive priority
Treat as routine but time-bound kernel maintenance. The business risk is localized denial of service, not confirmed compromise. Prioritize shared workstations, GPU-enabled systems, and any production Linux hosts using AMD GPUs, then fold the fix into normal kernel patch cycles.
Technical view
In atomctrl_get_smc_sclk_range_table(), amdgpu code failed to check whether smu_atom_get_data_table() returned NULL for the SMU_Info table. A later dereference could trigger a NULL pointer dereference. The CVE maps to CWE-476 and CVSS 3.1 score 5.5, local attack vector, low privileges, and high availability impact.
Likely exposure
Exposure is most relevant to Linux systems using AMDGPU with Polaris-era hardware and affected kernel builds. The bundle lists Linux as affected and references stable kernel fixes plus Debian LTS advisories. Systems without the affected driver path or hardware are less likely to be practically exposed.
Exploitation context
The source bundle does not show active exploitation, and KEV is false. The CVSS vector requires local access with low privileges and no user interaction. Maintainers also state the missing table should not happen in practice on the chips where this code is called.
Researcher notes
The vulnerability was found by Linux Verification Center using SVACE. The key uncertainty is practical reachability: upstream says the SMU_Info table should always be present on Polaris chips. Validation should focus on kernel lineage, driver use, and distro backports rather than assuming all Linux hosts are equally exposed.
Mitigation direction
- Update to a vendor-supported kernel containing the referenced stable fixes.
- Apply Debian LTS kernel updates where Debian advisories apply.
- Prioritize systems with AMD Polaris GPUs and the amdgpu driver loaded.
- Check Linux distribution guidance for exact fixed package versions.
- Use normal change control for kernel rollout and reboot planning.
Validation and detection
- Inventory Linux hosts with AMDGPU hardware or the amdgpu driver present.
- Compare running kernel versions against vendor fixed advisories.
- Confirm Debian LTS systems received the referenced kernel security updates.
- Review crash logs for NULL dereference traces in AMDGPU code.
- Document exceptions where affected hardware or driver paths are absent.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-476: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2024-58052 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H1.83.6CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
5.5MediumVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/a713ba7167c2d74c477dd7764dbbdbe3199f17f4CVE reference, Linux
- https://git.kernel.org/stable/c/c47066ed7c8f3b320ef87fa6217a2b8b24e127ccCVE reference, Linux
- https://git.kernel.org/stable/c/2396bc91935c6da0588ce07850d07897974bd350CVE reference, Linux
- https://git.kernel.org/stable/c/ae522ad211ec4b72eaf742b25f24b0a406afcba1CVE reference, Linux
- https://git.kernel.org/stable/c/6a30634a2e0f1dd3c6b39fd0f114c32893a9907aCVE reference, Linux
- https://git.kernel.org/stable/c/0b97cd8a61b2b40fd73cf92a4bb2256462d22adbCVE reference, Linux
- https://git.kernel.org/stable/c/396350adf0e5ad4bf05f01e4d79bfb82f0f6c41aCVE reference, Linux
- https://git.kernel.org/stable/c/357445e28ff004d7f10967aa93ddb4bffa5c3688CVE reference, Linux
- https://lists.debian.org/debian-lts-announce/2025/05/msg00030.htmlCVE reference, CVE
- https://lists.debian.org/debian-lts-announce/2025/03/msg00028.htmlCVE reference, CVE
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
NULL Pointer Dereference
NULL Pointer Dereference represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.