CVE-2024-56624

In the Linux kernel, the following vulnerability has been resolved: iommufd: Fix out_fput in iommufd_fault_alloc() As fput() calls the file->f_op->release op, where fault obj and ictx are getting released, there is no need to release these two after fput() one more time, which would result in imbalanced refcounts: refcount_t: decrement hit 0; leaking memory. WARNING: CPU: 48 PID: 2369 at lib/refcount.c:31 refcount_warn_saturate+0x60/0x230 Call trace: refcount_warn_saturate+0x60/0x230 (P) refcount_warn_saturate+0x60/0x230 (L) iommufd_fault_fops_release+0x9c/0xe0 [iommufd] ... VFS: Close: file count is 0 (f_op=iommufd_fops [iommufd]) WARNING: CPU: 48 PID: 2369 at fs/open.c:1507 filp_flush+0x3c/0xf0 Call trace: filp_flush+0x3c/0xf0 (P) filp_flush+0x3c/0xf0 (L) __arm64_sys_close+0x34/0x98 ... imbalanced put on file reference count WARNING: CPU: 48 PID: 2369 at fs/file.c:74 __file_ref_put+0x100/0x138 Call trace: __file_ref_put+0x100/0x138 (P) __file_ref_put+0x100/0x138 (L) __fput_sync+0x4c/0xd0 Drop those two lines to fix the warnings above.

The Linux Kernel, the operating system core itself.

Security Fix(es):

In the Linux kernel, the following vulnerability has been resolved: sh: cpuinfo: Fix a warning for CONFIG_CPUMASK_OFFSTACK When CONFIG_CPUMASK_OFFSTACK and CONFIG_DEBUG_PER_CPU_MAPS are selected, cpu_max_bits_warn() generates a runtime warning similar as below when showing /proc/cpuinfo. Fix this by using nr_cpu_ids (the runtime limit) instead of NR_CPUS to iterate CPUs. [ 3.052463] ------------[ cut here ]------------ [ 3.059679] WARNING: CPU: 3 PID: 1 at include/linux/cpumask.h:108 show_cpuinfo+0x5e8/0x5f0 [ 3.070072] Modules linked in: efivarfs autofs4 [ 3.076257] CPU: 0 PID: 1 Comm: systemd Not tainted 5.19-rc5+ #1052 [ 3.099465] Stack : 9000000100157b08 9000000000f18530 9000000000cf846c 9000000100154000 [ 3.109127] 9000000100157a50 0000000000000000 9000000100157a58 9000000000ef7430 [ 3.118774] 90000001001578e8 0000000000000040 0000000000000020 ffffffffffffffff [ 3.128412] 0000000000aaaaaa 1ab25f00eec96a37 900000010021de80 900000000101c890 [ 3.138056] 0000000000000000 0000000000000000 0000000000000000 0000000000aaaaaa [ 3.147711] ffff8000339dc220 0000000000000001 0000000006ab4000 0000000000000000 [ 3.157364] 900000000101c998 0000000000000004 9000000000ef7430 0000000000000000 [ 3.167012] 0000000000000009 000000000000006c 0000000000000000 0000000000000000 [ 3.176641] 9000000000d3de08 9000000001639390 90000000002086d8 00007ffff0080286 [ 3.186260] 00000000000000b0 0000000000000004 0000000000000000 0000000000071c1c [ 3.195868] ... [ 3.199917] Call Trace: [ 3.203941] [<90000000002086d8>] show_stack+0x38/0x14c [ 3.210666] [<9000000000cf846c>] dump_stack_lvl+0x60/0x88 [ 3.217625] [<900000000023d268>] __warn+0xd0/0x100 [ 3.223958] [<9000000000cf3c90>] warn_slowpath_fmt+0x7c/0xcc [ 3.231150] [<9000000000210220>] show_cpuinfo+0x5e8/0x5f0 [ 3.238080] [<90000000004f578c>] seq_read_iter+0x354/0x4b4 [ 3.245098] [<90000000004c2e90>] new_sync_read+0x17c/0x1c4 [ 3.252114] [<90000000004c5174>] vfs_read+0x138/0x1d0 [ 3.258694] [<90000000004c55f8>] ksys_read+0x70/0x100 [ 3.265265] [<9000000000cfde9c>] do_syscall+0x7c/0x94 [ 3.271820] [<9000000000202fe4>] handle_syscall+0xc4/0x160 [ 3.281824] ---[ end trace 8b484262b4b8c24c ]---(CVE-2022-49034)

In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Check null pointer before try to access it [why & how] Change the order of the pipe_ctx->plane_state check to ensure that plane_state is not null before accessing it.(CVE-2024-49906)

In the Linux kernel, the following vulnerability has been resolved: x86/CPU/AMD: Clear virtualized VMLOAD/VMSAVE on Zen4 client A number of Zen4 client SoCs advertise the ability to use virtualized VMLOAD/VMSAVE, but using these instructions is reported to be a cause of a random host reboot. These instructions aren't intended to be advertised on Zen4 client so clear the capability.(CVE-2024-53114)

In the Linux kernel, the following vulnerability has been resolved: vdpa: solidrun: Fix UB bug with devres In psnet_open_pf_bar() and snet_open_vf_bar() a string later passed to pcim_iomap_regions() is placed on the stack. Neither pcim_iomap_regions() nor the functions it calls copy that string. Should the string later ever be used, this, consequently, causes undefined behavior since the stack frame will by then have disappeared. Fix the bug by allocating the strings on the heap through devm_kasprintf().(CVE-2024-53126)

In the Linux kernel, the following vulnerability has been resolved: Revert "mmc: dw_mmc: Fix IDMAC operation with pages bigger than 4K" The commit 8396c793ffdf ("mmc: dw_mmc: Fix IDMAC operation with pages bigger than 4K") increased the max_req_size, even for 4K pages,…

The Linux Kernel, the operating system core itself.

Security Fix(es):

In the Linux kernel, the following vulnerability has been resolved: sh: cpuinfo: Fix a warning for CONFIG_CPUMASK_OFFSTACK When CONFIG_CPUMASK_OFFSTACK and CONFIG_DEBUG_PER_CPU_MAPS are selected, cpu_max_bits_warn() generates a runtime warning similar as below when showing /proc/cpuinfo. Fix this by using nr_cpu_ids (the runtime limit) instead of NR_CPUS to iterate CPUs. [ 3.052463] ------------[ cut here ]------------ [ 3.059679] WARNING: CPU: 3 PID: 1 at include/linux/cpumask.h:108 show_cpuinfo+0x5e8/0x5f0 [ 3.070072] Modules linked in: efivarfs autofs4 [ 3.076257] CPU: 0 PID: 1 Comm: systemd Not tainted 5.19-rc5+ #1052 [ 3.099465] Stack : 9000000100157b08 9000000000f18530 9000000000cf846c 9000000100154000 [ 3.109127] 9000000100157a50 0000000000000000 9000000100157a58 9000000000ef7430 [ 3.118774] 90000001001578e8 0000000000000040 0000000000000020 ffffffffffffffff [ 3.128412] 0000000000aaaaaa 1ab25f00eec96a37 900000010021de80 900000000101c890 [ 3.138056] 0000000000000000 0000000000000000 0000000000000000 0000000000aaaaaa [ 3.147711] ffff8000339dc220 0000000000000001 0000000006ab4000 0000000000000000 [ 3.157364] 900000000101c998 0000000000000004 9000000000ef7430 0000000000000000 [ 3.167012] 0000000000000009 000000000000006c 0000000000000000 0000000000000000 [ 3.176641] 9000000000d3de08 9000000001639390 90000000002086d8 00007ffff0080286 [ 3.186260] 00000000000000b0 0000000000000004 0000000000000000 0000000000071c1c [ 3.195868] ... [ 3.199917] Call Trace: [ 3.203941] [<90000000002086d8>] show_stack+0x38/0x14c [ 3.210666] [<9000000000cf846c>] dump_stack_lvl+0x60/0x88 [ 3.217625] [<900000000023d268>] __warn+0xd0/0x100 [ 3.223958] [<9000000000cf3c90>] warn_slowpath_fmt+0x7c/0xcc [ 3.231150] [<9000000000210220>] show_cpuinfo+0x5e8/0x5f0 [ 3.238080] [<90000000004f578c>] seq_read_iter+0x354/0x4b4 [ 3.245098] [<90000000004c2e90>] new_sync_read+0x17c/0x1c4 [ 3.252114] [<90000000004c5174>] vfs_read+0x138/0x1d0 [ 3.258694] [<90000000004c55f8>] ksys_read+0x70/0x100 [ 3.265265] [<9000000000cfde9c>] do_syscall+0x7c/0x94 [ 3.271820] [<9000000000202fe4>] handle_syscall+0xc4/0x160 [ 3.281824] ---[ end trace 8b484262b4b8c24c ]---(CVE-2022-49034)

In the Linux kernel, the following vulnerability has been resolved:

firmware: qcom: scm: Mark get_wq_ctx() as atomic call

Currently get_wq_ctx() is wrongly configured as a standard call. When two SMC calls are in sleep and one SMC wakes up, it calls get_wq_ctx() to resume the corresponding sleeping thread. But if get_wq_ctx() is interrupted, goes to sleep and another SMC call is waiting to be allocated a waitq context, it leads to a deadlock.

To avoid this get_wq_ctx() must be an atomic call and can't be a standard SMC call. Hence mark get_wq_ctx() as a fast call.(CVE-2024-46692)

In the Linux kernel, the following vulnerability has been resolved:

drm/vmwgfx: Prevent unmapping active read buffers

The kms paths keep a persistent map active to read and compare the cursor buffer. These maps can race with each other in simple scenario where: a) buffer "a" mapped for update b) buffer "a" mapped for compare c) do the compare d) unmap "a" for compare e) update the cursor f) unmap "a" for update At step "e" the buffer has been unmapped and the read contents is bogus.

Prevent unmapping of active read buffers by simply keeping a count of how many paths have currently active maps and unmap only when the count reaches 0.(CVE-2024-46710)

In the Linux kernel, the following vulnerability has been resolved:

xen: privcmd: Fix possible access to a freed kirqfd instance

Nothing prevents simultaneous ioctl calls to…

In the Linux kernel, the following vulnerability has been resolved: iommufd: Fix out_fput in iommufd_fault_alloc() As fput() calls the file->f_op->release op, where fault obj and ictx are getting released, there is no need to release these two after fput() one more time, which would result in imbalanced refcounts: refcount_t: decrement hit 0; leaking memory. WARNING: CPU: 48 PID: 2369 at lib/refcount.c:31 refcount_warn_saturate+0x60/0x230 Call trace: refcount_warn_saturate+0x60/0x230 (P) refcount_warn_saturate+0x60/0x230 (L) iommufd_fault_fops_release+0x9c/0xe0 [iommufd] ... VFS: Close: file count is 0 (f_op=iommufd_fops [iommufd]) WARNING: CPU: 48 PID: 2369 at fs/open.c:1507 filp_flush+0x3c/0xf0 Call trace: filp_flush+0x3c/0xf0 (P) filp_flush+0x3c/0xf0 (L) __arm64_sys_close+0x34/0x98 ... imbalanced put on file reference count WARNING: CPU: 48 PID: 2369 at fs/file.c:74 __file_ref_put+0x100/0x138 Call trace: __file_ref_put+0x100/0x138 (P) __file_ref_put+0x100/0x138 (L) __fput_sync+0x4c/0xd0 Drop those two lines to fix the warnings above.

Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:

• ARM64 architecture;
• MIPS architecture;
• PowerPC architecture;
• RISC-V architecture;
• S390 architecture;
• x86 architecture;
• Block layer subsystem;
• Compute Acceleration Framework;
• ACPI drivers;
• Drivers core;
• Ublk userspace block driver;
• Virtio block driver;
• Bluetooth drivers;
• Buffer Sharing and Synchronization framework;
• DMA engine subsystem;
• EFI core;
• GPIO subsystem;
• GPU drivers;
• HID subsystem;
• Microsoft Hyper-V drivers;
• Hardware monitoring drivers;
• I3C subsystem;
• IIO ADC drivers;
• IIO subsystem;
• InfiniBand drivers;
• IOMMU subsystem;
• LED subsystem;
• Multiple devices driver;
• Media drivers;
• Microchip PCI driver;
• MTD block device drivers;
• Network drivers;
• Mellanox network drivers;
• STMicroelectronics network drivers;
• NVME drivers;
• PCI subsystem;
• PHY drivers;
• Pin controllers subsystem;
• x86 platform drivers;
• i.MX PM domains;
• Power supply drivers;
• Voltage and Current Regulator drivers;
• SCSI subsystem;
• i.MX SoC drivers;
• SPI subsystem;
• UFS subsystem;
• USB Gadget drivers;
• TDX Guest driver;
• AFS file system;
• BTRFS file system;
• Ceph distributed file system;
• File systems infrastructure;
• F2FS file system;
• JFFS2 file system;
• JFS file system;
• Network file systems library;
• Network file system (NFS) server daemon;
• NILFS2 file system;
• File system notification infrastructure;
• Overlay file system;
• Diskquota system;
• SMB network file system;
• DRM display driver;
• BPF subsystem;
• VLANs driver;
• KASAN memory debugging framework;
• Memory management;
• StackDepot library;
• Bluetooth subsystem;
• LAPB network protocol;
• Netfilter;
• io_uring subsystem;
• Control group (cgroup);
• DMA mapping infrastructure;
• KCSAN framework;
• Scheduler infrastructure;
• Seccomp subsystem;
• Tracing infrastructure;
• Workqueue subsystem;
• KUnit library;
• CAN network layer;
• Networking core;
• DCCP (Datagram Congestion Control Protocol);
• HSR network protocol;
• IEEE802154.4 network protocol;
• IPv4 networking;
• IPv6 networking;
• MAC80211 subsystem;
• Multipath TCP;
• NET/ROM layer;
• Packet sockets;
• RDS protocol;
• Network traffic control;
• SCTP protocol;
• SMC sockets;
• TIPC protocol;
• Wireless networking;
• eXpress Data Path;
• SELinux security module;
• ALSA framework;
• Intel ASoC drivers;
• SOF drivers; (CVE-2024-57921, CVE-2024-56614, CVE-2024-56558, CVE-2024-56589, CVE-2024-56662, CVE-2024-56610, CVE-2024-56717, CVE-2024-57890, CVE-2024-55639, CVE-2024-56562, CVE-2025-21633, CVE-2024-56598, CVE-2024-47794, CVE-2024-41935, CVE-2024-57901, CVE-2024-56587, CVE-2024-56581, CVE-2024-56783, CVE-2024-57888, CVE-2024-57809, CVE-2024-57926, CVE-2025-21650, CVE-2024-56634, CVE-2025-21639, CVE-2025-21656, CVE-2024-56578, CVE-2025-21632, CVE-2024-56784, CVE-2025-21644, CVE-2024-56776, CVE-2024-56764, CVE-2024-56652, CVE-2024-56550, CVE-2024-56569, CVE-2024-57904, CVE-2024-49569, CVE-2024-56770, CVE-2024-56606, CVE-2024-57806, CVE-2024-56646, CVE-2024-57895, CVE-2024-57880, CVE-2024-56650, CVE-2024-56591, CVE-2024-56590, CVE-2024-56642, CVE-2024-56713, CVE-2025-21663, CVE-2024-57938, CVE-2024-56760, CVE-2024-56583, CVE-2025-21662, CVE-2024-56629, CVE-2024-47408, CVE-2024-57850, CVE-2024-56777, CVE-2024-56626, CVE-2024-56773, CVE-2024-56647, CVE-2025-21664, CVE-2024-56564, CVE-2024-56597, CVE-2024-56623, CVE-2024-57897, CVE-2024-56670, CVE-2024-56567, CVE-2024-57931, CVE-2024-56761, CVE-2024-57935, CVE-2024-53690, CVE-2025-21640, CVE-2024-56608, CVE-2024-57878, CVE-2025-21648, CVE-2024-57898, CVE-2024-57889, CVE-2024-56644, CVE-2024-56763, CVE-2024-57900,…

Attila Szász discovered that the HFS+ file system implementation in the Linux Kernel contained a heap overflow vulnerability. An attacker could use a specially crafted file system image that, when mounted, could cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2025-0927)

Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:

• ARM64 architecture;
• MIPS architecture;
• PowerPC architecture;
• RISC-V architecture;
• S390 architecture;
• x86 architecture;
• Block layer subsystem;
• Compute Acceleration Framework;
• ACPI drivers;
• Drivers core;
• Ublk userspace block driver;
• Virtio block driver;
• Bluetooth drivers;
• Buffer Sharing and Synchronization framework;
• DMA engine subsystem;
• EFI core;
• GPIO subsystem;
• GPU drivers;
• HID subsystem;
• Microsoft Hyper-V drivers;
• Hardware monitoring drivers;
• I3C subsystem;
• IIO ADC drivers;
• IIO subsystem;
• InfiniBand drivers;
• IOMMU subsystem;
• LED subsystem;
• Multiple devices driver;
• Media drivers;
• Microchip PCI driver;
• MTD block device drivers;
• Network drivers;
• Mellanox network drivers;
• STMicroelectronics network drivers;
• NVME drivers;
• PCI subsystem;
• PHY drivers;
• Pin controllers subsystem;
• x86 platform drivers;
• i.MX PM domains;
• Power supply drivers;
• Voltage and Current Regulator drivers;
• SCSI subsystem;
• i.MX SoC drivers;
• SPI subsystem;
• UFS subsystem;
• USB Gadget drivers;
• TDX Guest driver;
• AFS file system;
• BTRFS file system;
• Ceph distributed file system;
• File systems infrastructure;
• F2FS file system;
• JFFS2 file system;
• JFS file system;
• Network file systems library;
• Network file system (NFS) server daemon;
• NILFS2 file system;
• File system notification infrastructure;
• Overlay file system;
• Diskquota system;
• SMB network file system;
• DRM display driver;
• BPF subsystem;
• VLANs driver;
• KASAN memory debugging framework;
• Memory management;
• StackDepot library;
• Bluetooth subsystem;
• LAPB network protocol;
• Network namespace;
• Netfilter;
• io_uring subsystem;
• Control group (cgroup);
• DMA mapping infrastructure;
• KCSAN framework;
• Scheduler infrastructure;
• Seccomp subsystem;
• Tracing infrastructure;
• Workqueue subsystem;
• KUnit library;
• CAN network layer;
• Networking core;
• DCCP (Datagram Congestion Control Protocol);
• HSR network protocol;
• IEEE802154.4 network protocol;
• IPv4 networking;
• IPv6 networking;
• MAC80211 subsystem;
• Multipath TCP;
• NET/ROM layer;
• Packet sockets;
• RDS protocol;
• Network traffic control;
• SCTP protocol;
• SMC sockets;
• TIPC protocol;
• Wireless networking;
• eXpress Data Path;
• SELinux security module;
• ALSA framework;
• Intel ASoC drivers;
• SOF drivers; (CVE-2024-56712, CVE-2024-56761, CVE-2025-21661, CVE-2024-56565, CVE-2024-57804, CVE-2024-57887, CVE-2025-21642, CVE-2024-56779, CVE-2025-21656, CVE-2024-57890, CVE-2024-36476, CVE-2024-57843, CVE-2024-56594, CVE-2024-41932, CVE-2025-21653, CVE-2024-56567, CVE-2024-56665, CVE-2024-54191, CVE-2024-57893, CVE-2024-57932, CVE-2024-56656, CVE-2024-57945, CVE-2024-57931, CVE-2024-56599, CVE-2024-57897, CVE-2024-57903, CVE-2024-57918, CVE-2024-57795, CVE-2024-56662, CVE-2025-21639, CVE-2024-55881, CVE-2024-57889, CVE-2024-57884, CVE-2024-57934, CVE-2024-39282, CVE-2024-56718, CVE-2024-56644, CVE-2024-56760, CVE-2024-43098, CVE-2024-47143, CVE-2024-55642, CVE-2024-56634, CVE-2024-56564, CVE-2024-56768, CVE-2024-56649, CVE-2024-57919, CVE-2024-56620, CVE-2024-56625, CVE-2024-56655, CVE-2024-56772, CVE-2025-21637, CVE-2024-56617, CVE-2024-57879, CVE-2024-56715, CVE-2024-56550, CVE-2024-50051, CVE-2024-56673, CVE-2024-51729, CVE-2025-21664,…

Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:

• ARM64 architecture;
• MIPS architecture;
• PowerPC architecture;
• RISC-V architecture;
• S390 architecture;
• x86 architecture;
• Block layer subsystem;
• Compute Acceleration Framework;
• ACPI drivers;
• Drivers core;
• Ublk userspace block driver;
• Virtio block driver;
• Bluetooth drivers;
• Buffer Sharing and Synchronization framework;
• DMA engine subsystem;
• EFI core;
• GPIO subsystem;
• GPU drivers;
• HID subsystem;
• Microsoft Hyper-V drivers;
• Hardware monitoring drivers;
• I3C subsystem;
• IIO ADC drivers;
• IIO subsystem;
• InfiniBand drivers;
• IOMMU subsystem;
• LED subsystem;
• Multiple devices driver;
• Media drivers;
• Microchip PCI driver;
• MTD block device drivers;
• Network drivers;
• Mellanox network drivers;
• STMicroelectronics network drivers;
• NVME drivers;
• PCI subsystem;
• PHY drivers;
• Pin controllers subsystem;
• x86 platform drivers;
• i.MX PM domains;
• Power supply drivers;
• Voltage and Current Regulator drivers;
• SCSI subsystem;
• i.MX SoC drivers;
• SPI subsystem;
• UFS subsystem;
• USB Gadget drivers;
• TDX Guest driver;
• AFS file system;
• BTRFS file system;
• Ceph distributed file system;
• File systems infrastructure;
• F2FS file system;
• JFFS2 file system;
• JFS file system;
• Network file systems library;
• Network file system (NFS) server daemon;
• NILFS2 file system;
• File system notification infrastructure;
• Overlay file system;
• Diskquota system;
• SMB network file system;
• DRM display driver;
• BPF subsystem;
• VLANs driver;
• KASAN memory debugging framework;
• Memory management;
• StackDepot library;
• Bluetooth subsystem;
• LAPB network protocol;
• Netfilter;
• io_uring subsystem;
• Control group (cgroup);
• DMA mapping infrastructure;
• KCSAN framework;
• Scheduler infrastructure;
• Seccomp subsystem;
• Tracing infrastructure;
• Workqueue subsystem;
• KUnit library;
• CAN network layer;
• Networking core;
• DCCP (Datagram Congestion Control Protocol);
• HSR network protocol;
• IEEE802154.4 network protocol;
• IPv4 networking;
• IPv6 networking;
• MAC80211 subsystem;
• Multipath TCP;
• NET/ROM layer;
• Packet sockets;
• RDS protocol;
• Network traffic control;
• SCTP protocol;
• SMC sockets;
• TIPC protocol;
• Wireless networking;
• eXpress Data Path;
• SELinux security module;
• ALSA framework;
• Intel ASoC drivers;
• SOF drivers; (CVE-2024-47794, CVE-2025-21653, CVE-2024-55642, CVE-2024-56580, CVE-2024-36476, CVE-2024-56623, CVE-2024-56773, CVE-2024-48873, CVE-2024-47141, CVE-2024-57910, CVE-2024-56759, CVE-2024-54460, CVE-2024-57839, CVE-2024-56625, CVE-2024-55916, CVE-2025-21664, CVE-2025-21652, CVE-2024-56624, CVE-2024-56574, CVE-2024-50051, CVE-2025-21655, CVE-2024-56578, CVE-2024-56782, CVE-2024-57939, CVE-2024-57935, CVE-2024-56647, CVE-2024-57905, CVE-2024-57921, CVE-2024-56660, CVE-2025-21650, CVE-2025-21631, CVE-2024-56642, CVE-2024-56552, CVE-2024-57934, CVE-2024-56621, CVE-2024-57881, CVE-2024-41932, CVE-2024-56770, CVE-2024-57897, CVE-2024-56785, CVE-2024-56664, CVE-2024-57945, CVE-2024-57938, CVE-2024-56636, CVE-2024-56572, CVE-2024-43098, CVE-2024-56760, CVE-2024-57916, CVE-2024-56714, CVE-2025-21660, CVE-2024-57906, CVE-2025-21638, CVE-2024-53687, CVE-2024-56652, CVE-2024-51729, CVE-2024-49571, CVE-2024-57883, CVE-2024-54191, CVE-2024-56712, CVE-2024-49568, CVE-2024-57932, CVE-2024-57893, CVE-2024-56645, CVE-2024-56719, CVE-2024-56641, CVE-2024-57802, CVE-2024-56775, CVE-2024-56627, CVE-2024-56638, CVE-2024-57929, CVE-2024-56615, CVE-2024-56566, CVE-2024-56620, CVE-2024-56577, CVE-2025-21656, CVE-2024-57887, CVE-2024-52319, CVE-2024-56657, CVE-2024-57872,…