CVE-2024-39291

GPU initialization disruption via truncated firmware names

Published Jun 24, 2024 · Updated May 11, 2026

Buffer truncation in the AMDGPU gfx_v9_4_3 firmware loader in Linux 6.5 allows local users to disrupt GPU initialization. The gfx_v9_4_3_init_microcode path passes a chip-derived prefix of up to 29 bytes into 30-byte snprintf destinations that also need 16 bytes for firmware-name text, causing MEC or RLC names to be truncated. Reachability requires the affected AMDGPU initialization path on compatible hardware, and the bounded consequence is failure to load the intended GPU firmware.

CVSS severity7.8
High
EPSS probability0.24%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Buffer truncation in the AMDGPU gfx_v9_4_3 firmware loader in Linux 6.5 allows local users to disrupt GPU initialization. The gfx_v9_4_3_init_microcode path passes a chip-derived prefix of up to 29 bytes into 30-byte snprintf destinations that also need 16 bytes for firmware-name text, causing MEC or RLC names to be truncated. Reachability requires the affected AMDGPU initialization path on compatible hardware, and the bounded consequence is failure to load the intended GPU firmware.

The record

CVE
CVE-2024-39291
Published
Jun 24, 2024
Updated
May 11, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
CWE-120, T1499
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Jun 24, 2024CVE publishedPublication date reported by the CVE source.
  2. May 11, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=6.5
  2. Affected versionversion=86301129698be52f8398f92ea8564168f6bfcae1 <19bd9537b6bc1c882df25206c15917214d8e9460
  3. Affected versionversion=86301129698be52f8398f92ea8564168f6bfcae1 <acce6479e30f73ab0872e93a75aed1fb791d04ec
  4. Affected versionversion=86301129698be52f8398f92ea8564168f6bfcae1 <f1b6a016dfa45cedc080d36fa5d6f22237d80e8b

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

The Linux Kernel Organization · Linuxversion=6.5; version=86301129698be52f8398f92ea8564168f6bfcae1 <19bd9537b6bc1c882df25206c15917214d8e9460; version=86301129698be52f8398f92ea8564168f6bfcae1 <acce6479e30f73ab0872e93a75aed1fb791d04ec; version=86301129698be52f8398f92ea8564168f6bfcae1 <f1b6a016dfa45cedc080d36fa5d6f22237d80e8b

Published CVSS scores

7.8NIST NVDCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
7.8Canonical UbuntuCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-120Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')
T1499Endpoint Denial of Service

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo