HOL LogoGuard

Explore HOL

  • HOL home
  • AI agent registry
  • AI plugins
  • Open standards
  • HOL members

Guard product

  • Guard overviewLocal security and control for AI agents and the tools they use.
  • FeaturesRuntime protection, policy routing, review, and evidence.

Explore Guard

  • Product previewWalk through Guard surfaces in read-only demo mode.
  • ComparisonCompare Guard with native controls and AI security vendors.

AI tools

  • All AI toolsEvery supported AI tool and how Guard applies policy to it.
  • Codex
  • Claude Code
  • Cursor
  • Gemini CLI
  • OpenCode
  • Hermes
  • OpenClaw
  • GitHub Copilot CLI
  • Antigravity
  • Kimi
  • Grok
  • Pi / Oh My Pi
  • Zcode

Extensions

  • All extensionsBrowse command and MCP coverage with owners and stated limits.
  • Command coverageShell command protection across clouds, databases, backups, and packages.
  • MCP server coverageSee how Guard maps risk state across MCP tools and servers.
  • Core safetyThe safety floor listings that ship with Guard.
  • Data and resilienceBackup and storage command protection.
  • Cloud and infrastructureAWS, Azure, GCP, Kubernetes, and more.

Security

  • AI security hubSecurity research, advisories, and agent safety coverage.
  • AI tool securitySecurity profiles for each supported coding agent.
  • Safe labsHands-on attack simulations with safe boundaries.
  • Redacted warningsReal blocked actions with sensitive details removed.
  • AdvisoriesCoordinated disclosure reports for AI tooling.
  • Active CVEsSearch active CVEs affecting AI tooling.

Learn

  • Security guidesPractical guides for securing AI agent workflows.
  • DocsInstall, configure, and operate Guard with confidence.
  • ResearchPublished security research, benchmarks, and methodology.

Community

  • ReleasesVersion history, shipped changes and upgrade notes.
  • ContributorsThe people and contributions behind HOL Guard.
  • AffiliatesShare Guard with your audience and earn from referrals.
  • SponsorKeep agent security open: sponsor a project, place a banner, or fund a security initiative.
PricingEnterpriseOpen AppInstall Guard
  1. Guard
  2. Security
  3. CVEs
  4. CVE 2026 53143 drmamdkfd fix buffer overflow in sdma queue
HOL Guard

Public security guidance for teams protecting AI harnesses, MCP servers, skills, prompts, and local tool execution.

Install Guard

AI Security

  • Prompt injection
  • MCP security
  • OWASP MCP mapping
  • Supply chain

Resources

  • Trust packet
  • Harness setup
  • Redacted warnings
  • Safe labs

Product

  • Install Guard
  • Pricing
  • Open dashboard
Guard
  • Guard Overview
  • Releases
  • Contributors
  • Install Guard
  • Pricing
Docs
  • Documentation Index
  • Developer Hub
  • API Reference
  • Root OpenAPI
  • Registry OpenAPI
  • Run in Postman
  • Standards
  • Submit ERC-8004 Contract
  • Feature Your Agent
Best Plugins
  • Browse Plugins
  • Plugin Launches
  • Best Claude Plugins
  • Best Codex Plugins
  • Best Grok Plugins
  • Best Kimi Plugins
  • Best DeepSeek Plugins
  • Best Antigravity Plugins
  • Best MCP Servers
  • Best Cursor Plugins
  • Best OpenCode Plugins
Best Agents
  • Best ERC-8004 Agents
  • Best Virtuals Agents
  • Best MCP Servers
  • Best A2A Agents
  • Best x402 Payable
  • All Categories
Community
  • Telegram
  • X
More
  • About HOL
  • Contact
  • Blog
  • GitHub
  • Privacy
  • Terms of Service
Settings

Copyright ยฉ 2026 HOL DAO LLC. All rights reserved.

Back to active CVEs
High ยท CVSS 7.8CVE-2026-53143

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

Answer in brief

CVE-2026-53143 records a High severity (CVSS 7.8) vulnerability in drm/amdkfd: Fix buffer overflow in SDMA queue checkpoint/restore on GFX11. The current sources do not mark it as known exploited. The current feed maps Red Hat/kernel (generic), Red Hat/kernel-rt (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Jun 25, 2026Updated Aug 20, 2026Source checked Oct 4, 2026First seen by HOL Jun 25, 2026Material review Aug 20, 2026
Upstream Advisory

Key facts

Risk
High ยท CVSS 7.8
Exploitation
Not marked as known exploited
Affected software
11 mapped packages or products
Fix availability
Available

Why this deserves its current priority

CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Red Hat/kernel (generic), Red Hat/kernel-rt (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Affected products and reported versions
ProductAffected versionsFixed versions
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:linux:linux_kernel:7.1:rc1:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:linux:linux_kernel:7.1:rc2:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:linux:linux_kernel:7.1:rc3:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:linux:linux_kernel:7.1:rc4:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:linux:linux_kernel:7.1:rc5:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:linux:linux_kernel:7.1:rc6:*:*:*:*:*:*Not reportedNot reported
Mapped affected packages and fixed versions
PackageAffected rangeFixed version
Red Hat/kernelgeneric*Not reported
Red Hat/kernel-rtgeneric*Not reported
Linux/Linuxgeneric>=cc009e613de6560eb499f8bc92c80a737752cb30 <16dad1fb0d783a4008de30e32d0038c393de05b1 || >=cc009e613de6560eb499f8bc92c80a737752cb30 <2c5b66c9b4057b385566940935ebc32f6e6ebfd2 || >=cc009e613de6560eb499f8bc92c80a737752cb30 <d3efcadfe3eea5b4263b8f2d4463b15c9fc46a64 || >=cc009e613de6560eb499f8bc92c80a737752cb30 <d02f05d30f35b036f7cbaf72de634affb5b38ec6 || >=cc009e613de6560eb499f8bc92c80a737752cb30 <352ea59028ea48a6fff77f19ae28f98f71946a8016dad1fb0d783a4008de30e32d0038c393de05b1, 2c5b66c9b4057b385566940935ebc32f6e6ebfd2, d3efcadfe3eea5b4263b8f2d4463b15c9fc46a64, d02f05d30f35b036f7cbaf72de634affb5b38ec6, 352ea59028ea48a6fff77f19ae28f98f71946a80
Linux/Linuxgeneric5.19Not reported

Recommended response

  1. 1Check inventory. Check lockfiles and deployed manifests for Red Hat/kernel, Red Hat/kernel-rt, Linux/Linux.
  2. 2Review the reported fix. Update Linux/Linux to 16dad1fb0d783a4008de30e32d0038c393de05b1 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    Jun 25, 2026

    Evidence: source:cvelist:source_dates:source-dates:record
  2. Source modified

    Aug 20, 2026

    Evidence: source:cvelist:source_dates:source-dates:record
  3. First seen by HOL

    Jun 25, 2026

Sources and claim methodology

  • Source referenceaccess.redhat.com
  • Source referenceaccess.redhat.com
  • Source referenceaccess.redhat.com
  • Source referencebugzilla.redhat.com
  • Source referencegit.kernel.org
  • Source referencegit.kernel.org
  • Source referencegit.kernel.org
  • Source referencegit.kernel.org
  • Source referencegit.kernel.org
  • Source referencesecurity.access.redhat.com
Upstream source description

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)

Quoted source text, attributed separately from HOL analysis.

Related CVEs

  • WordPress TranslatePress plugin <= 3.3.6 - Cross Site Scripting (XSS) vulnerabilitySame generic ecosystem
  • WordPress Unlimited Elements For Elementor (Free Widgets, Addons, Templates) plugin <= 2.0.20 - Cross Site Scripting (XSS) vulnerabilitySame generic ecosystem
  • WordPress Gutenberg Blocks by Kadence Blocks plugin <= 3.7.11.1 - Cross Site Scripting (XSS) vulnerabilitySame generic ecosystem
  • WordPress Unlimited Elements For Elementor (Free Widgets, Addons, Templates) plugin <= 2.0.20 - SQL Injection vulnerabilitySame generic ecosystem
  • Razorpay for WooCommerce < 4.8.8 - Unauthenticated Order Shipping Modification via IDORSame generic ecosystem
  • Simple Shopping Cart < 5.2.6 - Admin+ Stored XSS via PayPal API CredentialsSame generic ecosystem

Record context

Vulnerability class
Memory Corruption
EPSS
Not reported
CWE IDs
CWE-131, CWE-787
Source
CVE List V5
Source checked
Oct 4, 2026
References
10 linked sources
Open source record