CVE-2024-42160

In the Linux kernel, the following vulnerability has been resolved: f2fs: check validation of fault attrs in f2fs_build_fault_attr() - It missed to check validation of fault attrs in parse_options(), let's fix to add check condition in f2fs_build_fault_attr(). - Use f2fs_build_fault_attr() in __sbi_store() to clean up code.

The Linux Kernel, the operating system core itself.

Security Fix(es):

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

NFSD: Fix the behavior of READ near OFFSET_MAX

Dan Aloni reports: > Due to commit 8cfb9015280d ("NFS: Always provide aligned buffers to > the RPC read layers") on the client, a read of 0xfff is aligned up > to server rsize of 0x1000. > > As a result, in a test where the server has a file of size > 0x7fffffffffffffff, and the client tries to read from the offset > 0x7ffffffffffff000, the read causes loff_t overflow in the server > and it returns an NFS code of EINVAL to the client. The client as > a result indefinitely retries the request.

The Linux NFS client does not handle NFS?ERR_INVAL, even though all NFS specifications permit servers to return that status code for a READ.

Instead of NFS?ERR_INVAL, have out-of-range READ requests succeed and return a short result. Set the EOF flag in the result to prevent the client from retrying the READ request. This behavior appears to be consistent with Solaris NFS servers.

Note that NFSv3 and NFSv4 use u64 offset values on the wire. These must be converted to loff_t internally before use -- an implicit type cast is not adequate for this purpose. Otherwise VFS checks against sb->s_maxbytes do not work properly.(CVE-2022-48827)

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

net: can: j1939: enhanced error handling for tightly received RTS messages in xtp_rx_rts_session_new

This patch enhances error handling in scenarios with RTS (Request to Send) messages arriving closely. It replaces the less informative WARN_ON_ONCE backtraces with a new error handling method. This provides clearer error messages and allows for the early termination of problematic sessions. Previously, sessions were only released at the end of j1939_xtp_rx_rts().

Potentially this could be reproduced with something like: testj1939 -r vcan0:0x80 & while true; do # send first RTS cansend vcan0 18EC8090#1014000303002301; # send second RTS cansend vcan0 18EC8090#1014000303002301; # send abort cansend vcan0 18EC8090#ff00000000002301; done(CVE-2023-52887)

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

kunit: Fix kthread reference

There is a race condition when a kthread finishes after the deadline and before the call to kthread_stop(), which may lead to use after free.(CVE-2024-38561)

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

net: stmmac: move the EST lock to struct stmmac_priv

Reinitialize the whole EST structure would also reset the mutex lock which is embedded in the EST structure, and then trigger the following warning. To address this, move the lock to struct stmmac_priv. We also need to reacquire the mutex lock when doing this initialization.

DEBUG_LOCKS_WARN_ON(lock->magic != lock) WARNING: CPU: 3 PID: 505 at kernel/locking/mutex.c:587 __mutex_lock+0xd84/0x1068 Modules linked in: CPU: 3 PID: 505 Comm: tc Not tainted 6.9.0-rc6-00053-g0106679839f7-dirty #29 Hardware name: NXP i.MX8MPlus EVK board (DT) pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : __mutex_lock+0xd84/0x1068 lr : __mutex_lock+0xd84/0x1068 sp : ffffffc0864e3570 x29: ffffffc0864e3570 x28: ffffffc0817bdc78 x27: 0000000000000003 x26: ffffff80c54f1808 x25: ffffff80c9164080 x24: ffffffc080d723ac x23: 0000000000000000 x22: 0000000000000002 x21: 0000000000000000 x20: 0000000000000000 x19: ffffffc083bc3000 x18: ffffffffffffffff x17: ffffffc08117b080 x16: 0000000000000002 x15: ffffff80d2d40000 x14: 00000000000002da x13: ffffff80d2d404b8 x12: ffffffc082b5a5c8 x11: ffffffc082bca680 x10: ffffffc082bb2640 x9 : ffffffc082bb2698 x8 : 0000000000017fe8 x7 : c0000000ffffefff x6 : 0000000000000001 x5 : ffffff8178fe0d48 x4 : 0000000000000000 x3 : 0000000000000027 x2 : ffffff8178fe0d50 x1 : 0000000000000000 x0 : 0000000000000000 …

The Linux Kernel, the operating system core itself.

Security Fix(es):

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

s390/qeth: fix deadlock during failing recovery

Commit 0b9902c1fcc5 ("s390/qeth: fix deadlock during recovery") removed taking discipline_mutex inside qeth_do_reset(), fixing potential deadlocks. An error path was missed though, that still takes discipline_mutex and thus has the original deadlock potential.

Intermittent deadlocks were seen when a qeth channel path is configured offline, causing a race between qeth_do_reset and ccwgroup_remove. Call qeth_set_offline() directly in the qeth_do_reset() error case and then a new variant of ccwgroup_set_offline(), without taking discipline_mutex.(CVE-2021-47382)

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

NFSD: Fix the behavior of READ near OFFSET_MAX

Dan Aloni reports: > Due to commit 8cfb9015280d ("NFS: Always provide aligned buffers to > the RPC read layers") on the client, a read of 0xfff is aligned up > to server rsize of 0x1000. > > As a result, in a test where the server has a file of size > 0x7fffffffffffffff, and the client tries to read from the offset > 0x7ffffffffffff000, the read causes loff_t overflow in the server > and it returns an NFS code of EINVAL to the client. The client as > a result indefinitely retries the request.

The Linux NFS client does not handle NFS?ERR_INVAL, even though all NFS specifications permit servers to return that status code for a READ.

Instead of NFS?ERR_INVAL, have out-of-range READ requests succeed and return a short result. Set the EOF flag in the result to prevent the client from retrying the READ request. This behavior appears to be consistent with Solaris NFS servers.

Note that NFSv3 and NFSv4 use u64 offset values on the wire. These must be converted to loff_t internally before use -- an implicit type cast is not adequate for this purpose. Otherwise VFS checks against sb->s_maxbytes do not work properly.(CVE-2022-48827)

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

net: can: j1939: enhanced error handling for tightly received RTS messages in xtp_rx_rts_session_new

This patch enhances error handling in scenarios with RTS (Request to Send) messages arriving closely. It replaces the less informative WARN_ON_ONCE backtraces with a new error handling method. This provides clearer error messages and allows for the early termination of problematic sessions. Previously, sessions were only released at the end of j1939_xtp_rx_rts().

Potentially this could be reproduced with something like: testj1939 -r vcan0:0x80 & while true; do # send first RTS cansend vcan0 18EC8090#1014000303002301; # send second RTS cansend vcan0 18EC8090#1014000303002301; # send abort cansend vcan0 18EC8090#ff00000000002301; done(CVE-2023-52887)

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

The Linux Kernel, the operating system core itself.

Security Fix(es):

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

s390/qeth: fix deadlock during failing recovery

Commit 0b9902c1fcc5 ("s390/qeth: fix deadlock during recovery") removed taking discipline_mutex inside qeth_do_reset(), fixing potential deadlocks. An error path was missed though, that still takes discipline_mutex and thus has the original deadlock potential.

Intermittent deadlocks were seen when a qeth channel path is configured offline, causing a race between qeth_do_reset and ccwgroup_remove. Call qeth_set_offline() directly in the qeth_do_reset() error case and then a new variant of ccwgroup_set_offline(), without taking discipline_mutex.(CVE-2021-47382)

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

ALSA: scarlett2: Add clamp() in scarlett2_mixer_ctl_put()

Ensure the value passed to scarlett2_mixer_ctl_put() is between 0 and SCARLETT2_MIXER_MAX_VALUE so we don't attempt to access outside scarlett2_mixer_values[].(CVE-2023-52674)

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

media: gspca: cpia1: shift-out-of-bounds in set_flicker

Syzkaller reported the following issue: UBSAN: shift-out-of-bounds in drivers/media/usb/gspca/cpia1.c:1031:27 shift exponent 245 is too large for 32-bit type 'int'

When the value of the variable "sd->params.exposure.gain" exceeds the number of bits in an integer, a shift-out-of-bounds error is reported. It is triggered because the variable "currentexp" cannot be left-shifted by more than the number of bits in an integer. In order to avoid invalid range during left-shift, the conditional expression is added.(CVE-2023-52764)

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

net: can: j1939: enhanced error handling for tightly received RTS messages in xtp_rx_rts_session_new

This patch enhances error handling in scenarios with RTS (Request to Send) messages arriving closely. It replaces the less informative WARN_ON_ONCE backtraces with a new error handling method. This provides clearer error messages and allows for the early termination of problematic sessions. Previously, sessions were only released at the end of j1939_xtp_rx_rts().

Potentially this could be reproduced with something like: testj1939 -r vcan0:0x80 & while true; do # send first RTS cansend vcan0 18EC8090#1014000303002301; # send second RTS cansend vcan0 18EC8090#1014000303002301; # send abort cansend vcan0 18EC8090#ff00000000002301; done(CVE-2023-52887)

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

The Linux Kernel, the operating system core itself.

Security Fix(es):

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

ethernet: Fix error handling in xemaclite_of_probe

This node pointer is returned by of_parse_phandle() with refcount incremented in this function. Calling of_node_put() to avoid the refcount leak. As the remove function do.(CVE-2022-48860)

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

HID: core: remove unnecessary WARN_ON() in implement()

Syzkaller hit a warning [1] in a call to implement() when trying to write a value into a field of smaller size in an output report.

Since implement() already has a warn message printed out with the help of hid_warn() and value in question gets trimmed with: ... value &= m; ... WARN_ON may be considered superfluous. Remove it to suppress future syzkaller triggers.

[1] WARNING: CPU: 0 PID: 5084 at drivers/hid/hid-core.c:1451 implement drivers/hid/hid-core.c:1451 [inline] WARNING: CPU: 0 PID: 5084 at drivers/hid/hid-core.c:1451 hid_output_report+0x548/0x760 drivers/hid/hid-core.c:1863 Modules linked in: CPU: 0 PID: 5084 Comm: syz-executor424 Not tainted 6.9.0-rc7-syzkaller-00183-gcf87f46fd34d #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024 RIP: 0010:implement drivers/hid/hid-core.c:1451 [inline] RIP: 0010:hid_output_report+0x548/0x760 drivers/hid/hid-core.c:1863 ... Call Trace: <TASK> __usbhid_submit_report drivers/hid/usbhid/hid-core.c:591 [inline] usbhid_submit_report+0x43d/0x9e0 drivers/hid/usbhid/hid-core.c:636 hiddev_ioctl+0x138b/0x1f00 drivers/hid/usbhid/hiddev.c:726 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:904 [inline] __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:890 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf5/0x240 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f ...(CVE-2024-39509)

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

filelock: Remove locks reliably when fcntl/close race is detected

When fcntl_setlk() races with close(), it removes the created lock with do_lock_file_wait(). However, LSMs can allow the first do_lock_file_wait() that created the lock while denying the second do_lock_file_wait() that tries to remove the lock. Separately, posix_lock_file() could also fail to remove a lock due to GFP_KERNEL allocation failure (when splitting a range in the middle).

After the bug has been triggered, use-after-free reads will occur in lock_get_status() when userspace reads /proc/locks. This can likely be used to read arbitrary kernel memory, but can't corrupt kernel memory.

Fix it by calling locks_remove_posix() instead, which is designed to reliably get rid of POSIX locks associated with the given file and files_struct and is also used by filp_flush().(CVE-2024-41012)

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

nilfs2: fix kernel bug on rename operation of broken directory

Syzbot reported that in rename directory operation on broken directory on nilfs2, __block_write_begin_int() called to prepare block write may fail BUG_ON check for access exceeding the folio/page size.

This is because nilfs_dotdot(), which gets parent directory reference entry ("..") of the directory to be moved or renamed, does not check consistency enough, and may return location exceeding folio/page size for broken directories.

Fix this issue by checking required directory entries ("." and "..") in the first chunk of the directory in nilfs_dotdot().(CVE-2024-41034)

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

USB: core: Fix duplicate endpoint bug by clearing reserved bits in the descriptor

Syzbot has identified a bug in usbcore (see the Closes: tag below) caused by our assumption that the reserved bits in an endpoint descriptor's bEndpointAddress field will…

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 …

Root has patched CVE-2024-42160 in the linux package for Root:Debian:11. Multiple fixed versions available.

In the Linux kernel, the following vulnerability has been resolved: f2fs: check validation of fault attrs in f2fs_build_fault_attr() - It missed to check validation of fault attrs in parse_options(), let's fix to add check condition in f2fs_build_fault_attr(). - Use f2fs_build_fault_attr() in __sbi_store() to clean up code.

[ Ubuntu: 4.15.0-234.245 ]

• CVE-url: https://ubuntu.com/security/CVE-2024-42236
  • usb: gadget: configfs: Prevent OOB read/write in usb_string_copy()
• CVE-url: https://ubuntu.com/security/CVE-2024-41095
  • drm/nouveau/dispnv04: fix null pointer dereference in nv17_tv_get_ld_modes
• CVE-url: https://ubuntu.com/security/CVE-2024-41098
  • ata: libata-core: Fix null pointer dereference on error
• CVE-url: https://ubuntu.com/security/CVE-2024-42244
  • USB: serial: mos7840: fix crash on resume
• CVE-url: https://ubuntu.com/security/CVE-2024-41089
  • drm/nouveau/dispnv04: fix null pointer dereference in nv17_tv_get_hd_modes
• CVE-url: https://ubuntu.com/security/CVE-2024-42232
  • libceph: fix race between delayed_work() and ceph_monc_stop()
• CVE-url: https://ubuntu.com/security/CVE-2024-42153
  • i2c: pnx: Fix potential deadlock warning from del_timer_sync() call in isr
• CVE-url: https://ubuntu.com/security/CVE-2022-48791
  • scsi: pm80xx: Fix TMF task completion race condition
  • scsi: pm8001: Fix use-after-free for aborted TMF sas_task
• CVE-url: https://ubuntu.com/security/CVE-2022-48788
  • nvme-rdma: fix possible use-after-free in transport error_recovery work
• CVE-url: https://ubuntu.com/security/CVE-2022-48792
  • scsi: pm8001: Fix use-after-free for aborted SSP/STP sas_task
• CVE-url: https://ubuntu.com/security/CVE-2022-48790
  • nvme: fix a possible use-after-free in controller reset during load
• CVE-url: https://ubuntu.com/security/CVE-2024-42154
  • tcp_metrics: validate source addr length
• CVE-url: https://ubuntu.com/security/CVE-2024-38596
  • af_unix: Fix data races in unix_release_sock/unix_stream_sendmsg
• CVE-url: https://ubuntu.com/security/CVE-2024-36270
  • netfilter: tproxy: bail out if IP has been disabled on the device
• CVE-url: https://ubuntu.com/security/CVE-2024-38780
  • dma-buf/sw-sync: don't enable IRQ from sync_print_obj()
• CVE-url: https://ubuntu.com/security/CVE-2024-36886
  • tipc: fix UAF in error path
• CVE-url: https://ubuntu.com/security/CVE-2024-42068
  • bpf: Take return from set_memory_ro() into account with bpf_prog_lock_ro()
• CVE-url: https://ubuntu.com/security/CVE-2024-42156
  • s390/pkey: Wipe copies of clear-key structures on failure
• CVE-url: https://ubuntu.com/security/CVE-2024-42079
  • gfs2: Fix NULL pointer dereference in gfs2_log_flush
• CVE-url: https://ubuntu.com/security/CVE-2024-42223
  • media: dvb-frontends: tda10048: Fix integer overflow
• CVE-url: https://ubuntu.com/security/CVE-2024-42157
  • s390/pkey: Wipe sensitive data on failure
• CVE-url: https://ubuntu.com/security/CVE-2024-42160
  • f2fs: indicate shutdown f2fs to allow unmount successfully
  • f2fs: support fault_type mount option
  • f2fs: check validation of fault attrs in f2fs_build_fault_attr()
• CVE-url: https://ubuntu.com/security/CVE-2024-42224
  • net: dsa: mv88e6xxx: Correct check for empty list
• CVE-url: https://ubuntu.com/security/CVE-2024-38570
  • gfs2: Rename sd_{ glock => kill }_wait
  • gfs2: Fix potential glock use-after-free on unmount
• CVE-url: https://ubuntu.com/security/CVE-2024-38583
  • nilfs2: fix use-after-free of timer for log writer thread
  • nilfs2: fix unexpected freezing of nilfs_segctor_sync()
  • nilfs2: fix potential hang in nilfs_detach_log_writer()
• CVE-url: https://ubuntu.com/security/CVE-2024-42070
  • netfilter: nf_tables: fully validate NFT_DATA_VALUE on store to data registers
• CVE-url: https://ubuntu.com/security/CVE-2024-42077
  • ocfs2: fix DIO failure due to insufficient transaction credits
• CVE-url: https://ubuntu.com/security/CVE-2024-42226
  • usb: xhci: prevent potential failure in handle_tx_event() for Transfer events without TRB
• CVE-url: https://ubuntu.com/security/CVE-2024-42228
  • drm/amdgpu: Using uninitialized value *size when…

• CVE-url: https://ubuntu.com/security/CVE-2024-42236
  • usb: gadget: configfs: Prevent OOB read/write in usb_string_copy()
• CVE-url: https://ubuntu.com/security/CVE-2024-41095
  • drm/nouveau/dispnv04: fix null pointer dereference in nv17_tv_get_ld_modes
• CVE-url: https://ubuntu.com/security/CVE-2024-41098
  • ata: libata-core: Fix null pointer dereference on error
• CVE-url: https://ubuntu.com/security/CVE-2024-42244
  • USB: serial: mos7840: fix crash on resume
• CVE-url: https://ubuntu.com/security/CVE-2024-41089
  • drm/nouveau/dispnv04: fix null pointer dereference in nv17_tv_get_hd_modes
• CVE-url: https://ubuntu.com/security/CVE-2024-42232
  • libceph: fix race between delayed_work() and ceph_monc_stop()
• CVE-url: https://ubuntu.com/security/CVE-2024-42153
  • i2c: pnx: Fix potential deadlock warning from del_timer_sync() call in isr
• CVE-url: https://ubuntu.com/security/CVE-2022-48791
  • scsi: pm80xx: Fix TMF task completion race condition
  • scsi: pm8001: Fix use-after-free for aborted TMF sas_task
• CVE-url: https://ubuntu.com/security/CVE-2022-48788
  • nvme-rdma: fix possible use-after-free in transport error_recovery work
• CVE-url: https://ubuntu.com/security/CVE-2022-48792
  • scsi: pm8001: Fix use-after-free for aborted SSP/STP sas_task
• CVE-url: https://ubuntu.com/security/CVE-2022-48790
  • nvme: fix a possible use-after-free in controller reset during load
• CVE-url: https://ubuntu.com/security/CVE-2024-42154
  • tcp_metrics: validate source addr length
• CVE-url: https://ubuntu.com/security/CVE-2024-38596
  • af_unix: Fix data races in unix_release_sock/unix_stream_sendmsg
• CVE-url: https://ubuntu.com/security/CVE-2024-36270
  • netfilter: tproxy: bail out if IP has been disabled on the device
• CVE-url: https://ubuntu.com/security/CVE-2024-38780
  • dma-buf/sw-sync: don't enable IRQ from sync_print_obj()
• CVE-url: https://ubuntu.com/security/CVE-2024-36886
  • tipc: fix UAF in error path
• CVE-url: https://ubuntu.com/security/CVE-2024-42068
  • bpf: Take return from set_memory_ro() into account with bpf_prog_lock_ro()
• CVE-url: https://ubuntu.com/security/CVE-2024-42156
  • s390/pkey: Wipe copies of clear-key structures on failure
• CVE-url: https://ubuntu.com/security/CVE-2024-42079
  • gfs2: Fix NULL pointer dereference in gfs2_log_flush
• CVE-url: https://ubuntu.com/security/CVE-2024-42223
  • media: dvb-frontends: tda10048: Fix integer overflow
• CVE-url: https://ubuntu.com/security/CVE-2024-42157
  • s390/pkey: Wipe sensitive data on failure
• CVE-url: https://ubuntu.com/security/CVE-2024-42160
  • f2fs: indicate shutdown f2fs to allow unmount successfully
  • f2fs: support fault_type mount option
  • f2fs: check validation of fault attrs in f2fs_build_fault_attr()
• CVE-url: https://ubuntu.com/security/CVE-2024-42224
  • net: dsa: mv88e6xxx: Correct check for empty list
• CVE-url: https://ubuntu.com/security/CVE-2024-38570
  • gfs2: Rename sd_{ glock => kill }_wait
  • gfs2: Fix potential glock use-after-free on unmount
• CVE-url: https://ubuntu.com/security/CVE-2024-38583
  • nilfs2: fix use-after-free of timer for log writer thread
  • nilfs2: fix unexpected freezing of nilfs_segctor_sync()
  • nilfs2: fix potential hang in nilfs_detach_log_writer()
• CVE-url: https://ubuntu.com/security/CVE-2024-42070
  • netfilter: nf_tables: fully validate NFT_DATA_VALUE on store to data registers
• CVE-url: https://ubuntu.com/security/CVE-2024-42077
  • ocfs2: fix DIO failure due to insufficient transaction credits
• CVE-url: https://ubuntu.com/security/CVE-2024-42226
  • usb: xhci: prevent potential failure in handle_tx_event() for Transfer events without TRB
• CVE-url: https://ubuntu.com/security/CVE-2024-42228
  • drm/amdgpu: Using uninitialized value *size when calling amdgpu_vce_cs_reloc

• CVE-url: https://ubuntu.com/security/CVE-2024-42236
  • usb: gadget: configfs: Prevent OOB read/write in usb_string_copy()
• CVE-url: https://ubuntu.com/security/CVE-2024-41095
  • drm/nouveau/dispnv04: fix null pointer dereference in nv17_tv_get_ld_modes
• CVE-url: https://ubuntu.com/security/CVE-2024-41098
  • ata: libata-core: Fix null pointer dereference on error
• CVE-url: https://ubuntu.com/security/CVE-2024-42244
  • USB: serial: mos7840: fix crash on resume
• CVE-url: https://ubuntu.com/security/CVE-2024-41089
  • drm/nouveau/dispnv04: fix null pointer dereference in nv17_tv_get_hd_modes
• CVE-url: https://ubuntu.com/security/CVE-2024-42232
  • libceph: fix race between delayed_work() and ceph_monc_stop()
• CVE-url: https://ubuntu.com/security/CVE-2024-42153
  • i2c: pnx: Fix potential deadlock warning from del_timer_sync() call in isr
• CVE-url: https://ubuntu.com/security/CVE-2022-48791
  • scsi: pm80xx: Fix TMF task completion race condition
  • scsi: pm8001: Fix use-after-free for aborted TMF sas_task
• CVE-url: https://ubuntu.com/security/CVE-2022-48788
  • nvme-rdma: fix possible use-after-free in transport error_recovery work
• CVE-url: https://ubuntu.com/security/CVE-2022-48792
  • scsi: pm8001: Fix use-after-free for aborted SSP/STP sas_task
• CVE-url: https://ubuntu.com/security/CVE-2022-48790
  • nvme: fix a possible use-after-free in controller reset during load
• CVE-url: https://ubuntu.com/security/CVE-2024-42154
  • tcp_metrics: validate source addr length
• CVE-url: https://ubuntu.com/security/CVE-2024-38596
  • af_unix: Fix data races in unix_release_sock/unix_stream_sendmsg
• CVE-url: https://ubuntu.com/security/CVE-2024-36270
  • netfilter: tproxy: bail out if IP has been disabled on the device
• CVE-url: https://ubuntu.com/security/CVE-2024-38780
  • dma-buf/sw-sync: don't enable IRQ from sync_print_obj()
• CVE-url: https://ubuntu.com/security/CVE-2024-36886
  • tipc: fix UAF in error path
• CVE-url: https://ubuntu.com/security/CVE-2024-42068
  • bpf: Take return from set_memory_ro() into account with bpf_prog_lock_ro()
• CVE-url: https://ubuntu.com/security/CVE-2024-42156
  • s390/pkey: Wipe copies of clear-key structures on failure
• CVE-url: https://ubuntu.com/security/CVE-2024-42079
  • gfs2: Fix NULL pointer dereference in gfs2_log_flush
• CVE-url: https://ubuntu.com/security/CVE-2024-42223
  • media: dvb-frontends: tda10048: Fix integer overflow
• CVE-url: https://ubuntu.com/security/CVE-2024-42157
  • s390/pkey: Wipe sensitive data on failure
• CVE-url: https://ubuntu.com/security/CVE-2024-42160
  • f2fs: indicate shutdown f2fs to allow unmount successfully
  • f2fs: support fault_type mount option
  • f2fs: check validation of fault attrs in f2fs_build_fault_attr()
• CVE-url: https://ubuntu.com/security/CVE-2024-42224
  • net: dsa: mv88e6xxx: Correct check for empty list
• CVE-url: https://ubuntu.com/security/CVE-2024-38570
  • gfs2: Rename sd_{ glock => kill }_wait
  • gfs2: Fix potential glock use-after-free on unmount
• CVE-url: https://ubuntu.com/security/CVE-2024-38583
  • nilfs2: fix use-after-free of timer for log writer thread
  • nilfs2: fix unexpected freezing of nilfs_segctor_sync()
  • nilfs2: fix potential hang in nilfs_detach_log_writer()
• CVE-url: https://ubuntu.com/security/CVE-2024-42070
  • netfilter: nf_tables: fully validate NFT_DATA_VALUE on store to data registers
• CVE-url: https://ubuntu.com/security/CVE-2024-42077
  • ocfs2: fix DIO failure due to insufficient transaction credits
• CVE-url: https://ubuntu.com/security/CVE-2024-42226
  • usb: xhci: prevent potential failure in handle_tx_event() for Transfer events without TRB
• CVE-url: https://ubuntu.com/security/CVE-2024-42228
  • drm/amdgpu: Using uninitialized value *size when calling amdgpu_vce_cs_reloc

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

f2fs: check validation of fault attrs in f2fs_build_fault_attr()

• It missed to check validation of fault attrs in parse_options(), let's fix to add check condition in f2fs_build_fault_attr().
• Use f2fs_build_fault_attr() in __sbi_store() to clean up code.

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.

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:

• GPU drivers;
• Network drivers;
• SCSI drivers;
• F2FS file system;
• BPF subsystem;
• IPv4 networking; (CVE-2024-42160, CVE-2024-42159, CVE-2024-42154, CVE-2024-41009, CVE-2024-42228, CVE-2024-42224)

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:

• GPU drivers;
• Network drivers;
• SCSI drivers;
• F2FS file system;
• BPF subsystem;
• IPv4 networking; (CVE-2024-42160, CVE-2024-42159, CVE-2024-42154, CVE-2024-41009, CVE-2024-42228, CVE-2024-42224)

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:

• GPU drivers;
• Network drivers;
• SCSI drivers;
• F2FS file system;
• BPF subsystem;
• IPv4 networking; (CVE-2024-42160, CVE-2024-42159, CVE-2024-42224, CVE-2024-41009, CVE-2024-42154, CVE-2024-42228)

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:

• GPU drivers;
• Network drivers;
• SCSI drivers;
• F2FS file system;
• BPF subsystem;
• IPv4 networking; (CVE-2024-42228, CVE-2024-42154, CVE-2024-42160, CVE-2024-42159, CVE-2024-41009, CVE-2024-42224)

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:

• GPU drivers;
• BTRFS file system;
• F2FS file system;
• GFS2 file system;
• BPF subsystem;
• Netfilter;
• RxRPC session sockets;
• Integrity Measurement Architecture(IMA) framework; (CVE-2024-39496, CVE-2024-41009, CVE-2024-26677, CVE-2024-42160, CVE-2024-27012, CVE-2024-42228, CVE-2024-39494, CVE-2024-38570)

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:

• GPU drivers;
• BTRFS file system;
• F2FS file system;
• GFS2 file system;
• BPF subsystem;
• Netfilter;
• RxRPC session sockets;
• Integrity Measurement Architecture(IMA) framework; (CVE-2024-27012, CVE-2024-39496, CVE-2024-26677, CVE-2024-42228, CVE-2024-38570, CVE-2024-39494, CVE-2024-42160, CVE-2024-41009)

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:

• GPU drivers;
• BTRFS file system;
• F2FS file system;
• GFS2 file system;
• BPF subsystem;
• Netfilter;
• RxRPC session sockets;
• Integrity Measurement Architecture(IMA) framework; (CVE-2024-39494, CVE-2024-38570, CVE-2024-27012, CVE-2024-39496, CVE-2024-42160, CVE-2024-41009, CVE-2024-42228, CVE-2024-26677)

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:

• GPU drivers;
• BTRFS file system;
• F2FS file system;
• GFS2 file system;
• BPF subsystem;
• Netfilter;
• RxRPC session sockets;
• Integrity Measurement Architecture(IMA) framework; (CVE-2024-41009, CVE-2024-26677, CVE-2024-42160, CVE-2024-39494, CVE-2024-39496, CVE-2024-38570, CVE-2024-27012, CVE-2024-42228)

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:

• GPU drivers;
• BTRFS file system;
• F2FS file system;
• GFS2 file system;
• BPF subsystem;
• Netfilter;
• RxRPC session sockets;
• Integrity Measurement Architecture(IMA) framework; (CVE-2024-27012, CVE-2024-38570, CVE-2024-42228, CVE-2024-41009, CVE-2024-39494, CVE-2024-42160, CVE-2024-39496, CVE-2024-26677)

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:

• GPU drivers;
• Modular ISDN driver;
• MMC subsystem;
• SCSI drivers;
• F2FS file system;
• GFS2 file system;
• Netfilter;
• RxRPC session sockets;
• Integrity Measurement Architecture(IMA) framework; (CVE-2021-47188, CVE-2024-27012, CVE-2024-42228, CVE-2022-48791, CVE-2024-39494, CVE-2022-48863, CVE-2024-26787, CVE-2024-42160, CVE-2024-38570, CVE-2024-26677)

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:

• GPU drivers;
• Modular ISDN driver;
• MMC subsystem;
• SCSI drivers;
• F2FS file system;
• GFS2 file system;
• Netfilter;
• RxRPC session sockets;
• Integrity Measurement Architecture(IMA) framework; (CVE-2021-47188, CVE-2024-42160, CVE-2024-42228, CVE-2022-48863, CVE-2024-26677, CVE-2024-26787, CVE-2024-38570, CVE-2024-39494, CVE-2022-48791, CVE-2024-27012)

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:

• GPU drivers;
• Modular ISDN driver;
• MMC subsystem;
• SCSI drivers;
• F2FS file system;
• GFS2 file system;
• Netfilter;
• RxRPC session sockets;
• Integrity Measurement Architecture(IMA) framework; (CVE-2021-47188, CVE-2024-39494, CVE-2022-48791, CVE-2022-48863, CVE-2024-42228, CVE-2024-38570, CVE-2024-42160, CVE-2024-26787, CVE-2024-27012, CVE-2024-26677)

It was discovered that the JFS file system contained an out-of-bounds read vulnerability when printing xattr debug information. A local attacker could use this to cause a denial of service (system crash).

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:

• GPU drivers;
• Greybus drivers;
• Modular ISDN driver;
• Multiple devices driver;
• Network drivers;
• SCSI drivers;
• VFIO drivers;
• F2FS file system;
• GFS2 file system;
• JFS file system;
• NILFS2 file system;
• Kernel debugger infrastructure;
• Bluetooth subsystem;
• IPv4 networking;
• L2TP protocol;
• Netfilter;
• RxRPC session sockets; (CVE-2024-42154, CVE-2023-52527, CVE-2024-26733, CVE-2024-42160, CVE-2021-47188, CVE-2024-38570, CVE-2024-26851, CVE-2024-26984, CVE-2024-26677, CVE-2024-39480, CVE-2024-27398, CVE-2022-48791, CVE-2024-42224, CVE-2024-38583, CVE-2024-40902, CVE-2023-52809, CVE-2024-39495, CVE-2024-26651, CVE-2024-26880, CVE-2024-42228, CVE-2024-27437, CVE-2022-48863)

It was discovered that the JFS file system contained an out-of-bounds read vulnerability when printing xattr debug information. A local attacker could use this to cause a denial of service (system crash).

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:

• GPU drivers;
• Greybus drivers;
• Modular ISDN driver;
• Multiple devices driver;
• Network drivers;
• SCSI drivers;
• VFIO drivers;
• F2FS file system;
• GFS2 file system;
• JFS file system;
• NILFS2 file system;
• Kernel debugger infrastructure;
• Bluetooth subsystem;
• IPv4 networking;
• L2TP protocol;
• Netfilter;
• RxRPC session sockets; (CVE-2024-42154, CVE-2023-52527, CVE-2024-26733, CVE-2024-42160, CVE-2021-47188, CVE-2024-38570, CVE-2024-26851, CVE-2024-26984, CVE-2024-26677, CVE-2024-39480, CVE-2024-27398, CVE-2022-48791, CVE-2024-42224, CVE-2024-38583, CVE-2024-40902, CVE-2023-52809, CVE-2024-39495, CVE-2024-26651, CVE-2024-26880, CVE-2024-42228, CVE-2024-27437, CVE-2022-48863)

Chenyuan Yang discovered that the CEC driver driver in the Linux kernel contained a use-after-free vulnerability. A local attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2024-23848)

It was discovered that the JFS file system contained an out-of-bounds read vulnerability when printing xattr debug information. A local attacker could use this to cause a denial of service (system crash). (CVE-2024-40902)

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;
• PA-RISC architecture;
• PowerPC architecture;
• RISC-V architecture;
• User-Mode Linux (UML);
• x86 architecture;
• Block layer subsystem;
• ACPI drivers;
• Drivers core;
• Null block device driver;
• Character device driver;
• TPM device driver;
• Clock framework and drivers;
• CPU frequency scaling framework;
• Hardware crypto device drivers;
• CXL (Compute Express Link) drivers;
• Buffer Sharing and Synchronization framework;
• DMA engine subsystem;
• EFI core;
• FPGA Framework;
• GPU drivers;
• Greybus drivers;
• HID subsystem;
• HW tracing;
• I2C subsystem;
• IIO subsystem;
• InfiniBand drivers;
• Input Device (Mouse) drivers;
• Mailbox framework;
• Media drivers;
• Microchip PCI driver;
• VMware VMCI Driver;
• MMC subsystem;
• Network drivers;
• PCI subsystem;
• x86 platform drivers;
• PTP clock framework;
• S/390 drivers;
• SCSI drivers;
• SoundWire subsystem;
• Sonic Silicon Backplane drivers;
• Greybus lights staging drivers;
• Thermal drivers;
• TTY drivers;
• USB subsystem;
• VFIO drivers;
• Framebuffer layer;
• Watchdog drivers;
• 9P distributed file system;
• BTRFS file system;
• File systems infrastructure;
• Ext4 file system;
• F2FS file system;
• JFS file system;
• Network file system server daemon;
• NILFS2 file system;
• NTFS3 file system;
• SMB network file system;
• Tracing file system;
• IOMMU subsystem;
• Tracing infrastructure;
• io_uring subsystem;
• Core kernel;
• BPF subsystem;
• Kernel debugger infrastructure;
• DMA mapping infrastructure;
• IRQ subsystem;
• Memory management;
• 9P file system network protocol;
• Amateur Radio drivers;
• B.A.T.M.A.N. meshing protocol;
• Ethernet bridge;
• Networking core;
• Ethtool driver;
• IPv4 networking;
• IPv6 networking;
• MAC80211 subsystem;
• Multipath TCP;
• Netfilter;
• NET/ROM layer;
• NFC subsystem;
• Network traffic control;
• Sun RPC protocol;
• TIPC protocol;
• TLS protocol;
• Unix domain sockets;
• Wireless networking;
• XFRM subsystem;
• AppArmor security module;
• Integrity Measurement Architecture(IMA) framework;
• Landlock security;
• Linux Security Modules (LSM) Framework;
• SELinux security module;
• Simplified Mandatory Access Control Kernel framework;
• ALSA framework;
• HD-audio driver;
• SOF drivers;
• KVM core; (CVE-2024-39498, CVE-2024-33847, CVE-2024-39510, CVE-2024-39462, CVE-2024-40930, CVE-2024-38634, CVE-2024-40962, CVE-2024-37078, CVE-2024-39371, CVE-2024-40972, CVE-2024-41002, CVE-2024-40920, CVE-2024-40982, CVE-2024-40915, CVE-2024-40942, CVE-2024-42154, CVE-2024-40937, CVE-2024-40967, CVE-2024-40909, CVE-2024-36244, CVE-2024-33619, CVE-2024-39277, CVE-2024-40900, CVE-2024-38661, CVE-2024-40974, CVE-2024-38618, CVE-2024-32936, CVE-2024-40906, CVE-2024-40919, CVE-2024-39470, CVE-2024-38390, CVE-2024-40966, CVE-2024-39467, CVE-2024-40938, CVE-2024-39471, CVE-2024-39485, CVE-2024-39495, CVE-2024-39492, CVE-2024-39475, CVE-2024-40953, CVE-2024-40939, CVE-2024-39493, CVE-2024-38637, CVE-2024-40945, CVE-2024-41006, CVE-2024-39461, CVE-2024-40948, CVE-2024-40916, CVE-2024-40925, CVE-2024-40956, CVE-2024-40970, CVE-2024-40912, CVE-2024-33621, CVE-2024-40989,…

Ziming Zhang discovered that the VMware Virtual GPU DRM driver in the Linux kernel contained an integer overflow vulnerability. A local attacker could use this to cause a denial of service (system crash). (CVE-2022-36402)

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;
• PowerPC architecture;
• User-Mode Linux (UML);
• x86 architecture;
• Block layer subsystem;
• Cryptographic API;
• Android drivers;
• Serial ATA and Parallel ATA drivers;
• ATM drivers;
• Drivers core;
• CPU frequency scaling framework;
• Device frequency scaling framework;
• GPU drivers;
• HID subsystem;
• Hardware monitoring drivers;
• InfiniBand drivers;
• Input Device core drivers;
• Input Device (Miscellaneous) drivers;
• IOMMU subsystem;
• IRQ chip drivers;
• ISDN/mISDN subsystem;
• Modular ISDN driver;
• LED subsystem;
• Multiple devices driver;
• Media drivers;
• EEPROM drivers;
• VMware VMCI Driver;
• MMC subsystem;
• Network drivers;
• Near Field Communication (NFC) drivers;
• NVME drivers;
• Device tree and open firmware driver;
• Parport drivers;
• PCI subsystem;
• Pin controllers subsystem;
• Remote Processor subsystem;
• S/390 drivers;
• SCSI drivers;
• QCOM SoC drivers;
• Direct Digital Synthesis drivers;
• TTY drivers;
• Userspace I/O 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;
• Watchdog drivers;
• BTRFS file system;
• File systems infrastructure;
• Ext4 file system;
• F2FS file system;
• GFS2 file system;
• JFS file system;
• NILFS2 file system;
• Netfilter;
• BPF subsystem;
• Core kernel;
• DMA mapping infrastructure;
• Tracing infrastructure;
• Radix Tree data structure library;
• Kernel userspace event delivery library;
• Objagg library;
• Memory management;
• Amateur Radio drivers;
• Bluetooth subsystem;
• CAN network layer;
• Networking core;
• Ethtool driver;
• IPv4 networking;
• IPv6 networking;
• IUCV driver;
• KCM (Kernel Connection Multiplexor) sockets driver;
• MAC80211 subsystem;
• RxRPC session sockets;
• Network traffic control;
• SCTP protocol;
• Sun RPC protocol;
• TIPC protocol;
• TLS protocol;
• Wireless networking;
• AppArmor security module;
• Integrity Measurement Architecture(IMA) framework;
• Simplified Mandatory Access Control Kernel framework;
• SoC audio core drivers;
• USB sound devices; (CVE-2024-46750, CVE-2024-43853, CVE-2024-46722, CVE-2024-42311, CVE-2024-46679, CVE-2023-52918, CVE-2024-42309, CVE-2024-42160, CVE-2024-26668, CVE-2024-42271, CVE-2024-40929, CVE-2024-46747, CVE-2024-41064, CVE-2024-43839, CVE-2024-46757, CVE-2024-41059, CVE-2024-42301, CVE-2024-46737, CVE-2024-42297, CVE-2024-41015, CVE-2024-43854, CVE-2024-42289, CVE-2024-41017, CVE-2024-26787, CVE-2024-47667, CVE-2024-46675, CVE-2024-42246, CVE-2024-46723, CVE-2024-46817, CVE-2024-43841, CVE-2024-26800, CVE-2024-41098, CVE-2022-48863, CVE-2023-52531, CVE-2024-42265, CVE-2024-46828, CVE-2024-41020, CVE-2024-42305, CVE-2024-46755, CVE-2024-46744, CVE-2024-43871, CVE-2024-43884, CVE-2024-41042, CVE-2024-43914, CVE-2024-43856, CVE-2024-27397, CVE-2024-26607, CVE-2024-42228, CVE-2024-41091, CVE-2024-26677, CVE-2024-38611, CVE-2024-43867, CVE-2024-46829, CVE-2021-47188, CVE-2024-46756, CVE-2024-45025, CVE-2024-42313, CVE-2024-44947, CVE-2024-26669, CVE-2024-47668, CVE-2024-44987, CVE-2024-42295, CVE-2024-42281, CVE-2024-43880, CVE-2024-46777, CVE-2024-46780, CVE-2024-42285, CVE-2024-26891, CVE-2024-46714, CVE-2024-44999, CVE-2024-41068, CVE-2024-44944, CVE-2024-43882, CVE-2024-27051, CVE-2024-41072, CVE-2024-46783, CVE-2024-46781, CVE-2024-26885, CVE-2024-46844, CVE-2024-47669,…

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