CVE-2024-46847

In the Linux kernel, the following vulnerability has been resolved: mm: vmalloc: ensure vmap_block is initialised before adding to queue Commit 8c61291fd850 ("mm: fix incorrect vbq reference in purge_fragmented_block") extended the 'vmap_block' structure to contain a 'cpu' field which is set at allocation time to the id of the initialising CPU. When a new 'vmap_block' is being instantiated by new_vmap_block(), the partially initialised structure is added to the local 'vmap_block_queue' xarray before the 'cpu' field has been initialised. If another CPU is concurrently walking the xarray (e.g. via vm_unmap_aliases()), then it may perform an out-of-bounds access to the remote queue thanks to an uninitialised index. This has been observed as UBSAN errors in Android: | Internal error: UBSAN: array index out of bounds: 00000000f2005512 [#1] PREEMPT SMP | | Call trace: | purge_fragmented_block+0x204/0x21c | _vm_unmap_aliases+0x170/0x378 | vm_unmap_aliases+0x1c/0x28 | change_memory_common+0x1dc/0x26c | set_memory_ro+0x18/0x24 | module_enable_ro+0x98/0x238 | do_init_module+0x1b0/0x310 Move the initialisation of 'vb->cpu' in new_vmap_block() ahead of the addition to the xarray.

The Linux Kernel, the operating system core itself.

Security Fix(es):

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

ksmbd: fix potencial out-of-bounds when buffer offset is invalid

I found potencial out-of-bounds when buffer offset fields of a few requests is invalid. This patch set the minimum value of buffer offset field to ->Buffer offset to validate buffer length.(CVE-2024-26952)

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

ksmbd: fix slab-out-of-bounds in smb_strndup_from_utf16()

If ->NameOffset of smb2_create_req is smaller than Buffer offset of smb2_create_req, slab-out-of-bounds read can happen from smb2_open. This patch set the minimum value of the name offset to the buffer offset to validate name length of smb2_create_req().(CVE-2024-26954)

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

fpga: bridge: add owner module and take its refcount

The current implementation of the fpga bridge assumes that the low-level module registers a driver for the parent device and uses its owner pointer to take the module's refcount. This approach is problematic since it can lead to a null pointer dereference while attempting to get the bridge if the parent device does not have a driver.

To address this problem, add a module owner pointer to the fpga_bridge struct and use it to take the module's refcount. Modify the function for registering a bridge to take an additional owner module parameter and rename it to avoid conflicts. Use the old function name for a helper macro that automatically sets the module that registers the bridge as the owner. This ensures compatibility with existing low-level control modules and reduces the chances of registering a bridge without setting the owner.

Also, update the documentation to keep it consistent with the new interface for registering an fpga bridge.

Other changes: opportunistically move put_device() from __fpga_bridge_get() to fpga_bridge_get() and of_fpga_bridge_get() to improve code clarity since the bridge device is taken in these functions.(CVE-2024-36479)

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

blk-iocost: avoid out of bounds shift

UBSAN catches undefined behavior in blk-iocost, where sometimes iocg->delay is shifted right by a number that is too large, resulting in undefined behavior on some architectures.

[ 186.556576] ------------[ cut here ]------------ UBSAN: shift-out-of-bounds in block/blk-iocost.c:1366:23 shift exponent 64 is too large for 64-bit type 'u64' (aka 'unsigned long long') CPU: 16 PID: 0 Comm: swapper/16 Tainted: G S E N 6.9.0-0_fbk700_debug_rc2_kbuilder_0_gc85af715cac0 #1 Hardware name: Quanta Twin Lakes MP/Twin Lakes Passive MP, BIOS F09_3A23 12/08/2020 Call Trace: <IRQ> dump_stack_lvl+0x8f/0xe0 __ubsan_handle_shift_out_of_bounds+0x22c/0x280 iocg_kick_delay+0x30b/0x310 ioc_timer_fn+0x2fb/0x1f80 __run_timer_base+0x1b6/0x250 ...

Avoid that undefined behavior by simply taking the "delay = 0" branch if the shift is too large.

I am not sure what the symptoms of an undefined value delay will be, but I suspect it could be more than a little annoying to debug.(CVE-2024-36916)

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

fpga: manager: add owner module and take its refcount

The current implementation of the fpga manager assumes that the low-level module registers a driver for the parent device and uses its owner pointer to take the module's refcount. This approach is problematic since it can lead to a null pointer dereference while attempting to get the manager if the parent device does not have a driver.

To address this problem, add a module owner pointer to the fpga_manager struct and use it to take the module's refcount. Modify the functions for registering the manager to take an additional owner module parameter and rename them to avoid conflicts. Use…

In the Linux kernel, the following vulnerability has been resolved: mm: vmalloc: ensure vmap_block is initialised before adding to queue Commit 8c61291fd850 ("mm: fix incorrect vbq reference in purge_fragmented_block") extended the 'vmap_block' structure to contain a 'cpu' field which is set at allocation time to the id of the initialising CPU. When a new 'vmap_block' is being instantiated by new_vmap_block(), the partially initialised structure is added to the local 'vmap_block_queue' xarray before the 'cpu' field has been initialised. If another CPU is concurrently walking the xarray (e.g. via vm_unmap_aliases()), then it may perform an out-of-bounds access to the remote queue thanks to an uninitialised index. This has been observed as UBSAN errors in Android: | Internal error: UBSAN: array index out of bounds: 00000000f2005512 [#1] PREEMPT SMP | | Call trace: | purge_fragmented_block+0x204/0x21c | _vm_unmap_aliases+0x170/0x378 | vm_unmap_aliases+0x1c/0x28 | change_memory_common+0x1dc/0x26c | set_memory_ro+0x18/0x24 | module_enable_ro+0x98/0x238 | do_init_module+0x1b0/0x310 Move the initialisation of 'vb->cpu' in new_vmap_block() ahead of the addition to the xarray.

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;
• User-Mode Linux (UML);
• x86 architecture;
• Block layer subsystem;
• Android drivers;
• ATM drivers;
• Drivers core;
• Ublk userspace block driver;
• Bluetooth drivers;
• Character device driver;
• Hardware crypto device drivers;
• Buffer Sharing and Synchronization framework;
• DMA engine subsystem;
• Qualcomm firmware drivers;
• GPIO subsystem;
• GPU drivers;
• HID subsystem;
• Hardware monitoring drivers;
• I2C subsystem;
• I3C subsystem;
• IIO subsystem;
• InfiniBand drivers;
• Input Device core drivers;
• Input Device (Miscellaneous) drivers;
• IOMMU subsystem;
• IRQ chip drivers;
• LED subsystem;
• Mailbox framework;
• Multiple devices driver;
• Media drivers;
• Fastrpc Driver;
• VMware VMCI Driver;
• MMC subsystem;
• Ethernet bonding driver;
• Network drivers;
• Mellanox network drivers;
• Microsoft Azure Network Adapter (MANA) driver;
• Near Field Communication (NFC) drivers;
• NVME drivers;
• Device tree and open firmware driver;
• Parport drivers;
• PCI subsystem;
• Pin controllers subsystem;
• x86 platform drivers;
• Power supply drivers;
• Remote Processor subsystem;
• S/390 drivers;
• SCSI subsystem;
• QCOM SoC drivers;
• SPI subsystem;
• Direct Digital Synthesis drivers;
• Thunderbolt and USB4 drivers;
• TTY drivers;
• UFS subsystem;
• Userspace I/O drivers;
• DesignWare USB3 driver;
• USB Gadget drivers;
• USB Host Controller drivers;
• USB Type-C Connector System Software Interface driver;
• USB over IP driver;
• Virtio Host (VHOST) subsystem;
• Framebuffer layer;
• Xen hypervisor drivers;
• File systems infrastructure;
• BTRFS file system;
• Ext4 file system;
• F2FS file system;
• JFS file system;
• Network file systems library;
• Network file system (NFS) client;
• Network file system (NFS) server daemon;
• NILFS2 file system;
• File system notification infrastructure;
• NTFS3 file system;
• Proc file system;
• SMB network file system;
• Tracing file system;
• Bitmap API;
• BPF subsystem;
• Memory Management;
• Objagg library;
• Perf events;
• Virtio network driver;
• VMware vSockets driver;
• KCM (Kernel Connection Multiplexor) sockets driver;
• Control group (cgroup);
• DMA mapping infrastructure;
• Locking primitives;
• Padata parallel execution mechanism;
• Scheduler infrastructure;
• Tracing infrastructure;
• Radix Tree data structure library;
• Kernel userspace event delivery library;
• KUnit for arithmetic overflow checks;
• Memory management;
• Bluetooth subsystem;
• Ethernet bridge;
• CAN network layer;
• Networking core;
• Ethtool driver;
• IPv4 networking;
• IPv6 networking;
• MAC80211 subsystem;
• Multipath TCP;
• Netfilter;
• Network traffic control;
• SCTP protocol;
• TIPC protocol;
• Wireless networking;
• AppArmor security module;
• Landlock security;
• SELinux security module;
• Simplified Mandatory Access Control Kernel framework;
• FireWire sound drivers;
• AMD SoC Alsa drivers;
• Texas InstrumentS Audio (ASoC/HDA) drivers;
• SoC Audio for Freescale CPUs drivers;
• Intel ASoC drivers;
• Amlogic Meson SoC drivers;
• SoC audio core drivers;
• USB sound devices;
• Real-Time Linux Analysis tools; (CVE-2024-46783, CVE-2024-44960, CVE-2024-46743, CVE-2024-45009, CVE-2024-43820, CVE-2024-43888, CVE-2024-45010, CVE-2024-43839, CVE-2024-42304, CVE-2024-43846, CVE-2024-42258, CVE-2024-45005, CVE-2024-46709, CVE-2024-46774, CVE-2024-43883, CVE-2024-43859, CVE-2024-46721, CVE-2024-44944, CVE-2024-43913, CVE-2024-43843, CVE-2024-43845, CVE-2024-45018, CVE-2024-43909,…

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;
• User-Mode Linux (UML);
• x86 architecture;
• Block layer subsystem;
• Android drivers;
• ATM drivers;
• Drivers core;
• Ublk userspace block driver;
• Bluetooth drivers;
• Character device driver;
• Hardware crypto device drivers;
• Buffer Sharing and Synchronization framework;
• DMA engine subsystem;
• Qualcomm firmware drivers;
• GPIO subsystem;
• GPU drivers;
• HID subsystem;
• Hardware monitoring drivers;
• I2C subsystem;
• I3C subsystem;
• IIO subsystem;
• InfiniBand drivers;
• Input Device core drivers;
• Input Device (Miscellaneous) drivers;
• IOMMU subsystem;
• IRQ chip drivers;
• LED subsystem;
• Mailbox framework;
• Multiple devices driver;
• Media drivers;
• Fastrpc Driver;
• VMware VMCI Driver;
• MMC subsystem;
• Ethernet bonding driver;
• Network drivers;
• Mellanox network drivers;
• Microsoft Azure Network Adapter (MANA) driver;
• Near Field Communication (NFC) drivers;
• NVME drivers;
• Device tree and open firmware driver;
• Parport drivers;
• PCI subsystem;
• Pin controllers subsystem;
• x86 platform drivers;
• Power supply drivers;
• Remote Processor subsystem;
• S/390 drivers;
• SCSI subsystem;
• QCOM SoC drivers;
• SPI subsystem;
• Direct Digital Synthesis drivers;
• Thunderbolt and USB4 drivers;
• TTY drivers;
• UFS subsystem;
• Userspace I/O drivers;
• DesignWare USB3 driver;
• USB Gadget drivers;
• USB Host Controller drivers;
• USB Type-C Connector System Software Interface driver;
• USB over IP driver;
• Virtio Host (VHOST) subsystem;
• Framebuffer layer;
• Xen hypervisor drivers;
• File systems infrastructure;
• BTRFS file system;
• Ext4 file system;
• F2FS file system;
• JFS file system;
• Network file systems library;
• Network file system (NFS) client;
• Network file system (NFS) server daemon;
• NILFS2 file system;
• File system notification infrastructure;
• NTFS3 file system;
• Proc file system;
• SMB network file system;
• Tracing file system;
• Bitmap API;
• BPF subsystem;
• Memory Management;
• Objagg library;
• Perf events;
• Virtio network driver;
• VMware vSockets driver;
• KCM (Kernel Connection Multiplexor) sockets driver;
• Control group (cgroup);
• DMA mapping infrastructure;
• Locking primitives;
• Padata parallel execution mechanism;
• Scheduler infrastructure;
• Tracing infrastructure;
• Radix Tree data structure library;
• Kernel userspace event delivery library;
• KUnit for arithmetic overflow checks;
• Memory management;
• Bluetooth subsystem;
• Ethernet bridge;
• CAN network layer;
• Networking core;
• Ethtool driver;
• IPv4 networking;
• IPv6 networking;
• MAC80211 subsystem;
• Multipath TCP;
• Netfilter;
• Network traffic control;
• SCTP protocol;
• TIPC protocol;
• Wireless networking;
• AppArmor security module;
• Landlock security;
• SELinux security module;
• Simplified Mandatory Access Control Kernel framework;
• FireWire sound drivers;
• AMD SoC Alsa drivers;
• Texas InstrumentS Audio (ASoC/HDA) drivers;
• SoC Audio for Freescale CPUs drivers;
• Intel ASoC drivers;
• Amlogic Meson SoC drivers;
• SoC audio core drivers;
• USB sound devices;
• Real-Time Linux Analysis tools; (CVE-2024-46783, CVE-2024-44960, CVE-2024-46743, CVE-2024-45009, CVE-2024-43820, CVE-2024-43888, CVE-2024-45010, CVE-2024-43839, CVE-2024-42304, CVE-2024-43846, CVE-2024-42258, CVE-2024-45005, CVE-2024-46709, CVE-2024-46774, CVE-2024-43883, CVE-2024-43859, CVE-2024-46721, CVE-2024-44944, CVE-2024-43913, CVE-2024-43843, CVE-2024-43845, CVE-2024-45018, CVE-2024-43909,…

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;
• User-Mode Linux (UML);
• x86 architecture;
• Block layer subsystem;
• Android drivers;
• ATM drivers;
• Drivers core;
• Ublk userspace block driver;
• Bluetooth drivers;
• Character device driver;
• Hardware crypto device drivers;
• Buffer Sharing and Synchronization framework;
• DMA engine subsystem;
• Qualcomm firmware drivers;
• GPIO subsystem;
• GPU drivers;
• HID subsystem;
• Hardware monitoring drivers;
• I2C subsystem;
• I3C subsystem;
• IIO subsystem;
• InfiniBand drivers;
• Input Device core drivers;
• Input Device (Miscellaneous) drivers;
• IOMMU subsystem;
• IRQ chip drivers;
• LED subsystem;
• Mailbox framework;
• Multiple devices driver;
• Media drivers;
• Fastrpc Driver;
• VMware VMCI Driver;
• MMC subsystem;
• Ethernet bonding driver;
• Network drivers;
• Mellanox network drivers;
• Microsoft Azure Network Adapter (MANA) driver;
• Near Field Communication (NFC) drivers;
• NVME drivers;
• Device tree and open firmware driver;
• Parport drivers;
• PCI subsystem;
• Pin controllers subsystem;
• x86 platform drivers;
• Power supply drivers;
• Remote Processor subsystem;
• S/390 drivers;
• SCSI subsystem;
• QCOM SoC drivers;
• SPI subsystem;
• Direct Digital Synthesis drivers;
• Thunderbolt and USB4 drivers;
• TTY drivers;
• UFS subsystem;
• Userspace I/O drivers;
• DesignWare USB3 driver;
• USB Gadget drivers;
• USB Host Controller drivers;
• USB Type-C Connector System Software Interface driver;
• USB over IP driver;
• Virtio Host (VHOST) subsystem;
• Framebuffer layer;
• Xen hypervisor drivers;
• File systems infrastructure;
• BTRFS file system;
• Ext4 file system;
• F2FS file system;
• JFS file system;
• Network file systems library;
• Network file system (NFS) client;
• Network file system (NFS) server daemon;
• NILFS2 file system;
• File system notification infrastructure;
• NTFS3 file system;
• Proc file system;
• SMB network file system;
• Tracing file system;
• Bitmap API;
• BPF subsystem;
• Memory Management;
• Objagg library;
• Perf events;
• Virtio network driver;
• VMware vSockets driver;
• KCM (Kernel Connection Multiplexor) sockets driver;
• Control group (cgroup);
• DMA mapping infrastructure;
• Locking primitives;
• Padata parallel execution mechanism;
• Scheduler infrastructure;
• Tracing infrastructure;
• Radix Tree data structure library;
• Kernel userspace event delivery library;
• KUnit for arithmetic overflow checks;
• Memory management;
• Bluetooth subsystem;
• Ethernet bridge;
• CAN network layer;
• Networking core;
• Ethtool driver;
• IPv4 networking;
• IPv6 networking;
• MAC80211 subsystem;
• Multipath TCP;
• Netfilter;
• Network traffic control;
• SCTP protocol;
• TIPC protocol;
• Wireless networking;
• AppArmor security module;
• Landlock security;
• SELinux security module;
• Simplified Mandatory Access Control Kernel framework;
• FireWire sound drivers;
• AMD SoC Alsa drivers;
• Texas InstrumentS Audio (ASoC/HDA) drivers;
• SoC Audio for Freescale CPUs drivers;
• Intel ASoC drivers;
• Amlogic Meson SoC drivers;
• SoC audio core drivers;
• USB sound devices;
• Real-Time Linux Analysis tools; (CVE-2024-43845, CVE-2024-42311, CVE-2024-46757, CVE-2024-46738, CVE-2024-44961, CVE-2024-44935, CVE-2024-46845, CVE-2024-46783, CVE-2024-42315, CVE-2023-52918, CVE-2024-46708, CVE-2024-44934, CVE-2024-42298, CVE-2024-46786, CVE-2024-46778, CVE-2024-44960, CVE-2024-42295, CVE-2024-43881, CVE-2024-44971, CVE-2024-43849, CVE-2024-43914, CVE-2024-44962, CVE-2024-43841,…

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;
• User-Mode Linux (UML);
• x86 architecture;
• Block layer subsystem;
• Android drivers;
• ATM drivers;
• Drivers core;
• Ublk userspace block driver;
• Bluetooth drivers;
• Character device driver;
• Hardware crypto device drivers;
• Buffer Sharing and Synchronization framework;
• DMA engine subsystem;
• Qualcomm firmware drivers;
• GPIO subsystem;
• GPU drivers;
• HID subsystem;
• Hardware monitoring drivers;
• I2C subsystem;
• I3C subsystem;
• IIO subsystem;
• InfiniBand drivers;
• Input Device core drivers;
• Input Device (Miscellaneous) drivers;
• IOMMU subsystem;
• IRQ chip drivers;
• LED subsystem;
• Mailbox framework;
• Multiple devices driver;
• Media drivers;
• Fastrpc Driver;
• VMware VMCI Driver;
• MMC subsystem;
• Ethernet bonding driver;
• Network drivers;
• Mellanox network drivers;
• Microsoft Azure Network Adapter (MANA) driver;
• Near Field Communication (NFC) drivers;
• NVME drivers;
• Device tree and open firmware driver;
• Parport drivers;
• PCI subsystem;
• Pin controllers subsystem;
• x86 platform drivers;
• Power supply drivers;
• Remote Processor subsystem;
• S/390 drivers;
• SCSI subsystem;
• QCOM SoC drivers;
• SPI subsystem;
• Direct Digital Synthesis drivers;
• Thunderbolt and USB4 drivers;
• TTY drivers;
• UFS subsystem;
• Userspace I/O drivers;
• DesignWare USB3 driver;
• USB Gadget drivers;
• USB Host Controller drivers;
• USB Type-C Connector System Software Interface driver;
• USB over IP driver;
• Virtio Host (VHOST) subsystem;
• Framebuffer layer;
• Xen hypervisor drivers;
• File systems infrastructure;
• BTRFS file system;
• Ext4 file system;
• F2FS file system;
• JFS file system;
• Network file systems library;
• Network file system (NFS) client;
• Network file system (NFS) server daemon;
• NILFS2 file system;
• File system notification infrastructure;
• NTFS3 file system;
• Proc file system;
• SMB network file system;
• Tracing file system;
• Bitmap API;
• BPF subsystem;
• Memory Management;
• Objagg library;
• Perf events;
• Virtio network driver;
• VMware vSockets driver;
• KCM (Kernel Connection Multiplexor) sockets driver;
• Control group (cgroup);
• DMA mapping infrastructure;
• Locking primitives;
• Padata parallel execution mechanism;
• Scheduler infrastructure;
• Tracing infrastructure;
• Radix Tree data structure library;
• Kernel userspace event delivery library;
• KUnit for arithmetic overflow checks;
• Memory management;
• Bluetooth subsystem;
• Ethernet bridge;
• CAN network layer;
• Networking core;
• Ethtool driver;
• IPv4 networking;
• IPv6 networking;
• MAC80211 subsystem;
• Multipath TCP;
• Netfilter;
• Network traffic control;
• SCTP protocol;
• TIPC protocol;
• Wireless networking;
• AppArmor security module;
• Landlock security;
• SELinux security module;
• Simplified Mandatory Access Control Kernel framework;
• FireWire sound drivers;
• AMD SoC Alsa drivers;
• Texas InstrumentS Audio (ASoC/HDA) drivers;
• SoC Audio for Freescale CPUs drivers;
• Intel ASoC drivers;
• Amlogic Meson SoC drivers;
• SoC audio core drivers;
• USB sound devices;
• Real-Time Linux Analysis tools; (CVE-2024-44979, CVE-2024-47658, CVE-2024-44970, CVE-2024-43913, CVE-2024-46816, CVE-2024-46738, CVE-2024-46777, CVE-2024-46730, CVE-2024-46811, CVE-2024-44954, CVE-2024-42317, CVE-2024-42279, CVE-2024-45002, CVE-2024-43826, CVE-2024-44967, CVE-2024-46721, CVE-2024-46763, CVE-2024-43856, CVE-2024-42284, CVE-2024-42289, CVE-2024-46806, CVE-2024-46776, CVE-2024-43843,…