CVE-2024-42067

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

bpf: Take return from set_memory_rox() into account with bpf_jit_binary_lock_ro()

set_memory_rox() can fail, leaving memory unprotected.

Check return and bail out when bpf_jit_binary_lock_ro() returns an error.

In the Linux kernel, the following vulnerability has been resolved: bpf: Take return from set_memory_rox() into account with bpf_jit_binary_lock_ro() set_memory_rox() can fail, leaving memory unprotected. Check return and bail out when bpf_jit_binary_lock_ro() returns an error.

The Linux Kernel, the operating system core itself.

Security Fix(es):

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

bpf: Take return from set_memory_rox() into account with bpf_jit_binary_lock_ro()

set_memory_rox() can fail, leaving memory unprotected.

Check return and bail out when bpf_jit_binary_lock_ro() returns an error.(CVE-2024-42067)

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

sysctl: always initialize i_uid/i_gid

Always initialize i_uid/i_gid inside the sysfs core so set_ownership() can safely skip setting them.

Commit 5ec27ec735ba ("fs/proc/proc_sysctl.c: fix the default values of i_uid/i_gid on /proc/sys inodes.") added defaults for i_uid/i_gid when set_ownership() was not implemented. It also missed adjusting net_ctl_set_ownership() to use the same default values in case the computation of a better value failed.(CVE-2024-42312)

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

parisc: fix a possible DMA corruption

ARCH_DMA_MINALIGN was defined as 16 - this is too small - it may be possible that two unrelated 16-byte allocations share a cache line. If one of these allocations is written using DMA and the other is written using cached write, the value that was written with DMA may be corrupted.

This commit changes ARCH_DMA_MINALIGN to be 128 on PA20 and 32 on PA1.1 - that's the largest possible cache line size.

As different parisc microarchitectures have different cache line size, we define arch_slab_minalign(), cache_line_size() and dma_get_cache_alignment() so that the kernel may tune slab cache parameters dynamically, based on the detected cache line size.(CVE-2024-44949)

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

sched/smt: Fix unbalance sched_smt_present dec/inc

I got the following warn report while doing stress test:

jump label: negative count! WARNING: CPU: 3 PID: 38 at kernel/jump_label.c:263 static_key_slow_try_dec+0x9d/0xb0 Call Trace: <TASK> __static_key_slow_dec_cpuslocked+0x16/0x70 sched_cpu_deactivate+0x26e/0x2a0 cpuhp_invoke_callback+0x3ad/0x10d0 cpuhp_thread_fun+0x3f5/0x680 smpboot_thread_fn+0x56d/0x8d0 kthread+0x309/0x400 ret_from_fork+0x41/0x70 ret_from_fork_asm+0x1b/0x30 </TASK>

Because when cpuset_cpu_inactive() fails in sched_cpu_deactivate(), the cpu offline failed, but sched_smt_present is decremented before calling sched_cpu_deactivate(), it leads to unbalanced dec/inc, so fix it by incrementing sched_smt_present in the error path.(CVE-2024-44958)

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

mptcp: pm: only decrement add_addr_accepted for MPJ req

Adding the following warning ...

WARN_ON_ONCE(msk->pm.add_addr_accepted == 0)

... before decrementing the add_addr_accepted counter helped to find a bug when running the "remove single subflow" subtest from the mptcp_join.sh selftest.

Removing a 'subflow' endpoint will first trigger a RM_ADDR, then the subflow closure. Before this patch, and upon the reception of the RM_ADDR, the other peer will then try to decrement this add_addr_accepted. That's not correct because the attached subflows have not been created upon the reception of an ADD_ADDR.

A way to solve that is to decrement the counter only if the attached subflow was an MP_JOIN to a remote id that was not 0, and initiated by the host receiving the RM_ADDR.(CVE-2024-45009)

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

char: xillybus: Check USB endpoints when probing device

Ensure, as the driver probes the device, that all endpoints that the driver may attempt to access exist and are of the correct type.

All XillyUSB devices must have a Bulk IN and Bulk OUT endpoint at address 1. This is verified in xillyusb_setup_base_eps().

On top of that, a XillyUSB device may have additional Bulk OUT endpoints. The…

The Linux Kernel, the operating system core itself.

Security Fix(es):

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

drm/i915/gt: Cleanup partial engine discovery failures

If we abort driver initialisation in the middle of gt/engine discovery, some engines will be fully setup and some not. Those incompletely setup engines only have 'engine->release == NULL' and so will leak any of the common objects allocated.

v2:

• Drop the destroy_pinned_context() helper for now. It's not really worth it with just a single callsite at the moment. (Janusz)(CVE-2022-48893)

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

f2fs: fix to avoid dirent corruption

As Al reported in link[1]:

f2fs_rename() ... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);

You want correct inumber in the ".." link. And cross-directory rename does move the source to new parent, even if you'd been asked to leave a whiteout in the old place.

[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/

With below testcase, it may cause dirent corruption, due to it missed to call f2fs_set_link() to update ".." link to new directory.

• mkdir -p dir/foo
• renameat2 -w dir/foo bar

[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for '..', parent parent ino is [0x3] [FSCK] other corrupted bugs Fail

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

efivarfs: force RO when remounting if SetVariable is not supported

If SetVariable at runtime is not supported by the firmware we never assign a callback for that function. At the same time mount the efivarfs as RO so no one can call that. However, we never check the permission flags when someone remounts the filesystem as RW. As a result this leads to a crash looking like this:

$ mount -o remount,rw /sys/firmware/efi/efivars $ efi-updatevar -f PK.auth PK

[ 303.279166] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000 [ 303.280482] Mem abort info: [ 303.280854] ESR = 0x0000000086000004 [ 303.281338] EC = 0x21: IABT (current EL), IL = 32 bits [ 303.282016] SET = 0, FnV = 0 [ 303.282414] EA = 0, S1PTW = 0 [ 303.282821] FSC = 0x04: level 0 translation fault [ 303.283771] user pgtable: 4k pages, 48-bit VAs, pgdp=000000004258c000 [ 303.284913] [0000000000000000] pgd=0000000000000000, p4d=0000000000000000 [ 303.286076] Internal error: Oops: 0000000086000004 [#1] PREEMPT SMP [ 303.286936] Modules linked in: qrtr tpm_tis tpm_tis_core crct10dif_ce arm_smccc_trng rng_core drm fuse ip_tables x_tables ipv6 [ 303.288586] CPU: 1 PID: 755 Comm: efi-updatevar Not tainted 6.3.0-rc1-00108-gc7d0c4695c68 #1 [ 303.289748] Hardware name: Unknown Unknown Product/Unknown Product, BIOS 2023.04-00627-g88336918701d 04/01/2023 [ 303.291150] pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 303.292123] pc : 0x0 [ 303.292443] lr : efivar_set_variable_locked+0x74/0xec [ 303.293156] sp : ffff800008673c10 [ 303.293619] x29: ffff800008673c10 x28: ffff0000037e8000 x27: 0000000000000000 [ 303.294592] x26: 0000000000000800 x25: ffff000002467400 x24: 0000000000000027 [ 303.295572] x23: ffffd49ea9832000 x22: ffff0000020c9800 x21: ffff000002467000 [ 303.296566] x20: 0000000000000001 x19: 00000000000007fc x18: 0000000000000000 [ 303.297531] x17: 0000000000000000 x16: 0000000000000000 x15: 0000aaaac807ab54 [ 303.298495] x14: ed37489f673633c0 x13: 71c45c606de13f80 x12: 47464259e219acf4 [ 303.299453] x11: ffff000002af7b01 x10: 0000000000000003 x9 : 0000000000000002 [ 303.300431] x8 : 0000000000000010 x7 : ffffd49ea8973230 x6 : 0000000000a85201 [ 303.301412] x5 : 0000000000000000 x4 : ffff0000020c9800 x3 : 00000000000007fc [ 303.302370] x2 :…

The Linux Kernel, the operating system core itself.

Security Fix(es):

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

i40e: Fix kernel crash during module removal

The driver incorrectly frees client instance and subsequent i40e module removal leads to kernel crash.

Reproducer:

1. Do ethtool offline test followed immediately by another one host# ethtool -t eth0 offline; ethtool -t eth0 offline
2. Remove recursively irdma module that also removes i40e module host# modprobe -r irdma

Result: [ 8675.035651] i40e 0000:3d:00.0 eno1: offline testing starting [ 8675.193774] i40e 0000:3d:00.0 eno1: testing finished [ 8675.201316] i40e 0000:3d:00.0 eno1: offline testing starting [ 8675.358921] i40e 0000:3d:00.0 eno1: testing finished [ 8675.496921] i40e 0000:3d:00.0: IRDMA hardware initialization FAILED init_state=2 status=-110 [ 8686.188955] i40e 0000:3d:00.1: i40e_ptp_stop: removed PHC on eno2 [ 8686.943890] i40e 0000:3d:00.1: Deleted LAN device PF1 bus=0x3d dev=0x00 func=0x01 [ 8686.952669] i40e 0000:3d:00.0: i40e_ptp_stop: removed PHC on eno1 [ 8687.761787] BUG: kernel NULL pointer dereference, address: 0000000000000030 [ 8687.768755] #PF: supervisor read access in kernel mode [ 8687.773895] #PF: error_code(0x0000) - not-present page [ 8687.779034] PGD 0 P4D 0 [ 8687.781575] Oops: 0000 [#1] PREEMPT SMP NOPTI [ 8687.785935] CPU: 51 PID: 172891 Comm: rmmod Kdump: loaded Tainted: G W I 5.19.0+ #2 [ 8687.794800] Hardware name: Intel Corporation S2600WFD/S2600WFD, BIOS SE5C620.86B.0X.02.0001.051420190324 05/14/2019 [ 8687.805222] RIP: 0010:i40e_lan_del_device+0x13/0xb0 [i40e] [ 8687.810719] Code: d4 84 c0 0f 84 b8 25 01 00 e9 9c 25 01 00 41 bc f4 ff ff ff eb 91 90 0f 1f 44 00 00 41 54 55 53 48 8b 87 58 08 00 00 48 89 fb <48> 8b 68 30 48 89 ef e8 21 8a 0f d5 48 89 ef e8 a9 78 0f d5 48 8b [ 8687.829462] RSP: 0018:ffffa604072efce0 EFLAGS: 00010202 [ 8687.834689] RAX: 0000000000000000 RBX: ffff8f43833b2000 RCX: 0000000000000000 [ 8687.841821] RDX: 0000000000000000 RSI: ffff8f4b0545b298 RDI: ffff8f43833b2000 [ 8687.848955] RBP: ffff8f43833b2000 R08: 0000000000000001 R09: 0000000000000000 [ 8687.856086] R10: 0000000000000000 R11: 000ffffffffff000 R12: ffff8f43833b2ef0 [ 8687.863218] R13: ffff8f43833b2ef0 R14: ffff915103966000 R15: ffff8f43833b2008 [ 8687.870342] FS: 00007f79501c3740(0000) GS:ffff8f4adffc0000(0000) knlGS:0000000000000000 [ 8687.878427] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 8687.884174] CR2: 0000000000000030 CR3: 000000014276e004 CR4: 00000000007706e0 [ 8687.891306] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 8687.898441] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ 8687.905572] PKRU: 55555554 [ 8687.908286] Call Trace: [ 8687.910737] <TASK> [ 8687.912843] i40e_remove+0x2c0/0x330 [i40e] [ 8687.917040] pci_device_remove+0x33/0xa0 [ 8687.920962] device_release_driver_internal+0x1aa/0x230 [ 8687.926188] driver_detach+0x44/0x90 [ 8687.929770] bus_remove_driver+0x55/0xe0 [ 8687.933693] pci_unregister_driver+0x2a/0xb0 [ 8687.937967] i40e_exit_module+0xc/0xf48 [i40e]

Two offline tests cause IRDMA driver failure (ETIMEDOUT) and this failure is indicated back to i40e_client_subtask() that calls i40e_client_del_instance() to free client instance referenced by pf->cinst and sets this pointer to NULL. During the module removal i40e_remove() calls i40e_lan_del_device() that dereferences pf->cinst that is NULL -> crash. Do not remove client instance when client open callbacks fails and just clear __I40E_CLIENT_INSTANCE_OPENED bit. The driver also needs to take care about this situation (when netdev is up and client is NOT opened) in i40e_notify_client_of_netdev_close() and calls client close callback only when __I40E_CLIENT_INSTANCE_OPENED is set.(CVE-2022-48688)

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

tracing/osnoise: Do not unregister events twice

Nicolas…

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:

drm/i915/gt: Cleanup partial engine discovery failures

If we abort driver initialisation in the middle of gt/engine discovery, some engines will be fully setup and some not. Those incompletely setup engines only have 'engine->release == NULL' and so will leak any of the common objects allocated.

v2:

• Drop the destroy_pinned_context() helper for now. It's not really worth it with just a single callsite at the moment. (Janusz)(CVE-2022-48893)

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

usb: gadget: ncm: Fix handling of zero block length packets

While connecting to a Linux host with CDC_NCM_NTB_DEF_SIZE_TX set to 65536, it has been observed that we receive short packets, which come at interval of 5-10 seconds sometimes and have block length zero but still contain 1-2 valid datagrams present.

According to the NCM spec:

"If wBlockLength = 0x0000, the block is terminated by a short packet. In this case, the USB transfer must still be shorter than dwNtbInMaxSize or dwNtbOutMaxSize. If exactly dwNtbInMaxSize or dwNtbOutMaxSize bytes are sent, and the size is a multiple of wMaxPacketSize for the given pipe, then no ZLP shall be sent.

wBlockLength= 0x0000 must be used with extreme care, because of the possibility that the host and device may get out of sync, and because of test issues.

wBlockLength = 0x0000 allows the sender to reduce latency by starting to send a very large NTB, and then shortening it when the sender discovers that there’s not sufficient data to justify sending a large NTB"

However, there is a potential issue with the current implementation, as it checks for the occurrence of multiple NTBs in a single giveback by verifying if the leftover bytes to be processed is zero or not. If the block length reads zero, we would process the same NTB infintely because the leftover bytes is never zero and it leads to a crash. Fix this by bailing out if block length reads zero.(CVE-2024-35825)

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

ipv6: fix race condition between ipv6_get_ifaddr and ipv6_del_addr

Although ipv6_get_ifaddr walks inet6_addr_lst under the RCU lock, it still means hlist_for_each_entry_rcu can return an item that got removed from the list. The memory itself of such item is not freed thanks to RCU but nothing guarantees the actual content of the memory is sane.

In particular, the reference count can be zero. This can happen if ipv6_del_addr is called in parallel. ipv6_del_addr removes the entry from inet6_addr_lst (hlist_del_init_rcu(&ifp->addr_lst)) and drops all references (__in6_ifa_put(ifp) + in6_ifa_put(ifp)). With bad enough timing, this can happen:

1. In ipv6_get_ifaddr, hlist_for_each_entry_rcu returns an entry.

2. Then, the whole ipv6_del_addr is executed for the given entry. The reference count drops to zero and kfree_rcu is scheduled.

3. ipv6_get_ifaddr continues and tries to increments the reference count (in6_ifa_hold).

4. The rcu is unlocked and the entry is freed.

5. The freed entry is returned.

Prevent increasing…

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

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

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

In the Linux kernel, the following vulnerability has been resolved: bpf: Take return from set_memory_rox() into account with bpf_jit_binary_lock_ro() set_memory_rox() can fail, leaving memory unprotected. Check return and bail out when bpf_jit_binary_lock_ro() returns an error.

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