LiveActive security incident?Get immediate response
CVE Record

CVE-2024-36951: drm/amdkfd: range check cp bad op exception interrupts

In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: range check cp bad op exception interrupts Due to a CP interrupt bug, bad packet garbage exception codes are raised. Do a range check so that the debugger and runtime do not receive garbage codes. Update the user api to guard exception code type checking as well.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue affects AMD GPU compute handling. A bad CP interrupt can produce invalid exception codes that may reach debugger or runtime components. The public data does not describe remote attack paths, active exploitation, CVSS, or business impact severity.

Executive priority

Track this as a kernel maintenance item unless AMD GPU compute hosts support sensitive or multi-tenant workloads. With no CVSS or exploitation evidence, urgency depends on local AMD GPU exposure and normal patch cadence.

Technical view

CVE-2024-36951 is in Linux drm/amdkfd. The fix range-checks CP bad-op exception interrupt codes and updates user API exception code type checking so invalid garbage codes are not passed onward. Public metadata lists affected Linux kernel versions but no CVSS, CWE, or exploit details.

Likely exposure

Exposure is most likely on Linux systems using AMD KFD/AMDGPU compute functionality with affected kernel builds. The bundle does not establish exposure for non-AMD GPU systems or systems where this kernel driver path is unused.

Exploitation context

The source bundle shows KEV is false and provides no evidence of active exploitation, public exploit code, or remote exploitation. Treat exploitation context as unproven until vendor advisories or threat intelligence say otherwise.

Researcher notes

Evidence is limited to Linux CNA text and upstream stable commit references. The issue appears to sanitize invalid exception codes rather than document a clear confidentiality, integrity, or availability impact. Avoid overstating risk without vendor impact analysis.

Mitigation direction

  • Update affected Linux kernels through your distribution or kernel vendor.
  • Confirm updates include the referenced upstream stable commits.
  • Prioritize systems running AMD GPU compute workloads or untrusted local workloads.
  • Check vendor guidance for fixed package versions and backports.
  • Monitor kernel and GPU runtime logs for abnormal exception handling symptoms.

Validation and detection

  • Inventory Linux hosts with AMDGPU/AMDKFD enabled.
  • Map installed kernel versions against vendor fixed-version advisories.
  • Verify patched kernels include the referenced stable commit lineage.
  • Confirm GPU compute workloads still run after kernel update.
  • Record systems where vendor fixed-version guidance is unavailable.
Prepared
Confidence
medium
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-36951 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
2ADP providers
4Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux4a488a7ad71401169cecee75dc94bcce642e2c53, 4a488a7ad71401169cecee75dc94bcce642e2c53, 4a488a7ad71401169cecee75dc94bcce642e2c53unaffected
LinuxLinux3.19, 0, 6.6.31, 6.8.10, 6.9affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.