CVSS: -EPSS: %CPEs: 5EXPL: 0CVE-2024-56777 – drm/sti: avoid potential dereference of error pointers in sti_gdp_atomic_check
https://notcve.org/view.php?id=CVE-2024-56777
08 Jan 2025 — In the Linux kernel, the following vulnerability has been resolved: drm/sti: avoid potential dereference of error pointers in sti_gdp_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. • https://git.kernel.org/stable/c/dd86dc2f9ae1102f46115be1f1422265c15540f1 •
CVSS: -EPSS: %CPEs: 5EXPL: 0CVE-2024-56776 – drm/sti: avoid potential dereference of error pointers
https://notcve.org/view.php?id=CVE-2024-56776
08 Jan 2025 — In the Linux kernel, the following vulnerability has been resolved: drm/sti: avoid potential dereference of error pointers 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. • https://git.kernel.org/stable/c/dd86dc2f9ae1102f46115be1f1422265c15540f1 •
CVSS: -EPSS: %CPEs: 2EXPL: 0CVE-2024-56775 – drm/amd/display: Fix handling of plane refcount
https://notcve.org/view.php?id=CVE-2024-56775
08 Jan 2025 — In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Fix handling of plane refcount [Why] The mechanism to backup and restore plane states doesn't maintain refcount, which can cause issues if the refcount of the plane changes in between backup and restore operations, such as memory leaks if the refcount was supposed to go down, or double frees / invalid memory accesses if the refcount was supposed to go up. [How] Cache and re-apply current refcount when restoring plane states... • https://git.kernel.org/stable/c/8cb2f6793845f135b28361ba8e96901cae3e5790 •
CVSS: -EPSS: %CPEs: 5EXPL: 0CVE-2024-56774 – btrfs: add a sanity check for btrfs root in btrfs_search_slot()
https://notcve.org/view.php?id=CVE-2024-56774
08 Jan 2025 — In the Linux kernel, the following vulnerability has been resolved: btrfs: add a sanity check for btrfs root in btrfs_search_slot() Syzbot reports a null-ptr-deref in btrfs_search_slot(). The reproducer is using rescue=ibadroots, and the extent tree root is corrupted thus the extent tree is NULL. When scrub tries to search the extent tree to gather the needed extent info, btrfs_search_slot() doesn't check if the target root is NULL or not, resulting the null-ptr-deref. Add sanity check for btrfs root before... • https://git.kernel.org/stable/c/42437a6386ffeaaf200731e73d723ea491f3fe7d •
CVSS: -EPSS: %CPEs: 2EXPL: 0CVE-2024-56773 – kunit: Fix potential null dereference in kunit_device_driver_test()
https://notcve.org/view.php?id=CVE-2024-56773
08 Jan 2025 — In the Linux kernel, the following vulnerability has been resolved: kunit: Fix potential null dereference in kunit_device_driver_test() kunit_kzalloc() may return a NULL pointer, dereferencing it without NULL check may lead to NULL dereference. Add a NULL check for test_state. • https://git.kernel.org/stable/c/d03c720e03bd9bf0b784d80b5d3ede7e2daf3b6e •
CVSS: -EPSS: %CPEs: 2EXPL: 0CVE-2024-56772 – kunit: string-stream: Fix a UAF bug in kunit_init_suite()
https://notcve.org/view.php?id=CVE-2024-56772
08 Jan 2025 — In the Linux kernel, the following vulnerability has been resolved: kunit: string-stream: Fix a UAF bug in kunit_init_suite() In kunit_debugfs_create_suite(), if alloc_string_stream() fails in the kunit_suite_for_each_test_case() loop, the "suite->log = stream" has assigned before, and the error path only free the suite->log's stream memory but not set it to NULL, so the later string_stream_clear() of suite->log in kunit_init_suite() will cause below UAF bug. Set stream pointer to NULL after free to fix it.... • https://git.kernel.org/stable/c/a3fdf784780ccb0008d630e8722d1389c49c7499 •
CVSS: -EPSS: %CPEs: 2EXPL: 0CVE-2024-56771 – mtd: spinand: winbond: Fix 512GW, 01GW, 01JW and 02JW ECC information
https://notcve.org/view.php?id=CVE-2024-56771
08 Jan 2025 — In the Linux kernel, the following vulnerability has been resolved: mtd: spinand: winbond: Fix 512GW, 01GW, 01JW and 02JW ECC information These four chips: * W25N512GW * W25N01GW * W25N01JW * W25N02JW all require a single bit of ECC strength and thus feature an on-die Hamming-like ECC engine. There is no point in filling a ->get_status() callback for them because the main ECC status bytes are located in standard places, and retrieving the number of bitflips in case of corrected chunk is both useless and uns... • https://git.kernel.org/stable/c/6a804fb72de56d6a99b799f565ae45f2cec7cd55 •
CVSS: -EPSS: %CPEs: 7EXPL: 0CVE-2024-56770 – net/sched: netem: account for backlog updates from child qdisc
https://notcve.org/view.php?id=CVE-2024-56770
08 Jan 2025 — In the Linux kernel, the following vulnerability has been resolved: net/sched: netem: account for backlog updates from child qdisc In general, 'qlen' of any classful qdisc should keep track of the number of packets that the qdisc itself and all of its children holds. In case of netem, 'qlen' only accounts for the packets in its internal tfifo. When netem is used with a child qdisc, the child qdisc can use 'qdisc_tree_reduce_backlog' to inform its parent, netem, about created or dropped SKBs. This function u... • https://git.kernel.org/stable/c/50612537e9ab29693122fab20fc1eed235054ffe •
CVSS: 7.2EPSS: 0%CPEs: 4EXPL: 0CVE-2024-56769 – media: dvb-frontends: dib3000mb: fix uninit-value in dib3000_write_reg
https://notcve.org/view.php?id=CVE-2024-56769
06 Jan 2025 — In the Linux kernel, the following vulnerability has been resolved: media: dvb-frontends: dib3000mb: fix uninit-value in dib3000_write_reg Syzbot reports [1] an uninitialized value issue found by KMSAN in dib3000_read_reg(). Local u8 rb[2] is used in i2c_transfer() as a read buffer; in case that call fails, the buffer may end up with some undefined values. Since no elaborate error handling is expected in dib3000_write_reg(), simply zero out rb buffer to mitigate the problem. [1] Syzkaller report dvb-usb: bu... • https://git.kernel.org/stable/c/74340b0a8bc60b400c7e5fe4950303aa6f914d16 •
CVSS: 5.5EPSS: 0%CPEs: 4EXPL: 0CVE-2024-56767 – dmaengine: at_xdmac: avoid null_prt_deref in at_xdmac_prep_dma_memset
https://notcve.org/view.php?id=CVE-2024-56767
06 Jan 2025 — In the Linux kernel, the following vulnerability has been resolved: dmaengine: at_xdmac: avoid null_prt_deref in at_xdmac_prep_dma_memset The at_xdmac_memset_create_desc may return NULL, which will lead to a null pointer dereference. For example, the len input is error, or the atchan->free_descs_list is empty and memory is exhausted. Therefore, add check to avoid this. En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: dmaengine: at_xdmac: evitar null_prt_deref en at_xdmac_prep_dma_memset El... • https://git.kernel.org/stable/c/b206d9a23ac71cb905f5fb6e0cd813406f89b678 •