CVSS: 5.5EPSS: 0%CPEs: 3EXPL: 0CVE-2021-47062 – KVM: SVM: Use online_vcpus, not created_vcpus, to iterate over vCPUs
https://notcve.org/view.php?id=CVE-2021-47062
29 Feb 2024 — In the Linux kernel, the following vulnerability has been resolved: KVM: SVM: Use online_vcpus, not created_vcpus, to iterate over vCPUs Use the kvm_for_each_vcpu() helper to iterate over vCPUs when encrypting VMSAs for SEV, which effectively switches to use online_vcpus instead of created_vcpus. This fixes a possible null-pointer dereference as created_vcpus does not guarantee a vCPU exists, since it is updated at the very beginning of KVM_CREATE_VCPU. created_vcpus exists to allow the bulk of vCPU creatio... • https://git.kernel.org/stable/c/ad73109ae7ec30d5bfb76be108e304f9f0af4829 •
CVSS: 7.8EPSS: 0%CPEs: 10EXPL: 0CVE-2021-47061 – KVM: Destroy I/O bus devices on unregister failure _after_ sync'ing SRCU
https://notcve.org/view.php?id=CVE-2021-47061
29 Feb 2024 — In the Linux kernel, the following vulnerability has been resolved: KVM: Destroy I/O bus devices on unregister failure _after_ sync'ing SRCU If allocating a new instance of an I/O bus fails when unregistering a device, wait to destroy the device until after all readers are guaranteed to see the new null bus. Destroying devices before the bus is nullified could lead to use-after-free since readers expect the devices on their reference of the bus to remain valid. En el kernel de Linux, se ha resuelto la sigui... • https://git.kernel.org/stable/c/f65886606c2d3b562716de030706dfe1bea4ed5e •
CVSS: 6.5EPSS: 0%CPEs: 10EXPL: 0CVE-2021-47060 – KVM: Stop looking for coalesced MMIO zones if the bus is destroyed
https://notcve.org/view.php?id=CVE-2021-47060
29 Feb 2024 — In the Linux kernel, the following vulnerability has been resolved: KVM: Stop looking for coalesced MMIO zones if the bus is destroyed Abort the walk of coalesced MMIO zones if kvm_io_bus_unregister_dev() fails to allocate memory for the new instance of the bus. If it can't instantiate a new bus, unregister_dev() destroys all devices _except_ the target device. But, it doesn't tell the caller that it obliterated the bus and invoked the destructor for all devices that were on the bus. In the coalesced MMIO c... • https://git.kernel.org/stable/c/41b2ea7a6a11e2b1a7f2c29e1675a709a6b2b98d •
CVSS: 5.5EPSS: 0%CPEs: 4EXPL: 0CVE-2021-47059 – crypto: sun8i-ss - fix result memory leak on error path
https://notcve.org/view.php?id=CVE-2021-47059
29 Feb 2024 — In the Linux kernel, the following vulnerability has been resolved: crypto: sun8i-ss - fix result memory leak on error path This patch fixes a memory leak on an error path. En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: crypto: sun8i-ss - resultado de corrección de pérdida de memoria en una ruta de error Este parche corrige una pérdida de memoria en una ruta de error. • https://git.kernel.org/stable/c/d9b45418a91773b7672e4c60037a28074b495c6d •
CVSS: 5.1EPSS: 0%CPEs: 6EXPL: 0CVE-2021-47058 – regmap: set debugfs_name to NULL after it is freed
https://notcve.org/view.php?id=CVE-2021-47058
29 Feb 2024 — In the Linux kernel, the following vulnerability has been resolved: regmap: set debugfs_name to NULL after it is freed There is a upstream commit cffa4b2122f5("regmap:debugfs: Fix a memory leak when calling regmap_attach_dev") that adds a if condition when create name for debugfs_name. With below function invoking logical, debugfs_name is freed in regmap_debugfs_exit(), but it is not created again because of the if condition introduced by above commit. regmap_reinit_cache() regmap_debugfs_exit() ... regmap_... • https://git.kernel.org/stable/c/5b654b03007917f3f1015b2a5c288c1ea6ae8f65 •
CVSS: 7.8EPSS: 0%CPEs: 4EXPL: 0CVE-2021-47057 – crypto: sun8i-ss - Fix memory leak of object d when dma_iv fails to map
https://notcve.org/view.php?id=CVE-2021-47057
29 Feb 2024 — In the Linux kernel, the following vulnerability has been resolved: crypto: sun8i-ss - Fix memory leak of object d when dma_iv fails to map In the case where the dma_iv mapping fails, the return error path leaks the memory allocated to object d. Fix this by adding a new error return label and jumping to this to ensure d is free'd before the return. Addresses-Coverity: ("Resource leak") En el kernel de Linux, se resolvió la siguiente vulnerabilidad: crypto: sun8i-ss: corrige la pérdida de memoria del objeto ... • https://git.kernel.org/stable/c/ac2614d721dea2ff273af19c6c5d508d58a2bb3e • CWE-770: Allocation of Resources Without Limits or Throttling •
CVSS: 5.5EPSS: 0%CPEs: 8EXPL: 0CVE-2021-47056 – crypto: qat - ADF_STATUS_PF_RUNNING should be set after adf_dev_init
https://notcve.org/view.php?id=CVE-2021-47056
29 Feb 2024 — In the Linux kernel, the following vulnerability has been resolved: crypto: qat - ADF_STATUS_PF_RUNNING should be set after adf_dev_init ADF_STATUS_PF_RUNNING is (only) used and checked by adf_vf2pf_shutdown() before calling adf_iov_putmsg()->mutex_lock(vf2pf_lock), however the vf2pf_lock is initialized in adf_dev_init(), which can fail and when it fail, the vf2pf_lock is either not initialized or destroyed, a subsequent use of vf2pf_lock will cause issue. To fix this issue, only set this flag if adf_dev_in... • https://git.kernel.org/stable/c/25c6ffb249f612c56a48ce48a3887adf57b8f4bd •
CVSS: 4.4EPSS: 0%CPEs: 11EXPL: 0CVE-2021-47055 – mtd: require write permissions for locking and badblock ioctls
https://notcve.org/view.php?id=CVE-2021-47055
29 Feb 2024 — In the Linux kernel, the following vulnerability has been resolved: mtd: require write permissions for locking and badblock ioctls MEMLOCK, MEMUNLOCK and OTPLOCK modify protection bits. Thus require write permission. Depending on the hardware MEMLOCK might even be write-once, e.g. for SPI-NOR flashes with their WP# tied to GND. OTPLOCK is always write-once. MEMSETBADBLOCK modifies the bad block table. • https://git.kernel.org/stable/c/1c9f9125892a43901438bf704ada6b7019e2a884 •
CVSS: 2.3EPSS: 0%CPEs: 8EXPL: 0CVE-2021-47054 – bus: qcom: Put child node before return
https://notcve.org/view.php?id=CVE-2021-47054
29 Feb 2024 — In the Linux kernel, the following vulnerability has been resolved: bus: qcom: Put child node before return Put child node before return to fix potential reference count leak. Generally, the reference count of child is incremented and decremented automatically in the macro for_each_available_child_of_node() and should be decremented manually if the loop is broken in loop body. En el kernel de Linux, se resolvió la siguiente vulnerabilidad: bus: qcom: Colocar el nodo secundario antes del retorno. Colocar el ... • https://git.kernel.org/stable/c/335a127548081322bd2b294d715418648912f20c •
CVSS: 5.5EPSS: 0%CPEs: 6EXPL: 0CVE-2021-47020 – soundwire: stream: fix memory leak in stream config error path
https://notcve.org/view.php?id=CVE-2021-47020
29 Feb 2024 — In the Linux kernel, the following vulnerability has been resolved: soundwire: stream: fix memory leak in stream config error path When stream config is failed, master runtime will release all slave runtime in the slave_rt_list, but slave runtime is not added to the list at this time. This patch frees slave runtime in the config error path to fix the memory leak. En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: soundwire: stream: corrige la pérdida de memoria en la ruta de error de configu... • https://git.kernel.org/stable/c/89e590535f32d4bc548bcf266f3b046e50942f6d •