Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-93176: drm/amd/display: Fix dangling pointer in plane reset function

Noroxi assessment

Priority: Monitor (action score 28/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. Special conditions such as timing or configuration are required.
  • Fixed version: Linux Linux 0999a267bdc13648b6b0db893e7eabe30bc13e7c, 154883749cae674fb38e83c1b3a096ce71122229, 3d8391d3149a1aeb93505a4f9fb9ed8364882c42.

Low priority for now. Upgrade to Linux Linux 0999a267bdc13648b6b0db893e7eabe30bc13e7c, 154883749cae674fb38e83c1b3a096ce71122229, 3d8391d3149a1aeb93505a4f9fb9ed8364882c42 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/amd/display: Fix dangling pointer in plane reset function amdgpu_dm_plane_drm_plane_reset() frees the old state before allocating a new one. If kzalloc() fails, the function returns without updating the state pointer, leaving a dangling pointer to already freed memory. Fix this by allocating the new state first. On allocation failure, the old state remains untouched and the function safely returns. Found by Linux Verification Center (linuxtesting.org) with SVACE. [adjust for movement around current amd-staging-drm-next]

HighCVSS 7.0 · v3.1—No exploit Fix available
Published
Sep 17, 2026
Updated
Oct 30, 2026
EPSS
0.1% · 4th percentile
CWE
—

Report tools

JSON

Action score

28

Monitor

Low priority for now.

CVSS
28 / 40 · 7.0 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CNA vs NVD score

NVD
—
CNA · Linux
7.0
NVD has not scored this yet; the score shown is the CNA’s.

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

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.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

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.

—

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.0affected
    • 5d945cbcd4b16a29d6470a80dfb19738f9a4319f and later · before 154883749cae674fb38e83c1b3a096ce71122229affected · git
    • 5d945cbcd4b16a29d6470a80dfb19738f9a4319f and later · before cda8af27b787d79eadc4eb8109d9f2e856dadac2affected · git
    • 5d945cbcd4b16a29d6470a80dfb19738f9a4319f and later · before 0999a267bdc13648b6b0db893e7eabe30bc13e7caffected · git
    • 5d945cbcd4b16a29d6470a80dfb19738f9a4319f and later · before 3d8391d3149a1aeb93505a4f9fb9ed8364882c42affected · git
    • 5d945cbcd4b16a29d6470a80dfb19738f9a4319f and later · before 80c0f51aced43d6eaf72f95a2833b0a77cf7880daffected · git
    • 5d945cbcd4b16a29d6470a80dfb19738f9a4319f and later · before 98cad4bd1443975d972f4c7f705980da03722a22affected · git
    • before 6.0not affected · semver
    • 6.1.191 and later · up to and including 6.1.*not affected · semver
    • 6.6.160 and later · up to and including 6.6.*not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxfrom 0—
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-93174Sep 17, 2026 · bpf: Copy per-CPU map value padding in copy_map_value_long()
    0Monitor
  • ← EarlierCVE-2026-93175Sep 17, 2026 · drm/amd/display: Fix dangling pointer in CRTC reset function
    31Monitor
  • Later →CVE-2026-93177Sep 17, 2026 · drm/amdgpu/pm/powerplay: bounds-check voltage index in Vega10 lookup
    29Monitor

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 Linux0999a267bdc13648b6b0db893e7eabe30bc13e7cVendor (CNA)
Linux Linux154883749cae674fb38e83c1b3a096ce71122229Vendor (CNA)
Linux Linux3d8391d3149a1aeb93505a4f9fb9ed8364882c42Vendor (CNA)
Linux Linux80c0f51aced43d6eaf72f95a2833b0a77cf7880dVendor (CNA)
Linux Linux98cad4bd1443975d972f4c7f705980da03722a22Vendor (CNA)
Linux Linuxcda8af27b787d79eadc4eb8109d9f2e856dadac2Vendor (CNA)
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).

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.
  • Special conditions such as timing or configuration are required.

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
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

—

CVSS vector

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

nvd-secondary

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 (5 more)

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

All records