Security readout for executives and security teams
Plain-English summary
This is a Linux kernel flaw in the AMD GPU KFD migration path. The kernel used inconsistent DMA mapping directions, which can trigger DMA core warnings during GPU memory migration. The sources do not provide CVSS, impact detail, or evidence of exploitation, so urgency depends on whether affected Linux kernels run AMD GPU workloads.
Executive priority
Treat this as a targeted kernel maintenance item, not an emergency, unless your environment relies on AMD GPU compute on affected kernels. Patch through normal kernel update channels and prioritize exposed GPU compute systems first.
Technical view
The issue is in drm/amdkfd SVM migration DMA handling. The DMA map direction did not match the unmap direction; the kernel fix aligns this by mapping as bidirectional. The supplied trace shows a DMA debug warning in check_unmap during an AMDGPU/KFD workload.
Likely exposure
Exposure appears limited to Linux systems running affected kernel versions with the AMDGPU KFD/SVM migration path in use. Systems without AMD GPU compute workloads are less likely to exercise the vulnerable path. Exact distribution exposure depends on vendor backports and kernel package status.
Exploitation context
CISA KEV is false in the supplied data. The bundle provides no public exploit, weaponization report, CVSS score, or attacker-controlled trigger details. The observable evidence is a kernel warning during a GPU runtime test workload, not confirmed real-world exploitation.
Researcher notes
Evidence is incomplete: no CWE, CVSS, exploitability analysis, or security impact beyond the DMA warning is supplied. Validation should focus on kernel branch mapping, commit presence, distribution backports, and whether amdgpu KFD SVM migration is reachable in deployed workloads.
Mitigation direction
Update to a vendor kernel containing the referenced stable Linux fixes.
For Debian LTS systems, review and apply the cited Debian LTS advisory update.
Prioritize AMD GPU compute hosts using affected Linux kernel branches.
If updates are unavailable, monitor vendor guidance for supported mitigations.
Avoid direct wrangler or deployment assumptions; this CVE is kernel-level.
Validation and detection
Inventory Linux kernel versions on hosts with AMD GPU workloads.
Check whether vendor kernel packages include the referenced stable commits.
Review kernel logs for DMA debug warnings in amdgpu or amdkfd paths.
Confirm patched systems run fixed kernel packages after reboot.
Track distribution advisories for backported fixes and affected status.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
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.
cve · low confidence lookup
CVE-2024-57897 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.
0CVSS vectors
3Timeline events
1ADP providers
7Source links
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.
Jan 15, 2025, 13:05 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.