crypto: hisilicon/qm - inject error before stopping queue
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 6c6dd5802c2d6769fa589c0e8de54299def199a7 · < c5f5b813e546f7fe133539c3d7a5086cc8dd2aa1| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
crypto: hisilicon/qm - inject error before stopping queue
The master ooo cannot be completely closed when the accelerator core reports memory error. Therefore, the driver needs to inject the qm error to close the master ooo. Currently, the qm error is injected after stopping queue, memory may be released immediately after stopping queue, causing the device to access the released memory. Therefore, error is injected to close master ooo before stopping queue to ensure that the device does not access the released memory.
From the CVE record · Linux
The Linux kernel’s hisilicon/qm driver can stop a queue before injecting an error when the accelerator core reports a memory error. This can let the device access memory after it has been released. The input does not specify an attacker path, authentication requirements, or user interaction.
Engineers running Linux kernels with the hisilicon/qm driver should check their exposure; affected versions are not specified.