habanalabs/gaudi: Fix a potential use after free in gaudi_memset_device_memory
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
habanalabs/gaudi: Fix a potential use after free in gaudi_memset_device_memory
Our code analyzer reported a uaf.
In gaudi_memset_device_memory, cb is get via hl_cb_kernel_create() with 2 refcount. If hl_cs_allocate_job() failed, the execution runs into release_cb branch. One ref of cb is dropped by hl_cb_put(cb) and could be freed if other thread also drops one ref. Then cb is used by cb->id later, which is a potential uaf.
My patch add a variable 'id' to accept the value of cb->id before the hl_cb_put(cb) is called, to avoid the potential uaf.
From the CVE record · Linux
The Linux kernel’s habanalabs Gaudi driver has a potential use-after-free in gaudi_memset_device_memory. If job allocation fails and another thread drops a reference to the same object, the code may access it after it is freed. The input does not specify whether exploitation requires local access, authentication, or user interaction.
Engineers running Linux kernels with the habanalabs Gaudi driver should check their kernel versions; affected versions are not specified.