Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-53143: drm/amdkfd: Fix buffer overflow in SDMA queue checkpoint/restore on GFX11

Noroxi assessment

Priority: Monitor (action score 31/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.15% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 16dad1fb0d783a4008de30e32d0038c393de05b1, 2c5b66c9b4057b385566940935ebc32f6e6ebfd2, 352ea59028ea48a6fff77f19ae28f98f71946a80; azl3 kernel 6.6.141.1-1 on Azure Linux 3.0 6.6.143.1-1.

Low priority for now. Upgrade to Linux Linux 16dad1fb0d783a4008de30e32d0038c393de05b1, 2c5b66c9b4057b385566940935ebc32f6e6ebfd2, 352ea59028ea48a6fff77f19ae28f98f71946a80; azl3 kernel 6.6.141.1-1 on Azure Linux 3.0 6.6.143.1-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: Fix buffer overflow in SDMA queue checkpoint/restore on GFX11 The v11 MQD manager incorrectly assigned the CP-compute variants of checkpoint_mqd/restore_mqd for KFD_MQD_TYPE_SDMA queues. These functions use sizeof(struct v11_compute_mqd) (2048 bytes) instead of sizeof(struct v11_sdma_mqd) (512 bytes), causing a 1536-byte overflow. During CRIU checkpoint of an SDMA queue on Navi3x: - checkpoint_mqd() reads 2048 bytes from a 512-byte SDMA MQD buffer, leaking 1536 bytes of adjacent GTT memory to userspace During CRIU restore: - restore_mqd() writes 2048 bytes into a 512-byte SDMA MQD buffer, corrupting 1536 bytes of adjacent GTT memory (often the ring buffer or neighboring MQDs) This is a copy-paste regression unique to v11. All other ASIC backends (cik, vi, v9, v10, v12) correctly use the SDMA-specific variants. Add checkpoint_mqd_sdma() and restore_mqd_sdma() functions that properly handle the smaller v11_sdma_mqd structure, matching the pattern used in other MQD managers. (cherry picked from commit 6fa41db7ffdec97d62433adf03b7b9b759af8c2c)

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Jun 25, 2026
Updated
Nov 6, 2026
EPSS
0.1% · 4th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
7.8
CNA · Linux
7.0
0.8 point gap

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-53143

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel5.19 and later · before 6.6.143
  • linux linux kernel6.7 and later · before 6.12.94
  • linux linux kernel6.13 and later · before 6.18.36
  • linux linux kernel6.19 and later · before 7.0.13
  • linux linux kernel7.1

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.19affected
    • cc009e613de6560eb499f8bc92c80a737752cb30 and later · before 16dad1fb0d783a4008de30e32d0038c393de05b1affected · git
    • cc009e613de6560eb499f8bc92c80a737752cb30 and later · before 2c5b66c9b4057b385566940935ebc32f6e6ebfd2affected · git
    • cc009e613de6560eb499f8bc92c80a737752cb30 and later · before d3efcadfe3eea5b4263b8f2d4463b15c9fc46a64affected · git
    • cc009e613de6560eb499f8bc92c80a737752cb30 and later · before d02f05d30f35b036f7cbaf72de634affb5b38ec6affected · git
    • cc009e613de6560eb499f8bc92c80a737752cb30 and later · before 352ea59028ea48a6fff77f19ae28f98f71946a80affected · git
    • before 5.19not affected · semver
    • 6.6.143 and later · up to and including 6.6.*not affected · semver
    • 6.12.94 and later · up to and including 6.12.*not affected · semver
    • 6.18.36 and later · up to and including 6.18.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10kernelbefore 6.12.0-211.49.1.el10_26.12.0-211.49.1.el10_2
AlmaLinux:10kernel-64kbefore 6.12.0-211.49.1.el10_26.12.0-211.49.1.el10_2
AlmaLinux:10kernel-64k-corebefore 6.12.0-211.49.1.el10_26.12.0-211.49.1.el10_2
AlmaLinux:10kernel-64k-debugbefore 6.12.0-211.49.1.el10_26.12.0-211.49.1.el10_2
AlmaLinux:10kernel-64k-debug-corebefore 6.12.0-211.49.1.el10_26.12.0-211.49.1.el10_2
AlmaLinux:10kernel-64k-debug-develbefore 6.12.0-211.49.1.el10_26.12.0-211.49.1.el10_2
AlmaLinux:10kernel-64k-debug-devel-matchedbefore 6.12.0-211.49.1.el10_26.12.0-211.49.1.el10_2
AlmaLinux:10kernel-64k-debug-modulesbefore 6.12.0-211.49.1.el10_26.12.0-211.49.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-corebefore 6.12.0-211.49.1.el10_26.12.0-211.49.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-extrabefore 6.12.0-211.49.1.el10_26.12.0-211.49.1.el10_2
AlmaLinux:10kernel-64k-develbefore 6.12.0-211.49.1.el10_26.12.0-211.49.1.el10_2
AlmaLinux:10kernel-64k-devel-matchedbefore 6.12.0-211.49.1.el10_26.12.0-211.49.1.el10_2
AlmaLinux:10kernel-64k-modulesbefore 6.12.0-211.49.1.el10_26.12.0-211.49.1.el10_2
AlmaLinux:10kernel-64k-modules-corebefore 6.12.0-211.49.1.el10_26.12.0-211.49.1.el10_2
AlmaLinux:10kernel-64k-modules-extrabefore 6.12.0-211.49.1.el10_26.12.0-211.49.1.el10_2
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-211.49.1.el10_26.12.0-211.49.1.el10_2
AlmaLinux:10kernel-corebefore 6.12.0-211.49.1.el10_26.12.0-211.49.1.el10_2
AlmaLinux:10kernel-cross-headersbefore 6.12.0-211.49.1.el10_26.12.0-211.49.1.el10_2
AlmaLinux:10kernel-debugbefore 6.12.0-211.49.1.el10_26.12.0-211.49.1.el10_2
AlmaLinux:10kernel-debug-corebefore 6.12.0-211.49.1.el10_26.12.0-211.49.1.el10_2
AlmaLinux:10kernel-debug-develbefore 6.12.0-211.49.1.el10_26.12.0-211.49.1.el10_2
AlmaLinux:10kernel-debug-devel-matchedbefore 6.12.0-211.49.1.el10_26.12.0-211.49.1.el10_2
AlmaLinux:10kernel-debug-modulesbefore 6.12.0-211.49.1.el10_26.12.0-211.49.1.el10_2
AlmaLinux:10kernel-debug-modules-corebefore 6.12.0-211.49.1.el10_26.12.0-211.49.1.el10_2

+96

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-53138Jun 25, 2026 · drm/amd/display: Bound VBIOS record-chain walk loops
    28Monitor
  • ← EarlierCVE-2026-53142Jun 25, 2026 · drm/xe/display: fix oops in suspend/shutdown without display
    22Monitor
  • Later →CVE-2026-53144Jun 25, 2026 · drm/amdkfd: fix NULL dereference in get_queue_ids()
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux16dad1fb0d783a4008de30e32d0038c393de05b1Vendor (CNA)
Linux Linux2c5b66c9b4057b385566940935ebc32f6e6ebfd2Vendor (CNA)
Linux Linux352ea59028ea48a6fff77f19ae28f98f71946a80Vendor (CNA)
Linux Linuxd02f05d30f35b036f7cbaf72de634affb5b38ec6Vendor (CNA)
Linux Linuxd3efcadfe3eea5b4263b8f2d4463b15c9fc46a64Vendor (CNA)
azl3 kernel 6.6.141.1-1 on Azure Linux 3.06.6.143.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
almalinux:kernel6.12.0-211.49.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k6.12.0-211.49.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-core6.12.0-211.49.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug6.12.0-211.49.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-core6.12.0-211.49.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-devel6.12.0-211.49.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched6.12.0-211.49.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules6.12.0-211.49.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules-core6.12.0-211.49.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra6.12.0-211.49.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-devel6.12.0-211.49.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-devel-matched6.12.0-211.49.1.el10_2 · AlmaLinux:10Package registry (OSV)
debian:linux6.12.94-1 · Debian:13Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:6.12.0-211.49.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debug-devel0:6.12.0-211.49.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debug-devel-matched0:6.12.0-211.49.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debuginfo0:6.12.0-211.49.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-devel0:6.12.0-211.49.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-devel-matched0:6.12.0-211.49.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-debuginfo0:6.12.0-211.49.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-devel0:6.12.0-211.49.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-devel-matched0:6.12.0-211.49.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debuginfo0:6.12.0-211.49.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debuginfo-common-aarch640:6.12.0-211.49.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)

+2

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-787 · Out-of-bounds Write

CVSS vector

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

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. SSVC exploitation— → none
  2. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records