CVSS: 5.5EPSS: 0%CPEs: 2EXPL: 0CVE-2021-47420 – drm/amdkfd: fix a potential ttm->sg memory leak
https://notcve.org/view.php?id=CVE-2021-47420
21 May 2024 — In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: fix a potential ttm->sg memory leak Memory is allocated for ttm->sg by kmalloc in kfd_mem_dmamap_userptr, but isn't freed by kfree in kfd_mem_dmaunmap_userptr. Free it! En el kernel de Linux, se resolvió la siguiente vulnerabilidad: drm/amdkfd: soluciona una posible pérdida de memoria de ttm->sg. La memoria se asigna para ttm->sg mediante kmalloc en kfd_mem_dmamap_userptr, pero kfree no la libera en kfd_mem_dmaunmap_userpt... • https://git.kernel.org/stable/c/264fb4d332f5e76743818480e482464437837c52 •
CVSS: 5.5EPSS: 0%CPEs: 4EXPL: 0CVE-2021-47419 – net/sched: sch_taprio: properly cancel timer from taprio_destroy()
https://notcve.org/view.php?id=CVE-2021-47419
21 May 2024 — In the Linux kernel, the following vulnerability has been resolved: net/sched: sch_taprio: properly cancel timer from taprio_destroy() There is a comment in qdisc_create() about us not calling ops->reset() in some cases. err_out4: /* * Any broken qdiscs that would require a ops->reset() here? * The qdisc was never in action so it shouldn't be necessary. */ As taprio sets a timer before actually receiving a packet, we need to cancel it from ops->destroy, just in case ops->reset has not been called. syzbot re... • https://git.kernel.org/stable/c/c71c512f4a65267e6a18163f4df729c489a51035 •
CVSS: 4.4EPSS: 0%CPEs: 8EXPL: 0CVE-2021-47418 – net_sched: fix NULL deref in fifo_set_limit()
https://notcve.org/view.php?id=CVE-2021-47418
21 May 2024 — In the Linux kernel, the following vulnerability has been resolved: net_sched: fix NULL deref in fifo_set_limit() syzbot reported another NULL deref in fifo_set_limit() [1] I could repro the issue with : unshare -n tc qd add dev lo root handle 1:0 tbf limit 200000 burst 70000 rate 100Mbit tc qd replace dev lo parent 1:0 pfifo_fast tc qd change dev lo root handle 1:0 tbf limit 300000 burst 70000 rate 100Mbit pfifo_fast does not have a change() operation. Make fifo_set_limit() more robust about this. [1] BUG:... • https://git.kernel.org/stable/c/fb0305ce1b03f6ff17f84f2c63daccecb45f2805 •
CVSS: 5.5EPSS: 0%CPEs: 2EXPL: 0CVE-2021-47417 – libbpf: Fix memory leak in strset
https://notcve.org/view.php?id=CVE-2021-47417
21 May 2024 — In the Linux kernel, the following vulnerability has been resolved: libbpf: Fix memory leak in strset Free struct strset itself, not just its internal parts. En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: libbpf: repara la pérdida de memoria en strset Libera la estructura strset en sí, no solo sus partes internas. • https://git.kernel.org/stable/c/90d76d3ececc74bf43b2a97f178dadfa1e52be54 •
CVSS: 3.3EPSS: 0%CPEs: 8EXPL: 0CVE-2021-47416 – phy: mdio: fix memory leak
https://notcve.org/view.php?id=CVE-2021-47416
21 May 2024 — In the Linux kernel, the following vulnerability has been resolved: phy: mdio: fix memory leak Syzbot reported memory leak in MDIO bus interface, the problem was in wrong state logic. MDIOBUS_ALLOCATED indicates 2 states: 1. Bus is only allocated 2. Bus allocated and __mdiobus_register() fails, but device_register() was called In case of device_register() has been called we should call put_device() to correctly free the memory allocated for this device, but mdiobus_free() calls just kfree(dev) in case of MD... • https://git.kernel.org/stable/c/46abc02175b3c246dd5141d878f565a8725060c9 •
CVSS: 5.5EPSS: 0%CPEs: 2EXPL: 0CVE-2021-47415 – iwlwifi: mvm: Fix possible NULL dereference
https://notcve.org/view.php?id=CVE-2021-47415
21 May 2024 — In the Linux kernel, the following vulnerability has been resolved: iwlwifi: mvm: Fix possible NULL dereference In __iwl_mvm_remove_time_event() check that 'te_data->vif' is NULL before dereferencing it. En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: iwlwifi: mvm: Corrige posible desreferencia NULL En __iwl_mvm_remove_time_event() comprueba que 'te_data->vif' sea NULL antes de desreferenciarlo. In the Linux kernel, the following vulnerability has been resolved: iwlwifi: mvm: Fix possi... • https://git.kernel.org/stable/c/7b3954a1d69a992a781e71036950f9254f8147f6 •
CVSS: 4.7EPSS: 0%CPEs: 3EXPL: 0CVE-2021-47414 – riscv: Flush current cpu icache before other cpus
https://notcve.org/view.php?id=CVE-2021-47414
21 May 2024 — In the Linux kernel, the following vulnerability has been resolved: riscv: Flush current cpu icache before other cpus On SiFive Unmatched, I recently fell onto the following BUG when booting: [ 0.000000] ftrace: allocating 36610 entries in 144 pages [ 0.000000] Oops - illegal instruction [#1] [ 0.000000] Modules linked in: [ 0.000000] CPU: 0 PID: 0 Comm: swapper Not tainted 5.13.1+ #5 [ 0.000000] Hardware name: SiFive HiFive Unmatched A00 (DT) [ 0.000000] epc : riscv_cpuid_to_hartid_mask+0x6/0xae [ 0.000000... • https://git.kernel.org/stable/c/fab957c11efe2f405e08b9f0d080524bc2631428 •
CVSS: 5.5EPSS: 0%CPEs: 3EXPL: 0CVE-2021-47413 – usb: chipidea: ci_hdrc_imx: Also search for 'phys' phandle
https://notcve.org/view.php?id=CVE-2021-47413
21 May 2024 — In the Linux kernel, the following vulnerability has been resolved: usb: chipidea: ci_hdrc_imx: Also search for 'phys' phandle When passing 'phys' in the devicetree to describe the USB PHY phandle (which is the recommended way according to Documentation/devicetree/bindings/usb/ci-hdrc-usb2.txt) the following NULL pointer dereference is observed on i.MX7 and i.MX8MM: [ 1.489344] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000098 [ 1.498170] Mem abort info: [ 1.500966] ESR = ... • https://git.kernel.org/stable/c/746f316b753a83e366bfc5f936cbf0d72d1c2d1d •
CVSS: 4.7EPSS: 0%CPEs: 2EXPL: 0CVE-2021-47412 – block: don't call rq_qos_ops->done_bio if the bio isn't tracked
https://notcve.org/view.php?id=CVE-2021-47412
21 May 2024 — In the Linux kernel, the following vulnerability has been resolved: block: don't call rq_qos_ops->done_bio if the bio isn't tracked rq_qos framework is only applied on request based driver, so: 1) rq_qos_done_bio() needn't to be called for bio based driver 2) rq_qos_done_bio() needn't to be called for bio which isn't tracked, such as bios ended from error handling code. Especially in bio_endio(): 1) request queue is referred via bio->bi_bdev->bd_disk->queue, which may be gone since request queue refcount ma... • https://git.kernel.org/stable/c/004b8f8a691205a93d9e80d98b786b2b97424d6e • CWE-388: 7PK - Errors •
CVSS: 5.5EPSS: 0%CPEs: 2EXPL: 0CVE-2021-47410 – drm/amdkfd: fix svm_migrate_fini warning
https://notcve.org/view.php?id=CVE-2021-47410
21 May 2024 — In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: fix svm_migrate_fini warning Device manager releases device-specific resources when a driver disconnects from a device, devm_memunmap_pages and devm_release_mem_region calls in svm_migrate_fini are redundant. It causes below warning trace after patch "drm/amdgpu: Split amdgpu_device_fini into early and late", so remove function svm_migrate_fini. BUG: https://gitlab.freedesktop.org/drm/amd/-/issues/1718 WARNING: CPU: 1 PID: 3646 ... • https://git.kernel.org/stable/c/ac7d732b24f4061f8a732ada49b054ab38c63e15 •