CVSS: 9.8EPSS: 0%CPEs: 5EXPL: 0CVE-2024-58085 – tomoyo: don't emit warning in tomoyo_write_control()
https://notcve.org/view.php?id=CVE-2024-58085
06 Mar 2025 — In the Linux kernel, the following vulnerability has been resolved: tomoyo: don't emit warning in tomoyo_write_control() syzbot is reporting too large allocation warning at tomoyo_write_control(), for one can write a very very long line without new line character. To fix this warning, I use __GFP_NOWARN rather than checking for KMALLOC_MAX_SIZE, for practically a valid line should be always shorter than 32KB where the "too small to fail" memory-allocation rule applies. One might try to write a valid line th... • https://git.kernel.org/stable/c/a01c200fa7eb59da4d2dbbb48b61f4a0d196c09f •
CVSS: 7.1EPSS: 0%CPEs: 4EXPL: 0CVE-2024-58084 – firmware: qcom: scm: Fix missing read barrier in qcom_scm_get_tzmem_pool()
https://notcve.org/view.php?id=CVE-2024-58084
06 Mar 2025 — In the Linux kernel, the following vulnerability has been resolved: firmware: qcom: scm: Fix missing read barrier in qcom_scm_get_tzmem_pool() Commit 2e4955167ec5 ("firmware: qcom: scm: Fix __scm and waitq completion variable initialization") introduced a write barrier in probe function to store global '__scm' variable. We all known barriers are paired (see memory-barriers.txt: "Note that write barriers should normally be paired with read or address-dependency barriers"), therefore accessing it from concurr... • https://git.kernel.org/stable/c/449d0d84bcd8246b508d07995326d13c54488b8c •
CVSS: 7.1EPSS: 0%CPEs: 8EXPL: 0CVE-2024-58083 – KVM: Explicitly verify target vCPU is online in kvm_get_vcpu()
https://notcve.org/view.php?id=CVE-2024-58083
06 Mar 2025 — In the Linux kernel, the following vulnerability has been resolved: KVM: Explicitly verify target vCPU is online in kvm_get_vcpu() Explicitly verify the target vCPU is fully online _prior_ to clamping the index in kvm_get_vcpu(). If the index is "bad", the nospec clamping will generate '0', i.e. KVM will return vCPU0 instead of NULL. In practice, the bug is unlikely to cause problems, as it will only come into play if userspace or the guest is buggy or misbehaving, e.g. KVM may send interrupts to vCPU0 inst... • https://git.kernel.org/stable/c/1d487e9bf8ba66a7174c56a0029c54b1eca8f99c •
CVSS: 9.8EPSS: 0%CPEs: 3EXPL: 0CVE-2024-58082 – media: nuvoton: Fix an error check in npcm_video_ece_init()
https://notcve.org/view.php?id=CVE-2024-58082
06 Mar 2025 — In the Linux kernel, the following vulnerability has been resolved: media: nuvoton: Fix an error check in npcm_video_ece_init() When function of_find_device_by_node() fails, it returns NULL instead of an error code. So the corresponding error check logic should be modified to check whether the return value is NULL and set the error code to be returned as -ENODEV. In the Linux kernel, the following vulnerability has been resolved: media: nuvoton: Fix an error check in npcm_video_ece_init() When function of_f... • https://git.kernel.org/stable/c/46c15a4ff1f4fe078c5b250fb2570020211eab38 •
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 •