Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-89812: drm/amdgpu: force complete the MES ring fences on reset

Noroxi assessment

Priority: Monitor (action score 0/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.20% (FIRST EPSS).
  • Fixed version: Linux Linux 48dc279c3010ac8f91b1845b2abb3a1e9943a0f5, 7d722821e2f626c4e34c8510f0ce1d6f10c77a3b, c48d5a4d2863e56a6692ecb6cd6c32404f40cd0f.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 48dc279c3010ac8f91b1845b2abb3a1e9943a0f5, 7d722821e2f626c4e34c8510f0ce1d6f10c77a3b, c48d5a4d2863e56a6692ecb6cd6c32404f40cd0f 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/amdgpu: force complete the MES ring fences on reset The MES scheduler ring has no drm scheduler (no_scheduler = true), so it is skipped by the force-completion loop in amdgpu_device_pre_asic_reset(). It uses a polling fence whose hw value lives in wb (GTT) memory and survives a MODE1 reset, while fence_drv.sync_seq keeps advancing for every packet. When the reset is triggered because MES itself stopped responding, the timed-out packets advance sync_seq past the last hw fence value MES wrote. After resume the first MES submission polls forever on a seq that is never written back, failing the resume and wedging the box on a second reset: amdgpu: MES ring buffer is full. amdgpu: *ERROR* ring gfx_0.0.0 test failed (-110) amdgpu: resume of IP block <gfx_v11_0> failed -110 amdgpu: GPU reset end with ret = -110 Force complete the MES scheduler ring fences together with the scheduler rings so their hw fence is realigned to sync_seq. v2: cover all XCCs (one scheduler ring each), not just mes.ring[0].

—No exploit Fix available
Published
Sep 16, 2026
Updated
Oct 21, 2026
EPSS
0.2% · 11th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

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-89812

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

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

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records
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.

—

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

    • 6.12affected
    • 34e087e8920e635c62e2ed6a758b0cd27f836d13 and later · before c48d5a4d2863e56a6692ecb6cd6c32404f40cd0faffected · git
    • 34e087e8920e635c62e2ed6a758b0cd27f836d13 and later · before 7d722821e2f626c4e34c8510f0ce1d6f10c77a3baffected · git
    • 34e087e8920e635c62e2ed6a758b0cd27f836d13 and later · before ebe7542553d008e2285e0fbba0c63f0295a7e694affected · git
    • 34e087e8920e635c62e2ed6a758b0cd27f836d13 and later · before 48dc279c3010ac8f91b1845b2abb3a1e9943a0f5affected · git
    • before 6.12not affected · semver
    • 6.12.114 and later · up to and including 6.12.*not affected · semver
    • 6.18.57 and later · up to and including 6.18.*not affected · semver
    • 7.2.5 and later · up to and including 7.2.*not affected · semver
    • 7.3 and laternot affected · original_commit_for_fix

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:13linuxbefore 6.12.115-26.12.115-2
Debian:14linuxbefore 7.2.6-17.2.6-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-89810Sep 16, 2026 · drm/amdkfd: Fix error path at svm_migrate_copy_to_ram
    31Monitor
  • ← EarlierCVE-2026-89811Sep 16, 2026 · drm/amdkfd: Add TLB flush after MES queue eviction/suspension
    35Monitor
  • Later →CVE-2026-89813Sep 16, 2026 · drm/amdgpu: force complete the KIQ ring fences on reset
    0Monitor

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 Linux48dc279c3010ac8f91b1845b2abb3a1e9943a0f5Vendor (CNA)
Linux Linux7d722821e2f626c4e34c8510f0ce1d6f10c77a3bVendor (CNA)
Linux Linuxc48d5a4d2863e56a6692ecb6cd6c32404f40cd0fVendor (CNA)
Linux Linuxebe7542553d008e2285e0fbba0c63f0295a7e694Vendor (CNA)
azl3 kernel 6.6.150.1-1 on Azure Linux 3.0—Microsoft (MSRC)
debian:linux6.12.115-2 · Debian:13Package registry (OSV)
debian:linux7.2.6-1 · Debian:14Package registry (OSV)

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.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

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.

Credits

All researchers

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

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

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. Fix✗ → ✓

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

References

Show all references (3 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records