CVSS: 5.5EPSS: 0%CPEs: 7EXPL: 0CVE-2024-43098 – i3c: Use i3cdev->desc->info instead of calling i3c_device_get_info() to avoid deadlock
https://notcve.org/view.php?id=CVE-2024-43098
11 Jan 2025 — In the Linux kernel, the following vulnerability has been resolved: i3c: Use i3cdev->desc->info instead of calling i3c_device_get_info() to avoid deadlock A deadlock may happen since the i3c_master_register() acquires &i3cbus->lock twice. See the log below. Use i3cdev->desc->info instead of calling i3c_device_info() to avoid acquiring the lock twice. v2: - Modified the title and commit message ============================================ WARNING: possible recursive locking detected 6.11.0-mainline ---------... • https://git.kernel.org/stable/c/3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 • CWE-667: Improper Locking •
CVSS: 7.1EPSS: 0%CPEs: 3EXPL: 0CVE-2024-41935 – f2fs: fix to shrink read extent node in batches
https://notcve.org/view.php?id=CVE-2024-41935
11 Jan 2025 — In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to shrink read extent node in batches We use rwlock to protect core structure data of extent tree during its shrink, however, if there is a huge number of extent nodes in extent tree, during shrink of extent tree, it may hold rwlock for a very long time, which may trigger kernel hang issue. This patch fixes to shrink read extent node in batches, so that, critical region of the rwlock can be shrunk to avoid its extreme long time ho... • https://git.kernel.org/stable/c/98e4da8ca301e062d79ae168c67e56f3c3de3ce4 •
CVSS: 4.7EPSS: 0%CPEs: 2EXPL: 0CVE-2024-41932 – sched: fix warning in sched_setaffinity
https://notcve.org/view.php?id=CVE-2024-41932
11 Jan 2025 — In the Linux kernel, the following vulnerability has been resolved: sched: fix warning in sched_setaffinity Commit 8f9ea86fdf99b added some logic to sched_setaffinity that included a WARN when a per-task affinity assignment races with a cpuset update. Specifically, we can have a race where a cpuset update results in the task affinity no longer being a subset of the cpuset. That's fine; we have a fallback to instead use the cpuset mask. However, we have a WARN set up that will trigger if the cpuset mask has ... • https://git.kernel.org/stable/c/8f9ea86fdf99b81458cc21fc1c591fcd4a0fa1f4 •
CVSS: 7.1EPSS: 0%CPEs: 5EXPL: 0CVE-2024-56787 – soc: imx8m: Probe the SoC driver as platform driver
https://notcve.org/view.php?id=CVE-2024-56787
08 Jan 2025 — In the Linux kernel, the following vulnerability has been resolved: soc: imx8m: Probe the SoC driver as platform driver With driver_async_probe=* on kernel command line, the following trace is produced because on i.MX8M Plus hardware because the soc-imx8m.c driver calls of_clk_get_by_name() which returns -EPROBE_DEFER because the clock driver is not yet probed. This was not detected during regular testing without driver_async_probe. Convert the SoC code to platform driver and instantiate a platform device i... • https://git.kernel.org/stable/c/a7e26f356ca12906a164d83c9e9f8527ee7da022 •
CVSS: 7.8EPSS: 0%CPEs: 6EXPL: 0CVE-2024-56785 – MIPS: Loongson64: DTS: Really fix PCIe port nodes for ls7a
https://notcve.org/view.php?id=CVE-2024-56785
08 Jan 2025 — In the Linux kernel, the following vulnerability has been resolved: MIPS: Loongson64: DTS: Really fix PCIe port nodes for ls7a Fix the dtc warnings: arch/mips/boot/dts/loongson/ls7a-pch.dtsi:68.16-416.5: Warning (interrupt_provider): /bus@10000000/pci@1a000000: '#interrupt-cells' found, but node is not an interrupt provider arch/mips/boot/dts/loongson/ls7a-pch.dtsi:68.16-416.5: Warning (interrupt_provider): /bus@10000000/pci@1a000000: '#interrupt-cells' found, but node is not an interrupt provider arch/mips... • https://git.kernel.org/stable/c/24af105962c8004edb9f5bf84bc587cbb30e52de •
CVSS: 5.5EPSS: 0%CPEs: 5EXPL: 0CVE-2024-56783 – netfilter: nft_socket: remove WARN_ON_ONCE on maximum cgroup level
https://notcve.org/view.php?id=CVE-2024-56783
08 Jan 2025 — In the Linux kernel, the following vulnerability has been resolved: netfilter: nft_socket: remove WARN_ON_ONCE on maximum cgroup level cgroup maximum depth is INT_MAX by default, there is a cgroup toggle to restrict this maximum depth to a more reasonable value not to harm performance. Remove unnecessary WARN_ON_ONCE which is reachable from userspace. In the Linux kernel, the following vulnerability has been resolved: netfilter: nft_socket: remove WARN_ON_ONCE on maximum cgroup level cgroup maximum depth is... • https://git.kernel.org/stable/c/ace0db36b4a1db07a48517c4f04488d1cd05e5f5 • CWE-617: Reachable Assertion •
CVSS: 5.5EPSS: 0%CPEs: 3EXPL: 0CVE-2024-56782 – ACPI: x86: Add adev NULL check to acpi_quirk_skip_serdev_enumeration()
https://notcve.org/view.php?id=CVE-2024-56782
08 Jan 2025 — In the Linux kernel, the following vulnerability has been resolved: ACPI: x86: Add adev NULL check to acpi_quirk_skip_serdev_enumeration() acpi_dev_hid_match() does not check for adev == NULL, dereferencing it unconditional. Add a check for adev being NULL before calling acpi_dev_hid_match(). At the moment acpi_quirk_skip_serdev_enumeration() is never called with a controller_parent without an ACPI companion, but better safe than sorry. In the Linux kernel, the following vulnerability has been resolved: ACP... • https://git.kernel.org/stable/c/99b572e6136eab69a8c91d72cf8595b256e304b5 • CWE-476: NULL Pointer Dereference •
CVSS: 5.5EPSS: 0%CPEs: 10EXPL: 0CVE-2024-56780 – quota: flush quota_release_work upon quota writeback
https://notcve.org/view.php?id=CVE-2024-56780
08 Jan 2025 — In the Linux kernel, the following vulnerability has been resolved: quota: flush quota_release_work upon quota writeback One of the paths quota writeback is called from is: freeze_super() sync_filesystem() ext4_sync_fs() dquot_writeback_dquots() Since we currently don't always flush the quota_release_work queue in this path, we can end up with the following race: 1. dquot are added to releasing_dquots list during regular operations. 2. FS Freeze starts, however, this does not flush the quota_release_work qu... • https://git.kernel.org/stable/c/d40c192e119892799dd4ddf94f5cea6fa93775ef •
CVSS: 6.3EPSS: 0%CPEs: 7EXPL: 0CVE-2024-56779 – nfsd: fix nfs4_openowner leak when concurrent nfsd4_open occur
https://notcve.org/view.php?id=CVE-2024-56779
08 Jan 2025 — In the Linux kernel, the following vulnerability has been resolved: nfsd: fix nfs4_openowner leak when concurrent nfsd4_open occur The action force umount(umount -f) will attempt to kill all rpc_task even umount operation may ultimately fail if some files remain open. Consequently, if an action attempts to open a file, it can potentially send two rpc_task to nfs server. NFS CLIENT thread1 thread2 open("file") ... nfs4_do_open _nfs4_do_open _nfs4_open_and_get_state _nfs4_proc_open nfs4_run_open_task /* rpc_t... • https://git.kernel.org/stable/c/3234975f477f746c22d076ea178a79ea104b2ca7 • CWE-401: Missing Release of Memory after Effective Lifetime •
CVSS: 5.5EPSS: 0%CPEs: 5EXPL: 0CVE-2024-56778 – drm/sti: avoid potential dereference of error pointers in sti_hqvdp_atomic_check
https://notcve.org/view.php?id=CVE-2024-56778
08 Jan 2025 — In the Linux kernel, the following vulnerability has been resolved: drm/sti: avoid potential dereference of error pointers in sti_hqvdp_atomic_check The return value of drm_atomic_get_crtc_state() needs to be checked. To avoid use of error pointer 'crtc_state' in case of the failure. In the Linux kernel, the following vulnerability has been resolved: drm/sti: avoid potential dereference of error pointers in sti_hqvdp_atomic_check The return value of drm_atomic_get_crtc_state() needs to be checked. To avoid ... • https://git.kernel.org/stable/c/dd86dc2f9ae1102f46115be1f1422265c15540f1 • CWE-754: Improper Check for Unusual or Exceptional Conditions •