5.5
MEDIUM CVSS 3.1
CVE-2026-53293
drm/amdgpu: fix AMDGPU_INFO_READ_MMR_REG
Description

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: fix AMDGPU_INFO_READ_MMR_REG There were multiple issues in that code. First of all the order between the reset semaphore and the mm_lock was wrong (e.g. copy_to_user) was called while holding the lock. Then we allocated memory while holding the reset semaphore which is also a pretty big bug and can deadlock. Then we used down_read_trylock() instead of waiting for the reset to finish. (cherry picked from commit 361b6e6b303d4b691f6c5974d3eaab67ca6dd90e)

INFO

Published Date :

June 26, 2026, 8:17 p.m.

Last Modified :

July 8, 2026, 3:53 a.m.

Remotely Exploit :

No

Source :

416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Products

The following products are affected by CVE-2026-53293 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

ID Vendor Product Action
1 Linux linux_kernel
CVSS Scores
The Common Vulnerability Scoring System is a standardized framework for assessing the severity of vulnerabilities in software and systems. We collect and displays CVSS scores from various sources for each CVE.
Score Version Severity Vector Exploitability Score Impact Score Source
CVSS 3.1 MEDIUM [email protected]
Solution
Apply kernel patch to fix semaphore and lock ordering, memory allocation bugs, and trylock usage.
  • Apply the provided kernel patch.
  • Ensure correct semaphore and lock ordering.
  • Avoid memory allocation while holding semaphores.
  • Use appropriate locking mechanisms.
Public PoC/Exploit Available at Github

CVE-2026-53293 has a 1 public PoC/Exploit available at Github. Go to the Public Exploits tab to see the list.

References to Advisories, Solutions, and Tools
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-53293 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-53293 weaknesses.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Linux_News_Daily

HTML

Updated: 3 weeks, 1 day ago
0 stars 0 fork 0 watcher
Born at : June 18, 2026, 2:26 a.m. This repo has been linked 2 different CVEs too.

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2026-53293 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2026-53293 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • Initial Analysis by [email protected]

    Jul. 08, 2026

    Action Type Old Value New Value
    Added CVSS V3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
    Added CWE CWE-667
    Added CPE Configuration OR *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.10.14 up to (excluding) 6.11 *cpe:2.3:o:linux:linux_kernel:7.1:rc1:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.13 up to (excluding) 6.18.33 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.19 up to (excluding) 7.0.10 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.11.3 up to (excluding) 6.12.91 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.6.55 up to (excluding) 6.6.141
    Added Reference Type kernel.org: https://git.kernel.org/stable/c/0ef196a208385b7d7da79f411c161b04e97283e2 Types: Patch
    Added Reference Type kernel.org: https://git.kernel.org/stable/c/5c29d20470d4566d1b68df57097d642d01f8b427 Types: Patch
    Added Reference Type kernel.org: https://git.kernel.org/stable/c/61957c2e467b39b528a290016367d32a433fa846 Types: Patch
    Added Reference Type kernel.org: https://git.kernel.org/stable/c/8c4254c8f5836e77ae83e7fc037f02b69f7a0977 Types: Patch
    Added Reference Type kernel.org: https://git.kernel.org/stable/c/a31c3feb54b15a90232e497ad0e27e8a82052d8d Types: Patch
  • New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    Jun. 26, 2026

    Action Type Old Value New Value
    Added Affected [{'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '8361e3f7882876d98ba98cae0d3149450dd80912', 'lessThan': '8c4254c8f5836e77ae83e7fc037f02b69f7a0977', 'versionType': 'git'}, {'status': 'affected', 'version': '9e823f307074c0f82b5f6044943b0086e3079bed', 'lessThan': '61957c2e467b39b528a290016367d32a433fa846', 'versionType': 'git'}, {'status': 'affected', 'version': '9e823f307074c0f82b5f6044943b0086e3079bed', 'lessThan': 'a31c3feb54b15a90232e497ad0e27e8a82052d8d', 'versionType': 'git'}, {'status': 'affected', 'version': '9e823f307074c0f82b5f6044943b0086e3079bed', 'lessThan': '5c29d20470d4566d1b68df57097d642d01f8b427', 'versionType': 'git'}, {'status': 'affected', 'version': '9e823f307074c0f82b5f6044943b0086e3079bed', 'lessThan': '0ef196a208385b7d7da79f411c161b04e97283e2', 'versionType': 'git'}, {'status': 'affected', 'version': '17a98c942cb106ec08564e8f43b5470a4dd5d3f6', 'versionType': 'git'}, {'status': 'affected', 'version': '9a98563345697bdb1d3410ff428473b2e781f4db', 'versionType': 'git'}, {'status': 'affected', 'version': '6.6.55', 'lessThan': '6.6.141', 'versionType': 'semver'}, {'status': 'affected', 'version': '6.10.14', 'lessThan': '6.11', 'versionType': 'semver'}, {'status': 'affected', 'version': '6.11.3', 'lessThan': '6.12', 'versionType': 'semver'}], 'programFiles': ['drivers/gpu/drm/amd/amdgpu/amdgpu_kms.c'], 'defaultStatus': 'unaffected'}, {'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '6.12'}, {'status': 'unaffected', 'version': '0', 'lessThan': '6.12', 'versionType': 'semver'}, {'status': 'unaffected', 'version': '6.6.141', 'versionType': 'semver', 'lessThanOrEqual': '6.6.*'}, {'status': 'unaffected', 'version': '6.12.91', 'versionType': 'semver', 'lessThanOrEqual': '6.12.*'}, {'status': 'unaffected', 'version': '6.18.33', 'versionType': 'semver', 'lessThanOrEqual': '6.18.*'}, {'status': 'unaffected', 'version': '7.0.10', 'versionType': 'semver', 'lessThanOrEqual': '7.0.*'}, {'status': 'unaffected', 'version': '7.1', 'versionType': 'original_commit_for_fix', 'lessThanOrEqual': '*'}], 'programFiles': ['drivers/gpu/drm/amd/amdgpu/amdgpu_kms.c'], 'defaultStatus': 'affected'}]
    Added Description In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: fix AMDGPU_INFO_READ_MMR_REG There were multiple issues in that code. First of all the order between the reset semaphore and the mm_lock was wrong (e.g. copy_to_user) was called while holding the lock. Then we allocated memory while holding the reset semaphore which is also a pretty big bug and can deadlock. Then we used down_read_trylock() instead of waiting for the reset to finish. (cherry picked from commit 361b6e6b303d4b691f6c5974d3eaab67ca6dd90e)
    Added Reference https://git.kernel.org/stable/c/0ef196a208385b7d7da79f411c161b04e97283e2
    Added Reference https://git.kernel.org/stable/c/5c29d20470d4566d1b68df57097d642d01f8b427
    Added Reference https://git.kernel.org/stable/c/61957c2e467b39b528a290016367d32a433fa846
    Added Reference https://git.kernel.org/stable/c/8c4254c8f5836e77ae83e7fc037f02b69f7a0977
    Added Reference https://git.kernel.org/stable/c/a31c3feb54b15a90232e497ad0e27e8a82052d8d
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.