crypto: hisilicon/qm - set NULL to qm->debug.qm_diff_regs
3Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackepss 0.2%
exploitation probability
0.2%top 91% of all CVEs
observed exploitation
nono source reports it
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.
Affected products
Linux · LinuxReferences
https://git.kernel.org/stable/c/1750f1ec143ebabdbdfa013668665c9d5042c430https://git.kernel.org/stable/c/7226a0650ad5705bd8d39a11be270fa21ed1e6a5https://git.kernel.org/stable/c/a7836260d5121949ba734e840d42a86ab4a32fcchttps://git.kernel.org/stable/c/a87a21a56244b8f4eb357f6bad879247005bbe38https://git.kernel.org/stable/c/f0cafb02de883b3b413d34eb079c9680782a9cc1