CVE-2024-41030

The Linux Kernel, the operating system core itself.

Security Fix(es):

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

ipvlan: Dont Use skb->sk in ipvlan_process_v{4,6}_outbound

Raw packet from PF_PACKET socket ontop of an IPv6-backed ipvlan device will hit WARN_ON_ONCE() in sk_mc_loop() through sch_direct_xmit() path.

WARNING: CPU: 2 PID: 0 at net/core/sock.c:775 sk_mc_loop+0x2d/0x70 Modules linked in: sch_netem ipvlan rfkill cirrus drm_shmem_helper sg drm_kms_helper CPU: 2 PID: 0 Comm: swapper/2 Kdump: loaded Not tainted 6.9.0+ #279 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014 RIP: 0010:sk_mc_loop+0x2d/0x70 Code: fa 0f 1f 44 00 00 65 0f b7 15 f7 96 a3 4f 31 c0 66 85 d2 75 26 48 85 ff 74 1c RSP: 0018:ffffa9584015cd78 EFLAGS: 00010212 RAX: 0000000000000011 RBX: ffff91e585793e00 RCX: 0000000002c6a001 RDX: 0000000000000000 RSI: 0000000000000040 RDI: ffff91e589c0f000 RBP: ffff91e5855bd100 R08: 0000000000000000 R09: 3d00545216f43d00 R10: ffff91e584fdcc50 R11: 00000060dd8616f4 R12: ffff91e58132d000 R13: ffff91e584fdcc68 R14: ffff91e5869ce800 R15: ffff91e589c0f000 FS: 0000000000000000(0000) GS:ffff91e898100000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f788f7c44c0 CR3: 0000000008e1a000 CR4: 00000000000006f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <IRQ> ? __warn (kernel/panic.c:693) ? sk_mc_loop (net/core/sock.c:760) ? report_bug (lib/bug.c:201 lib/bug.c:219) ? handle_bug (arch/x86/kernel/traps.c:239) ? exc_invalid_op (arch/x86/kernel/traps.c:260 (discriminator 1)) ? asm_exc_invalid_op (./arch/x86/include/asm/idtentry.h:621) ? sk_mc_loop (net/core/sock.c:760) ip6_finish_output2 (net/ipv6/ip6_output.c:83 (discriminator 1)) ? nf_hook_slow (net/netfilter/core.c:626) ip6_finish_output (net/ipv6/ip6_output.c:222) ? __pfx_ip6_finish_output (net/ipv6/ip6_output.c:215) ipvlan_xmit_mode_l3 (drivers/net/ipvlan/ipvlan_core.c:602) ipvlan ipvlan_start_xmit (drivers/net/ipvlan/ipvlan_main.c:226) ipvlan dev_hard_start_xmit (net/core/dev.c:3594) sch_direct_xmit (net/sched/sch_generic.c:343) __qdisc_run (net/sched/sch_generic.c:416) net_tx_action (net/core/dev.c:5286) handle_softirqs (kernel/softirq.c:555) __irq_exit_rcu (kernel/softirq.c:589) sysvec_apic_timer_interrupt (arch/x86/kernel/apic/apic.c:1043)

The warning triggers as this: packet_sendmsg packet_snd //skb->sk is packet sk __dev_queue_xmit __dev_xmit_skb //q->enqueue is not NULL __qdisc_run sch_direct_xmit dev_hard_start_xmit ipvlan_start_xmit ipvlan_xmit_mode_l3 //l3 mode ipvlan_process_outbound //vepa flag ipvlan_process_v6_outbound ip6_local_out __ip6_finish_output ip6_finish_output2 //multicast packet sk_mc_loop //sk->sk_family is AF_PACKET

Call ip{6}_local_out() with NULL sk in ipvlan as other tunnels to fix this.(CVE-2024-33621)

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

f2fs: compress: don't allow unaligned truncation on released compress inode

f2fs image may be corrupted after below testcase:

• mkfs.f2fs -O extra_attr,compression -f /dev/vdb
• mount /dev/vdb /mnt/f2fs
• touch /mnt/f2fs/file
• f2fs_io setflags compression /mnt/f2fs/file
• dd if=/dev/zero of=/mnt/f2fs/file bs=4k count=4
• f2fs_io release_cblocks /mnt/f2fs/file
• truncate -s 8192 /mnt/f2fs/file
• umount /mnt/f2fs
• fsck.f2fs /dev/vdb

[ASSERT] (fsck_chk_inode_blk:1256) --> ino: 0x5 has i_blocks: 0x00000002, but has 0x3 blocks [FSCK] valid_block_count matching with CP [Fail] [0x4, 0x5] [FSCK] other corrupted bugs …

The Linux Kernel, the operating system core itself.

Security Fix(es):

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

ALSA: usb-audio: Stop parsing channels bits when all channels are found.

If a usb audio device sets more bits than the amount of channels it could write outside of the map array.(CVE-2024-27436)

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

usb: gadget: f_fs: Fix race between aio_cancel() and AIO request complete

FFS based applications can utilize the aio_cancel() callback to dequeue pending USB requests submitted to the UDC. There is a scenario where the FFS application issues an AIO cancel call, while the UDC is handling a soft disconnect. For a DWC3 based implementation, the callstack looks like the following:

DWC3 Gadget                               FFS Application

dwc3_gadget_soft_disconnect() ... --> dwc3_stop_active_transfers() --> dwc3_gadget_giveback(-ESHUTDOWN) --> ffs_epfile_async_io_complete() ffs_aio_cancel() --> usb_ep_free_request() --> usb_ep_dequeue()

There is currently no locking implemented between the AIO completion handler and AIO cancel, so the issue occurs if the completion routine is running in parallel to an AIO cancel call coming from the FFS application. As the completion call frees the USB request (io_data->req) the FFS application is also referencing it for the usb_ep_dequeue() call. This can lead to accessing a stale/hanging pointer.

commit b566d38857fc ("usb: gadget: f_fs: use io_data->status consistently") relocated the usb_ep_free_request() into ffs_epfile_async_io_complete(). However, in order to properly implement locking to mitigate this issue, the spinlock can't be added to ffs_epfile_async_io_complete(), as usb_ep_dequeue() (if successfully dequeuing a USB request) will call the function driver's completion handler in the same context. Hence, leading into a deadlock.

Fix this issue by moving the usb_ep_free_request() back to ffs_user_copy_worker(), and ensuring that it explicitly sets io_data->req to NULL after freeing it within the ffs->eps_lock. This resolves the race condition above, as the ffs_aio_cancel() routine will not continue attempting to dequeue a request that has already been freed, or the ffs_user_copy_work() not freeing the USB request until the AIO cancel is done referencing it.

This fix depends on commit b566d38857fc ("usb: gadget: f_fs: use io_data->status consistently")(CVE-2024-36894)

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

scsi: bfa: Ensure the copied buf is NUL terminated

Currently, we allocate a nbytes-sized kernel buffer and copy nbytes from userspace to that buffer. Later, we use sscanf on this buffer but we don't ensure that the string is terminated inside the buffer, this can lead to OOB read when using sscanf. Fix this issue by using memdup_user_nul instead of memdup_user.(CVE-2024-38560)

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

enic: Validate length of nl attributes in enic_set_vf_port

enic_set_vf_port assumes that the nl attribute IFLA_PORT_PROFILE is of length PORT_PROFILE_MAX and that the nl attributes IFLA_PORT_INSTANCE_UUID, IFLA_PORT_HOST_UUID are of length PORT_UUID_MAX. These attributes are validated (in the function do_setlink in rtnetlink.c) using the nla_policy ifla_port_policy. The policy defines IFLA_PORT_PROFILE as NLA_STRING, IFLA_PORT_INSTANCE_UUID as NLA_BINARY and IFLA_PORT_HOST_UUID as NLA_STRING. That means that the length validation using the policy is for the max size of the attributes and not on exact size so the length of these attributes might be less than the sizes that enic_set_vf_port expects. This might cause an out of bands read access in the memcpys of the data of these attributes in enic_set_vf_port.(CVE-2024-38659)

In the Linux kernel,…

The Linux Kernel, the operating system core itself.

Security Fix(es):

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

ALSA: usb-audio: Stop parsing channels bits when all channels are found.

If a usb audio device sets more bits than the amount of channels it could write outside of the map array.(CVE-2024-27436)

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

usb: gadget: f_fs: Fix race between aio_cancel() and AIO request complete

FFS based applications can utilize the aio_cancel() callback to dequeue pending USB requests submitted to the UDC. There is a scenario where the FFS application issues an AIO cancel call, while the UDC is handling a soft disconnect. For a DWC3 based implementation, the callstack looks like the following:

DWC3 Gadget                               FFS Application

dwc3_gadget_soft_disconnect() ... --> dwc3_stop_active_transfers() --> dwc3_gadget_giveback(-ESHUTDOWN) --> ffs_epfile_async_io_complete() ffs_aio_cancel() --> usb_ep_free_request() --> usb_ep_dequeue()

There is currently no locking implemented between the AIO completion handler and AIO cancel, so the issue occurs if the completion routine is running in parallel to an AIO cancel call coming from the FFS application. As the completion call frees the USB request (io_data->req) the FFS application is also referencing it for the usb_ep_dequeue() call. This can lead to accessing a stale/hanging pointer.

commit b566d38857fc ("usb: gadget: f_fs: use io_data->status consistently") relocated the usb_ep_free_request() into ffs_epfile_async_io_complete(). However, in order to properly implement locking to mitigate this issue, the spinlock can't be added to ffs_epfile_async_io_complete(), as usb_ep_dequeue() (if successfully dequeuing a USB request) will call the function driver's completion handler in the same context. Hence, leading into a deadlock.

Fix this issue by moving the usb_ep_free_request() back to ffs_user_copy_worker(), and ensuring that it explicitly sets io_data->req to NULL after freeing it within the ffs->eps_lock. This resolves the race condition above, as the ffs_aio_cancel() routine will not continue attempting to dequeue a request that has already been freed, or the ffs_user_copy_work() not freeing the USB request until the AIO cancel is done referencing it.

This fix depends on commit b566d38857fc ("usb: gadget: f_fs: use io_data->status consistently")(CVE-2024-36894)

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

scsi: bfa: Ensure the copied buf is NUL terminated

Currently, we allocate a nbytes-sized kernel buffer and copy nbytes from userspace to that buffer. Later, we use sscanf on this buffer but we don't ensure that the string is terminated inside the buffer, this can lead to OOB read when using sscanf. Fix this issue by using memdup_user_nul instead of memdup_user.(CVE-2024-38560)

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

enic: Validate length of nl attributes in enic_set_vf_port

enic_set_vf_port assumes that the nl attribute IFLA_PORT_PROFILE is of length PORT_PROFILE_MAX and that the nl attributes IFLA_PORT_INSTANCE_UUID, IFLA_PORT_HOST_UUID are of length PORT_UUID_MAX. These attributes are validated (in the function do_setlink in rtnetlink.c) using the nla_policy ifla_port_policy. The policy defines IFLA_PORT_PROFILE as NLA_STRING, IFLA_PORT_INSTANCE_UUID as NLA_BINARY and IFLA_PORT_HOST_UUID as NLA_STRING. That means that the length validation using the policy is for the max size of the attributes and not on exact size so the length of these attributes might be less than the sizes that enic_set_vf_port expects. This might cause an out of bands read access in the memcpys of the data of these attributes in enic_set_vf_port.(CVE-2024-38659)

In the Linux kernel,…

The Linux Kernel, the operating system core itself.

Security Fix(es):

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

bcache: fix variable length array abuse in btree_iter

btree_iter is used in two ways: either allocated on the stack with a fixed size MAX_BSETS, or from a mempool with a dynamic size based on the specific cache set. Previously, the struct had a fixed-length array of size MAX_BSETS which was indexed out-of-bounds for the dynamically-sized iterators, which causes UBSAN to complain.

This patch uses the same approach as in bcachefs's sort_iter and splits the iterator into a btree_iter with a flexible array member and a btree_iter_stack which embeds a btree_iter as well as a fixed-length data array.(CVE-2024-39482)

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

ksmbd: discard write access to the directory open

may_open() does not allow a directory to be opened with the write access. However, some writing flags set by client result in adding write access on server, making ksmbd incompatible with FUSE file system. Simply, let's discard the write access when opening a directory.

list_add corruption. next is NULL. ------------[ cut here ]------------ kernel BUG at lib/list_debug.c:26! pc : __list_add_valid+0x88/0xbc lr : __list_add_valid+0x88/0xbc Call trace: __list_add_valid+0x88/0xbc fuse_finish_open+0x11c/0x170 fuse_open_common+0x284/0x5e8 fuse_dir_open+0x14/0x24 do_dentry_open+0x2a4/0x4e0 dentry_open+0x50/0x80 smb2_open+0xbe4/0x15a4 handle_ksmbd_work+0x478/0x5ec process_one_work+0x1b4/0x448 worker_thread+0x25c/0x430 kthread+0x104/0x1d4 ret_from_fork+0x10/0x20(CVE-2024-41030)

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

drm/nouveau/dispnv04: fix null pointer dereference in nv17_tv_get_ld_modes

In nv17_tv_get_ld_modes(), the return value of drm_mode_duplicate() is assigned to mode, which will lead to a possible NULL pointer dereference on failure of drm_mode_duplicate(). Add a check to avoid npd.(CVE-2024-41095)

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

media: xc2028: avoid use-after-free in load_firmware_cb()

syzkaller reported use-after-free in load_firmware_cb() 1. The reason is because the module allocated a struct tuner in tuner_probe(), and then the module initialization failed, the struct tuner was released. A worker which created during module initialization accesses this struct tuner later, it caused use-after-free.

The process is as follows:

task-6504 worker_thread tuner_probe <= alloc dvb_frontend [2] ... request_firmware_nowait <= create a worker ... tuner_remove <= free dvb_frontend ... request_firmware_work_func <= the firmware is ready load_firmware_cb <= but now the dvb_frontend has been freed

To fix the issue, check the dvd_frontend in load_firmware_cb(), if it is null, report a warning and just return.

BUG: KASAN: use-after-free in load_firmware_cb+0x1310/0x17a0 Read of size 8 at addr ffff8000d7ca2308 by task kworker/2:3/6504

 Call trace:
  load_firmware_cb+0x1310/0x17a0
  request_firmware_work_func+0x128/0x220
  process_one_work+0x770/0x1824
  worker_thread+0x488/0xea0
  kthread+0x300/0x430
  ret_from_fork+0x10/0x20

 Allocated by task 6504:
  kzalloc
  tuner_probe+0xb0/0x1430
  i2c_device_probe+0x92c/0xaf0
  really_probe+0x678/0xcd0
  driver_probe_device+0x280/0x370
  __device_attach_driver+0x220/0x330
  bus_for_each_drv+0x134/0x1c0
  __device_attach+0x1f4/0x410
  device_initial_probe+0x20/0x30
  bus_probe_device+0x184/0x200
  device_add+0x924/0x12c0
  device_register+0x24/0x30
  i2c_new_device+0x4e0/0xc44
 …

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

In the Linux kernel, the following vulnerability has been resolved: ksmbd: discard write access to the directory open may_open() does not allow a directory to be opened with the write access. However, some writing flags set by client result in adding write access on server, making ksmbd incompatible with FUSE file system. Simply, let's discard the write access when opening a directory. list_add corruption. next is NULL. ------------[ cut here ]------------ kernel BUG at lib/list_debug.c:26! pc : __list_add_valid+0x88/0xbc lr : __list_add_valid+0x88/0xbc Call trace: __list_add_valid+0x88/0xbc fuse_finish_open+0x11c/0x170 fuse_open_common+0x284/0x5e8 fuse_dir_open+0x14/0x24 do_dentry_open+0x2a4/0x4e0 dentry_open+0x50/0x80 smb2_open+0xbe4/0x15a4 handle_ksmbd_work+0x478/0x5ec process_one_work+0x1b4/0x448 worker_thread+0x25c/0x430 kthread+0x104/0x1d4 ret_from_fork+0x10/0x20

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

ksmbd: discard write access to the directory open

may_open() does not allow a directory to be opened with the write access. However, some writing flags set by client result in adding write access on server, making ksmbd incompatible with FUSE file system. Simply, let's discard the write access when opening a directory.

list_add corruption. next is NULL. ------------[ cut here ]------------ kernel BUG at lib/list_debug.c:26! pc : __list_add_valid+0x88/0xbc lr : __list_add_valid+0x88/0xbc Call trace: __list_add_valid+0x88/0xbc fuse_finish_open+0x11c/0x170 fuse_open_common+0x284/0x5e8 fuse_dir_open+0x14/0x24 do_dentry_open+0x2a4/0x4e0 dentry_open+0x50/0x80 smb2_open+0xbe4/0x15a4 handle_ksmbd_work+0x478/0x5ec process_one_work+0x1b4/0x448 worker_thread+0x25c/0x430 kthread+0x104/0x1d4 ret_from_fork+0x10/0x20

Upstream kernel version 6.6.43 fix bugs and vulnerabilities. The kmod-virtualbox and kmod-xtables-addons packages have been updated to work with this new kernel. For information about the vulnerabilities see the links.

Vanilla upstream kernel version 6.6.43 fix bugs and vulnerabilities. For information about the vulnerabilities see the links.

Chenyuan Yang discovered that the USB Gadget subsystem in the Linux kernel did not properly check for the device to be enabled before writing. A local attacker could possibly use this to cause a denial of service. (CVE-2024-25741)

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:

• ARM32 architecture;
• MIPS architecture;
• PA-RISC architecture;
• PowerPC architecture;
• RISC-V architecture;
• S390 architecture;
• x86 architecture;
• Cryptographic API;
• Serial ATA and Parallel ATA drivers;
• Null block device driver;
• Bluetooth drivers;
• Cdrom driver;
• Clock framework and drivers;
• Hardware crypto device drivers;
• CXL (Compute Express Link) drivers;
• Cirrus firmware drivers;
• GPIO subsystem;
• GPU drivers;
• I2C subsystem;
• IIO subsystem;
• InfiniBand drivers;
• ISDN/mISDN subsystem;
• LED subsystem;
• Multiple devices driver;
• Media drivers;
• Fastrpc Driver;
• Network drivers;
• Microsoft Azure Network Adapter (MANA) driver;
• Near Field Communication (NFC) drivers;
• NVME drivers;
• NVMEM (Non Volatile Memory) drivers;
• PCI subsystem;
• Pin controllers subsystem;
• x86 platform drivers;
• S/390 drivers;
• SCSI drivers;
• Thermal drivers;
• TTY drivers;
• UFS subsystem;
• USB DSL drivers;
• USB core drivers;
• DesignWare USB3 driver;
• USB Gadget drivers;
• USB Serial drivers;
• VFIO drivers;
• VHOST drivers;
• File systems infrastructure;
• BTRFS file system;
• GFS2 file system;
• JFFS2 file system;
• JFS file system;
• Network file systems library;
• Network file system client;
• NILFS2 file system;
• NTFS3 file system;
• SMB network file system;
• Memory management;
• Netfilter;
• Tracing infrastructure;
• io_uring subsystem;
• BPF subsystem;
• Core kernel;
• Bluetooth subsystem;
• CAN network layer;
• Ceph Core library;
• Networking core;
• IPv4 networking;
• IPv6 networking;
• IUCV driver;
• MAC80211 subsystem;
• Network traffic control;
• Sun RPC protocol;
• Wireless networking;
• AMD SoC Alsa drivers;
• SoC Audio for Freescale CPUs drivers;
• MediaTek ASoC drivers;
• SoC audio core drivers;
• SOF drivers;
• Sound sequencer drivers; (CVE-2024-42104, CVE-2024-42084, CVE-2024-42252, CVE-2024-41096, CVE-2024-42237, CVE-2024-42140, CVE-2024-42150, CVE-2024-41031, CVE-2024-41059, CVE-2024-41062, CVE-2024-41051, CVE-2024-41028, CVE-2024-41090, CVE-2024-41092, CVE-2024-43855, CVE-2024-41021, CVE-2024-42229, CVE-2024-41056, CVE-2024-41048, CVE-2024-41036, CVE-2024-42094, CVE-2024-41089, CVE-2024-41068, CVE-2024-41039, CVE-2024-41095, CVE-2024-41069, CVE-2024-42234, CVE-2024-42136, CVE-2024-41025, CVE-2024-42157, CVE-2024-42248, CVE-2024-42087, CVE-2024-41041, CVE-2024-42230, CVE-2024-42151, CVE-2024-42130, CVE-2024-42244, CVE-2024-41079, CVE-2024-42253, CVE-2024-42092, CVE-2024-41022, CVE-2024-42137, CVE-2024-42132, CVE-2024-42108, CVE-2024-42155, CVE-2024-42127, CVE-2024-41060, CVE-2024-42074, CVE-2024-41081, CVE-2024-42066, CVE-2024-42098, CVE-2024-42082, CVE-2024-42093, CVE-2024-42245, CVE-2024-41072, CVE-2024-41052, CVE-2024-42161, CVE-2024-42096, CVE-2024-42115, CVE-2024-41074, CVE-2024-42120, CVE-2024-41046, CVE-2024-42239, CVE-2024-41063, CVE-2024-42090, CVE-2024-41023, CVE-2024-42069, CVE-2024-41087, CVE-2024-42158, CVE-2024-41067, CVE-2024-41084, CVE-2024-41077, CVE-2024-42240, CVE-2024-42145, CVE-2024-42102, CVE-2024-41020, CVE-2024-42231, CVE-2024-41053, CVE-2024-42131, CVE-2024-42089, CVE-2024-41083, CVE-2024-42247, CVE-2024-42105, CVE-2024-41044, CVE-2024-42128, CVE-2024-42271, CVE-2024-41037, CVE-2024-42114, CVE-2024-42106, CVE-2024-41076, CVE-2024-42088, CVE-2024-41057, CVE-2024-41091, CVE-2024-42152, CVE-2024-41070, CVE-2024-41035, CVE-2024-41050, CVE-2024-39487, CVE-2024-42113, CVE-2024-42250, CVE-2024-41047,…

Chenyuan Yang discovered that the USB Gadget subsystem in the Linux kernel did not properly check for the device to be enabled before writing. A local attacker could possibly use this to cause a denial of service. (CVE-2024-25741)

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:

• ARM32 architecture;
• MIPS architecture;
• PA-RISC architecture;
• PowerPC architecture;
• RISC-V architecture;
• S390 architecture;
• x86 architecture;
• Cryptographic API;
• Serial ATA and Parallel ATA drivers;
• Null block device driver;
• Bluetooth drivers;
• Cdrom driver;
• Clock framework and drivers;
• Hardware crypto device drivers;
• CXL (Compute Express Link) drivers;
• Cirrus firmware drivers;
• GPIO subsystem;
• GPU drivers;
• I2C subsystem;
• IIO subsystem;
• InfiniBand drivers;
• ISDN/mISDN subsystem;
• LED subsystem;
• Multiple devices driver;
• Media drivers;
• Fastrpc Driver;
• Network drivers;
• Microsoft Azure Network Adapter (MANA) driver;
• Near Field Communication (NFC) drivers;
• NVME drivers;
• NVMEM (Non Volatile Memory) drivers;
• PCI subsystem;
• Pin controllers subsystem;
• x86 platform drivers;
• S/390 drivers;
• SCSI drivers;
• Thermal drivers;
• TTY drivers;
• UFS subsystem;
• USB DSL drivers;
• USB core drivers;
• DesignWare USB3 driver;
• USB Gadget drivers;
• USB Serial drivers;
• VFIO drivers;
• VHOST drivers;
• File systems infrastructure;
• BTRFS file system;
• GFS2 file system;
• JFFS2 file system;
• JFS file system;
• Network file systems library;
• Network file system client;
• NILFS2 file system;
• NTFS3 file system;
• SMB network file system;
• Memory management;
• Netfilter;
• Tracing infrastructure;
• io_uring subsystem;
• BPF subsystem;
• Core kernel;
• Bluetooth subsystem;
• CAN network layer;
• Ceph Core library;
• Networking core;
• IPv4 networking;
• IPv6 networking;
• IUCV driver;
• MAC80211 subsystem;
• Network traffic control;
• Sun RPC protocol;
• Wireless networking;
• AMD SoC Alsa drivers;
• SoC Audio for Freescale CPUs drivers;
• MediaTek ASoC drivers;
• SoC audio core drivers;
• SOF drivers;
• Sound sequencer drivers; (CVE-2024-42104, CVE-2024-42101, CVE-2024-41052, CVE-2024-42157, CVE-2024-41020, CVE-2024-41055, CVE-2024-42124, CVE-2023-52888, CVE-2024-42079, CVE-2024-43858, CVE-2024-41075, CVE-2024-42073, CVE-2024-42113, CVE-2024-42110, CVE-2024-41080, CVE-2024-42097, CVE-2024-41046, CVE-2024-42076, CVE-2024-41010, CVE-2024-41018, CVE-2024-42115, CVE-2024-41048, CVE-2024-42231, CVE-2024-42241, CVE-2024-41034, CVE-2024-42065, CVE-2024-42140, CVE-2024-42094, CVE-2024-41029, CVE-2024-42225, CVE-2024-41096, CVE-2024-42088, CVE-2024-41087, CVE-2023-52887, CVE-2024-42141, CVE-2024-42135, CVE-2024-42247, CVE-2024-39487, CVE-2024-42229, CVE-2024-42147, CVE-2024-42252, CVE-2024-41038, CVE-2024-41083, CVE-2024-42091, CVE-2024-42156, CVE-2024-42149, CVE-2024-41015, CVE-2024-41047, CVE-2024-42129, CVE-2024-42120, CVE-2024-41097, CVE-2024-42243, CVE-2024-42084, CVE-2024-42250, CVE-2024-41023, CVE-2024-41028, CVE-2024-42108, CVE-2024-41045, CVE-2024-42098, CVE-2024-41064, CVE-2024-42087, CVE-2024-42080, CVE-2024-41049, CVE-2024-42271, CVE-2024-41037, CVE-2024-42114, CVE-2024-41044, CVE-2024-42126, CVE-2024-42119, CVE-2024-42223, CVE-2024-42280, CVE-2024-42112, CVE-2024-41019, CVE-2024-42133, CVE-2024-42152, CVE-2024-41074, CVE-2024-41042, CVE-2024-41093, CVE-2024-41025, CVE-2024-42253, CVE-2024-42136, CVE-2024-42127, CVE-2024-41036, CVE-2024-42237, CVE-2024-42111, CVE-2024-41031, CVE-2024-41069, CVE-2024-41084, CVE-2024-41076, CVE-2024-41090, CVE-2024-41088, CVE-2024-41070, CVE-2024-42118, CVE-2024-42238, CVE-2024-42234, CVE-2024-41089, CVE-2024-41095, CVE-2024-41085, CVE-2024-42106, CVE-2024-42155, CVE-2024-42146,…

Chenyuan Yang discovered that the USB Gadget subsystem in the Linux kernel did not properly check for the device to be enabled before writing. A local attacker could possibly use this to cause a denial of service. (CVE-2024-25741)

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:

• ARM32 architecture;
• MIPS architecture;
• PA-RISC architecture;
• PowerPC architecture;
• RISC-V architecture;
• S390 architecture;
• x86 architecture;
• Cryptographic API;
• Serial ATA and Parallel ATA drivers;
• Null block device driver;
• Bluetooth drivers;
• Cdrom driver;
• Clock framework and drivers;
• Hardware crypto device drivers;
• CXL (Compute Express Link) drivers;
• Cirrus firmware drivers;
• GPIO subsystem;
• GPU drivers;
• I2C subsystem;
• IIO subsystem;
• InfiniBand drivers;
• ISDN/mISDN subsystem;
• LED subsystem;
• Multiple devices driver;
• Media drivers;
• Fastrpc Driver;
• Network drivers;
• Microsoft Azure Network Adapter (MANA) driver;
• Near Field Communication (NFC) drivers;
• NVME drivers;
• NVMEM (Non Volatile Memory) drivers;
• PCI subsystem;
• Pin controllers subsystem;
• x86 platform drivers;
• S/390 drivers;
• SCSI drivers;
• Thermal drivers;
• TTY drivers;
• UFS subsystem;
• USB DSL drivers;
• USB core drivers;
• DesignWare USB3 driver;
• USB Gadget drivers;
• USB Serial drivers;
• VFIO drivers;
• VHOST drivers;
• File systems infrastructure;
• BTRFS file system;
• GFS2 file system;
• JFFS2 file system;
• JFS file system;
• Network file systems library;
• Network file system client;
• NILFS2 file system;
• NTFS3 file system;
• SMB network file system;
• Memory management;
• Netfilter;
• Tracing infrastructure;
• io_uring subsystem;
• BPF subsystem;
• Core kernel;
• Bluetooth subsystem;
• CAN network layer;
• Ceph Core library;
• Networking core;
• IPv4 networking;
• IPv6 networking;
• IUCV driver;
• MAC80211 subsystem;
• Network traffic control;
• Sun RPC protocol;
• Wireless networking;
• AMD SoC Alsa drivers;
• SoC Audio for Freescale CPUs drivers;
• MediaTek ASoC drivers;
• SoC audio core drivers;
• SOF drivers;
• Sound sequencer drivers; (CVE-2024-42239, CVE-2024-42079, CVE-2024-41080, CVE-2024-42064, CVE-2024-42127, CVE-2024-41049, CVE-2024-41086, CVE-2024-42142, CVE-2024-42244, CVE-2024-41060, CVE-2024-42131, CVE-2024-42085, CVE-2024-42246, CVE-2024-41062, CVE-2024-42115, CVE-2024-42234, CVE-2024-42080, CVE-2024-41095, CVE-2024-41063, CVE-2024-42227, CVE-2024-41089, CVE-2024-42133, CVE-2024-43858, CVE-2024-42135, CVE-2024-42113, CVE-2024-42120, CVE-2024-42149, CVE-2024-42132, CVE-2024-41038, CVE-2024-41069, CVE-2024-41090, CVE-2024-41059, CVE-2024-41028, CVE-2024-42126, CVE-2024-42121, CVE-2024-42155, CVE-2024-42110, CVE-2024-41021, CVE-2024-41044, CVE-2024-42098, CVE-2024-42235, CVE-2024-41083, CVE-2024-41065, CVE-2024-42094, CVE-2024-42229, CVE-2024-42240, CVE-2024-42225, CVE-2024-42230, CVE-2024-41088, CVE-2024-42073, CVE-2024-42145, CVE-2024-42076, CVE-2024-42087, CVE-2024-42241, CVE-2024-41019, CVE-2024-41052, CVE-2024-42093, CVE-2024-42063, CVE-2024-41039, CVE-2024-42106, CVE-2024-42108, CVE-2024-42237, CVE-2024-41048, CVE-2024-41033, CVE-2023-52888, CVE-2024-41096, CVE-2024-41032, CVE-2024-41091, CVE-2024-42238, CVE-2024-41056, CVE-2024-42091, CVE-2024-42088, CVE-2024-41047, CVE-2024-42271, CVE-2024-41064, CVE-2024-42223, CVE-2024-42129, CVE-2024-42102, CVE-2024-42146, CVE-2024-42138, CVE-2024-41079, CVE-2024-42232, CVE-2024-42112, CVE-2024-39487, CVE-2024-42245, CVE-2024-41093, CVE-2024-41066, CVE-2024-43855, CVE-2024-41055, CVE-2024-42100, CVE-2024-41053, CVE-2024-42069, CVE-2024-42252, CVE-2024-42243, CVE-2024-42124, CVE-2024-41054, CVE-2024-42151, CVE-2024-42118, CVE-2024-42251, CVE-2024-42137, CVE-2024-41071,…

Chenyuan Yang discovered that the USB Gadget subsystem in the Linux kernel did not properly check for the device to be enabled before writing. A local attacker could possibly use this to cause a denial of service. (CVE-2024-25741)

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:

• ARM32 architecture;
• MIPS architecture;
• PA-RISC architecture;
• PowerPC architecture;
• RISC-V architecture;
• S390 architecture;
• x86 architecture;
• Cryptographic API;
• Serial ATA and Parallel ATA drivers;
• Null block device driver;
• Bluetooth drivers;
• Cdrom driver;
• Clock framework and drivers;
• Hardware crypto device drivers;
• CXL (Compute Express Link) drivers;
• Cirrus firmware drivers;
• GPIO subsystem;
• GPU drivers;
• I2C subsystem;
• IIO subsystem;
• InfiniBand drivers;
• ISDN/mISDN subsystem;
• LED subsystem;
• Multiple devices driver;
• Media drivers;
• Fastrpc Driver;
• Network drivers;
• Microsoft Azure Network Adapter (MANA) driver;
• Near Field Communication (NFC) drivers;
• NVME drivers;
• NVMEM (Non Volatile Memory) drivers;
• PCI subsystem;
• Pin controllers subsystem;
• x86 platform drivers;
• S/390 drivers;
• SCSI drivers;
• Thermal drivers;
• TTY drivers;
• UFS subsystem;
• USB DSL drivers;
• USB core drivers;
• DesignWare USB3 driver;
• USB Gadget drivers;
• USB Serial drivers;
• VFIO drivers;
• VHOST drivers;
• File systems infrastructure;
• BTRFS file system;
• GFS2 file system;
• JFFS2 file system;
• JFS file system;
• Network file systems library;
• Network file system client;
• NILFS2 file system;
• NTFS3 file system;
• SMB network file system;
• Memory management;
• Netfilter;
• Tracing infrastructure;
• io_uring subsystem;
• BPF subsystem;
• Core kernel;
• Bluetooth subsystem;
• CAN network layer;
• Ceph Core library;
• Networking core;
• IPv4 networking;
• IPv6 networking;
• IUCV driver;
• MAC80211 subsystem;
• Network traffic control;
• Sun RPC protocol;
• Wireless networking;
• AMD SoC Alsa drivers;
• SoC Audio for Freescale CPUs drivers;
• MediaTek ASoC drivers;
• SoC audio core drivers;
• SOF drivers;
• Sound sequencer drivers; (CVE-2024-41064, CVE-2024-41087, CVE-2023-52888, CVE-2024-42098, CVE-2024-42111, CVE-2024-42076, CVE-2024-42088, CVE-2024-42135, CVE-2024-42145, CVE-2024-42142, CVE-2024-41036, CVE-2024-41071, CVE-2024-41012, CVE-2024-42091, CVE-2024-42253, CVE-2024-42119, CVE-2024-42097, CVE-2024-42243, CVE-2024-39487, CVE-2024-42235, CVE-2024-42120, CVE-2024-42149, CVE-2024-41015, CVE-2024-41074, CVE-2024-42067, CVE-2024-42090, CVE-2024-42128, CVE-2024-41038, CVE-2024-42113, CVE-2024-42102, CVE-2024-42231, CVE-2024-42080, CVE-2024-42241, CVE-2024-42106, CVE-2024-42130, CVE-2024-42073, CVE-2024-42153, CVE-2024-42156, CVE-2024-42118, CVE-2024-41007, CVE-2024-41049, CVE-2024-39486, CVE-2024-42240, CVE-2024-41018, CVE-2024-42251, CVE-2024-42280, CVE-2024-42096, CVE-2024-42121, CVE-2024-42246, CVE-2024-42092, CVE-2024-41090, CVE-2024-42157, CVE-2024-43858, CVE-2024-42150, CVE-2024-42110, CVE-2024-41010, CVE-2024-41081, CVE-2024-41061, CVE-2024-41078, CVE-2024-41094, CVE-2024-41039, CVE-2024-42114, CVE-2024-42109, CVE-2024-41030, CVE-2024-42066, CVE-2024-41035, CVE-2024-42146, CVE-2024-42131, CVE-2024-41059, CVE-2024-41067, CVE-2024-42138, CVE-2024-41050, CVE-2024-41034, CVE-2024-41077, CVE-2024-41076, CVE-2024-41088, CVE-2024-41096, CVE-2024-41073, CVE-2024-41037, CVE-2024-42232, CVE-2024-41063, CVE-2024-42117, CVE-2024-42155, CVE-2024-41080, CVE-2024-42132, CVE-2024-42084, CVE-2024-42136, CVE-2024-42223, CVE-2024-41068, CVE-2024-42225, CVE-2024-42065, CVE-2024-41051, CVE-2024-43855, CVE-2024-42238, CVE-2024-42250, CVE-2024-42112, CVE-2024-41070, CVE-2023-52887, CVE-2024-42094, CVE-2024-42095, CVE-2024-41086,…

Chenyuan Yang discovered that the USB Gadget subsystem in the Linux kernel did not properly check for the device to be enabled before writing. A local attacker could possibly use this to cause a denial of service. (CVE-2024-25741)

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:

• ARM32 architecture;
• MIPS architecture;
• PA-RISC architecture;
• PowerPC architecture;
• RISC-V architecture;
• S390 architecture;
• x86 architecture;
• Cryptographic API;
• Serial ATA and Parallel ATA drivers;
• Null block device driver;
• Bluetooth drivers;
• Cdrom driver;
• Clock framework and drivers;
• Hardware crypto device drivers;
• CXL (Compute Express Link) drivers;
• Cirrus firmware drivers;
• GPIO subsystem;
• GPU drivers;
• I2C subsystem;
• IIO subsystem;
• InfiniBand drivers;
• ISDN/mISDN subsystem;
• LED subsystem;
• Multiple devices driver;
• Media drivers;
• Fastrpc Driver;
• Network drivers;
• Microsoft Azure Network Adapter (MANA) driver;
• Near Field Communication (NFC) drivers;
• NVME drivers;
• NVMEM (Non Volatile Memory) drivers;
• PCI subsystem;
• Pin controllers subsystem;
• x86 platform drivers;
• S/390 drivers;
• SCSI drivers;
• Thermal drivers;
• TTY drivers;
• UFS subsystem;
• USB DSL drivers;
• USB core drivers;
• DesignWare USB3 driver;
• USB Gadget drivers;
• USB Serial drivers;
• VFIO drivers;
• VHOST drivers;
• File systems infrastructure;
• BTRFS file system;
• GFS2 file system;
• JFFS2 file system;
• JFS file system;
• Network file systems library;
• Network file system client;
• NILFS2 file system;
• NTFS3 file system;
• SMB network file system;
• Memory management;
• Netfilter;
• Tracing infrastructure;
• io_uring subsystem;
• BPF subsystem;
• Core kernel;
• Bluetooth subsystem;
• CAN network layer;
• Ceph Core library;
• Networking core;
• IPv4 networking;
• IPv6 networking;
• IUCV driver;
• MAC80211 subsystem;
• Network traffic control;
• Sun RPC protocol;
• Wireless networking;
• AMD SoC Alsa drivers;
• SoC Audio for Freescale CPUs drivers;
• MediaTek ASoC drivers;
• SoC audio core drivers;
• SOF drivers;
• Sound sequencer drivers; (CVE-2024-42223, CVE-2024-42244, CVE-2024-42105, CVE-2024-42100, CVE-2024-42235, CVE-2024-41007, CVE-2024-41047, CVE-2024-42088, CVE-2024-42079, CVE-2024-41053, CVE-2024-41094, CVE-2024-42227, CVE-2024-42253, CVE-2024-42150, CVE-2024-41049, CVE-2024-42096, CVE-2024-42093, CVE-2024-41079, CVE-2024-41037, CVE-2024-42129, CVE-2024-41031, CVE-2024-39486, CVE-2024-41065, CVE-2024-42101, CVE-2024-41082, CVE-2024-42135, CVE-2024-42236, CVE-2024-41078, CVE-2024-42098, CVE-2024-41056, CVE-2024-41096, CVE-2024-41074, CVE-2024-42246, CVE-2024-42137, CVE-2024-42232, CVE-2024-42121, CVE-2024-41093, CVE-2024-41076, CVE-2024-42157, CVE-2024-41062, CVE-2024-42104, CVE-2024-42085, CVE-2024-41092, CVE-2024-41034, CVE-2024-41036, CVE-2024-41072, CVE-2024-41012, CVE-2024-39487, CVE-2024-42124, CVE-2024-42065, CVE-2024-41061, CVE-2024-41064, CVE-2024-41091, CVE-2024-42119, CVE-2024-41088, CVE-2024-42089, CVE-2024-41048, CVE-2024-41032, CVE-2024-41020, CVE-2024-42066, CVE-2024-42068, CVE-2024-42238, CVE-2024-41069, CVE-2024-41044, CVE-2024-41025, CVE-2024-42161, CVE-2023-52887, CVE-2024-42127, CVE-2024-42239, CVE-2024-42149, CVE-2024-42091, CVE-2024-42097, CVE-2024-41054, CVE-2024-41041, CVE-2024-42131, CVE-2024-41089, CVE-2024-41018, CVE-2024-42067, CVE-2024-41039, CVE-2024-42128, CVE-2024-42248, CVE-2024-41090, CVE-2024-42073, CVE-2024-43858, CVE-2024-42225, CVE-2024-42077, CVE-2024-42247, CVE-2024-42109, CVE-2024-41045, CVE-2024-41019, CVE-2024-42231, CVE-2024-41017, CVE-2024-42145, CVE-2024-41046, CVE-2024-42063, CVE-2024-41087, CVE-2024-41033, CVE-2024-41021, CVE-2024-42241, CVE-2024-42229, CVE-2024-41015,…

Chenyuan Yang discovered that the USB Gadget subsystem in the Linux kernel did not properly check for the device to be enabled before writing. A local attacker could possibly use this to cause a denial of service. (CVE-2024-25741)

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:

• ARM32 architecture;
• MIPS architecture;
• PA-RISC architecture;
• PowerPC architecture;
• RISC-V architecture;
• S390 architecture;
• x86 architecture;
• Cryptographic API;
• Serial ATA and Parallel ATA drivers;
• Null block device driver;
• Bluetooth drivers;
• Cdrom driver;
• Clock framework and drivers;
• Hardware crypto device drivers;
• CXL (Compute Express Link) drivers;
• Cirrus firmware drivers;
• GPIO subsystem;
• GPU drivers;
• I2C subsystem;
• IIO subsystem;
• InfiniBand drivers;
• ISDN/mISDN subsystem;
• LED subsystem;
• Multiple devices driver;
• Media drivers;
• Fastrpc Driver;
• Network drivers;
• Microsoft Azure Network Adapter (MANA) driver;
• Near Field Communication (NFC) drivers;
• NVME drivers;
• NVMEM (Non Volatile Memory) drivers;
• PCI subsystem;
• Pin controllers subsystem;
• x86 platform drivers;
• S/390 drivers;
• SCSI drivers;
• Thermal drivers;
• TTY drivers;
• UFS subsystem;
• USB DSL drivers;
• USB core drivers;
• DesignWare USB3 driver;
• USB Gadget drivers;
• USB Serial drivers;
• VFIO drivers;
• VHOST drivers;
• File systems infrastructure;
• BTRFS file system;
• GFS2 file system;
• JFFS2 file system;
• JFS file system;
• Network file systems library;
• Network file system client;
• NILFS2 file system;
• NTFS3 file system;
• SMB network file system;
• Memory management;
• Netfilter;
• Tracing infrastructure;
• io_uring subsystem;
• BPF subsystem;
• Core kernel;
• Bluetooth subsystem;
• CAN network layer;
• Ceph Core library;
• Networking core;
• IPv4 networking;
• IPv6 networking;
• IUCV driver;
• MAC80211 subsystem;
• Network traffic control;
• Sun RPC protocol;
• Wireless networking;
• AMD SoC Alsa drivers;
• SoC Audio for Freescale CPUs drivers;
• MediaTek ASoC drivers;
• SoC audio core drivers;
• SOF drivers;
• Sound sequencer drivers; (CVE-2024-41062, CVE-2024-41029, CVE-2024-42142, CVE-2024-41070, CVE-2024-41066, CVE-2024-42150, CVE-2024-42120, CVE-2023-52888, CVE-2024-42141, CVE-2024-41032, CVE-2024-42245, CVE-2024-41053, CVE-2024-42247, CVE-2024-42161, CVE-2024-42094, CVE-2024-41072, CVE-2024-42076, CVE-2024-42091, CVE-2024-42103, CVE-2024-41007, CVE-2024-42064, CVE-2024-41075, CVE-2024-42157, CVE-2024-42069, CVE-2024-41045, CVE-2024-42068, CVE-2024-42090, CVE-2024-41071, CVE-2024-42082, CVE-2024-42146, CVE-2024-41018, CVE-2024-42238, CVE-2024-41079, CVE-2024-42241, CVE-2024-42067, CVE-2024-42132, CVE-2024-42121, CVE-2024-41025, CVE-2024-42231, CVE-2024-42225, CVE-2024-41080, CVE-2024-41086, CVE-2024-41012, CVE-2024-42234, CVE-2024-41088, CVE-2024-42129, CVE-2024-42158, CVE-2024-41078, CVE-2024-41038, CVE-2024-41055, CVE-2024-42106, CVE-2024-42227, CVE-2024-42102, CVE-2024-41082, CVE-2024-42108, CVE-2024-41085, CVE-2024-41020, CVE-2024-41054, CVE-2024-42085, CVE-2024-42140, CVE-2024-42089, CVE-2024-41047, CVE-2024-42092, CVE-2024-41044, CVE-2024-42246, CVE-2024-41035, CVE-2024-42250, CVE-2024-42070, CVE-2024-41039, CVE-2024-41061, CVE-2024-42147, CVE-2024-42104, CVE-2024-41090, CVE-2024-41096, CVE-2024-41063, CVE-2024-41084, CVE-2024-41059, CVE-2024-41097, CVE-2024-41089, CVE-2024-42093, CVE-2024-42126, CVE-2024-42135, CVE-2024-42128, CVE-2024-42098, CVE-2024-42105, CVE-2024-42124, CVE-2024-42101, CVE-2024-41091, CVE-2024-42127, CVE-2024-41077, CVE-2024-42111, CVE-2024-41037, CVE-2024-42136, CVE-2024-41083, CVE-2024-42243, CVE-2024-41033, CVE-2024-41046, CVE-2024-42230, CVE-2024-42080, CVE-2024-42096, CVE-2024-42100,…

Chenyuan Yang discovered that the USB Gadget subsystem in the Linux kernel did not properly check for the device to be enabled before writing. A local attacker could possibly use this to cause a denial of service. (CVE-2024-25741)

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:

• ARM32 architecture;
• MIPS architecture;
• PA-RISC architecture;
• PowerPC architecture;
• RISC-V architecture;
• S390 architecture;
• x86 architecture;
• Cryptographic API;
• Serial ATA and Parallel ATA drivers;
• Null block device driver;
• Bluetooth drivers;
• Cdrom driver;
• Clock framework and drivers;
• Hardware crypto device drivers;
• CXL (Compute Express Link) drivers;
• Cirrus firmware drivers;
• GPIO subsystem;
• GPU drivers;
• I2C subsystem;
• IIO subsystem;
• InfiniBand drivers;
• ISDN/mISDN subsystem;
• LED subsystem;
• Multiple devices driver;
• Media drivers;
• Fastrpc Driver;
• Network drivers;
• Microsoft Azure Network Adapter (MANA) driver;
• Near Field Communication (NFC) drivers;
• NVME drivers;
• NVMEM (Non Volatile Memory) drivers;
• PCI subsystem;
• Pin controllers subsystem;
• x86 platform drivers;
• S/390 drivers;
• SCSI drivers;
• Thermal drivers;
• TTY drivers;
• UFS subsystem;
• USB DSL drivers;
• USB core drivers;
• DesignWare USB3 driver;
• USB Gadget drivers;
• USB Serial drivers;
• VFIO drivers;
• VHOST drivers;
• File systems infrastructure;
• BTRFS file system;
• GFS2 file system;
• JFFS2 file system;
• JFS file system;
• Network file systems library;
• Network file system client;
• NILFS2 file system;
• NTFS3 file system;
• SMB network file system;
• Memory management;
• Netfilter;
• Tracing infrastructure;
• io_uring subsystem;
• BPF subsystem;
• Core kernel;
• Bluetooth subsystem;
• CAN network layer;
• Ceph Core library;
• Networking core;
• IPv4 networking;
• IPv6 networking;
• IUCV driver;
• MAC80211 subsystem;
• Network traffic control;
• Sun RPC protocol;
• Wireless networking;
• AMD SoC Alsa drivers;
• SoC Audio for Freescale CPUs drivers;
• MediaTek ASoC drivers;
• SoC audio core drivers;
• SOF drivers;
• Sound sequencer drivers; (CVE-2024-42104, CVE-2024-42084, CVE-2024-42252, CVE-2024-41096, CVE-2024-42237, CVE-2024-42140, CVE-2024-42150, CVE-2024-41031, CVE-2024-41059, CVE-2024-41062, CVE-2024-41051, CVE-2024-41028, CVE-2024-41090, CVE-2024-41092, CVE-2024-43855, CVE-2024-41021, CVE-2024-42229, CVE-2024-41056, CVE-2024-41048, CVE-2024-41036, CVE-2024-42094, CVE-2024-41089, CVE-2024-41068, CVE-2024-41039, CVE-2024-41095, CVE-2024-41069, CVE-2024-42234, CVE-2024-42136, CVE-2024-41025, CVE-2024-42157, CVE-2024-42248, CVE-2024-42087, CVE-2024-41041, CVE-2024-42230, CVE-2024-42151, CVE-2024-42130, CVE-2024-42244, CVE-2024-41079, CVE-2024-42253, CVE-2024-42092, CVE-2024-41022, CVE-2024-42137, CVE-2024-42132, CVE-2024-42108, CVE-2024-42155, CVE-2024-42127, CVE-2024-41060, CVE-2024-42074, CVE-2024-41081, CVE-2024-42066, CVE-2024-42098, CVE-2024-42082, CVE-2024-42093, CVE-2024-42245, CVE-2024-41072, CVE-2024-41052, CVE-2024-42161, CVE-2024-42096, CVE-2024-42115, CVE-2024-41074, CVE-2024-42120, CVE-2024-41046, CVE-2024-42239, CVE-2024-41063, CVE-2024-42090, CVE-2024-41023, CVE-2024-42069, CVE-2024-41087, CVE-2024-42158, CVE-2024-41067, CVE-2024-41084, CVE-2024-41077, CVE-2024-42240, CVE-2024-42145, CVE-2024-42102, CVE-2024-41020, CVE-2024-42231, CVE-2024-41053, CVE-2024-42131, CVE-2024-42089, CVE-2024-41083, CVE-2024-42247, CVE-2024-42105, CVE-2024-41044, CVE-2024-42128, CVE-2024-42271, CVE-2024-41037, CVE-2024-42114, CVE-2024-42106, CVE-2024-41076, CVE-2024-42088, CVE-2024-41057, CVE-2024-41091, CVE-2024-42152, CVE-2024-41070, CVE-2024-41035, CVE-2024-41050, CVE-2024-39487, CVE-2024-42113, CVE-2024-42250, CVE-2024-41047,…

Chenyuan Yang discovered that the USB Gadget subsystem in the Linux kernel did not properly check for the device to be enabled before writing. A local attacker could possibly use this to cause a denial of service. (CVE-2024-25741)

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:

• ARM32 architecture;
• MIPS architecture;
• PA-RISC architecture;
• PowerPC architecture;
• RISC-V architecture;
• S390 architecture;
• x86 architecture;
• Cryptographic API;
• Serial ATA and Parallel ATA drivers;
• Null block device driver;
• Bluetooth drivers;
• Cdrom driver;
• Clock framework and drivers;
• Hardware crypto device drivers;
• CXL (Compute Express Link) drivers;
• Cirrus firmware drivers;
• GPIO subsystem;
• GPU drivers;
• I2C subsystem;
• IIO subsystem;
• InfiniBand drivers;
• ISDN/mISDN subsystem;
• LED subsystem;
• Multiple devices driver;
• Media drivers;
• Fastrpc Driver;
• Network drivers;
• Microsoft Azure Network Adapter (MANA) driver;
• Near Field Communication (NFC) drivers;
• NVME drivers;
• NVMEM (Non Volatile Memory) drivers;
• PCI subsystem;
• Pin controllers subsystem;
• x86 platform drivers;
• S/390 drivers;
• SCSI drivers;
• Thermal drivers;
• TTY drivers;
• UFS subsystem;
• USB DSL drivers;
• USB core drivers;
• DesignWare USB3 driver;
• USB Gadget drivers;
• USB Serial drivers;
• VFIO drivers;
• VHOST drivers;
• File systems infrastructure;
• BTRFS file system;
• GFS2 file system;
• JFFS2 file system;
• JFS file system;
• Network file systems library;
• Network file system client;
• NILFS2 file system;
• NTFS3 file system;
• SMB network file system;
• Memory management;
• Netfilter;
• Tracing infrastructure;
• io_uring subsystem;
• BPF subsystem;
• Core kernel;
• Bluetooth subsystem;
• CAN network layer;
• Ceph Core library;
• Networking core;
• IPv4 networking;
• IPv6 networking;
• IUCV driver;
• MAC80211 subsystem;
• Network traffic control;
• Sun RPC protocol;
• Wireless networking;
• AMD SoC Alsa drivers;
• SoC Audio for Freescale CPUs drivers;
• MediaTek ASoC drivers;
• SoC audio core drivers;
• SOF drivers;
• Sound sequencer drivers; (CVE-2024-42064, CVE-2024-43858, CVE-2024-42251, CVE-2024-42113, CVE-2024-41020, CVE-2024-41093, CVE-2024-45016, CVE-2024-42150, CVE-2024-42069, CVE-2024-42157, CVE-2024-42126, CVE-2024-42144, CVE-2024-42093, CVE-2024-41035, CVE-2024-41032, CVE-2024-41077, CVE-2024-42097, CVE-2024-41071, CVE-2024-42227, CVE-2024-42253, CVE-2024-42237, CVE-2024-41060, CVE-2024-42080, CVE-2024-42068, CVE-2024-41058, CVE-2024-42140, CVE-2024-42231, CVE-2024-42127, CVE-2024-42243, CVE-2023-52887, CVE-2024-39486, CVE-2024-41063, CVE-2024-42128, CVE-2024-42074, CVE-2024-41028, CVE-2024-42110, CVE-2024-45001, CVE-2024-41090, CVE-2024-41084, CVE-2024-41088, CVE-2024-42118, CVE-2024-41094, CVE-2024-41091, CVE-2024-41007, CVE-2024-42280, CVE-2024-41044, CVE-2024-41012, CVE-2024-42063, CVE-2024-41078, CVE-2024-42082, CVE-2024-41055, CVE-2024-41031, CVE-2024-42142, CVE-2024-41083, CVE-2024-42145, CVE-2024-41039, CVE-2024-41019, CVE-2024-42149, CVE-2024-42248, CVE-2024-42111, CVE-2024-41074, CVE-2024-42096, CVE-2024-42100, CVE-2024-41010, CVE-2024-43855, CVE-2024-42136, CVE-2024-41054, CVE-2024-41053, CVE-2024-41061, CVE-2024-42104, CVE-2024-41025, CVE-2024-42129, CVE-2024-41086, CVE-2024-42133, CVE-2024-42115, CVE-2024-42158, CVE-2024-42091, CVE-2024-42088, CVE-2024-42161, CVE-2024-42236, CVE-2024-41065, CVE-2024-41062, CVE-2024-42153, CVE-2024-41030, CVE-2024-41079, CVE-2023-52888, CVE-2024-42223, CVE-2024-42119, CVE-2024-42238, CVE-2024-41052, CVE-2024-41064, CVE-2024-42138, CVE-2024-41081, CVE-2024-41034, CVE-2024-42147, CVE-2024-41095, CVE-2024-42132, CVE-2024-42137, CVE-2024-42106, CVE-2024-41041, CVE-2024-41073,…

Chenyuan Yang discovered that the USB Gadget subsystem in the Linux kernel did not properly check for the device to be enabled before writing. A local attacker could possibly use this to cause a denial of service. (CVE-2024-25741)

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:

• ARM32 architecture;
• MIPS architecture;
• PA-RISC architecture;
• PowerPC architecture;
• RISC-V architecture;
• S390 architecture;
• x86 architecture;
• Cryptographic API;
• Serial ATA and Parallel ATA drivers;
• Null block device driver;
• Bluetooth drivers;
• Cdrom driver;
• Clock framework and drivers;
• Hardware crypto device drivers;
• CXL (Compute Express Link) drivers;
• Cirrus firmware drivers;
• GPIO subsystem;
• GPU drivers;
• I2C subsystem;
• IIO subsystem;
• InfiniBand drivers;
• ISDN/mISDN subsystem;
• LED subsystem;
• Multiple devices driver;
• Media drivers;
• Fastrpc Driver;
• Network drivers;
• Microsoft Azure Network Adapter (MANA) driver;
• Near Field Communication (NFC) drivers;
• NVME drivers;
• NVMEM (Non Volatile Memory) drivers;
• PCI subsystem;
• Pin controllers subsystem;
• x86 platform drivers;
• S/390 drivers;
• SCSI drivers;
• Thermal drivers;
• TTY drivers;
• UFS subsystem;
• USB DSL drivers;
• USB core drivers;
• DesignWare USB3 driver;
• USB Gadget drivers;
• USB Serial drivers;
• VFIO drivers;
• VHOST drivers;
• File systems infrastructure;
• BTRFS file system;
• GFS2 file system;
• JFFS2 file system;
• JFS file system;
• Network file systems library;
• Network file system client;
• NILFS2 file system;
• NTFS3 file system;
• SMB network file system;
• Memory management;
• Netfilter;
• Tracing infrastructure;
• io_uring subsystem;
• BPF subsystem;
• Core kernel;
• Bluetooth subsystem;
• CAN network layer;
• Ceph Core library;
• Networking core;
• IPv4 networking;
• IPv6 networking;
• IUCV driver;
• MAC80211 subsystem;
• Network traffic control;
• Sun RPC protocol;
• Wireless networking;
• AMD SoC Alsa drivers;
• SoC Audio for Freescale CPUs drivers;
• MediaTek ASoC drivers;
• SoC audio core drivers;
• SOF drivers;
• Sound sequencer drivers; (CVE-2024-42271, CVE-2024-42068, CVE-2024-42086, CVE-2024-42132, CVE-2024-42074, CVE-2024-41017, CVE-2024-42090, CVE-2024-42280, CVE-2024-41030, CVE-2024-41037, CVE-2024-42248, CVE-2024-42084, CVE-2024-41057, CVE-2024-42252, CVE-2024-41055, CVE-2024-42158, CVE-2024-42097, CVE-2024-42101, CVE-2024-42095, CVE-2024-41084, CVE-2024-41051, CVE-2024-41032, CVE-2024-41046, CVE-2024-42231, CVE-2024-42133, CVE-2024-42089, CVE-2024-41062, CVE-2024-41033, CVE-2024-41012, CVE-2024-41077, CVE-2024-41064, CVE-2024-41082, CVE-2024-41090, CVE-2024-42065, CVE-2024-41096, CVE-2024-42119, CVE-2024-41054, CVE-2024-42064, CVE-2024-42253, CVE-2024-42237, CVE-2024-42120, CVE-2024-41066, CVE-2024-41083, CVE-2024-42129, CVE-2024-41085, CVE-2024-41058, CVE-2024-42146, CVE-2024-42156, CVE-2024-42076, CVE-2024-42149, CVE-2024-42069, CVE-2024-41039, CVE-2024-42110, CVE-2024-42150, CVE-2024-41015, CVE-2024-39486, CVE-2024-42144, CVE-2024-42131, CVE-2024-42087, CVE-2024-42091, CVE-2024-42236, CVE-2024-42088, CVE-2024-42112, CVE-2024-42142, CVE-2024-42082, CVE-2024-42111, CVE-2024-41028, CVE-2024-45001, CVE-2024-42077, CVE-2024-42102, CVE-2024-42239, CVE-2024-42140, CVE-2024-41091, CVE-2024-41050, CVE-2024-41034, CVE-2024-43858, CVE-2024-42145, CVE-2024-42227, CVE-2024-41029, CVE-2024-42230, CVE-2024-42096, CVE-2024-42238, CVE-2024-41027, CVE-2024-42063, CVE-2024-41023, CVE-2024-41041, CVE-2024-41038, CVE-2024-41073, CVE-2024-41067, CVE-2024-41025, CVE-2024-42152, CVE-2024-42247, CVE-2024-41065, CVE-2024-42121, CVE-2024-42157, CVE-2024-42080, CVE-2024-41076, CVE-2024-41059, CVE-2024-42108, CVE-2024-42251, CVE-2024-42093,…

Chenyuan Yang discovered that the USB Gadget subsystem in the Linux kernel did not properly check for the device to be enabled before writing. A local attacker could possibly use this to cause a denial of service. (CVE-2024-25741)

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:

• ARM32 architecture;
• ARM64 architecture;
• MIPS architecture;
• PA-RISC architecture;
• PowerPC architecture;
• RISC-V architecture;
• S390 architecture;
• User-Mode Linux (UML);
• x86 architecture;
• Block layer subsystem;
• Cryptographic API;
• Android drivers;
• Serial ATA and Parallel ATA drivers;
• ATM drivers;
• Drivers core;
• Null block device driver;
• Ublk userspace block driver;
• Bluetooth drivers;
• Cdrom driver;
• Character device driver;
• Clock framework and drivers;
• Hardware crypto device drivers;
• CXL (Compute Express Link) drivers;
• Buffer Sharing and Synchronization framework;
• DMA engine subsystem;
• Cirrus firmware drivers;
• 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;
• ISDN/mISDN subsystem;
• 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;
• NVMEM (Non Volatile Memory) 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;
• Thermal drivers;
• Thunderbolt and USB4 drivers;
• TTY drivers;
• UFS subsystem;
• Userspace I/O drivers;
• USB DSL drivers;
• USB core drivers;
• DesignWare USB3 driver;
• USB Gadget drivers;
• USB Host Controller drivers;
• USB Serial drivers;
• USB Type-C Connector System Software Interface driver;
• USB over IP driver;
• VFIO drivers;
• Virtio Host (VHOST) subsystem;
• Framebuffer layer;
• Xen hypervisor drivers;
• File systems infrastructure;
• BTRFS file system;
• Ext4 file system;
• F2FS file system;
• GFS2 file system;
• JFFS2 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;
• Syscall compatibility layer;
• Memory Management;
• Memory management;
• Objagg library;
• Perf events;
• Syscall interfaces;
• Virtio network driver;
• VMware vSockets driver;
• KCM (Kernel Connection Multiplexor) sockets driver;
• Netfilter;
• Tracing infrastructure;
• io_uring subsystem;
• Control group (cgroup);
• DMA mapping infrastructure;
• Locking primitives;
• Padata parallel execution mechanism;
• Scheduler infrastructure;
• Closures library;
• Radix Tree data structure library;
• Kernel userspace event delivery library;
• KUnit for arithmetic overflow checks;
• Bluetooth subsystem;
• Ethernet bridge;
• CAN network layer;
• Ceph Core library;
• Networking core;
• Ethtool driver;
• IPv4 networking;
• IPv6 networking;
• IUCV driver;
• MAC80211 subsystem;
• Multipath TCP;
• Network traffic control;…