LiveActive security incident?Get immediate response
CVE Record

CVE-2023-52825: drm/amdkfd: Fix a race condition of vram buffer unref in svm code

In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: Fix a race condition of vram buffer unref in svm code prange->svm_bo unref can happen in both mmu callback and a callback after migrate to system ram. Both are async call in different tasks. Sync svm_bo unref operation to avoid random "use-after-free".

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel race condition in AMD GPU memory-management code. A local, low-privileged user could cause a use-after-free condition that affects system availability. The public sources do not show data theft, privilege escalation, or active exploitation.

Executive priority

Treat this as a moderate availability risk. It is not presented as remotely exploitable or actively exploited, but kernel defects can cause operational disruption on shared Linux or GPU compute systems. Patch during the next normal kernel maintenance cycle unless affected hosts are high-availability or multi-tenant.

Technical view

CVE-2023-52825 is a CWE-362 race in drm/amdkfd SVM handling. Asynchronous callbacks can both unreference prange->svm_bo, producing a random use-after-free. CVSS 3.1 is 5.5 with local access, low complexity, low privileges, no user interaction, and high availability impact only.

Likely exposure

Exposure is most relevant to Linux systems running affected kernel versions and using AMDGPU KFD/SVM paths, such as GPU compute or AMD graphics workloads. Systems without the affected kernel code path are less likely exposed, but kernel package mapping should come from the distributor.

Exploitation context

The bundle marks KEV as false and provides no cited evidence of active exploitation. The CVSS vector indicates exploitation requires local access and low privileges. Expected impact is denial of service or instability rather than confidentiality or integrity compromise.

Researcher notes

The core issue is unsynchronized svm_bo unreference across asynchronous MMU and migration callbacks. The fix synchronizes the unref path to avoid random use-after-free. Public evidence is limited to the CVE record and Linux stable commits; no exploit details or active exploitation indicators are provided.

Mitigation direction

  • Apply the relevant Linux stable kernel fix or distributor kernel update.
  • Prioritize multi-user systems with AMD GPU or GPU compute workloads.
  • Check vendor or distribution advisories for exact package-to-kernel mapping.
  • Restrict unnecessary local shell access until patched.
  • Schedule reboot where required for kernel updates to take effect.

Validation and detection

  • Inventory running Linux kernel versions against distributor advisories.
  • Confirm updated kernels include the relevant stable fix commit.
  • Identify hosts using AMDGPU KFD or SVM-related workloads.
  • Review crash or kernel logs for unexplained AMDGPU/KFD instability.
  • Verify post-update systems are running the patched kernel.
Prepared
Confidence
high
Sources
7

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.

cwe · low confidence lookup

CWE-362: 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 lookup
cve · low confidence lookup

CVE-2023-52825 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
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

Official CVE source material

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.

1CVSS vectors
3Timeline events
2ADP providers
6Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
5.5CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H1.83.6CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

5.5Medium
CVSS 3.1 vector shape for CVE-2023-52825Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxe49fe4040a10c1cd3b215c511f658d15aa7c8be9, e49fe4040a10c1cd3b215c511f658d15aa7c8be9, e49fe4040a10c1cd3b215c511f658d15aa7c8be9, e49fe4040a10c1cd3b215c511f658d15aa7c8be9, e49fe4040a10c1cd3b215c511f658d15aa7c8be9unaffected
LinuxLinux5.14, 0, 5.15.140, 6.1.64, 6.5.13, 6.6.3, 6.7affected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-362 · source CWE mapping

Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.