crypto: hisilicon/qm - set NULL to qm->debug.qm_diff_regs
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
e0a2d2df9ba7bd6bd7e0a9b6a5e3894f7e8445b3| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
crypto: hisilicon/qm - set NULL to qm->debug.qm_diff_regs
When the initialization of qm->debug.acc_diff_reg fails, the probe process does not exit. However, after qm->debug.qm_diff_regs is freed, it is not set to NULL. This can lead to a double free when the remove process attempts to free it again. Therefore, qm->debug.qm_diff_regs should be set to NULL after it is freed.
From the CVE record · Linux
In the Linux kernel's hisilicon/qm crypto driver, a failed debug-register initialization can leave a pointer to freed memory. A subsequent device removal can free it again; the input does not specify an attacker path or required access.
Engineers running Linux kernels with the hisilicon/qm crypto driver should check whether their kernel is affected; no affected versions are specified.