CVE-2024-36022 (GCVE-0-2024-36022)
Vulnerability from cvelistv5 – Published: 2024-05-30 15:03 – Updated: 2025-06-19 13:03
VLAI
EPSS
VEX
This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
Show details on NVD website{
"containers": {
"cna": {
"providerMetadata": {
"dateUpdated": "2025-06-19T13:03:48.081Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"rejectedReasons": [
{
"lang": "en",
"value": "This CVE ID has been rejected or withdrawn by its CVE Numbering Authority."
}
]
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2024-36022",
"datePublished": "2024-05-30T15:03:59.678Z",
"dateRejected": "2025-06-19T13:03:48.081Z",
"dateReserved": "2024-05-17T13:50:33.157Z",
"dateUpdated": "2025-06-19T13:03:48.081Z",
"state": "REJECTED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.1",
"vulnerability-lookup:meta": {
"fkie_nvd": {
"descriptions": "[{\"lang\": \"en\", \"value\": \"In the Linux kernel, the following vulnerability has been resolved:\\n\\ndrm/amdgpu: Init zone device and drm client after mode-1 reset on reload\\n\\nIn passthrough environment, when amdgpu is reloaded after unload, mode-1\\nis triggered after initializing the necessary IPs, That init does not\\ninclude KFD, and KFD init waits until the reset is completed. KFD init\\nis called in the reset handler, but in this case, the zone device and\\ndrm client is not initialized, causing app to create kernel panic.\\n\\nv2: Removing the init KFD condition from amdgpu_amdkfd_drm_client_create.\\nAs the previous version has the potential of creating DRM client twice.\\n\\nv3: v2 patch results in SDMA engine hung as DRM open causes VM clear to SDMA\\nbefore SDMA init. Adding the condition to in drm client creation, on top of v1,\\nto guard against drm client creation call multiple times.\"}, {\"lang\": \"es\", \"value\": \"En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: drm/amdgpu: dispositivo de zona de inicio y cliente drm despu\\u00e9s del restablecimiento del modo 1 al recargar. En el entorno de paso a trav\\u00e9s, cuando amdgpu se recarga despu\\u00e9s de la descarga, el modo 1 se activa despu\\u00e9s de inicializar las IP necesarias. Ese inicio no incluye KFD, y el inicio de KFD espera hasta que se complete el reinicio. Se llama a KFD init en el controlador de reinicio, pero en este caso, el dispositivo de zona y el cliente drm no se inicializan, lo que hace que la aplicaci\\u00f3n genere p\\u00e1nico en el kernel. v2: Eliminaci\\u00f3n de la condici\\u00f3n KFD inicial de amdgpu_amdkfd_drm_client_create. Como la versi\\u00f3n anterior tiene el potencial de crear un cliente DRM dos veces. v3: el parche v2 hace que el motor SDMA se bloquee porque la apertura de DRM hace que la VM se borre a SDMA antes de que se inicie SDMA. Agregar la condici\\u00f3n a la creaci\\u00f3n del cliente DRM, adem\\u00e1s de la versi\\u00f3n 1, para protegerse contra llamadas de creaci\\u00f3n del cliente DRM varias veces.\"}]",
"id": "CVE-2024-36022",
"lastModified": "2024-11-21T09:21:27.403",
"published": "2024-05-30T15:15:49.263",
"references": "[{\"url\": \"https://git.kernel.org/stable/c/4f8154f775197d0021b690c2945d6a4d8094c8f6\", \"source\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}, {\"url\": \"https://git.kernel.org/stable/c/f679fd6057fbf5ab34aaee28d58b7f81af0cbf48\", \"source\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}, {\"url\": \"https://git.kernel.org/stable/c/4f8154f775197d0021b690c2945d6a4d8094c8f6\", \"source\": \"af854a3a-2127-422b-91ae-364da2661108\"}, {\"url\": \"https://git.kernel.org/stable/c/f679fd6057fbf5ab34aaee28d58b7f81af0cbf48\", \"source\": \"af854a3a-2127-422b-91ae-364da2661108\"}]",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Awaiting Analysis"
},
"nvd": "{\"cve\":{\"id\":\"CVE-2024-36022\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2024-05-30T15:15:49.263\",\"lastModified\":\"2025-06-19T14:15:45.160\",\"vulnStatus\":\"Rejected\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.\"}],\"metrics\":{},\"references\":[]}}",
"redhat_vex": {
"aggregate_severity": "None",
"current_release_date": "2026-06-28T07:54:52+00:00",
"cve": "CVE-2024-36022",
"id": "CVE-2024-36022",
"initial_release_date": "2024-05-30T00:00:00+00:00",
"product_status:fixed": "280",
"product_status:known_affected": "98",
"product_status:known_not_affected": "22",
"source": "Red Hat CSAF VEX",
"status": "final",
"title": "kernel: drm/amdgpu: Init zone device and drm client after mode-1 reset on reload",
"url": "https://security.access.redhat.com/data/csaf/v2/vex/2024/cve-2024-36022.json",
"version": "3"
},
"suse_vex": {
"aggregate_severity": "moderate",
"current_release_date": "2026-09-03T16:41:52Z",
"cve": "CVE-2024-36022",
"id": "CVE-2024-36022",
"initial_release_date": "2024-06-01T02:24:09Z",
"product_status:known_not_affected": "385",
"product_status:recommended": "47",
"source": "SUSE CSAF VEX",
"status": "interim",
"title": "SUSE CVE CVE-2024-36022",
"url": "https://ftp.suse.com/pub/projects/security/csaf-vex/cve-2024-36022.json",
"version": "20"
},
"vulnrichment": {
"containers": "{\"cna\": {\"rejectedReasons\": [{\"lang\": \"en\", \"value\": \"This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.\"}], \"providerMetadata\": {\"orgId\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"shortName\": \"Linux\", \"dateUpdated\": \"2025-06-19T13:03:48.081Z\"}}}",
"cveMetadata": "{\"cveId\": \"CVE-2024-36022\", \"assignerOrgId\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"state\": \"REJECTED\", \"assignerShortName\": \"Linux\", \"dateReserved\": \"2024-05-17T13:50:33.157Z\", \"datePublished\": \"2024-05-30T15:03:59.678Z\", \"dateUpdated\": \"2025-06-19T13:03:48.081Z\", \"dateRejected\": \"2025-06-19T13:03:48.081Z\"}",
"dataType": "CVE_RECORD",
"dataVersion": "5.1"
}
}
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Loading…
Loading…