Use After Free Affecting kernel-bootwrapper package, versions *
Threat Intelligence
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk ID SNYK-RHEL7-KERNELBOOTWRAPPER-6604692
- published 12 Apr 2024
- disclosed 10 Apr 2024
Introduced: 10 Apr 2024
CVE-2021-47195 Open this link in a new tabHow to fix?
There is no fixed version for RHEL:7
kernel-bootwrapper
.
NVD Description
Note: Versions mentioned in the description apply only to the upstream kernel-bootwrapper
package and not the kernel-bootwrapper
package as distributed by RHEL
.
See How to fix?
for RHEL:7
relevant fixed versions and status.
In the Linux kernel, the following vulnerability has been resolved:
spi: fix use-after-free of the add_lock mutex
Commit 6098475d4cb4 ("spi: Fix deadlock when adding SPI controllers on SPI buses") introduced a per-controller mutex. But mutex_unlock() of said lock is called after the controller is already freed:
spi_unregister_controller(ctlr) -> put_device(&ctlr->dev) -> spi_controller_release(dev) -> mutex_unlock(&ctrl->add_lock)
Move the put_device() after the mutex_unlock().
References
- https://access.redhat.com/security/cve/CVE-2021-47195
- https://git.kernel.org/stable/c/11eab327a2a8bd36c38afbff920ae1bd45588dd4
- https://git.kernel.org/stable/c/54c2c96eafcfd242e52e932ab54ace4784efe1dd
- https://git.kernel.org/stable/c/37330f37f6666c7739a44b2b6b95b047ccdbed2d
- https://git.kernel.org/stable/c/6c53b45c71b4920b5e62f0ea8079a1da382b9434