dbcve.org
Linux KernelOperating system · Linux

CVE-2026-53293

MEDIUM · 5.5 CVSS v3.1 Published 2026-06-26
Fix available
A fix is available. Upgrade to 6.6.141 / 6.11 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click Patch available 8 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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)

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis
How this class of weakness works · CWE-667

Shared resources are accessed without correct locking, so concurrent operations interleave into inconsistent — and sometimes exploitable — states, or deadlock the service outright. These bugs are subtle and timing-dependent. The fix is correct, consistent locking or atomic operations around every shared resource.

General guidance for the improper locking class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Linux KernelOperating system
Affected:>= 6.6.55, < 6.6.141>= 6.10.14, < 6.11>= 6.11.3, < 6.12.91>= 6.13, < 6.18.33>= 6.19, < 7.0.10= 7.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 6.6.141 / 6.11 / 6.12.91 or later
Fixed in 6.6.1416.116.12.91
Vendor patch git.kernel.org →
Recommended fix High confidence

6.6.141, 6.11, 6.12.91, or 6.18.33 (depending on your current branch)

  1. 1. Identify the currently running Linux kernel version using `uname -r`
  2. 2. Check which version branch your current kernel belongs to (e.g., 6.6.x, 6.10.x, 6.11.x, 6.13.x)
  3. 3. For kernels in the 6.6.x branch (>= 6.6.55): upgrade to kernel version 6.6.141 or later
  4. 4. For kernels in the 6.10.x branch: upgrade to kernel version 6.11 or later
  5. 5. For kernels in the 6.11.x branch (>= 6.11.3): upgrade to kernel version 6.12.91 or later
  6. 6. For kernels in the 6.13.x or later branch: upgrade to kernel version 6.18.33 or later
  7. 7. After upgrading, reboot the system to load the fixed kernel
  8. 8. Verify the fix is applied by checking the kernel version matches a fixed release
Caveat Kernel upgrades may require system reboot and could introduce regressions in third-party drivers; ensure compatibility with critical hardware before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-53293 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-53293 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data