CVE-2024-38561

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:

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 …

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.

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.

Upstream kernel version 6.6.37 fix bugs and vulnerabilities. The dwarves, 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.37 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:

• ARM32 architecture;
• ARM64 architecture;
• M68K architecture;
• OpenRISC architecture;
• PowerPC architecture;
• RISC-V architecture;
• x86 architecture;
• Block layer subsystem;
• Accessibility subsystem;
• Bluetooth drivers;
• Clock framework and drivers;
• CPU frequency scaling framework;
• Hardware crypto device drivers;
• DMA engine subsystem;
• DPLL subsystem;
• FireWire subsystem;
• EFI core;
• Qualcomm firmware drivers;
• GPIO subsystem;
• GPU drivers;
• Microsoft Hyper-V drivers;
• InfiniBand drivers;
• IOMMU subsystem;
• IRQ chip drivers;
• Macintosh device drivers;
• Multiple devices driver;
• Media drivers;
• EEPROM drivers;
• MMC subsystem;
• Network drivers;
• STMicroelectronics network drivers;
• Device tree and open firmware driver;
• HiSilicon SoC PMU drivers;
• PHY drivers;
• Pin controllers subsystem;
• Remote Processor subsystem;
• S/390 drivers;
• SCSI drivers;
• SPI subsystem;
• Media staging drivers;
• Thermal drivers;
• Userspace I/O drivers;
• USB subsystem;
• DesignWare USB3 driver;
• ACRN Hypervisor Service Module driver;
• Virtio drivers;
• 9P distributed file system;
• BTRFS file system;
• eCrypt file system;
• EROFS file system;
• File systems infrastructure;
• GFS2 file system;
• JFFS2 file system;
• Network file systems library;
• Network file system client;
• Network file system server daemon;
• NILFS2 file system;
• Proc file system;
• SMB network file system;
• Tracing file system;
• Mellanox drivers;
• Memory management;
• Socket messages infrastructure;
• Slab allocator;
• Tracing infrastructure;
• User-space API (UAPI);
• Core kernel;
• BPF subsystem;
• DMA mapping infrastructure;
• RCU subsystem;
• Dynamic debug library;
• KUnit library;
• Maple Tree data structure library;
• Heterogeneous memory management;
• Amateur Radio drivers;
• Bluetooth subsystem;
• Ethernet bridge;
• Networking core;
• IPv4 networking;
• IPv6 networking;
• Multipath TCP;
• Netfilter;
• NET/ROM layer;
• NFC subsystem;
• NSH protocol;
• Open vSwitch;
• Phonet protocol;
• SMC sockets;
• TIPC protocol;
• Unix domain sockets;
• Wireless networking;
• Key management;
• ALSA framework;
• HD-audio driver;
• Kirkwood ASoC drivers;
• MediaTek ASoC drivers; (CVE-2024-36006, CVE-2024-36922, CVE-2024-38567, CVE-2024-38584, CVE-2024-36923, CVE-2024-36892, CVE-2024-35855, CVE-2024-35853, CVE-2024-38562, CVE-2024-36920, CVE-2024-38543, CVE-2024-38576, CVE-2024-38572, CVE-2024-36898, CVE-2024-38560, CVE-2024-36004, CVE-2024-36956, CVE-2024-36881, CVE-2024-36977, CVE-2024-36955, CVE-2024-36906, CVE-2024-36013, CVE-2024-36884, CVE-2024-38563, CVE-2024-36966, CVE-2024-38547, CVE-2024-38594, CVE-2024-36926, CVE-2024-38587, CVE-2024-38566, CVE-2024-27400, CVE-2024-36941, CVE-2024-36017, CVE-2024-38544, CVE-2024-36899, CVE-2024-35851, CVE-2024-38577, CVE-2024-38590, CVE-2024-38568, CVE-2024-38559, CVE-2024-38611, CVE-2024-36887, CVE-2024-36886, CVE-2024-35996, CVE-2024-38612, CVE-2024-36925, CVE-2024-38586, CVE-2024-38596, CVE-2024-36932, CVE-2024-39482, CVE-2024-38585, CVE-2024-36033, CVE-2024-38614, CVE-2024-35852, CVE-2024-36908, CVE-2024-36939, CVE-2024-36963, CVE-2024-27401, CVE-2024-36029, CVE-2024-38540, CVE-2024-38565, CVE-2024-36927, CVE-2024-36910, CVE-2024-42134, CVE-2024-36888, CVE-2024-35859, CVE-2024-36911, CVE-2024-35947, CVE-2024-36940, CVE-2024-36921, CVE-2024-36913, CVE-2024-36943, CVE-2024-35986, CVE-2024-38616, CVE-2024-36900, CVE-2024-36954, CVE-2024-36915, CVE-2024-38602, CVE-2024-41011, CVE-2024-35991, CVE-2024-36909, CVE-2024-38603, CVE-2023-52882, CVE-2024-36953, CVE-2024-38599, CVE-2024-38574, CVE-2024-36967, CVE-2024-36895, CVE-2024-36003,…

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;
• M68K architecture;
• OpenRISC architecture;
• PowerPC architecture;
• RISC-V architecture;
• x86 architecture;
• Block layer subsystem;
• Accessibility subsystem;
• Bluetooth drivers;
• Clock framework and drivers;
• CPU frequency scaling framework;
• Hardware crypto device drivers;
• DMA engine subsystem;
• DPLL subsystem;
• FireWire subsystem;
• EFI core;
• Qualcomm firmware drivers;
• GPIO subsystem;
• GPU drivers;
• Microsoft Hyper-V drivers;
• InfiniBand drivers;
• IOMMU subsystem;
• IRQ chip drivers;
• Macintosh device drivers;
• Multiple devices driver;
• Media drivers;
• EEPROM drivers;
• MMC subsystem;
• Network drivers;
• STMicroelectronics network drivers;
• Device tree and open firmware driver;
• HiSilicon SoC PMU drivers;
• PHY drivers;
• Pin controllers subsystem;
• Remote Processor subsystem;
• S/390 drivers;
• SCSI drivers;
• SPI subsystem;
• Media staging drivers;
• Thermal drivers;
• Userspace I/O drivers;
• USB subsystem;
• DesignWare USB3 driver;
• ACRN Hypervisor Service Module driver;
• Virtio drivers;
• 9P distributed file system;
• BTRFS file system;
• eCrypt file system;
• EROFS file system;
• File systems infrastructure;
• GFS2 file system;
• JFFS2 file system;
• Network file systems library;
• Network file system client;
• Network file system server daemon;
• NILFS2 file system;
• Proc file system;
• SMB network file system;
• Tracing file system;
• Mellanox drivers;
• Memory management;
• Socket messages infrastructure;
• Slab allocator;
• Tracing infrastructure;
• User-space API (UAPI);
• Core kernel;
• BPF subsystem;
• DMA mapping infrastructure;
• RCU subsystem;
• Dynamic debug library;
• KUnit library;
• Maple Tree data structure library;
• Heterogeneous memory management;
• Amateur Radio drivers;
• Bluetooth subsystem;
• Ethernet bridge;
• Networking core;
• IPv4 networking;
• IPv6 networking;
• Multipath TCP;
• Netfilter;
• NET/ROM layer;
• NFC subsystem;
• NSH protocol;
• Open vSwitch;
• Phonet protocol;
• SMC sockets;
• TIPC protocol;
• Unix domain sockets;
• Wireless networking;
• Key management;
• ALSA framework;
• HD-audio driver;
• Kirkwood ASoC drivers;
• MediaTek ASoC drivers; (CVE-2024-36006, CVE-2024-36922, CVE-2024-38567, CVE-2024-38584, CVE-2024-36923, CVE-2024-36892, CVE-2024-35855, CVE-2024-35853, CVE-2024-38562, CVE-2024-36920, CVE-2024-38543, CVE-2024-38576, CVE-2024-38572, CVE-2024-36898, CVE-2024-38560, CVE-2024-36004, CVE-2024-36956, CVE-2024-36881, CVE-2024-36977, CVE-2024-36955, CVE-2024-36906, CVE-2024-36013, CVE-2024-36884, CVE-2024-38563, CVE-2024-36966, CVE-2024-38547, CVE-2024-38594, CVE-2024-36926, CVE-2024-38587, CVE-2024-38566, CVE-2024-27400, CVE-2024-36941, CVE-2024-36017, CVE-2024-38544, CVE-2024-36899, CVE-2024-35851, CVE-2024-38577, CVE-2024-38590, CVE-2024-38568, CVE-2024-38559, CVE-2024-38611, CVE-2024-36887, CVE-2024-36886, CVE-2024-35996, CVE-2024-38612, CVE-2024-36925, CVE-2024-38586, CVE-2024-38596, CVE-2024-36932, CVE-2024-39482, CVE-2024-38585, CVE-2024-36033, CVE-2024-38614, CVE-2024-35852, CVE-2024-36908, CVE-2024-36939, CVE-2024-36963, CVE-2024-27401, CVE-2024-36029, CVE-2024-38540, CVE-2024-38565, CVE-2024-36927, CVE-2024-36910, CVE-2024-42134, CVE-2024-36888, CVE-2024-35859, CVE-2024-36911, CVE-2024-35947, CVE-2024-36940, CVE-2024-36921, CVE-2024-36913, CVE-2024-36943, CVE-2024-35986, CVE-2024-38616, CVE-2024-36900, CVE-2024-36954, CVE-2024-36915, CVE-2024-38602, CVE-2024-41011, CVE-2024-35991, CVE-2024-36909, CVE-2024-38603, CVE-2023-52882, CVE-2024-36953, CVE-2024-38599, CVE-2024-38574, CVE-2024-36967, CVE-2024-36895, CVE-2024-36003,…

Benedict Schlüter, Supraja Sridhara, Andrin Bertschi, and Shweta Shinde discovered that an untrusted hypervisor could inject malicious #VC interrupts and compromise the security guarantees of AMD SEV-SNP. This flaw is known as WeSee. A local attacker in control of the hypervisor could use this to expose sensitive information or possibly execute arbitrary code in the trusted execution environment. (CVE-2024-25742)

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;
• M68K architecture;
• OpenRISC architecture;
• PowerPC architecture;
• RISC-V architecture;
• x86 architecture;
• Block layer subsystem;
• Accessibility subsystem;
• Bluetooth drivers;
• Clock framework and drivers;
• CPU frequency scaling framework;
• Hardware crypto device drivers;
• DMA engine subsystem;
• DPLL subsystem;
• FireWire subsystem;
• EFI core;
• Qualcomm firmware drivers;
• GPIO subsystem;
• GPU drivers;
• HID subsystem;
• Microsoft Hyper-V drivers;
• I2C subsystem;
• InfiniBand drivers;
• IOMMU subsystem;
• IRQ chip drivers;
• Macintosh device drivers;
• Multiple devices driver;
• Media drivers;
• EEPROM drivers;
• MMC subsystem;
• Network drivers;
• STMicroelectronics network drivers;
• Device tree and open firmware driver;
• HiSilicon SoC PMU drivers;
• PHY drivers;
• Pin controllers subsystem;
• Remote Processor subsystem;
• S/390 drivers;
• SCSI drivers;
• SPI subsystem;
• Media staging drivers;
• Thermal drivers;
• TTY drivers;
• Userspace I/O drivers;
• USB subsystem;
• DesignWare USB3 driver;
• ACRN Hypervisor Service Module driver;
• Virtio drivers;
• 9P distributed file system;
• BTRFS file system;
• eCrypt file system;
• EROFS file system;
• File systems infrastructure;
• GFS2 file system;
• JFFS2 file system;
• Network file systems library;
• Network file system client;
• Network file system server daemon;
• NILFS2 file system;
• Proc file system;
• SMB network file system;
• Tracing file system;
• Mellanox drivers;
• Memory management;
• Socket messages infrastructure;
• Slab allocator;
• Tracing infrastructure;
• User-space API (UAPI);
• Core kernel;
• BPF subsystem;
• DMA mapping infrastructure;
• RCU subsystem;
• Dynamic debug library;
• KUnit library;
• Maple Tree data structure library;
• Heterogeneous memory management;
• Amateur Radio drivers;
• Bluetooth subsystem;
• Ethernet bridge;
• Networking core;
• IPv4 networking;
• IPv6 networking;
• Multipath TCP;
• Netfilter;
• NET/ROM layer;
• NFC subsystem;
• NSH protocol;
• Open vSwitch;
• Phonet protocol;
• SMC sockets;
• TIPC protocol;
• Unix domain sockets;
• Wireless networking;
• Key management;
• ALSA framework;
• HD-audio driver;
• Kirkwood ASoC drivers;
• MediaTek ASoC drivers; (CVE-2024-38601, CVE-2024-36935, CVE-2024-35991, CVE-2024-36032, CVE-2024-35988, CVE-2024-36886, CVE-2024-36913, CVE-2024-36928, CVE-2024-38553, CVE-2024-36927, CVE-2024-38615, CVE-2024-36958, CVE-2024-36977, CVE-2024-36889, CVE-2024-38554, CVE-2024-38590, CVE-2024-42134, CVE-2024-35857, CVE-2024-35850, CVE-2024-35986, CVE-2024-36921, CVE-2024-38569, CVE-2024-36966, CVE-2024-38542, CVE-2024-38585, CVE-2024-36884, CVE-2024-36006, CVE-2024-38577, CVE-2024-36016, CVE-2024-38584, CVE-2024-36887, CVE-2024-38598, CVE-2024-35994, CVE-2024-38603, CVE-2024-35998, CVE-2024-27401, CVE-2024-35852, CVE-2024-36944, CVE-2024-38572, CVE-2024-36917, CVE-2024-36943, CVE-2024-36009, CVE-2024-38587, CVE-2024-35949, CVE-2024-36945, CVE-2024-36004, CVE-2024-36919, CVE-2024-27398, CVE-2024-38582, CVE-2024-35847, CVE-2024-38580, CVE-2024-38602, CVE-2024-36916, CVE-2024-36903, CVE-2024-38555, CVE-2024-36952, CVE-2024-38589, CVE-2024-27394, CVE-2024-36933,…

Benedict Schlüter, Supraja Sridhara, Andrin Bertschi, and Shweta Shinde discovered that an untrusted hypervisor could inject malicious #VC interrupts and compromise the security guarantees of AMD SEV-SNP. This flaw is known as WeSee. A local attacker in control of the hypervisor could use this to expose sensitive information or possibly execute arbitrary code in the trusted execution environment. (CVE-2024-25742)

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;
• M68K architecture;
• OpenRISC architecture;
• PowerPC architecture;
• RISC-V architecture;
• x86 architecture;
• Block layer subsystem;
• Accessibility subsystem;
• Bluetooth drivers;
• Clock framework and drivers;
• CPU frequency scaling framework;
• Hardware crypto device drivers;
• DMA engine subsystem;
• DPLL subsystem;
• FireWire subsystem;
• EFI core;
• Qualcomm firmware drivers;
• GPIO subsystem;
• GPU drivers;
• HID subsystem;
• Microsoft Hyper-V drivers;
• I2C subsystem;
• InfiniBand drivers;
• IOMMU subsystem;
• IRQ chip drivers;
• Macintosh device drivers;
• Multiple devices driver;
• Media drivers;
• EEPROM drivers;
• MMC subsystem;
• Network drivers;
• STMicroelectronics network drivers;
• Device tree and open firmware driver;
• HiSilicon SoC PMU drivers;
• PHY drivers;
• Pin controllers subsystem;
• Remote Processor subsystem;
• S/390 drivers;
• SCSI drivers;
• SPI subsystem;
• Media staging drivers;
• Thermal drivers;
• TTY drivers;
• Userspace I/O drivers;
• USB subsystem;
• DesignWare USB3 driver;
• ACRN Hypervisor Service Module driver;
• Virtio drivers;
• 9P distributed file system;
• BTRFS file system;
• eCrypt file system;
• EROFS file system;
• File systems infrastructure;
• GFS2 file system;
• JFFS2 file system;
• Network file systems library;
• Network file system client;
• Network file system server daemon;
• NILFS2 file system;
• Proc file system;
• SMB network file system;
• Tracing file system;
• Mellanox drivers;
• Memory management;
• Socket messages infrastructure;
• Slab allocator;
• Tracing infrastructure;
• User-space API (UAPI);
• Core kernel;
• BPF subsystem;
• DMA mapping infrastructure;
• RCU subsystem;
• Dynamic debug library;
• KUnit library;
• Maple Tree data structure library;
• Heterogeneous memory management;
• Amateur Radio drivers;
• Bluetooth subsystem;
• Ethernet bridge;
• Networking core;
• IPv4 networking;
• IPv6 networking;
• Multipath TCP;
• Netfilter;
• NET/ROM layer;
• NFC subsystem;
• NSH protocol;
• Open vSwitch;
• Phonet protocol;
• SMC sockets;
• TIPC protocol;
• Unix domain sockets;
• Wireless networking;
• Key management;
• ALSA framework;
• HD-audio driver;
• Kirkwood ASoC drivers;
• MediaTek ASoC drivers; (CVE-2024-38601, CVE-2024-36935, CVE-2024-35991, CVE-2024-36032, CVE-2024-35988, CVE-2024-36886, CVE-2024-36913, CVE-2024-36928, CVE-2024-38553, CVE-2024-36927, CVE-2024-38615, CVE-2024-36958, CVE-2024-36977, CVE-2024-36889, CVE-2024-38554, CVE-2024-38590, CVE-2024-42134, CVE-2024-35857, CVE-2024-35850, CVE-2024-35986, CVE-2024-36921, CVE-2024-38569, CVE-2024-36966, CVE-2024-38542, CVE-2024-38585, CVE-2024-36884, CVE-2024-36006, CVE-2024-38577, CVE-2024-36016, CVE-2024-38584, CVE-2024-36887, CVE-2024-38598, CVE-2024-35994, CVE-2024-38603, CVE-2024-35998, CVE-2024-27401, CVE-2024-35852, CVE-2024-36944, CVE-2024-38572, CVE-2024-36917, CVE-2024-36943, CVE-2024-36009, CVE-2024-38587, CVE-2024-35949, CVE-2024-36945, CVE-2024-36004, CVE-2024-36919, CVE-2024-27398, CVE-2024-38582, CVE-2024-35847, CVE-2024-38580, CVE-2024-38602, CVE-2024-36916, CVE-2024-36903, CVE-2024-38555, CVE-2024-36952, CVE-2024-38589, CVE-2024-27394, CVE-2024-36933,…

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;
• M68K architecture;
• OpenRISC architecture;
• PowerPC architecture;
• RISC-V architecture;
• x86 architecture;
• Block layer subsystem;
• Accessibility subsystem;
• Bluetooth drivers;
• Clock framework and drivers;
• CPU frequency scaling framework;
• Hardware crypto device drivers;
• DMA engine subsystem;
• DPLL subsystem;
• FireWire subsystem;
• EFI core;
• Qualcomm firmware drivers;
• GPIO subsystem;
• GPU drivers;
• Microsoft Hyper-V drivers;
• InfiniBand drivers;
• IOMMU subsystem;
• IRQ chip drivers;
• Macintosh device drivers;
• Multiple devices driver;
• Media drivers;
• EEPROM drivers;
• MMC subsystem;
• Network drivers;
• STMicroelectronics network drivers;
• Device tree and open firmware driver;
• HiSilicon SoC PMU drivers;
• PHY drivers;
• Pin controllers subsystem;
• Remote Processor subsystem;
• S/390 drivers;
• SCSI drivers;
• SPI subsystem;
• Media staging drivers;
• Thermal drivers;
• Userspace I/O drivers;
• USB subsystem;
• DesignWare USB3 driver;
• ACRN Hypervisor Service Module driver;
• Virtio drivers;
• 9P distributed file system;
• BTRFS file system;
• eCrypt file system;
• EROFS file system;
• File systems infrastructure;
• GFS2 file system;
• JFFS2 file system;
• Network file systems library;
• Network file system client;
• Network file system server daemon;
• NILFS2 file system;
• Proc file system;
• SMB network file system;
• Tracing file system;
• Mellanox drivers;
• Memory management;
• Socket messages infrastructure;
• Slab allocator;
• Tracing infrastructure;
• User-space API (UAPI);
• Core kernel;
• BPF subsystem;
• DMA mapping infrastructure;
• RCU subsystem;
• Dynamic debug library;
• KUnit library;
• Maple Tree data structure library;
• Heterogeneous memory management;
• Amateur Radio drivers;
• Bluetooth subsystem;
• Ethernet bridge;
• Networking core;
• IPv4 networking;
• IPv6 networking;
• Multipath TCP;
• Netfilter;
• NET/ROM layer;
• NFC subsystem;
• NSH protocol;
• Open vSwitch;
• Phonet protocol;
• SMC sockets;
• TIPC protocol;
• Unix domain sockets;
• Wireless networking;
• Key management;
• ALSA framework;
• HD-audio driver;
• Kirkwood ASoC drivers;
• MediaTek ASoC drivers; (CVE-2024-35987, CVE-2024-36931, CVE-2024-38614, CVE-2024-35857, CVE-2024-36949, CVE-2024-38599, CVE-2024-35994, CVE-2024-35849, CVE-2024-36916, CVE-2024-38590, CVE-2024-36944, CVE-2024-38561, CVE-2024-38538, CVE-2024-36017, CVE-2024-38593, CVE-2024-36028, CVE-2024-36960, CVE-2024-36002, CVE-2024-36967, CVE-2024-36898, CVE-2024-35989, CVE-2024-36975, CVE-2024-38578, CVE-2024-38582, CVE-2024-38588, CVE-2024-38579, CVE-2024-38617, CVE-2024-36901, CVE-2024-38550, CVE-2023-52882, CVE-2024-38603, CVE-2024-38620, CVE-2024-36956, CVE-2024-36880, CVE-2024-36895, CVE-2024-36979, CVE-2024-36887, CVE-2024-27396, CVE-2024-27400, CVE-2024-36952, CVE-2024-36886, CVE-2024-36905, CVE-2024-36883, CVE-2024-38540, CVE-2024-38605, CVE-2024-36029, CVE-2024-36934, CVE-2024-27395, CVE-2024-36000, CVE-2024-38549, CVE-2024-35999, CVE-2024-38585, CVE-2024-38589, CVE-2024-38565, CVE-2024-36917, CVE-2024-36930, CVE-2024-36940, CVE-2024-36900, CVE-2024-35850, CVE-2024-38592, CVE-2024-38553, CVE-2024-36929, CVE-2024-36915, CVE-2024-36004, CVE-2024-38573, CVE-2024-36941, CVE-2024-38607, CVE-2024-36009, CVE-2024-27398, CVE-2024-36909, CVE-2024-35848, CVE-2024-36950, CVE-2024-38564, CVE-2024-36947, CVE-2024-38613, CVE-2024-38570, CVE-2024-38612, CVE-2024-38580, CVE-2024-38557, CVE-2024-36959, CVE-2024-27399, CVE-2024-41011, CVE-2024-36928, CVE-2024-38543, CVE-2024-38541, CVE-2024-38583, CVE-2024-35855, CVE-2024-38611, CVE-2024-36891,…