CVE-2026-68118

In the Linux kernel, the following vulnerability has been resolved: tcp: challenge ACK for non-exact RST in SYN-RECEIVED The SYN-RECEIVED request-socket path in tcp_check_req() accepts an in-window RST without requiring SEG.SEQ to exactly match RCV.NXT. A non-exact RST therefore removes the request instead of eliciting a challenge ACK. RFC 9293 section 3.10.7.4 applies the RFC 5961 reset check in SYN-RECEIVED: an exact RST resets the connection, while a non-exact in-window RST must trigger a challenge ACK and be dropped. Apply that check before the ACK-field validation, following the RFC sequence-number, RST, then ACK processing order. Factor the per-netns challenge ACK quota out of tcp_send_challenge_ack() so request sockets can share it. Use the request socket's send_ack() callback and its own out-of-window ACK timestamp to send and rate-limit the response.

The Linux Kernel, the operating system core itself.

Security Fix(es):

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

seg6: separate dst_cache for input and output paths in seg6 lwtunnel

The seg6 lwtunnel uses a single dst_cache per encap route, shared between seg6_input_core() and seg6_output_core(). These two paths can perform the post-encap SID lookup in different routing contexts (e.g., ip rules matching on the ingress interface, or VRF table separation). Whichever path runs first populates the cache, and the other reuses it blindly, bypassing its own lookup.

Fix this by splitting the cache into cache_input and cache_output, so each path maintains its own cached dst independently.(CVE-2026-31668)

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

RDMA/rxe: Fix iova-to-va conversion for MR page sizes != PAGE_SIZE

The current implementation incorrectly handles memory regions (MRs) with page sizes different from the system PAGE_SIZE. The core issue is that rxe_set_page() is called with mr->page_size step increments, but the page_list stores individual struct page pointers, each representing PAGE_SIZE of memory.

ib_sg_to_page() has ensured that when i>=1 either a) SG[i-1].dma_end and SG[i].dma_addr are contiguous or b) SG[i-1].dma_end and SG[i].dma_addr are mr->page_size aligned.

This leads to incorrect iova-to-va conversion in scenarios:

1. page_size < PAGE_SIZE (e.g., MR: 4K, system: 64K): ibmr->iova = 0x181800 sg[0]: dma_addr=0x181800, len=0x800 sg[1]: dma_addr=0x173000, len=0x1000

   Access iova = 0x181800 + 0x810 = 0x182010 Expected VA: 0x173010 (second SG, offset 0x10) Before fix:

   • index = (0x182010 >> 12) - (0x181800 >> 12) = 1
   • page_offset = 0x182010 & 0xFFF = 0x10
   • xarray[1] stores system page base 0x170000
   • Resulting VA: 0x170000 + 0x10 = 0x170010 (wrong)

2. page_size > PAGE_SIZE (e.g., MR: 64K, system: 4K): ibmr->iova = 0x18f800 sg[0]: dma_addr=0x18f800, len=0x800 sg[1]: dma_addr=0x170000, len=0x1000

   Access iova = 0x18f800 + 0x810 = 0x190010 Expected VA: 0x170010 (second SG, offset 0x10) Before fix:

   • index = (0x190010 >> 16) - (0x18f800 >> 16) = 1
   • page_offset = 0x190010 & 0xFFFF = 0x10
   • xarray[1] stores system page for dma_addr 0x170000
   • Resulting VA: system page of 0x170000 + 0x10 = 0x170010 (wrong)

Yi Zhang reported a kernel panic[1] years ago related to this defect.

Solution:

1. Replace xarray with pre-allocated rxe_mr_page array for sequential indexing (all MR page indices are contiguous)
2. Each rxe_mr_page stores both struct page* and offset within the system page
3. Handle MR page_size != PAGE_SIZE relationships:
   • page_size > PAGE_SIZE: Split MR pages into multiple system pages
   • page_size <= PAGE_SIZE: Store offset within system page
4. Add boundary checks and compatibility validation

This ensures correct iova-to-va conversion regardless of MR page size and system PAGE_SIZE relationship, while improving performance through array-based sequential access.

Tests on 4K and 64K PAGE_SIZE hosts:

• rdma-core/pytests $ ./build/bin/run_tests.py --dev eth0_rxe
• blktest: $ TIMEOUT=30 QUICK_RUN=1 USE_RXE=1 NVMET_TRTYPES=rdma ./check nvme srp rnbd

[1] https://lore.kernel.org/all/CAHj4cs9XRqE25jyVw9rj9YugffLn5+f=1znaBEnu1usLOciD+g@mail.gmail.com/T/(CVE-2026-46325)

In the Linux kernel, compat_riscv_gpr_set() calls cregs_to_regs() unconditionally, even when user_regset_copyin() fails. Since cregs is an uninitialized stack variable, a copyin failure causes uninitialized stack data to be written into the target task's pt_regs, corrupting its register state and potentially leaking kernel stack contents. compat_restore_sigcontext() has the same issue: it calls cregs_to_regs() even when __copy_from_user() fails, leading to the same corruption of the signal-returning task's register state on…

The Linux Kernel, the operating system core itself.

Security Fix(es):

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

Bluetooth: hci_conn: Fix null ptr deref in hci_abort_conn()

hci_abort_conn() read hci_skb_event(hdev->sent_cmd) when a connection was pending, but hdev->sent_cmd can be NULL while req_status is still HCI_REQ_PEND, leading to a NULL pointer dereference and a general protection fault from the hci_rx_work() receive path.

Instead of inspecting hdev->sent_cmd, track the in-flight create connection command with a new per-connection HCI_CONN_CREATE flag and route all cancellation through hci_cancel_connect_sync(), which dispatches to a dedicated per-type cancel function. The create command is in exactly one of two states: still queued, or in flight. The cancel function holds cmd_sync_work_lock across the whole decision: the worker takes this lock to dequeue every entry, so while it is held a queued command cannot start running and an in-flight command cannot complete and let the next command become pending. This keeps the flag test and hci_cmd_sync_cancel() atomic with respect to the worker, so a queued command is simply dequeued, and an in-flight command owned by this connection is cancelled without the risk of cancelling an unrelated command that became pending in the meantime. CIS uses the same flag mechanism via HCI_CONN_CREATE_CIS but cannot be dequeued per-connection.

hci_acl_create_conn_sync() and hci_le_create_conn_sync() clear HCI_CONN_CREATE after the create command completes, but the command status handler can free conn via hci_conn_del() (for example when the controller rejects the connection) while the worker is still blocked on the connection complete event. Hold a reference on conn across the create command so the flag can be cleared without a use-after-free.(CVE-2026-64405)

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

fuse-uring: fix race between registration and connection abortion

This fixes this race:

• thread a: io_uring_enter -> register sqe -> fuse_uring_create_ring_ent -> allocate ent but doesn't grab queue_ref yet
• thread b: fuse_conn_destroy() -> fuse_chan_abort() -> fuse_uring_abort() is a no-op due to queue ref being 0
• thread a: grabs the queue_ref, queue_ref is now 1, rest of fuse_uring_do_register() logic executes
• thread b: fuse_chan_abort() returns, fuse_chan_wait_aborted() now runs and calls "wait_event(ring->stop_waitq, atomic_read(&ring->queue_refs) == 0);" The abort/unmount thread will hang indefinitely in unkillable state as nothing will decrement queue_refs or wake stop_waitq, and the ring, queue, and ent are leaked.

Fix this by checking fch->connected under fch->lock after the created ent has grabbed a ref count on the queue. This ensures that in the scenario above, it is guaranteed that we either release the queue ref and wake up stop_waitq (in case fuse_chan_wait_aborted() is already waiting) in fuse_uring_do_register() when we detect !fch->connected, or if the connection is aborted after the check, it is guaranteed that the async teardown worker will be running in the background cleaning up ents and decrementing the ent's ref on the queue, which will unblock the eventual queue and ring teardown.(CVE-2026-68095)

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

tcp: challenge ACK for non-exact RST in SYN-RECEIVED

The SYN-RECEIVED request-socket path in tcp_check_req() accepts an in-window RST without requiring SEG.SEQ to exactly match RCV.NXT. A non-exact RST therefore removes the request instead of eliciting a challenge ACK.

RFC 9293 section 3.10.7.4 applies the RFC 5961 reset check in SYN-RECEIVED: an exact RST resets the connection, while a non-exact in-window RST must trigger a challenge ACK and be dropped.

Apply that check before the ACK-field validation, following the RFC sequence-number, RST, then ACK processing…

In the Linux kernel, the following vulnerability has been resolved: tcp: challenge ACK for non-exact RST in SYN-RECEIVED The SYN-RECEIVED request-socket path in tcp_check_req() accepts an in-window RST without requiring SEG.SEQ to exactly match RCV.NXT. A non-exact RST therefore removes the request instead of eliciting a challenge ACK. RFC 9293 section 3.10.7.4 applies the RFC 5961 reset check in SYN-RECEIVED: an exact RST resets the connection, while a non-exact in-window RST must trigger a challenge ACK and be dropped. Apply that check before the ACK-field validation, following the RFC sequence-number, RST, then ACK processing order. Factor the per-netns challenge ACK quota out of tcp_send_challenge_ack() so request sockets can share it. Use the request socket's send_ack() callback and its own out-of-window ACK timestamp to send and rate-limit the response.

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

tcp: challenge ACK for non-exact RST in SYN-RECEIVED

The SYN-RECEIVED request-socket path in tcp_check_req() accepts an in-window RST without requiring SEG.SEQ to exactly match RCV.NXT. A non-exact RST therefore removes the request instead of eliciting a challenge ACK.

RFC 9293 section 3.10.7.4 applies the RFC 5961 reset check in SYN-RECEIVED: an exact RST resets the connection, while a non-exact in-window RST must trigger a challenge ACK and be dropped.

Apply that check before the ACK-field validation, following the RFC sequence-number, RST, then ACK processing order. Factor the per-netns challenge ACK quota out of tcp_send_challenge_ack() so request sockets can share it. Use the request socket's send_ack() callback and its own out-of-window ACK timestamp to send and rate-limit the response.

• Input: synaptics-rmi4 - bound the F30 keymap to the GPIO/LED count {CVE-2026-64276}
• media: av7110: prevent underflow in write_ts_to_decoder() {CVE-2023-54284}
• usb: usbtmc: check URB actual_length for interrupt-IN notifications {CVE-2026-63904}
• usb: usbfs: fix use-after-free of usb_device in usbdev_release() {CVE-2026-80824}
• HID: alps: fix use-after-free on input2 registration failure {CVE-2026-98501}
• scsi: lpfc: Fix ioremap issues in lpfc_sli4_pci_mem_setup() {CVE-2023-53754}
• net: atl1: fix soft lockup on out-of-range cmb_tpd_next_to_clean read {CVE-2026-98494}
• net: atl1e: fix soft lockup on out-of-range hw_next_to_clean read {CVE-2026-98488}
• net: atl1c: fix soft lockup on out-of-range tpd_cons read {CVE-2026-98489}
• net: ena: fix MMIO read buffer leak on probe failure {CVE-2026-98486}
• HID: wacom: Fix OOB write in wacom_hid_set_device_mode() {CVE-2026-63916}
• net/mlx5: E-Switch: fix use-after-free in mlx5_eswitch_termtbl_put {CVE-2026-98015}
• RDMA/srp: Do not call scsi_done() from srp_abort() {CVE-2023-52515}
• net: usb: kalmia: bound RX frame length in kalmia_rx_fixup() {CVE-2026-64351}
• dm: fix a buffer overflow in ioctl processing {CVE-2026-46294}
• ext4: fix dirtyclusters double decrement on fs shutdown {CVE-2026-45920}
• NFSv4/flexfiles: reject zero filehandle version count {CVE-2026-53392}
• btrfs: fix race when deleting free space root from the dirty cow roots list {CVE-2023-54067}
• libnvdimm/labels: Prevent integer overflow in __nd_label_validate() {CVE-2026-89559}
• nvdimm/btt: reject an arena whose nfree is below the lane count {CVE-2026-89965}
• NFSv4.2: fix LAYOUTSTATS send buffer exhaustion {CVE-2026-90103}
• vsock/vmci: fix UAF when peer resets connection during handshake {CVE-2026-64115}
• ip6: vti: Use ip6_tnl.net in vti6_siocdevprivate(). {CVE-2026-63921}
• net/sched: act_tunnel_key: Defer dst_release to RCU callback {CVE-2026-68377}
• RDMA/srp: fix heap information leak on a truncated SRP_CRED_REQ {CVE-2026-90307}
• ALSA: usbusx2y: validate URB actual_length in interrupt callback {CVE-2026-97929}
• ALSA: usbusx2y: fix in04_last array size mismatch with in04_buf {CVE-2026-97930}
• udf: Mark LVID buffer as uptodate before marking it dirty {CVE-2026-93140}
• PCI/proc: Use file_ns_capable() when checking config space read access {CVE-2026-93206}
• wifi: iwlwifi: mvm: validate TX_CMD response layout {CVE-2026-93793}
• smb: client: honor forceuid/forcegid when mapping SIDs to uid/gid {CVE-2026-97561}
• wifi: brcmfmac: fix P2P action frame handling without device vif {CVE-2026-90345}
• IB/isert: post the full-feature receive buffers after session registration {CVE-2026-90293}
• IB/isert: delay the final Login Response until the session is registered {CVE-2026-90294}
• NFSv4: remove callback IDR entry on client allocation failure {CVE-2026-90151}
• sunrpc: xprtsock: annotate shared socket callbacks with READ_ONCE/WRITE_ONCE {CVE-2026-90235}
• RDMA/core: Reject unregistering netdevs in ib_get_eth_speed {CVE-2026-98359}
• ipv6: mcast: use rcu_assign_pointer() for __rcu list updates {CVE-2026-98099}
• wifi: cfg80211: reject duplicate wiphy cipher suite entries {CVE-2026-97518}
• IB/iser: reject a remote invalidation of an unregistered direction {CVE-2026-98358}
• ext4: validate readdir offset before accessing dirent {CVE-2026-92499}
• mtd: part: reject MTDPART_OFS_RETAIN in mtd_add_partition() {CVE-2026-93048}
• misc: sgi-gru: remove interrupt-context page-table walks {CVE-2026-90383}
• ACPI: bus: Introduce acpi_bus_get_primary_device() {CVE-2026-93251}
• scsi: qla2xxx: Hold vport reference in qla24xx_report_id_acquisition() {CVE-2026-89861}
• smb: client: reject a tree connect response whose byte count is too small {CVE-2026-89631}
• tcp: clamp route advmss to TCP_MIN_MSS {CVE-2026-80847}
• fsnotify: Fix stale object mask after concurrent mark updates {CVE-2026-89595}
• smb: client: clear setuid/setgid bit on write with cifsacl/modefromsid/posix extensions {CVE-2026-89638}
• sunrpc: init…

• Input: synaptics-rmi4 - bound the F30 keymap to the GPIO/LED count {CVE-2026-64276}
• media: av7110: prevent underflow in write_ts_to_decoder() {CVE-2023-54284}
• usb: usbtmc: check URB actual_length for interrupt-IN notifications {CVE-2026-63904}
• usb: usbfs: fix use-after-free of usb_device in usbdev_release() {CVE-2026-80824}
• HID: alps: fix use-after-free on input2 registration failure {CVE-2026-98501}
• scsi: lpfc: Fix ioremap issues in lpfc_sli4_pci_mem_setup() {CVE-2023-53754}
• net: atl1: fix soft lockup on out-of-range cmb_tpd_next_to_clean read {CVE-2026-98494}
• net: atl1e: fix soft lockup on out-of-range hw_next_to_clean read {CVE-2026-98488}
• net: atl1c: fix soft lockup on out-of-range tpd_cons read {CVE-2026-98489}
• net: ena: fix MMIO read buffer leak on probe failure {CVE-2026-98486}
• HID: wacom: Fix OOB write in wacom_hid_set_device_mode() {CVE-2026-63916}
• net/mlx5: E-Switch: fix use-after-free in mlx5_eswitch_termtbl_put {CVE-2026-98015}
• RDMA/srp: Do not call scsi_done() from srp_abort() {CVE-2023-52515}
• net: usb: kalmia: bound RX frame length in kalmia_rx_fixup() {CVE-2026-64351}
• dm: fix a buffer overflow in ioctl processing {CVE-2026-46294}
• ext4: fix dirtyclusters double decrement on fs shutdown {CVE-2026-45920}
• NFSv4/flexfiles: reject zero filehandle version count {CVE-2026-53392}
• btrfs: fix race when deleting free space root from the dirty cow roots list {CVE-2023-54067}
• libnvdimm/labels: Prevent integer overflow in __nd_label_validate() {CVE-2026-89559}
• nvdimm/btt: reject an arena whose nfree is below the lane count {CVE-2026-89965}
• NFSv4.2: fix LAYOUTSTATS send buffer exhaustion {CVE-2026-90103}
• vsock/vmci: fix UAF when peer resets connection during handshake {CVE-2026-64115}
• ip6: vti: Use ip6_tnl.net in vti6_siocdevprivate(). {CVE-2026-63921}
• net/sched: act_tunnel_key: Defer dst_release to RCU callback {CVE-2026-68377}
• RDMA/srp: fix heap information leak on a truncated SRP_CRED_REQ {CVE-2026-90307}
• ALSA: usbusx2y: validate URB actual_length in interrupt callback {CVE-2026-97929}
• ALSA: usbusx2y: fix in04_last array size mismatch with in04_buf {CVE-2026-97930}
• udf: Mark LVID buffer as uptodate before marking it dirty {CVE-2026-93140}
• PCI/proc: Use file_ns_capable() when checking config space read access {CVE-2026-93206}
• wifi: iwlwifi: mvm: validate TX_CMD response layout {CVE-2026-93793}
• smb: client: honor forceuid/forcegid when mapping SIDs to uid/gid {CVE-2026-97561}
• wifi: brcmfmac: fix P2P action frame handling without device vif {CVE-2026-90345}
• IB/isert: post the full-feature receive buffers after session registration {CVE-2026-90293}
• IB/isert: delay the final Login Response until the session is registered {CVE-2026-90294}
• NFSv4: remove callback IDR entry on client allocation failure {CVE-2026-90151}
• sunrpc: xprtsock: annotate shared socket callbacks with READ_ONCE/WRITE_ONCE {CVE-2026-90235}
• RDMA/core: Reject unregistering netdevs in ib_get_eth_speed {CVE-2026-98359}
• ipv6: mcast: use rcu_assign_pointer() for __rcu list updates {CVE-2026-98099}
• wifi: cfg80211: reject duplicate wiphy cipher suite entries {CVE-2026-97518}
• IB/iser: reject a remote invalidation of an unregistered direction {CVE-2026-98358}
• ext4: validate readdir offset before accessing dirent {CVE-2026-92499}
• mtd: part: reject MTDPART_OFS_RETAIN in mtd_add_partition() {CVE-2026-93048}
• misc: sgi-gru: remove interrupt-context page-table walks {CVE-2026-90383}
• ACPI: bus: Introduce acpi_bus_get_primary_device() {CVE-2026-93251}
• scsi: qla2xxx: Hold vport reference in qla24xx_report_id_acquisition() {CVE-2026-89861}
• smb: client: reject a tree connect response whose byte count is too small {CVE-2026-89631}
• tcp: clamp route advmss to TCP_MIN_MSS {CVE-2026-80847}
• fsnotify: Fix stale object mask after concurrent mark updates {CVE-2026-89595}
• smb: client: clear setuid/setgid bit on write with cifsacl/modefromsid/posix extensions {CVE-2026-89638}
• sunrpc: init…

Upstream kernel 6.18.44 version fixes bugs and vulnerabilities. The kmod-xtables-addons, kmod-virtualbox, kmod-nvidia-current-wopengpu & drakx-installer-images packages have been updated to work with this new kernel.

Vanilla upstream kernel version 6.18.44 fixes vulnerabilities. For information about the vulnerabilities see the links.

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;
• OpenRISC architecture;
• PowerPC architecture;
• S390 architecture;
• x86 architecture;
• Block layer subsystem;
• Cryptographic API;
• Intel NPU Driver;
• Android drivers;
• Rados block device (RBD) driver;
• Bluetooth drivers;
• Hardware random number generator core;
• TPM device driver;
• CPU frequency scaling framework;
• Hardware crypto device drivers;
• DMA engine subsystem;
• FireWire subsystem;
• Arm Firmware Framework for ARMv8-A(FFA);
• GPIO subsystem;
• GPU drivers;
• HID subsystem;
• Hardware monitoring drivers;
• CoreSight HW tracing drivers;
• I2C subsystem;
• IIO ADC drivers;
• IIO subsystem;
• InfiniBand drivers;
• Input Device core drivers;
• Input Device (Mouse) drivers;
• IOMMU subsystem;
• Multiple devices driver;
• Media drivers;
• Multifunction device drivers;
• Fastrpc Driver;
• Amazon Nitro Secure Module driver;
• MMC subsystem;
• MTD block device drivers;
• Ethernet bonding driver;
• Network drivers;
• Mellanox network drivers;
• Texas Instruments network drivers;
• NTB driver;
• NVME drivers;
• NVMEM (Non Volatile Memory) drivers;
• Parport drivers;
• Pin controllers subsystem;
• x86 platform drivers;
• i.MX PM domains;
• System reset/shutdown drivers;
• PTP clock framework;
• Voltage and Current Regulator drivers;
• S/390 drivers;
• SCSI subsystem;
• SPI subsystem;
• Realtek RTL8723BS SDIO drivers;
• VME bus staging drivers;
• Thermal drivers;
• Thunderbolt and USB4 drivers;
• TTY drivers;
• DesignWare USB2 driver;
• USB Gadget drivers;
• USB Host Controller drivers;
• USB Dual Role (OTG-ready) Controller drivers;
• USB Serial drivers;
• USB Type-C Port Controller Manager driver;
• vDPA drivers;
• Virtio Host (VHOST) subsystem;
• Framebuffer layer;
• Watchdog drivers;
• 9P distributed file system;
• AFS file system;
• File systems infrastructure;
• BTRFS file system;
• Ceph distributed file system;
• EROFS file system;
• exFAT file system;
• F2FS file system;
• FUSE (File system in Userspace);
• Journaling layer for block devices (JBD2);
• Network file system (NFS) client;
• Network file system (NFS) server daemon;
• NTFS3 file system;
• OCFS2 file system;
• Proc file system;
• SMB network file system;
• Tracing file system;
• UDF file system;
• XFS file system;
• Key management;
• BPF subsystem;
• Control group (cgroup);
• Glob pattern matching library;
• MAC80211 subsystem;
• Mellanox drivers;
• Networking core;
• Network sockets;
• IPv6 networking;
• Bluetooth subsystem;
• Wireless networking;
• IPv4 networking;
• Netfilter;
• Network traffic control;
• SCTP protocol;
• TCP network protocol;
• XFRM subsystem;
• RDMA verbs API;
• io_uring subsystem;
• IPC subsystem;
• Audit subsystem;
• Kernel CPU control infrastructure;
• Perf events;
• Kernel exit() syscall;
• Kernel fork() syscall;
• Scheduler infrastructure;
• Signal handling mechanism;
• Timer subsystem;
• Tracing infrastructure;
• Resizable hashtable library;
• Memory management;
• 6LoWPAN network protocol;
• Asynchronous Transfer Mode (ATM) subsystem;
• B.A.T.M.A.N. meshing protocol;
• Ethernet bridge;
• CAN network layer;
• Ceph Core library;
• Ethtool driver;
• HSR network protocol;
• IEEE802154.4 network protocol;
• IUCV driver;
• KCM (Kernel Connection Multiplexor) sockets driver;
• IEEE 802.15.4 subsystem;
• Multipath TCP;
• Open vSwitch;
• Packet sockets;
• Phonet protocol;
• Qualcomm IPC Router (QRTR);
• RDS protocol;
• RxRPC session sockets;
• 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:

• ARM64 architecture;
• NVDIMM (Non-Volatile Memory Device) drivers;
• Handshake API;
• ARM32 architecture;
• MIPS architecture;
• OpenRISC architecture;
• PowerPC architecture;
• RISC-V architecture;
• S390 architecture;
• x86 architecture;
• Cryptographic API;
• Compute Acceleration Framework;
• Intel NPU Driver;
• ACPI drivers;
• Android drivers;
• Serial ATA and Parallel ATA drivers;
• Drivers core;
• Rados block device (RBD) driver;
• Ublk userspace block driver;
• Bluetooth drivers;
• Cdrom driver;
• Character device driver;
• TPM device driver;
• Data acquisition framework and drivers;
• Hardware crypto device drivers;
• CXL (Compute Express Link) drivers;
• DAX dirext access to differentiated memory framework;
• DIBS (Direct Internal Buffer Sharing) drivers;
• Buffer Sharing and Synchronization framework;
• DMA engine subsystem;
• DPLL subsystem;
• EDAC drivers;
• FireWire subsystem;
• Arm Firmware Framework for ARMv8-A(FFA);
• ARM SCMI message protocol;
• Intel Stratix 10 firmware drivers;
• FPGA Framework;
• GPIB drivers;
• 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;
• I3C subsystem;
• IIO subsystem;
• IIO ADC drivers;
• IIO Magnetometer sensors drivers;
• InfiniBand drivers;
• Input Device (Miscellaneous) 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;
• Texas Instruments network drivers;
• MediaTek network drivers;
• NTB driver;
• NVME drivers;
• Device tree and open firmware driver;
• Operating Performance Points (OPP) driver;
• PCI subsystem;
• Pin controllers subsystem;
• x86 platform drivers;
• i.MX PM domains;
• MediaTek PM domains;
• Power supply drivers;
• PTP clock framework;
• RapidIO drivers;
• Voltage and Current Regulator drivers;
• Remote Processor subsystem;
• MPAM driver;
• Reset controller framework;
• Real Time Clock drivers;
• S/390 drivers;
• SCSI subsystem;
• Xilinx SoC drivers;
• SoundWire subsystem;
• SPI subsystem;
• Media staging drivers;
• Media Oriented Systems Transport (MOST) driver;
• NVIDIA Tegra embedded controller (NVEC) staging driver;
• Realtek RTL8723BS SDIO drivers;
• TTY drivers;
• UFS subsystem;
• USB DSL drivers;
• USB core drivers;
• DesignWare USB3 driver;
• USB Gadget drivers;
• USB Host Controller drivers;
• USB Dual Role (OTG-ready) Controller drivers;
• USB Serial drivers;
• vDPA drivers;
• VFIO drivers;
• Virtio Host (VHOST) subsystem;
• Framebuffer layer;
• Virtio drivers;
• Watchdog drivers;
• Xen hypervisor drivers;
• 9P distributed file system;
• AFS file system;
• File systems infrastructure;
• BTRFS file system;
• Ceph distributed file system;
• Ext4 file system;
• F2FS file system;
• FUSE (File system in Userspace);
• Journaling layer for block devices (JBD2);
• Network file systems library;
• Network…

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:

• ARM64 architecture;
• NVDIMM (Non-Volatile Memory Device) drivers;
• Handshake API;
• ARM32 architecture;
• MIPS architecture;
• OpenRISC architecture;
• PowerPC architecture;
• RISC-V architecture;
• S390 architecture;
• x86 architecture;
• Cryptographic API;
• Compute Acceleration Framework;
• Intel NPU Driver;
• ACPI drivers;
• Android drivers;
• Serial ATA and Parallel ATA drivers;
• Drivers core;
• Rados block device (RBD) driver;
• Ublk userspace block driver;
• Bluetooth drivers;
• Cdrom driver;
• Character device driver;
• TPM device driver;
• Data acquisition framework and drivers;
• Hardware crypto device drivers;
• CXL (Compute Express Link) drivers;
• DAX dirext access to differentiated memory framework;
• DIBS (Direct Internal Buffer Sharing) drivers;
• Buffer Sharing and Synchronization framework;
• DMA engine subsystem;
• DPLL subsystem;
• EDAC drivers;
• FireWire subsystem;
• Arm Firmware Framework for ARMv8-A(FFA);
• ARM SCMI message protocol;
• Intel Stratix 10 firmware drivers;
• FPGA Framework;
• GPIB drivers;
• 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;
• I3C subsystem;
• IIO subsystem;
• IIO ADC drivers;
• IIO Magnetometer sensors drivers;
• InfiniBand drivers;
• Input Device (Miscellaneous) 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;
• Texas Instruments network drivers;
• MediaTek network drivers;
• NTB driver;
• NVME drivers;
• Device tree and open firmware driver;
• Operating Performance Points (OPP) driver;
• PCI subsystem;
• Pin controllers subsystem;
• x86 platform drivers;
• i.MX PM domains;
• MediaTek PM domains;
• Power supply drivers;
• PTP clock framework;
• RapidIO drivers;
• Voltage and Current Regulator drivers;
• Remote Processor subsystem;
• MPAM driver;
• Reset controller framework;
• Real Time Clock drivers;
• S/390 drivers;
• SCSI subsystem;
• Xilinx SoC drivers;
• SoundWire subsystem;
• SPI subsystem;
• Media staging drivers;
• Media Oriented Systems Transport (MOST) driver;
• NVIDIA Tegra embedded controller (NVEC) staging driver;
• Realtek RTL8723BS SDIO drivers;
• TTY drivers;
• UFS subsystem;
• USB DSL drivers;
• USB core drivers;
• DesignWare USB3 driver;
• USB Gadget drivers;
• USB Host Controller drivers;
• USB Dual Role (OTG-ready) Controller drivers;
• USB Serial drivers;
• vDPA drivers;
• VFIO drivers;
• Virtio Host (VHOST) subsystem;
• Framebuffer layer;
• Virtio drivers;
• Watchdog drivers;
• Xen hypervisor drivers;
• 9P distributed file system;
• AFS file system;
• File systems infrastructure;
• BTRFS file system;
• Ceph distributed file system;
• Ext4 file system;
• F2FS file system;
• FUSE (File system in Userspace);
• Journaling layer for block devices (JBD2);
• Network file systems library;
• Network…

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:

• ARM64 architecture;
• NVDIMM (Non-Volatile Memory Device) drivers;
• Handshake API;
• ARM32 architecture;
• MIPS architecture;
• OpenRISC architecture;
• PowerPC architecture;
• RISC-V architecture;
• S390 architecture;
• x86 architecture;
• Cryptographic API;
• Compute Acceleration Framework;
• Intel NPU Driver;
• ACPI drivers;
• Android drivers;
• Serial ATA and Parallel ATA drivers;
• Drivers core;
• Rados block device (RBD) driver;
• Ublk userspace block driver;
• Bluetooth drivers;
• Cdrom driver;
• Character device driver;
• TPM device driver;
• Data acquisition framework and drivers;
• Hardware crypto device drivers;
• CXL (Compute Express Link) drivers;
• DAX dirext access to differentiated memory framework;
• DIBS (Direct Internal Buffer Sharing) drivers;
• Buffer Sharing and Synchronization framework;
• DMA engine subsystem;
• DPLL subsystem;
• EDAC drivers;
• FireWire subsystem;
• Arm Firmware Framework for ARMv8-A(FFA);
• ARM SCMI message protocol;
• Intel Stratix 10 firmware drivers;
• FPGA Framework;
• GPIB drivers;
• 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;
• I3C subsystem;
• IIO subsystem;
• IIO ADC drivers;
• IIO Magnetometer sensors drivers;
• InfiniBand drivers;
• Input Device (Miscellaneous) 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;
• Texas Instruments network drivers;
• MediaTek network drivers;
• NTB driver;
• NVME drivers;
• Device tree and open firmware driver;
• Operating Performance Points (OPP) driver;
• PCI subsystem;
• Pin controllers subsystem;
• x86 platform drivers;
• i.MX PM domains;
• MediaTek PM domains;
• Power supply drivers;
• PTP clock framework;
• RapidIO drivers;
• Voltage and Current Regulator drivers;
• Remote Processor subsystem;
• MPAM driver;
• Reset controller framework;
• Real Time Clock drivers;
• S/390 drivers;
• SCSI subsystem;
• Xilinx SoC drivers;
• SoundWire subsystem;
• SPI subsystem;
• Media staging drivers;
• Media Oriented Systems Transport (MOST) driver;
• NVIDIA Tegra embedded controller (NVEC) staging driver;
• Realtek RTL8723BS SDIO drivers;
• TTY drivers;
• UFS subsystem;
• USB DSL drivers;
• USB core drivers;
• DesignWare USB3 driver;
• USB Gadget drivers;
• USB Host Controller drivers;
• USB Dual Role (OTG-ready) Controller drivers;
• USB Serial drivers;
• vDPA drivers;
• VFIO drivers;
• Virtio Host (VHOST) subsystem;
• Framebuffer layer;
• Virtio drivers;
• Watchdog drivers;
• Xen hypervisor drivers;
• 9P distributed file system;
• AFS file system;
• File systems infrastructure;
• BTRFS file system;
• Ceph distributed file system;
• Ext4 file system;
• F2FS file system;
• FUSE (File system in Userspace);
• Journaling layer for block devices (JBD2);
• Network file systems library;
• Network…

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:

• ARM64 architecture;
• NVDIMM (Non-Volatile Memory Device) drivers;
• Handshake API;
• ARM32 architecture;
• MIPS architecture;
• OpenRISC architecture;
• PowerPC architecture;
• RISC-V architecture;
• S390 architecture;
• x86 architecture;
• Cryptographic API;
• Compute Acceleration Framework;
• 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;
• Ublk userspace block driver;
• Bluetooth drivers;
• Cdrom driver;
• Character device driver;
• TPM device driver;
• Data acquisition framework and drivers;
• Hardware crypto device drivers;
• CXL (Compute Express Link) drivers;
• DAX dirext access to differentiated memory framework;
• DIBS (Direct Internal Buffer Sharing) drivers;
• Buffer Sharing and Synchronization framework;
• DMA engine subsystem;
• DPLL subsystem;
• EDAC drivers;
• FireWire subsystem;
• Arm Firmware Framework for ARMv8-A(FFA);
• ARM SCMI message protocol;
• Intel Stratix 10 firmware drivers;
• FPGA Framework;
• GPIB drivers;
• 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;
• I3C subsystem;
• IIO subsystem;
• IIO ADC drivers;
• IIO Magnetometer sensors drivers;
• InfiniBand drivers;
• Input Device (Miscellaneous) 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;
• Texas Instruments network drivers;
• MediaTek network drivers;
• NTB driver;
• NVME drivers;
• Device tree and open firmware driver;
• Operating Performance Points (OPP) driver;
• PCI subsystem;
• Pin controllers subsystem;
• x86 platform drivers;
• i.MX PM domains;
• MediaTek PM domains;
• Power supply drivers;
• PTP clock framework;
• RapidIO drivers;
• Voltage and Current Regulator drivers;
• Remote Processor subsystem;
• MPAM driver;
• Reset controller framework;
• Real Time Clock drivers;
• S/390 drivers;
• SCSI subsystem;
• Xilinx SoC drivers;
• SoundWire subsystem;
• SPI subsystem;
• Media staging drivers;
• Media Oriented Systems Transport (MOST) driver;
• NVIDIA Tegra embedded controller (NVEC) staging driver;
• Realtek RTL8723BS SDIO drivers;
• TCM subsystem;
• TTY drivers;
• UFS subsystem;
• USB DSL drivers;
• USB core drivers;
• DesignWare USB3 driver;
• USB Gadget drivers;
• USB Host Controller drivers;
• USB Dual Role (OTG-ready) Controller drivers;
• USB Serial drivers;
• vDPA drivers;
• VFIO drivers;
• Virtio Host (VHOST) subsystem;
• Framebuffer layer;
• Virtio drivers;
• Watchdog drivers;
• Xen hypervisor drivers;
• 9P distributed file system;
• AFS file system;
• File systems infrastructure;
• BTRFS file system;
• Ceph distributed file system;
• Ext4 file system;
• F2FS file system;
• FUSE (File system in Userspace);
• Journaling layer…

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:

• ARM64 architecture;
• NVDIMM (Non-Volatile Memory Device) drivers;
• Handshake API;
• ARM32 architecture;
• MIPS architecture;
• OpenRISC architecture;
• PowerPC architecture;
• RISC-V architecture;
• S390 architecture;
• x86 architecture;
• Cryptographic API;
• Compute Acceleration Framework;
• 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;
• Ublk userspace block driver;
• Bluetooth drivers;
• Cdrom driver;
• Character device driver;
• TPM device driver;
• Data acquisition framework and drivers;
• Hardware crypto device drivers;
• CXL (Compute Express Link) drivers;
• DAX dirext access to differentiated memory framework;
• DIBS (Direct Internal Buffer Sharing) drivers;
• Buffer Sharing and Synchronization framework;
• DMA engine subsystem;
• DPLL subsystem;
• EDAC drivers;
• FireWire subsystem;
• Arm Firmware Framework for ARMv8-A(FFA);
• ARM SCMI message protocol;
• Intel Stratix 10 firmware drivers;
• FPGA Framework;
• GPIB drivers;
• 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;
• I3C subsystem;
• IIO subsystem;
• IIO ADC drivers;
• IIO Magnetometer sensors drivers;
• InfiniBand drivers;
• Input Device (Miscellaneous) 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;
• Texas Instruments network drivers;
• MediaTek network drivers;
• NTB driver;
• NVME drivers;
• Device tree and open firmware driver;
• Operating Performance Points (OPP) driver;
• PCI subsystem;
• Pin controllers subsystem;
• x86 platform drivers;
• i.MX PM domains;
• MediaTek PM domains;
• Power supply drivers;
• PTP clock framework;
• RapidIO drivers;
• Voltage and Current Regulator drivers;
• Remote Processor subsystem;
• MPAM driver;
• Reset controller framework;
• Real Time Clock drivers;
• S/390 drivers;
• SCSI subsystem;
• Xilinx SoC drivers;
• SoundWire subsystem;
• SPI subsystem;
• Media staging drivers;
• Media Oriented Systems Transport (MOST) driver;
• NVIDIA Tegra embedded controller (NVEC) staging driver;
• Realtek RTL8723BS SDIO drivers;
• TCM subsystem;
• TTY drivers;
• UFS subsystem;
• USB DSL drivers;
• USB core drivers;
• DesignWare USB3 driver;
• USB Gadget drivers;
• USB Host Controller drivers;
• USB Dual Role (OTG-ready) Controller drivers;
• USB Serial drivers;
• vDPA drivers;
• VFIO drivers;
• Virtio Host (VHOST) subsystem;
• Framebuffer layer;
• Virtio drivers;
• Watchdog drivers;
• Xen hypervisor drivers;
• 9P distributed file system;
• AFS file system;
• File systems infrastructure;
• BTRFS file system;
• Ceph distributed file system;
• Ext4 file system;
• F2FS file system;
• FUSE (File system in Userspace);
• Journaling layer…

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:

• ARM64 architecture;
• NVDIMM (Non-Volatile Memory Device) drivers;
• Handshake API;
• ARM32 architecture;
• MIPS architecture;
• OpenRISC architecture;
• PowerPC architecture;
• RISC-V architecture;
• S390 architecture;
• x86 architecture;
• Cryptographic API;
• Compute Acceleration Framework;
• Intel NPU Driver;
• ACPI drivers;
• Android drivers;
• Serial ATA and Parallel ATA drivers;
• Drivers core;
• Rados block device (RBD) driver;
• Ublk userspace block driver;
• Bluetooth drivers;
• Cdrom driver;
• Character device driver;
• TPM device driver;
• Data acquisition framework and drivers;
• Hardware crypto device drivers;
• CXL (Compute Express Link) drivers;
• DAX dirext access to differentiated memory framework;
• DIBS (Direct Internal Buffer Sharing) drivers;
• Buffer Sharing and Synchronization framework;
• DMA engine subsystem;
• DPLL subsystem;
• EDAC drivers;
• FireWire subsystem;
• Arm Firmware Framework for ARMv8-A(FFA);
• ARM SCMI message protocol;
• Intel Stratix 10 firmware drivers;
• FPGA Framework;
• GPIB drivers;
• 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;
• I3C subsystem;
• IIO subsystem;
• IIO ADC drivers;
• IIO Magnetometer sensors drivers;
• InfiniBand drivers;
• Input Device (Miscellaneous) 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;
• Texas Instruments network drivers;
• MediaTek network drivers;
• NTB driver;
• NVME drivers;
• Device tree and open firmware driver;
• Operating Performance Points (OPP) driver;
• PCI subsystem;
• Pin controllers subsystem;
• x86 platform drivers;
• i.MX PM domains;
• MediaTek PM domains;
• Power supply drivers;
• PTP clock framework;
• RapidIO drivers;
• Voltage and Current Regulator drivers;
• Remote Processor subsystem;
• MPAM driver;
• Reset controller framework;
• Real Time Clock drivers;
• S/390 drivers;
• SCSI subsystem;
• Xilinx SoC drivers;
• SoundWire subsystem;
• SPI subsystem;
• Media staging drivers;
• Media Oriented Systems Transport (MOST) driver;
• NVIDIA Tegra embedded controller (NVEC) staging driver;
• Realtek RTL8723BS SDIO drivers;
• TTY drivers;
• UFS subsystem;
• USB DSL drivers;
• USB core drivers;
• DesignWare USB3 driver;
• USB Gadget drivers;
• USB Host Controller drivers;
• USB Dual Role (OTG-ready) Controller drivers;
• USB Serial drivers;
• vDPA drivers;
• VFIO drivers;
• Virtio Host (VHOST) subsystem;
• Framebuffer layer;
• Virtio drivers;
• Watchdog drivers;
• Xen hypervisor drivers;
• 9P distributed file system;
• AFS file system;
• File systems infrastructure;
• BTRFS file system;
• Ceph distributed file system;
• Ext4 file system;
• F2FS file system;
• FUSE (File system in Userspace);
• Journaling layer for block devices (JBD2);
• Network file systems library;
• Network…

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:

• ARM64 architecture;
• NVDIMM (Non-Volatile Memory Device) drivers;
• Handshake API;
• ARM32 architecture;
• MIPS architecture;
• OpenRISC architecture;
• PowerPC architecture;
• RISC-V architecture;
• S390 architecture;
• x86 architecture;
• Cryptographic API;
• Compute Acceleration Framework;
• 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;
• Ublk userspace block driver;
• Bluetooth drivers;
• Cdrom driver;
• Character device driver;
• TPM device driver;
• Data acquisition framework and drivers;
• Hardware crypto device drivers;
• CXL (Compute Express Link) drivers;
• DAX dirext access to differentiated memory framework;
• DIBS (Direct Internal Buffer Sharing) drivers;
• Buffer Sharing and Synchronization framework;
• DMA engine subsystem;
• DPLL subsystem;
• EDAC drivers;
• FireWire subsystem;
• Arm Firmware Framework for ARMv8-A(FFA);
• ARM SCMI message protocol;
• Intel Stratix 10 firmware drivers;
• FPGA Framework;
• GPIB drivers;
• 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;
• I3C subsystem;
• IIO subsystem;
• IIO ADC drivers;
• IIO Magnetometer sensors drivers;
• InfiniBand drivers;
• Input Device (Miscellaneous) 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;
• Texas Instruments network drivers;
• MediaTek network drivers;
• NTB driver;
• NVME drivers;
• Device tree and open firmware driver;
• Operating Performance Points (OPP) driver;
• PCI subsystem;
• Pin controllers subsystem;
• x86 platform drivers;
• i.MX PM domains;
• MediaTek PM domains;
• Power supply drivers;
• PTP clock framework;
• RapidIO drivers;
• Voltage and Current Regulator drivers;
• Remote Processor subsystem;
• MPAM driver;
• Reset controller framework;
• Real Time Clock drivers;
• S/390 drivers;
• SCSI subsystem;
• Xilinx SoC drivers;
• SoundWire subsystem;
• SPI subsystem;
• Media staging drivers;
• Media Oriented Systems Transport (MOST) driver;
• NVIDIA Tegra embedded controller (NVEC) staging driver;
• Realtek RTL8723BS SDIO drivers;
• TCM subsystem;
• TTY drivers;
• UFS subsystem;
• USB DSL drivers;
• USB core drivers;
• DesignWare USB3 driver;
• USB Gadget drivers;
• USB Host Controller drivers;
• USB Dual Role (OTG-ready) Controller drivers;
• USB Serial drivers;
• vDPA drivers;
• VFIO drivers;
• Virtio Host (VHOST) subsystem;
• Framebuffer layer;
• Virtio drivers;
• Watchdog drivers;
• Xen hypervisor drivers;
• 9P distributed file system;
• AFS file system;
• File systems infrastructure;
• BTRFS file system;
• Ceph distributed file system;
• Ext4 file system;
• F2FS file system;
• FUSE (File system in Userspace);
• Journaling layer…