CVSS: 5.5EPSS: 0%CPEs: 5EXPL: 0CVE-2024-58072 – wifi: rtlwifi: remove unused check_buddy_priv
https://notcve.org/view.php?id=CVE-2024-58072
06 Mar 2025 — In the Linux kernel, the following vulnerability has been resolved: wifi: rtlwifi: remove unused check_buddy_priv Commit 2461c7d60f9f ("rtlwifi: Update header file") introduced a global list of private data structures. Later on, commit 26634c4b1868 ("rtlwifi Modify existing bits to match vendor version 2013.02.07") started adding the private data to that list at probe time and added a hook, check_buddy_priv to find the private data from a similar device. However, that function was never used. Besides, thoug... • https://git.kernel.org/stable/c/26634c4b1868323f49f8cd24c3493b57819867fd •
CVSS: 4.9EPSS: 0%CPEs: 5EXPL: 0CVE-2024-58071 – team: prevent adding a device which is already a team device lower
https://notcve.org/view.php?id=CVE-2024-58071
06 Mar 2025 — In the Linux kernel, the following vulnerability has been resolved: team: prevent adding a device which is already a team device lower Prevent adding a device which is already a team device lower, e.g. adding veth0 if vlan1 was already added and veth0 is a lower of vlan1. This is not useful in practice and can lead to recursive locking: $ ip link add veth0 type veth peer name veth1 $ ip link set veth0 up $ ip link set veth1 up $ ip link add link veth0 name veth0.1 type vlan protocol 802.1Q id 1 $ ip link ad... • https://git.kernel.org/stable/c/3d249d4ca7d0ed6629a135ea1ea21c72286c0d80 •
CVSS: 9.8EPSS: 0%CPEs: 4EXPL: 0CVE-2024-58070 – bpf: bpf_local_storage: Always use bpf_mem_alloc in PREEMPT_RT
https://notcve.org/view.php?id=CVE-2024-58070
06 Mar 2025 — In the Linux kernel, the following vulnerability has been resolved: bpf: bpf_local_storage: Always use bpf_mem_alloc in PREEMPT_RT In PREEMPT_RT, kmalloc(GFP_ATOMIC) is still not safe in non preemptible context. bpf_mem_alloc must be used in PREEMPT_RT. This patch is to enforce bpf_mem_alloc in the bpf_local_storage when CONFIG_PREEMPT_RT is enabled. [ 35.118559] BUG: sleeping function called from invalid context at kernel/locking/spinlock_rt.c:48 [ 35.118566] in_atomic(): 1, irqs_disabled(): 0, non_block: ... • https://git.kernel.org/stable/c/08a7ce384e33e53e0732c500a8af67a73f8fceca •
CVSS: 9.8EPSS: 0%CPEs: 5EXPL: 0CVE-2024-58069 – rtc: pcf85063: fix potential OOB write in PCF85063 NVMEM read
https://notcve.org/view.php?id=CVE-2024-58069
06 Mar 2025 — In the Linux kernel, the following vulnerability has been resolved: rtc: pcf85063: fix potential OOB write in PCF85063 NVMEM read The nvmem interface supports variable buffer sizes, while the regmap interface operates with fixed-size storage. If an nvmem client uses a buffer size less than 4 bytes, regmap_read will write out of bounds as it expects the buffer to point at an unsigned int. Fix this by using an intermediary unsigned int to hold the value. In the Linux kernel, the following vulnerability has be... • https://git.kernel.org/stable/c/fadfd092ee9138825d8c2a4f95719d2e2e3202b9 •
CVSS: 5.5EPSS: 0%CPEs: 5EXPL: 0CVE-2024-58068 – OPP: fix dev_pm_opp_find_bw_*() when bandwidth table not initialized
https://notcve.org/view.php?id=CVE-2024-58068
06 Mar 2025 — In the Linux kernel, the following vulnerability has been resolved: OPP: fix dev_pm_opp_find_bw_*() when bandwidth table not initialized If a driver calls dev_pm_opp_find_bw_ceil/floor() the retrieve bandwidth from the OPP table but the bandwidth table was not created because the interconnect properties were missing in the OPP consumer node, the kernel will crash with: Unable to handle kernel NULL pointer dereference at virtual address 0000000000000004 ... pc : _read_bw+0x8/0x10 lr : _opp_table_find_key+0x9... • https://git.kernel.org/stable/c/add1dc094a7456d3c56782b7478940b6a550c7ed •
CVSS: 5.5EPSS: 0%CPEs: 5EXPL: 0CVE-2024-58063 – wifi: rtlwifi: fix memory leaks and invalid access at probe error path
https://notcve.org/view.php?id=CVE-2024-58063
06 Mar 2025 — In the Linux kernel, the following vulnerability has been resolved: wifi: rtlwifi: fix memory leaks and invalid access at probe error path Deinitialize at reverse order when probe fails. When init_sw_vars fails, rtl_deinit_core should not be called, specially now that it destroys the rtl_wq workqueue. And call rtl_pci_deinit and deinit_sw_vars, otherwise, memory will be leaked. Remove pci_set_drvdata call as it will already be cleaned up by the core driver code and could lead to memory leaks too. cf. commit... • https://git.kernel.org/stable/c/0c8173385e549f95cd80c3fff5aab87b4f881d8d •
CVSS: 9.8EPSS: 0%CPEs: 5EXPL: 0CVE-2024-58061 – wifi: mac80211: prohibit deactivating all links
https://notcve.org/view.php?id=CVE-2024-58061
06 Mar 2025 — In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: prohibit deactivating all links In the internal API this calls this is a WARN_ON, but that should remain since internally we want to know about bugs that may cause this. Prevent deactivating all links in the debugfs write directly. In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: prohibit deactivating all links In the internal API this calls this is a WARN_ON, but that should remain since i... • https://git.kernel.org/stable/c/3d901102922723eedce6ef10ebd03315a7abb8a5 •
CVSS: 5.5EPSS: 0%CPEs: 5EXPL: 0CVE-2024-58058 – ubifs: skip dumping tnc tree when zroot is null
https://notcve.org/view.php?id=CVE-2024-58058
06 Mar 2025 — In the Linux kernel, the following vulnerability has been resolved: ubifs: skip dumping tnc tree when zroot is null Clearing slab cache will free all znode in memory and make c->zroot.znode = NULL, then dumping tnc tree will access c->zroot.znode which cause null pointer dereference. In the Linux kernel, the following vulnerability has been resolved: ubifs: skip dumping tnc tree when zroot is null Clearing slab cache will free all znode in memory and make c->zroot.znode = NULL, then dumping tnc tree will ac... • https://git.kernel.org/stable/c/1e51764a3c2ac05a23a22b2a95ddee4d9bffb16d •
CVSS: 7.1EPSS: 0%CPEs: 5EXPL: 0CVE-2024-58056 – remoteproc: core: Fix ida_free call while not allocated
https://notcve.org/view.php?id=CVE-2024-58056
06 Mar 2025 — In the Linux kernel, the following vulnerability has been resolved: remoteproc: core: Fix ida_free call while not allocated In the rproc_alloc() function, on error, put_device(&rproc->dev) is called, leading to the call of the rproc_type_release() function. An error can occurs before ida_alloc is called. In such case in rproc_type_release(), the condition (rproc->index >= 0) is true as rproc->index has been initialized to 0. ida_free() is called reporting a warning: [ 4.181906] WARNING: CPU: 1 PID: 24 at li... • https://git.kernel.org/stable/c/08333b911f01862e71e51b7065fb4baca3cd2e67 •
CVSS: 9.8EPSS: 0%CPEs: 5EXPL: 0CVE-2024-58055 – usb: gadget: f_tcm: Don't free command immediately
https://notcve.org/view.php?id=CVE-2024-58055
06 Mar 2025 — In the Linux kernel, the following vulnerability has been resolved: usb: gadget: f_tcm: Don't free command immediately Don't prematurely free the command. Wait for the status completion of the sense status. It can be freed then. Otherwise we will double-free the command. In the Linux kernel, the following vulnerability has been resolved: usb: gadget: f_tcm: Don't free command immediately Don't prematurely free the command. • https://git.kernel.org/stable/c/cff834c16d23d614388aab1b86d19eb67b3f80c4 •