CVSS: 5.5EPSS: 0%CPEs: 4EXPL: 0CVE-2024-58081 – clk: mmp2: call pm_genpd_init() only after genpd.name is set
https://notcve.org/view.php?id=CVE-2024-58081
06 Mar 2025 — In the Linux kernel, the following vulnerability has been resolved: clk: mmp2: call pm_genpd_init() only after genpd.name is set Setting the genpd's struct device's name with dev_set_name() is happening within pm_genpd_init(). If it remains NULL, things can blow up later, such as when crafting the devfs hierarchy for the power domain: Unable to handle kernel NULL pointer dereference at virtual address 00000000 when read ... Call trace: strlen from start_creating+0x90/0x138 start_creating from debugfs_create... • https://git.kernel.org/stable/c/899f44531fe6cac4b024710fec647ecc127724b8 •
CVSS: 9.8EPSS: 0%CPEs: 5EXPL: 0CVE-2024-58080 – clk: qcom: dispcc-sm6350: Add missing parent_map for a clock
https://notcve.org/view.php?id=CVE-2024-58080
06 Mar 2025 — In the Linux kernel, the following vulnerability has been resolved: clk: qcom: dispcc-sm6350: Add missing parent_map for a clock If a clk_rcg2 has a parent, it should also have parent_map defined, otherwise we'll get a NULL pointer dereference when calling clk_set_rate like the following: [ 3.388105] Call trace: [ 3.390664] qcom_find_src_index+0x3c/0x70 (P) [ 3.395301] qcom_find_src_index+0x1c/0x70 (L) [ 3.399934] _freq_tbl_determine_rate+0x48/0x100 [ 3.404753] clk_rcg2_determine_rate+0x1c/0x28 [ 3.409387] ... • https://git.kernel.org/stable/c/837519775f1d3945e3d4019641f7120d58325059 •
CVSS: 5.5EPSS: 0%CPEs: 5EXPL: 0CVE-2024-58079 – media: uvcvideo: Fix crash during unbind if gpio unit is in use
https://notcve.org/view.php?id=CVE-2024-58079
06 Mar 2025 — In the Linux kernel, the following vulnerability has been resolved: media: uvcvideo: Fix crash during unbind if gpio unit is in use We used the wrong device for the device managed functions. We used the usb device, when we should be using the interface device. If we unbind the driver from the usb interface, the cleanup functions are never called. In our case, the IRQ is never disabled. If an IRQ is triggered, it will try to access memory sections that are already free, causing an OOPS. • https://git.kernel.org/stable/c/2886477ff98740cc3333cf785e4de0b1ff3d7a28 •
CVSS: 9.8EPSS: 0%CPEs: 4EXPL: 0CVE-2024-58078 – misc: misc_minor_alloc to use ida for all dynamic/misc dynamic minors
https://notcve.org/view.php?id=CVE-2024-58078
06 Mar 2025 — In the Linux kernel, the following vulnerability has been resolved: misc: misc_minor_alloc to use ida for all dynamic/misc dynamic minors misc_minor_alloc was allocating id using ida for minor only in case of MISC_DYNAMIC_MINOR but misc_minor_free was always freeing ids using ida_free causing a mismatch and following warn: > > WARNING: CPU: 0 PID: 159 at lib/idr.c:525 ida_free+0x3e0/0x41f > > ida_free called for id=127 which is not allocated. > > <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< ... > > [<60941eb4>] ... • https://git.kernel.org/stable/c/ab760791c0cfbb1d7a668f46a135264f56c8f018 •
CVSS: 9.8EPSS: 0%CPEs: 5EXPL: 0CVE-2024-58077 – ASoC: soc-pcm: don't use soc_pcm_ret() on .prepare callback
https://notcve.org/view.php?id=CVE-2024-58077
06 Mar 2025 — In the Linux kernel, the following vulnerability has been resolved: ASoC: soc-pcm: don't use soc_pcm_ret() on .prepare callback commit 1f5664351410 ("ASoC: lower "no backend DAIs enabled for ... Port" log severity") ignores -EINVAL error message on common soc_pcm_ret(). It is used from many functions, ignoring -EINVAL is over-kill. The reason why -EINVAL was ignored was it really should only be used upon invalid parameters coming from userspace and in that case we don't want to log an error since we do not ... • https://git.kernel.org/stable/c/b65ba768302adc7ddc70811116cef80ca089af59 •
CVSS: 9.8EPSS: 0%CPEs: 5EXPL: 0CVE-2024-58076 – clk: qcom: gcc-sm6350: Add missing parent_map for two clocks
https://notcve.org/view.php?id=CVE-2024-58076
06 Mar 2025 — In the Linux kernel, the following vulnerability has been resolved: clk: qcom: gcc-sm6350: Add missing parent_map for two clocks If a clk_rcg2 has a parent, it should also have parent_map defined, otherwise we'll get a NULL pointer dereference when calling clk_set_rate like the following: [ 3.388105] Call trace: [ 3.390664] qcom_find_src_index+0x3c/0x70 (P) [ 3.395301] qcom_find_src_index+0x1c/0x70 (L) [ 3.399934] _freq_tbl_determine_rate+0x48/0x100 [ 3.404753] clk_rcg2_determine_rate+0x1c/0x28 [ 3.409387] ... • https://git.kernel.org/stable/c/131abae905df99f63d825e47b4df100d34f518ce •
CVSS: 9.8EPSS: 0%CPEs: 5EXPL: 0CVE-2025-21830 – landlock: Handle weird files
https://notcve.org/view.php?id=CVE-2025-21830
06 Mar 2025 — In the Linux kernel, the following vulnerability has been resolved: landlock: Handle weird files A corrupted filesystem (e.g. bcachefs) might return weird files. Instead of throwing a warning and allowing access to such file, treat them as regular files. In the Linux kernel, the following vulnerability has been resolved: landlock: Handle weird files A corrupted filesystem (e.g. bcachefs) might return weird files. Instead of throwing a warning and allowing access to such file, treat them as regular files. • https://git.kernel.org/stable/c/cb2c7d1a1776057c9a1f48ed1250d85e94d4850d •
CVSS: 5.5EPSS: 0%CPEs: 5EXPL: 0CVE-2025-21829 – RDMA/rxe: Fix the warning "__rxe_cleanup+0x12c/0x170 [rdma_rxe]"
https://notcve.org/view.php?id=CVE-2025-21829
06 Mar 2025 — In the Linux kernel, the following vulnerability has been resolved: RDMA/rxe: Fix the warning "__rxe_cleanup+0x12c/0x170 [rdma_rxe]" The Call Trace is as below: " <TASK> ? show_regs.cold+0x1a/0x1f ? __rxe_cleanup+0x12c/0x170 [rdma_rxe] ? __warn+0x84/0xd0 ? __rxe_cleanup+0x12c/0x170 [rdma_rxe] ? • https://git.kernel.org/stable/c/215d0a755e1bcd92cbe6a71a21194ce7c82ec106 •
CVSS: 5.5EPSS: 0%CPEs: 4EXPL: 0CVE-2025-21828 – wifi: mac80211: don't flush non-uploaded STAs
https://notcve.org/view.php?id=CVE-2025-21828
06 Mar 2025 — In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: don't flush non-uploaded STAs If STA state is pre-moved to AUTHORIZED (such as in IBSS scenarios) and insertion fails, the station is freed. In this case, the driver never knew about the station, so trying to flush it is unexpected and may crash. Check if the sta was uploaded to the driver before and fix this. In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: don't flush non-uploaded STAs If... • https://git.kernel.org/stable/c/d00800a289c9349bb659a698cbd7bc04521dc927 •
CVSS: 5.5EPSS: 0%CPEs: 3EXPL: 0CVE-2025-21827 – Bluetooth: btusb: mediatek: Add locks for usb_driver_claim_interface()
https://notcve.org/view.php?id=CVE-2025-21827
06 Mar 2025 — In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btusb: mediatek: Add locks for usb_driver_claim_interface() The documentation for usb_driver_claim_interface() says that "the device lock" is needed when the function is called from places other than probe(). This appears to be the lock for the USB interface device. The Mediatek btusb code gets called via this path: Workqueue: hci0 hci_power_on [bluetooth] Call trace: usb_driver_claim_interface btusb_mtk_claim_iso_intf btusb_mtk_... • https://git.kernel.org/stable/c/ceac1cb0259de682d78f5c784ef8e0b13022e9d9 •