Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-46276: drm/amdgpu: fix zero-size GDS range init on RDNA4

Noroxi assessment

Priority: Monitor (action score 22/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.12% (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 095a8b0ad3c3b5cdc3850d961adb8a8f735220bb, 0e21db1a77967bc15df662efdca8ea8a61d124ea, 1f5d33e7b0a9a2a140f46e22fb52eede323c5946.

Low priority for now. Upgrade to Linux Linux 095a8b0ad3c3b5cdc3850d961adb8a8f735220bb, 0e21db1a77967bc15df662efdca8ea8a61d124ea, 1f5d33e7b0a9a2a140f46e22fb52eede323c5946 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: fix zero-size GDS range init on RDNA4 RDNA4 (GFX 12) hardware removes the GDS, GWS, and OA on-chip memory resources. The gfx_v12_0 initialisation code correctly leaves adev->gds.gds_size, adev->gds.gws_size, and adev->gds.oa_size at zero to reflect this. amdgpu_ttm_init() unconditionally calls amdgpu_ttm_init_on_chip() for each of these resources regardless of size. When the size is zero, amdgpu_ttm_init_on_chip() forwards the call to ttm_range_man_init(), which calls drm_mm_init(mm, 0, 0). drm_mm_init() immediately fires DRM_MM_BUG_ON(start + size <= start) -- trivially true when size is zero -- crashing the kernel during modprobe of amdgpu on an RX 9070 XT. Guard against this by returning 0 early from amdgpu_ttm_init_on_chip() when size_in_page is zero. This skips TTM resource manager registration for hardware resources that are absent, without affecting any other GPU type. DRM_MM_BUG_ON() only asserts if CONFIG_DRM_DEBUG_MM is enabled in the kernel config. This is apparently rarely enabled as these chips have been in the market for over a year and this issue was only reported now. Oops-Analysis: http://oops.fenrus.org/reports/bugzilla.korg/221376/report.html (cherry picked from commit 5719ce5865279cad4fd5f01011fe037168503f2d)

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Jun 8, 2026
Updated
Jul 23, 2026
EPSS
0.1% · 2th percentile
CWE
—

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

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

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.

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 kernel4.20 and later · before 5.10.258
  • linux linux kernel5.11 and later · before 5.15.209
  • linux linux kernel5.16 and later · before 6.1.175
  • linux linux kernel6.2 and later · before 6.6.140
  • linux linux kernel6.7 and later · before 6.12.86
  • linux linux kernel6.13 and later · before 6.18.27
  • linux linux kernel6.19 and later · before 7.0.4
  • 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

    • 4.20affected
    • c832c346cdf9022872655be621880e0f66f4135d and later · before 1f5d33e7b0a9a2a140f46e22fb52eede323c5946affected · git
    • c832c346cdf9022872655be621880e0f66f4135d and later · before 9bc925759c05feae7dfa9570e77131d54729c8eaaffected · git
    • c832c346cdf9022872655be621880e0f66f4135d and later · before 36f9602fb22ede69fcc8b422be0cf8105bf655adaffected · git
    • c832c346cdf9022872655be621880e0f66f4135d and later · before be0376affcafa0bbb371bb501579a825eae32281affected · git
    • c832c346cdf9022872655be621880e0f66f4135d and later · before 0e21db1a77967bc15df662efdca8ea8a61d124eaaffected · git
    • c832c346cdf9022872655be621880e0f66f4135d and later · before 30c000a49094ec568c9b51b7421f7a4a3f0b0298affected · git
    • c832c346cdf9022872655be621880e0f66f4135d and later · before 3e26c76891ab99fa173e9c501119fbb5c9f4600faffected · git
    • c832c346cdf9022872655be621880e0f66f4135d and later · before 095a8b0ad3c3b5cdc3850d961adb8a8f735220bbaffected · git
    • before 4.20not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.176-16.1.176-1
Debian:13linuxbefore 6.12.86-16.12.86-1
Debian:14linuxbefore 7.0.4-17.0.4-1
openSUSE:Tumbleweedkernel-sourcebefore 7.0.12-1.17.0.12-1.1

Same product

linux: all records

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-2025-71315Jun 8, 2026 · drm/vkms: Convert to DRM's vblank timer
    22Monitor
  • ← EarlierCVE-2026-46274Jun 8, 2026 · io-wq: check that the predecessor is hashed in io_wq_remove_pending()
    31Monitor
  • Later →CVE-2026-46277Jun 8, 2026 · mm/zone_device: do not touch device folio after calling ->folio_free()
    31Monitor

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 Linux095a8b0ad3c3b5cdc3850d961adb8a8f735220bbVendor (CNA)
Linux Linux0e21db1a77967bc15df662efdca8ea8a61d124eaVendor (CNA)
Linux Linux1f5d33e7b0a9a2a140f46e22fb52eede323c5946Vendor (CNA)
Linux Linux30c000a49094ec568c9b51b7421f7a4a3f0b0298Vendor (CNA)
Linux Linux36f9602fb22ede69fcc8b422be0cf8105bf655adVendor (CNA)
Linux Linux3e26c76891ab99fa173e9c501119fbb5c9f4600fVendor (CNA)
Linux Linux9bc925759c05feae7dfa9570e77131d54729c8eaVendor (CNA)
Linux Linuxbe0376affcafa0bbb371bb501579a825eae32281Vendor (CNA)
debian:linux6.1.176-1 · Debian:12Package registry (OSV)
opensuse:kernel-source7.0.12-1.1 · openSUSE:TumbleweedPackage 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.

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.

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.
  • No special conditions are required; it is repeatable.

If successful

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

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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. Fix✗ → ✓

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

References

Show all references (7 more)

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

All records