CVSS: -EPSS: 0%CPEs: 4EXPL: 0CVE-2024-56538 – drm: zynqmp_kms: Unplug DRM device before removal
https://notcve.org/view.php?id=CVE-2024-56538
In the Linux kernel, the following vulnerability has been resolved: drm: zynqmp_kms: Unplug DRM device before removal Prevent userspace accesses to the DRM device from causing use-after-frees by unplugging the device before we remove it. This causes any further userspace accesses to result in an error without further calls into this driver's internals. • https://git.kernel.org/stable/c/d76271d22694e874ed70791702db9252ffe96a4c https://git.kernel.org/stable/c/a17b9afe58c474657449cf87e238b1788200576b https://git.kernel.org/stable/c/4fb97432e28a7e136b2d76135d50e988ada8e1af https://git.kernel.org/stable/c/692f52aedccbf79b212a1e14e3735192b4c24a7d https://git.kernel.org/stable/c/2e07c88914fc5289c21820b1aa94f058feb38197 •
CVSS: -EPSS: 0%CPEs: 3EXPL: 0CVE-2024-56537 – drm: xlnx: zynqmp_disp: layer may be null while releasing
https://notcve.org/view.php?id=CVE-2024-56537
In the Linux kernel, the following vulnerability has been resolved: drm: xlnx: zynqmp_disp: layer may be null while releasing layer->info can be null if we have an error on the first layer in zynqmp_disp_create_layers • https://git.kernel.org/stable/c/1836fd5ed98db85f249bf755978c964c2607a25d https://git.kernel.org/stable/c/ce7e62bbd55d20cf250396eb4e8f65b3b5a5e685 https://git.kernel.org/stable/c/9218be402aeb1999cc119fc616e21c3cc7cdeec0 https://git.kernel.org/stable/c/223842c7702b52846b1c5aef8aca7474ec1fd29b •
CVSS: -EPSS: 0%CPEs: 3EXPL: 0CVE-2024-56536 – wifi: cw1200: Fix potential NULL dereference
https://notcve.org/view.php?id=CVE-2024-56536
In the Linux kernel, the following vulnerability has been resolved: wifi: cw1200: Fix potential NULL dereference A recent refactoring was identified by static analysis to cause a potential NULL dereference, fix this! • https://git.kernel.org/stable/c/2719a9e7156c4b3983b43db467c1ff96801bda99 https://git.kernel.org/stable/c/0ec90ac5f7bd9dd573bd5d964cbdc3beaa93a33e https://git.kernel.org/stable/c/67c914f2d64b28409796a6b9036c131e93f8af6c https://git.kernel.org/stable/c/2b94751626a6d49bbe42a19cc1503bd391016bd5 •
CVSS: -EPSS: 0%CPEs: 3EXPL: 0CVE-2024-56535 – wifi: rtw89: coex: check NULL return of kmalloc in btc_fw_set_monreg()
https://notcve.org/view.php?id=CVE-2024-56535
In the Linux kernel, the following vulnerability has been resolved: wifi: rtw89: coex: check NULL return of kmalloc in btc_fw_set_monreg() kmalloc may fail, return value might be NULL and will cause NULL pointer dereference. Add check NULL return of kmalloc in btc_fw_set_monreg(). • https://git.kernel.org/stable/c/b952cb0a6e2d2e6942de3f8c6a1bd985815b9550 https://git.kernel.org/stable/c/051577414271961f3f4c3bff87b427924b486219 https://git.kernel.org/stable/c/64db1a42d98307001a48cec1b3e68ce9f905e73d https://git.kernel.org/stable/c/81df5ed446b448bdc327b7c7f0b50121fc1f4aa2 •
CVSS: -EPSS: 0%CPEs: 3EXPL: 0CVE-2024-56534 – isofs: avoid memory leak in iocharset
https://notcve.org/view.php?id=CVE-2024-56534
In the Linux kernel, the following vulnerability has been resolved: isofs: avoid memory leak in iocharset A memleak was found as below: unreferenced object 0xffff0000d10164d8 (size 8): comm "pool-udisksd", pid 108217, jiffies 4295408555 hex dump (first 8 bytes): 75 74 66 38 00 cc cc cc utf8.... backtrace (crc de430d31): [<ffff800081046e6c>] kmemleak_alloc+0xb8/0xc8 [<ffff8000803e6c3c>] __kmalloc_node_track_caller_noprof+0x380/0x474 [<ffff800080363b74>] kstrdup+0x70/0xfc [<ffff80007bb3c6a4>] isofs_parse_param+0x228/0x2c0 [isofs] [<ffff8000804d7f68>] vfs_parse_fs_param+0xf4/0x164 [<ffff8000804d8064>] vfs_parse_fs_string+0x8c/0xd4 [<ffff8000804d815c>] vfs_parse_monolithic_sep+0xb0/0xfc [<ffff8000804d81d8>] generic_parse_monolithic+0x30/0x3c [<ffff8000804d8bfc>] parse_monolithic_mount_data+0x40/0x4c [<ffff8000804b6a64>] path_mount+0x6c4/0x9ec [<ffff8000804b6e38>] do_mount+0xac/0xc4 [<ffff8000804b7494>] __arm64_sys_mount+0x16c/0x2b0 [<ffff80008002b8dc>] invoke_syscall+0x7c/0x104 [<ffff80008002ba44>] el0_svc_common.constprop.1+0xe0/0x104 [<ffff80008002ba94>] do_el0_svc+0x2c/0x38 [<ffff800081041108>] el0_svc+0x3c/0x1b8 The opt->iocharset is freed inside the isofs_fill_super function, But there may be situations where it's not possible to enter this function. For example, in the get_tree_bdev_flags function,when encountering the situation where "Can't mount, would change RO state," In such a case, isofs_fill_super will not have the opportunity to be called,which means that opt->iocharset will not have the chance to be freed,ultimately leading to a memory leak. Let's move the memory freeing of opt->iocharset into isofs_free_fc function. • https://git.kernel.org/stable/c/1b17a46c9243e9421ee1ac6d628604bbc4ae2201 https://git.kernel.org/stable/c/34f090ddb3630a26e5a6b220bf3bfaf5c7b70393 https://git.kernel.org/stable/c/0fbab266ca8000333c966f5b58cb9b9cac658573 https://git.kernel.org/stable/c/0b5bbeee4de616a268db77e2f40f19ab010a367b •