CVE-2024-56552

In the Linux kernel, the following vulnerability has been resolved: drm/xe/guc_submit: fix race around suspend_pending Currently in some testcases we can trigger: xe 0000:03:00.0: [drm] Assertion exec_queue_destroyed(q) failed! .... WARNING: CPU: 18 PID: 2640 at drivers/gpu/drm/xe/xe_guc_submit.c:1826 xe_guc_sched_done_handler+0xa54/0xef0 [xe] xe 0000:03:00.0: [drm] ERROR GT1: DEREGISTER_DONE: Unexpected engine state 0x00a1, guc_id=57 Looking at a snippet of corresponding ftrace for this GuC id we can see: 162.673311: xe_sched_msg_add: dev=0000:03:00.0, gt=1 guc_id=57, opcode=3 162.673317: xe_sched_msg_recv: dev=0000:03:00.0, gt=1 guc_id=57, opcode=3 162.673319: xe_exec_queue_scheduling_disable: dev=0000:03:00.0, 1:0x2, gt=1, width=1, guc_id=57, guc_state=0x29, flags=0x0 162.674089: xe_exec_queue_kill: dev=0000:03:00.0, 1:0x2, gt=1, width=1, guc_id=57, guc_state=0x29, flags=0x0 162.674108: xe_exec_queue_close: dev=0000:03:00.0, 1:0x2, gt=1, width=1, guc_id=57, guc_state=0xa9, flags=0x0 162.674488: xe_exec_queue_scheduling_done: dev=0000:03:00.0, 1:0x2, gt=1, width=1, guc_id=57, guc_state=0xa9, flags=0x0 162.678452: xe_exec_queue_deregister: dev=0000:03:00.0, 1:0x2, gt=1, width=1, guc_id=57, guc_state=0xa1, flags=0x0 It looks like we try to suspend the queue (opcode=3), setting suspend_pending and triggering a disable_scheduling. The user then closes the queue. However the close will also forcefully signal the suspend fence after killing the queue, later when the G2H response for disable_scheduling comes back we have now cleared suspend_pending when signalling the suspend fence, so the disable_scheduling now incorrectly tries to also deregister the queue. This leads to warnings since the queue has yet to even be marked for destruction. We also seem to trigger errors later with trying to double unregister the same queue. To fix this tweak the ordering when handling the response to ensure we don't race with a disable_scheduling that didn't actually intend to perform an unregister. The destruction path should now also correctly wait for any pending_disable before marking as destroyed. (cherry picked from commit f161809b362f027b6d72bd998e47f8f0bad60a2e)

In the Linux kernel, the following vulnerability has been resolved: drm/xe/guc_submit: fix race around suspend_pending Currently in some testcases we can trigger: xe 0000:03:00.0: [drm] Assertion exec_queue_destroyed(q) failed! .... WARNING: CPU: 18 PID: 2640 at drivers/gpu/drm/xe/xe_guc_submit.c:1826 xe_guc_sched_done_handler+0xa54/0xef0 [xe] xe 0000:03:00.0: [drm] ERROR GT1: DEREGISTER_DONE: Unexpected engine state 0x00a1, guc_id=57 Looking at a snippet of corresponding ftrace for this GuC id we can see: 162.673311: xe_sched_msg_add: dev=0000:03:00.0, gt=1 guc_id=57, opcode=3 162.673317: xe_sched_msg_recv: dev=0000:03:00.0, gt=1 guc_id=57, opcode=3 162.673319: xe_exec_queue_scheduling_disable: dev=0000:03:00.0, 1:0x2, gt=1, width=1, guc_id=57, guc_state=0x29, flags=0x0 162.674089: xe_exec_queue_kill: dev=0000:03:00.0, 1:0x2, gt=1, width=1, guc_id=57, guc_state=0x29, flags=0x0 162.674108: xe_exec_queue_close: dev=0000:03:00.0, 1:0x2, gt=1, width=1, guc_id=57, guc_state=0xa9, flags=0x0 162.674488: xe_exec_queue_scheduling_done: dev=0000:03:00.0, 1:0x2, gt=1, width=1, guc_id=57, guc_state=0xa9, flags=0x0 162.678452: xe_exec_queue_deregister: dev=0000:03:00.0, 1:0x2, gt=1, width=1, guc_id=57, guc_state=0xa1, flags=0x0 It looks like we try to suspend the queue (opcode=3), setting suspend_pending and triggering a disable_scheduling. The user then closes the queue. However the close will also forcefully signal the suspend fence after killing the queue, later when the G2H response for disable_scheduling comes back we have now cleared suspend_pending when signalling the suspend fence, so the disable_scheduling now incorrectly tries to also deregister the queue. This leads to warnings since the queue has yet to even be marked for destruction. We also seem to trigger errors later with trying to double unregister the same queue. To fix this tweak the ordering when handling the response to ensure we don't race with a disable_scheduling that didn't actually intend to perform an unregister. The destruction path should now also correctly wait for any pending_disable before marking as destroyed. (cherry picked from commit f161809b362f027b6d72bd998e47f8f0bad60a2e)

Root has patched CVE-2024-56552 in the linux package for Root:Ubuntu:24.04. Multiple fixed versions available.

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,…

It was discovered that some Arm processors could complete a broadcast translation lookaside buffer (TLB) invalidation before memory writes made through the invalidated translation were globally observed. A local attacker could possibly use this to write to memory after permission to do so had been revoked, bypassing memory protections or escalating privileges. (CVE-2025-10263)

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;
• User-space API (UAPI);
• Kernel build system;
• ARM32 architecture;
• PowerPC architecture;
• RISC-V architecture;
• S390 architecture;
• User-Mode Linux (UML);
• x86 architecture;
• Cryptographic API;
• Intel NPU Driver;
• Compute Acceleration Framework;
• ACPI drivers;
• Drivers core;
• DRBD Distributed Replicated Block Device drivers;
• Rados block device (RBD) driver;
• Ublk userspace block driver;
• Compressed RAM block device driver;
• Bluetooth drivers;
• Hardware crypto device drivers;
• CXL (Compute Express Link) drivers;
• Arm Firmware Framework for ARMv8-A(FFA);
• EFI core;
• FPGA Framework;
• GPU drivers;
• HID subsystem;
• Hardware monitoring drivers;
• I2C subsystem;
• I3C subsystem;
• InfiniBand drivers;
• Input Device core drivers;
• Input Device (Mouse) drivers;
• IOMMU subsystem;
• Multiple devices driver;
• Media drivers;
• Fastrpc Driver;
• Network drivers;
• Mellanox network drivers;
• Microsoft Azure Network Adapter (MANA) driver;
• MediaTek network drivers;
• NVME drivers;
• Operating Performance Points (OPP) driver;
• PCI subsystem;
• PTP clock framework;
• RPMSG subsystem;
• SCSI subsystem;
• SoundWire subsystem;
• SPI subsystem;
• Greybus lights staging drivers;
• Media staging drivers;
• NVIDIA Tegra embedded controller (NVEC) staging driver;
• Realtek RTL8723BS SDIO drivers;
• TCM subsystem;
• Trusted Execution Environment drivers;
• Thunderbolt and USB4 drivers;
• TTY drivers;
• USB Gadget drivers;
• USB Dual Role (OTG-ready) Controller drivers;
• USB Serial drivers;
• vDPA drivers;
• VFIO drivers;
• Virtio Host (VHOST) subsystem;
• Virtio drivers;
• Xen hypervisor drivers;
• 9P distributed file system;
• AFS file system;
• File systems infrastructure;
• BTRFS file system;
• Ceph distributed file system;
• exFAT file system;
• F2FS file system;
• GFS2 file system;
• HFS file system;
• HFS+ file system;
• JFS file system;
• Network file systems library;
• Network file system (NFS) client;
• Network file system (NFS) server daemon;
• NTFS3 file system;
• OCFS2 file system;
• OrangeFS file system;
• SMB network file system;
• BPF subsystem;
• File system encryption (fscrypt);
• Software nodes and device properties;
• IPv4 networking;
• KVM subsystem;
• Mellanox drivers;
• Memory management;
• Networking core;
• Netfilter;
• Socket messages infrastructure;
• MediaTek SoC drivers;
• Sun RPC protocol;
• Network traffic control;
• IPv6 networking;
• Amateur Radio drivers;
• Bluetooth subsystem;
• IP tunnels definitions;
• KCM (Kernel Connection Multiplexor) sockets driver;
• MultiProtocol Label Switching driver;
• TCP network protocol;
• XFRM subsystem;
• Tracing infrastructure;
• io_uring subsystem;
• Control group (cgroup);
• Perf events;
• IRQ subsystem;
• Locking primitives;
• KProbes tracing;
• 9P file system network protocol;
• B.A.T.M.A.N. meshing protocol;
• Ethernet bridge;
• CAN network layer;
• Ceph Core library;
• Handshake API;
• HSR network protocol;
• IFE protocol;
• L2TP protocol;
• MAC80211 subsystem;
• IEEE 802.15.4 subsystem;
• Multipath TCP;
• NFC subsystem;
• Open vSwitch;
• Phonet protocol;
• RDS protocol;
• RxRPC session sockets;
• SCTP protocol;
• SMC…

It was discovered that some AMD processors did not properly perform Reverse Map Table (RMP) checks when the IOMMU accessed certain host buffers. A local attacker with hypervisor access could possibly use this to trigger an out-of-bounds condition and compromise the integrity of SEV-SNP guest memory. (CVE-2023-20585)

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:

• NVDIMM (Non-Volatile Memory Device) drivers;
• Handshake API;
• ARM32 architecture;
• ARM64 architecture;
• MIPS architecture;
• PowerPC architecture;
• RISC-V architecture;
• S390 architecture;
• x86 architecture;
• Block layer subsystem;
• Cryptographic API;
• Intel NPU Driver;
• ACPI drivers;
• Android drivers;
• Serial ATA and Parallel ATA drivers;
• Drivers core;
• DRBD Distributed Replicated Block Device drivers;
• Rados block device (RBD) driver;
• Bluetooth drivers;
• Cdrom driver;
• Character device driver;
• Hardware random number generator core;
• TPM device driver;
• Data acquisition framework and drivers;
• CPU frequency scaling framework;
• Hardware crypto device drivers;
• DAX dirext access to differentiated memory framework;
• Buffer Sharing and Synchronization framework;
• DMA engine subsystem;
• FireWire subsystem;
• Arm Firmware Framework for ARMv8-A(FFA);
• ARM SCMI message protocol;
• Intel Stratix 10 firmware drivers;
• FPGA Framework;
• GPIO subsystem;
• GPU drivers;
• HID subsystem;
• Microsoft Hyper-V drivers;
• Hardware monitoring drivers;
• CoreSight HW tracing drivers;
• Intel Trace Hub HW tracing drivers;
• I2C subsystem;
• IIO subsystem;
• IIO ADC drivers;
• IIO Magnetometer sensors drivers;
• InfiniBand drivers;
• Input Device core drivers;
• Input Device (Miscellaneous) drivers;
• Input Device (Mouse) drivers;
• IOMMU subsystem;
• IRQ chip drivers;
• LED subsystem;
• Mailbox framework;
• Multiple devices driver;
• Media drivers;
• MemoryStick subsystem;
• Multifunction device drivers;
• Intel Management Engine Interface driver;
• Amazon Nitro Secure Module driver;
• MMC subsystem;
• MTD block device drivers;
• Network drivers;
• Ethernet bonding driver;
• Mellanox network drivers;
• Microsoft Azure Network Adapter (MANA) driver;
• MediaTek network drivers;
• NTB driver;
• NVME drivers;
• PCI subsystem;
• x86 platform drivers;
• i.MX PM domains;
• System reset/shutdown drivers;
• Power supply drivers;
• RapidIO drivers;
• Voltage and Current Regulator drivers;
• Remote Processor subsystem;
• Reset controller framework;
• RPMSG subsystem;
• Real Time Clock drivers;
• S/390 drivers;
• SCSI subsystem;
• Xilinx SoC drivers;
• SPI subsystem;
• Media staging drivers;
• Media Oriented Systems Transport (MOST) driver;
• NVIDIA Tegra embedded controller (NVEC) staging driver;
• Realtek RTL8723BS SDIO drivers;
• VME bus staging drivers;
• TCM subsystem;
• TTY drivers;
• USB DSL drivers;
• Cadence USB3 driver;
• ULPI bus;
• USB core drivers;
• DesignWare USB3 driver;
• Faraday FOTG210 USB2 dual-role controller driver;
• USB Gadget drivers;
• USB Host Controller drivers;
• USB ChaosKey driver;
• Siemens ID Mouse USB driver;
• IOWarrior USB driver;
• LD Didactic USB driver;
• LEGO USB Tower driver;
• USS720 USB parallel port adapter driver;
• MediaTek USB3 DRD driver;
• USB Dual Role (OTG-ready) Controller drivers;
• USB Serial drivers;
• USB Type-C Port Controller Manager driver;
• USB Type-C Connector System Software Interface driver;
• USB over IP driver;
• vDPA drivers;
• VFIO drivers;
• Virtio Host (VHOST) subsystem;
• Framebuffer layer;
• Watchdog drivers;
• Xen hypervisor drivers;
• 9P distributed file system;
• AFS file system;
• File systems infrastructure;
• BTRFS file…

It was discovered that some AMD processors did not properly perform Reverse Map Table (RMP) checks when the IOMMU accessed certain host buffers. A local attacker with hypervisor access could possibly use this to trigger an out-of-bounds condition and compromise the integrity of SEV-SNP guest memory. (CVE-2023-20585)

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:

• NVDIMM (Non-Volatile Memory Device) drivers;
• Handshake API;
• ARM32 architecture;
• ARM64 architecture;
• MIPS architecture;
• PowerPC architecture;
• RISC-V architecture;
• S390 architecture;
• x86 architecture;
• Block layer subsystem;
• Cryptographic API;
• Intel NPU Driver;
• ACPI drivers;
• Android drivers;
• Serial ATA and Parallel ATA drivers;
• Drivers core;
• DRBD Distributed Replicated Block Device drivers;
• Rados block device (RBD) driver;
• Bluetooth drivers;
• Cdrom driver;
• Character device driver;
• Hardware random number generator core;
• TPM device driver;
• Data acquisition framework and drivers;
• CPU frequency scaling framework;
• Hardware crypto device drivers;
• DAX dirext access to differentiated memory framework;
• Buffer Sharing and Synchronization framework;
• DMA engine subsystem;
• FireWire subsystem;
• Arm Firmware Framework for ARMv8-A(FFA);
• ARM SCMI message protocol;
• Intel Stratix 10 firmware drivers;
• FPGA Framework;
• GPIO subsystem;
• GPU drivers;
• HID subsystem;
• Microsoft Hyper-V drivers;
• Hardware monitoring drivers;
• CoreSight HW tracing drivers;
• Intel Trace Hub HW tracing drivers;
• I2C subsystem;
• IIO subsystem;
• IIO ADC drivers;
• IIO Magnetometer sensors drivers;
• InfiniBand drivers;
• Input Device core drivers;
• Input Device (Miscellaneous) drivers;
• Input Device (Mouse) drivers;
• IOMMU subsystem;
• IRQ chip drivers;
• LED subsystem;
• Mailbox framework;
• Multiple devices driver;
• Media drivers;
• MemoryStick subsystem;
• Multifunction device drivers;
• Intel Management Engine Interface driver;
• Amazon Nitro Secure Module driver;
• MMC subsystem;
• MTD block device drivers;
• Network drivers;
• Ethernet bonding driver;
• Mellanox network drivers;
• Microsoft Azure Network Adapter (MANA) driver;
• MediaTek network drivers;
• NTB driver;
• NVME drivers;
• PCI subsystem;
• x86 platform drivers;
• i.MX PM domains;
• System reset/shutdown drivers;
• Power supply drivers;
• RapidIO drivers;
• Voltage and Current Regulator drivers;
• Remote Processor subsystem;
• Reset controller framework;
• RPMSG subsystem;
• Real Time Clock drivers;
• S/390 drivers;
• SCSI subsystem;
• Xilinx SoC drivers;
• SPI subsystem;
• Media staging drivers;
• Media Oriented Systems Transport (MOST) driver;
• NVIDIA Tegra embedded controller (NVEC) staging driver;
• Realtek RTL8723BS SDIO drivers;
• VME bus staging drivers;
• TCM subsystem;
• TTY drivers;
• USB DSL drivers;
• Cadence USB3 driver;
• ULPI bus;
• USB core drivers;
• DesignWare USB3 driver;
• Faraday FOTG210 USB2 dual-role controller driver;
• USB Gadget drivers;
• USB Host Controller drivers;
• USB ChaosKey driver;
• Siemens ID Mouse USB driver;
• IOWarrior USB driver;
• LD Didactic USB driver;
• LEGO USB Tower driver;
• USS720 USB parallel port adapter driver;
• MediaTek USB3 DRD driver;
• USB Dual Role (OTG-ready) Controller drivers;
• USB Serial drivers;
• USB Type-C Port Controller Manager driver;
• USB Type-C Connector System Software Interface driver;
• USB over IP driver;
• vDPA drivers;
• VFIO drivers;
• Virtio Host (VHOST) subsystem;
• Framebuffer layer;
• Watchdog drivers;
• Xen hypervisor drivers;
• 9P distributed file system;
• AFS file system;
• File systems infrastructure;
• BTRFS file…