CVE-2024-42129

The Linux Kernel, the operating system core itself.

Security Fix(es):

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

efi: libstub: only free priv.runtime_map when allocated

priv.runtime_map is only allocated when efi_novamap is not set. Otherwise, it is an uninitialized value. In the error path, it is freed unconditionally. Avoid passing an uninitialized value to free_pool. Free priv.runtime_map only when it was allocated.

This bug was discovered and resolved using Coverity Static Analysis Security Testing (SAST) by Synopsys, Inc.(CVE-2024-33619)

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

fpga: region: add owner module and take its refcount

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

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

Also, update the documentation to keep it consistent with the new interface for registering an fpga region.(CVE-2024-35247)

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

eeprom: at24: fix memory corruption race condition

If the eeprom is not accessible, an nvmem device will be registered, the read will fail, and the device will be torn down. If another driver accesses the nvmem device after the teardown, it will reference invalid memory.

Move the failure point before registering the nvmem device.(CVE-2024-35848)

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

block: fix module reference leakage from bdev_open_by_dev error path

At the time bdev_may_open() is called, module reference is grabbed already, hence module reference should be released if bdev_may_open() failed.

This problem is found by code review.(CVE-2024-35859)

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

Bluetooth: RFCOMM: Fix not validating setsockopt user input

syzbot reported rfcomm_sock_setsockopt_old() is copying data without checking user input length.

BUG: KASAN: slab-out-of-bounds in copy_from_sockptr_offset include/linux/sockptr.h:49 [inline] BUG: KASAN: slab-out-of-bounds in copy_from_sockptr include/linux/sockptr.h:55 [inline] BUG: KASAN: slab-out-of-bounds in rfcomm_sock_setsockopt_old net/bluetooth/rfcomm/sock.c:632 [inline] BUG: KASAN: slab-out-of-bounds in rfcomm_sock_setsockopt+0x893/0xa70 net/bluetooth/rfcomm/sock.c:673 Read of size 4 at addr ffff8880209a8bc3 by task syz-executor632/5064(CVE-2024-35966)

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

mm/slab: make __free(kfree) accept error pointers

Currently, if an automatically freed allocation is an error pointer that will lead to a crash. An example of this is in wm831x_gpio_dbg_show().

171 char *label __free(kfree) = gpiochip_dup_line_label(chip, i); 172 if (IS_ERR(label)) { 173 dev_err(wm831x->dev, "Failed to duplicate label\n"); 174 continue; 175 }

The auto clean up function should check for error pointers as well, otherwise we're going to keep hitting issues like this.(CVE-2024-36890)

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

USB: core: Fix access violation during port device removal

Testing with KASAN and syzkaller…

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:

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-42129 in the linux package for Root:Debian:11. Multiple fixed versions available.

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

In the Linux kernel, the following vulnerability has been resolved: leds: mlxreg: Use devm_mutex_init() for mutex initialization In this driver LEDs are registered using devm_led_classdev_register() so they are automatically unregistered after module's remove() is done. led_classdev_unregister() calls module's led_set_brightness() to turn off the LEDs and that callback uses mutex which was destroyed already in module's remove() so use devm API instead.

• gpiolib: cdev: Set lineevent_state::irq after IRQ register successfully {CVE-2022-48660}
• ipv4: check for NULL idev in ip_route_use_hint() {CVE-2024-36008}
• KEYS: trusted: Do not use WARN when encode fails {CVE-2024-36975}
• Fix userfaultfd_api to return EINVAL as expected {CVE-2024-41027}
• xhci: Fix null pointer dereference when host dies {CVE-2023-52898}
• sctp: sysctl: auth_enable: avoid using current->nsproxy {CVE-2025-21638}
• blk-mq: fix IO hang from sbitmap wakeup race {CVE-2024-26671}
• net: openvswitch: fix flow memory leak in ovs_flow_cmd_new {CVE-2023-52977}
• gpiolib: fix memory leak in gpiochip_setup_dev() {CVE-2022-48975}
• HID: betop: check shape of output reports {CVE-2023-53015}
• mm/swapfile: add cond_resched() in get_swap_pages() {CVE-2023-52932}
• HV: hv_balloon: fix memory leak with using debugfs_lookup() {CVE-2023-52937}
• drm/i915: Fix a memory leak with reused mmap_offset {CVE-2023-53002}
• ptdma: pt_core_execute_cmd() should use spinlock {CVE-2023-53013}
• RDMA/core: Fix ib block iterator counter overflow {CVE-2023-53026}
• Bluetooth: hci_conn: Fix memory leaks {CVE-2023-53018}
• scsi: target: pscsi: Fix bio_put() for error case {CVE-2024-26760}
• sctp: Prevent TOCTOU out-of-bounds write {CVE-2025-40331}
• pnfs/flexfiles: Fix memory leak in nfs4_ff_alloc_deviceid_node() {CVE-2026-23038}
• cpufreq: intel_pstate: Fix object lifecycle issue in update_qos_request() {CVE-2025-40194}
• ALSA: hda/cs8409: Fix possible NULL dereference {CVE-2024-50160}
• nbd: don't allow reconnect after disconnect {CVE-2025-21731}
• openvswitch: fix lockup on tx to unregistering netdev with carrier {CVE-2025-21681}
• ext4: detect invalid INLINE_DATA + EXTENTS flag combination {CVE-2025-40167}
• ext4: xattr: fix null pointer deref in ext4_raw_inode() {CVE-2025-68820}
• net: fix memory leak in skb_segment_list for GRO packets {CVE-2026-22979}
• wifi: brcmfmac: fix crash while sending Action Frames in standalone AP Mode {CVE-2025-40321}
• ipvs: fix ipv4 null-ptr-deref in route error path {CVE-2025-68813}
• ASoC: Intel: bytcr_rt5651: Fix invalid quirk input mapping {CVE-2025-40121}
• i40e: Fix macvlan leak by synchronizing access to mac_filter_hash {CVE-2024-50041}
• net/mlx5e: Fix NULL deref in mlx5e_tir_builder_alloc() {CVE-2024-50000}
• bpf: Fix reference count leak in bpf_prog_test_run_xdp() {CVE-2026-22994}
• xsk: check IFF_UP earlier in Tx path {CVE-2023-53240}
• firmware: cs_dsp: Prevent buffer overrun when processing V2 alg headers {CVE-2024-41038}
• virtgpu: don't reset on shutdown {CVE-2025-38064}
• xen/netfront: fix crash when removing device {CVE-2022-48969}
• mptcp: do not fallback when OoO is present {CVE-2024-50185}
• can: j1939: add missing calls in NETDEV_UNREGISTER notification handler {CVE-2025-39925}
• netfilter: nf_tables: remove redundant chain validation on register store {CVE-2025-71160}
• xfs: fix use-after-free in xattr node block inactivation {CVE-2026-43053}
• ext4: fix racy may inline data check in dio write {CVE-2023-52786}
• drm/amdgpu/fence: Fix oops due to non-matching drm_sched init/fini {CVE-2023-52738}
• macsec: fix UAF bug for real_dev {CVE-2022-49390}
• drm/i915/gem: Fix Virtual Memory mapping boundaries calculation {CVE-2024-42259}
• mm/shmem: disable PMD-sized page cache if needed {CVE-2024-42241}
• driver: iio: add missing checks on iio_info's callback access {CVE-2024-46715}
• udmabuf: fix memory leak on last export_udmabuf() error path {CVE-2024-56712}
• ALSA: control: Avoid WARN() for symlink errors {CVE-2024-56657}
• mm/mempolicy: fix migrate_to_node() assuming there is at least one VMA in a MM {CVE-2024-56611}
• eth: bnxt: always recalculate features after XDP clearing, fix null-deref {CVE-2025-21682}
• net: annotate data-races around sk->sk_{data_ready,write_space} {CVE-2026-23302}
• udmabuf: change folios array from kmalloc to kvmalloc {CVE-2024-56544}
• RDMA/mlx5: Move events notifier registration to be after device registration {CVE-2024-53224}
• dlm: fix possible lkb_resource…

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

leds: mlxreg: Use devm_mutex_init() for mutex initialization

In this driver LEDs are registered using devm_led_classdev_register() so they are automatically unregistered after module's remove() is done. led_classdev_unregister() calls module's led_set_brightness() to turn off the LEDs and that callback uses mutex which was destroyed already in module's remove() so use devm API instead.

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