Skip to content
Noroxi
CVE-2024-26656· NVD / CVE Program· CNA Linux

drm/amdgpu: fix use-after-free bug

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.23% (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 22207fd5c80177b860279653d017474b2812af5e, 22f665ecfd1225afa1309ace623157d12bb9bb0c, 2e13f88e01ae7e28a7e831bf5c2409c4748e0a60.
  • Severity is disputed: the assigning authority (CNA) scores it 7.8, NVD 5.5.
  • Mentioned 2 times in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 22207fd5c80177b860279653d017474b2812af5e, 22f665ecfd1225afa1309ace623157d12bb9bb0c, 2e13f88e01ae7e28a7e831bf5c2409c4748e0a60 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 use-after-free bug The bug can be triggered by sending a single amdgpu_gem_userptr_ioctl to the AMDGPU DRM driver on any ASICs with an invalid address and size. The bug was reported by Joonkyo Jung <joonkyoj@yonsei.ac.kr>. For example the following code: static void Syzkaller1(int fd) { struct drm_amdgpu_gem_userptr arg; int ret; arg.addr = 0xffffffffffff0000; arg.size = 0x80000000; /*2 Gb*/ arg.flags = 0x7; ret = drmIoctl(fd, 0xc1186451/*amdgpu_gem_userptr_ioctl*/, &arg); } Due to the address and size are not valid there is a failure in amdgpu_hmm_register->mmu_interval_notifier_insert->__mmu_interval_notifier_insert-> check_shl_overflow, but we even the amdgpu_hmm_register failure we still call amdgpu_hmm_unregister into amdgpu_gem_object_free which causes access to a bad address. The following stack is below when the issue is reproduced when Kazan is enabled: [ +0.000014] Hardware name: ASUS System Product Name/ROG STRIX B550-F GAMING (WI-FI), BIOS 1401 12/03/2020 [ +0.000009] RIP: 0010:mmu_interval_notifier_remove+0x327/0x340 [ +0.000017] Code: ff ff 49 89 44 24 08 48 b8 00 01 00 00 00 00 ad de 4c 89 f7 49 89 47 40 48 83 c0 22 49 89 47 48 e8 ce d1 2d 01 e9 32 ff ff ff <0f> 0b e9 16 ff ff ff 4c 89 ef e8 fa 14 b3 ff e9 36 ff ff ff e8 80 [ +0.000014] RSP: 0018:ffffc90002657988 EFLAGS: 00010246 [ +0.000013] RAX: 0000000000000000 RBX: 1ffff920004caf35 RCX: ffffffff8160565b [ +0.000011] RDX: dffffc0000000000 RSI: 0000000000000004 RDI: ffff8881a9f78260 [ +0.000010] RBP: ffffc90002657a70 R08: 0000000000000001 R09: fffff520004caf25 [ +0.000010] R10: 0000000000000003 R11: ffffffff8161d1d6 R12: ffff88810e988c00 [ +0.000010] R13: ffff888126fb5a00 R14: ffff88810e988c0c R15: ffff8881a9f78260 [ +0.000011] FS: 00007ff9ec848540(0000) GS:ffff8883cc880000(0000) knlGS:0000000000000000 [ +0.000012] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ +0.000010] CR2: 000055b3f7e14328 CR3: 00000001b5770000 CR4: 0000000000350ef0 [ +0.000010] Call Trace: [ +0.000006] <TASK> [ +0.000007] ? show_regs+0x6a/0x80 [ +0.000018] ? __warn+0xa5/0x1b0 [ +0.000019] ? mmu_interval_notifier_remove+0x327/0x340 [ +0.000018] ? report_bug+0x24a/0x290 [ +0.000022] ? handle_bug+0x46/0x90 [ +0.000015] ? exc_invalid_op+0x19/0x50 [ +0.000016] ? asm_exc_invalid_op+0x1b/0x20 [ +0.000017] ? kasan_save_stack+0x26/0x50 [ +0.000017] ? mmu_interval_notifier_remove+0x23b/0x340 [ +0.000019] ? mmu_interval_notifier_remove+0x327/0x340 [ +0.000019] ? mmu_interval_notifier_remove+0x23b/0x340 [ +0.000020] ? __pfx_mmu_interval_notifier_remove+0x10/0x10 [ +0.000017] ? kasan_save_alloc_info+0x1e/0x30 [ +0.000018] ? srso_return_thunk+0x5/0x5f [ +0.000014] ? __kasan_kmalloc+0xb1/0xc0 [ +0.000018] ? srso_return_thunk+0x5/0x5f [ +0.000013] ? __kasan_check_read+0x11/0x20 [ +0.000020] amdgpu_hmm_unregister+0x34/0x50 [amdgpu] [ +0.004695] amdgpu_gem_object_free+0x66/0xa0 [amdgpu] [ +0.004534] ? __pfx_amdgpu_gem_object_free+0x10/0x10 [amdgpu] [ +0.004291] ? do_syscall_64+0x5f/0xe0 [ +0.000023] ? srso_return_thunk+0x5/0x5f [ +0.000017] drm_gem_object_free+0x3b/0x50 [drm] [ +0.000489] amdgpu_gem_userptr_ioctl+0x306/0x500 [amdgpu] [ +0.004295] ? __pfx_amdgpu_gem_userptr_ioctl+0x10/0x10 [amdgpu] [ +0.004270] ? srso_return_thunk+0x5/0x5f [ +0.000014] ? __this_cpu_preempt_check+0x13/0x20 [ +0.000015] ? srso_return_thunk+0x5/0x5f [ +0.000013] ? sysvec_apic_timer_interrupt+0x57/0xc0 [ +0.000020] ? srso_return_thunk+0x5/0x5f [ +0.000014] ? asm_sysvec_apic_timer_interrupt+0x1b/0x20 [ +0.000022] ? drm_ioctl_kernel+0x17b/0x1f0 [drm] [ +0.000496] ? __pfx_amdgpu_gem_userptr_ioctl+0x10/0x10 [amdgpu] [ +0.004272] ? drm_ioctl_kernel+0x190/0x1f0 [drm] [ +0.000492] drm_ioctl_kernel+0x140/0x1f0 [drm] [ +0.000497] ? __pfx_amdgpu_gem_userptr_ioctl+0x10/0x10 [amdgpu] [ +0.004297] ? __pfx_drm_ioctl_kernel+0x10/0x10 [d ---truncated---

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Apr 2, 2024
Updated
Aug 5, 2026
EPSS
0.2% · 13th percentile

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.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
5.5
CNA · Linux
7.8
2.3 point gap

CVSS:3.1/AV:L/AC:L/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-2024-26656

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 kernelbefore 6.9

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.2affected
    • d38ceaf99ed015f2a0b9af3499791bd3a3daae21 and later · before 2e13f88e01ae7e28a7e831bf5c2409c4748e0a60affected · git
    • d38ceaf99ed015f2a0b9af3499791bd3a3daae21 and later · before e87e08c94c9541b4e18c4c13f2f605935f512605affected · git
    • d38ceaf99ed015f2a0b9af3499791bd3a3daae21 and later · before af054a5fb24a144f99895afce9519d709891894caffected · git
    • d38ceaf99ed015f2a0b9af3499791bd3a3daae21 and later · before 22f665ecfd1225afa1309ace623157d12bb9bb0caffected · git
    • d38ceaf99ed015f2a0b9af3499791bd3a3daae21 and later · before 22207fd5c80177b860279653d017474b2812af5eaffected · git
    • before 4.2not affected · semver
    • 6.1.132 and later · up to and including 6.1.*not affected · semver
    • 6.6.24 and later · up to and including 6.6.*not affected · semver
    • 6.7.12 and later · up to and including 6.7.*not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:11linux-6.1before 6.1.137-1~deb11u16.1.137-1~deb11u1
Debian:12linuxbefore 6.1.133-16.1.133-1
Debian:13linuxbefore 6.7.12-16.7.12-1
Red Hat:rhel_aus:8.6::baseosbpftoolbefore 0:4.18.0-372.129.1.el8_60:4.18.0-372.129.1.el8_6
Red Hat:rhel_aus:8.6::baseosbpftool-debuginfobefore 0:4.18.0-372.129.1.el8_60:4.18.0-372.129.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernelbefore 0:4.18.0-372.129.1.el8_60:4.18.0-372.129.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-abi-stablelistsbefore 0:4.18.0-372.129.1.el8_60:4.18.0-372.129.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-corebefore 0:4.18.0-372.129.1.el8_60:4.18.0-372.129.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-debugbefore 0:4.18.0-372.129.1.el8_60:4.18.0-372.129.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-debug-corebefore 0:4.18.0-372.129.1.el8_60:4.18.0-372.129.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-debug-debuginfobefore 0:4.18.0-372.129.1.el8_60:4.18.0-372.129.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-debug-develbefore 0:4.18.0-372.129.1.el8_60:4.18.0-372.129.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-debug-modulesbefore 0:4.18.0-372.129.1.el8_60:4.18.0-372.129.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-debug-modules-extrabefore 0:4.18.0-372.129.1.el8_60:4.18.0-372.129.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-debuginfobefore 0:4.18.0-372.129.1.el8_60:4.18.0-372.129.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-debuginfo-common-x86_64before 0:4.18.0-372.129.1.el8_60:4.18.0-372.129.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-develbefore 0:4.18.0-372.129.1.el8_60:4.18.0-372.129.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-docbefore 0:4.18.0-372.129.1.el8_60:4.18.0-372.129.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-modulesbefore 0:4.18.0-372.129.1.el8_60:4.18.0-372.129.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-modules-extrabefore 0:4.18.0-372.129.1.el8_60:4.18.0-372.129.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-toolsbefore 0:4.18.0-372.129.1.el8_60:4.18.0-372.129.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-tools-debuginfobefore 0:4.18.0-372.129.1.el8_60:4.18.0-372.129.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-tools-libsbefore 0:4.18.0-372.129.1.el8_60:4.18.0-372.129.1.el8_6
Red Hat:rhel_aus:8.6::baseosperfbefore 0:4.18.0-372.129.1.el8_60:4.18.0-372.129.1.el8_6

+96

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • 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
  • CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV
    83Now

Published before and after this one in the same product

  • ← EarlierCVE-2023-52635Apr 2, 2024 · PM / devfreq: Synchronize devfreq_monitor_[start/stop]
    22Monitor
  • ← EarlierCVE-2023-52636Apr 2, 2024 · libceph: just wait for more data to be available on the socket
    22Monitor
  • Later →CVE-2024-26657Apr 2, 2024 · drm/sched: fix null-ptr-deref in init entity
    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 Linux22207fd5c80177b860279653d017474b2812af5eVendor (CNA)
Linux Linux22f665ecfd1225afa1309ace623157d12bb9bb0cVendor (CNA)
Linux Linux2e13f88e01ae7e28a7e831bf5c2409c4748e0a60Vendor (CNA)
Linux Linuxaf054a5fb24a144f99895afce9519d709891894cVendor (CNA)
Linux Linuxe87e08c94c9541b4e18c4c13f2f605935f512605Vendor (CNA)
debian:linux6.1.133-1 · Debian:12Package registry (OSV)
debian:linux-6.16.1.137-1~deb11u1 · Debian:11Package registry (OSV)
red hat:bpftool0:4.18.0-477.64.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:bpftool-debuginfo0:4.18.0-477.64.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel0:4.18.0-477.64.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel-abi-stablelists0:4.18.0-477.64.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel-core0:4.18.0-477.64.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel-debug0:4.18.0-477.64.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel-debug-core0:4.18.0-477.64.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel-debug-debuginfo0:4.18.0-477.64.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel-debug-devel0:4.18.0-477.64.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel-debug-modules0:4.18.0-477.64.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel-debug-modules-extra0:4.18.0-477.64.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel-debuginfo0:4.18.0-477.64.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage 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

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)

CWE-416 · Use After Free

CVSS vector

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

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

c
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&dev->lock);

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