CVE-2024-39292

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

um: Add winch to winch_handlers before registering winch IRQ

Registering a winch IRQ is racy, an interrupt may occur before the winch is added to the winch_handlers list.

If that happens, register_winch_irq() adds to that list a winch that is scheduled to be (or has already been) freed, causing a panic later in winch_cleanup().

Avoid the race by adding the winch to the winch_handlers list before registering the IRQ, and rolling back if um_request_irq() fails.

In the Linux kernel, the following vulnerability has been resolved: um: Add winch to winch_handlers before registering winch IRQ Registering a winch IRQ is racy, an interrupt may occur before the winch is added to the winch_handlers list. If that happens, register_winch_irq() adds to that list a winch that is scheduled to be (or has already been) freed, causing a panic later in winch_cleanup(). Avoid the race by adding the winch to the winch_handlers list before registering the IRQ, and rolling back if um_request_irq() fails.

The Linux Kernel, the operating system core itself.

Security Fix(es):

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

usb: gadget: ncm: Avoid dropping datagrams of properly parsed NTBs

It is observed sometimes when tethering is used over NCM with Windows 11 as host, at some instances, the gadget_giveback has one byte appended at the end of a proper NTB. When the NTB is parsed, unwrap call looks for any leftover bytes in SKB provided by u_ether and if there are any pending bytes, it treats them as a separate NTB and parses it. But in case the second NTB (as per unwrap call) is faulty/corrupt, all the datagrams that were parsed properly in the first NTB and saved in rx_list are dropped.

Adding a few custom traces showed the following: [002] d..1 7828.532866: dwc3_gadget_giveback: ep1out: req 000000003868811a length 1025/16384 zsI ==> 0 [002] d..1 7828.532867: ncm_unwrap_ntb: K: ncm_unwrap_ntb toprocess: 1025 [002] d..1 7828.532867: ncm_unwrap_ntb: K: ncm_unwrap_ntb nth: 1751999342 [002] d..1 7828.532868: ncm_unwrap_ntb: K: ncm_unwrap_ntb seq: 0xce67 [002] d..1 7828.532868: ncm_unwrap_ntb: K: ncm_unwrap_ntb blk_len: 0x400 [002] d..1 7828.532868: ncm_unwrap_ntb: K: ncm_unwrap_ntb ndp_len: 0x10 [002] d..1 7828.532869: ncm_unwrap_ntb: K: Parsed NTB with 1 frames

In this case, the giveback is of 1025 bytes and block length is 1024. The rest 1 byte (which is 0x00) won't be parsed resulting in drop of all datagrams in rx_list.

Same is case with packets of size 2048: [002] d..1 7828.557948: dwc3_gadget_giveback: ep1out: req 0000000011dfd96e length 2049/16384 zsI ==> 0 [002] d..1 7828.557949: ncm_unwrap_ntb: K: ncm_unwrap_ntb nth: 1751999342 [002] d..1 7828.557950: ncm_unwrap_ntb: K: ncm_unwrap_ntb blk_len: 0x800

Lecroy shows one byte coming in extra confirming that the byte is coming in from PC:

Transfer 2959 - Bytes Transferred(1025) Timestamp((18.524 843 590)

• Transaction 8391 - Data(1025 bytes) Timestamp(18.524 843 590) --- Packet 4063861 Data(1024 bytes) Duration(2.117us) Idle(14.700ns) Timestamp(18.524 843 590) --- Packet 4063863 Data(1 byte) Duration(66.160ns) Time(282.000ns) Timestamp(18.524 845 722)

According to Windows driver, no ZLP is needed if wBlockLength is non-zero, because the non-zero wBlockLength has already told the function side the size of transfer to be expected. However, there are in-market NCM devices that rely on ZLP as long as the wBlockLength is multiple of wMaxPacketSize. To deal with such devices, it pads an extra 0 at end so the transfer is no longer multiple of wMaxPacketSize.(CVE-2024-27405)

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

ipv6: fix potential "struct net" leak in inet6_rtm_getaddr()

It seems that if userspace provides a correct IFA_TARGET_NETNSID value but no IFA_ADDRESS and IFA_LOCAL attributes, inet6_rtm_getaddr() returns -EINVAL with an elevated "struct net" refcount.(CVE-2024-27417)

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

netfilter: nf_tables: flush pending destroy work before exit_net release

Similar to 2c9f0293280e ("netfilter: nf_tables: flush pending destroy work before netlink notifier") to address a race between exit_net and the destroy workqueue.

The trace below shows an element to be released via destroy workqueue while exit_net path (triggered via module removal) has already released the set that is used in such transaction.

[ 1360.547789] BUG: KASAN: slab-use-after-free in nf_tables_trans_destroy_work+0x3f5/0x590 [nf_tables] [ 1360.547861] Read of size 8 at addr ffff888140500cc0 by task kworker/4:1/152465 [ 1360.547870] CPU: 4 PID: 152465 Comm: kworker/4:1 Not tainted 6.8.0+ #359 [ 1360.547882] Workqueue: events nf_tables_trans_destroy_work [nf_tables] [ 1360.547984] Call Trace: [ 1360.547991] <TASK> [ 1360.547998] dump_stack_lvl+0x53/0x70 [ 1360.548014] …

The Linux Kernel, the operating system core itself.

Security Fix(es):

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

net: ethernet: fix potential use-after-free in ec_bhf_remove

static void ec_bhf_remove(struct pci_dev *dev) { ... struct ec_bhf_priv *priv = netdev_priv(net_dev);

unregister_netdev(net_dev);
free_netdev(net_dev);

pci_iounmap(dev, priv->dma_io);
pci_iounmap(dev, priv->io);

... }

priv is netdev private data, but it is used after free_netdev(). It can cause use-after-free when accessing priv pointer. So, fix it by moving free_netdev() after pci_iounmap() calls.(CVE-2021-47235)

Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.(CVE-2021-47285)

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

mac80211: track only QoS data frames for admission control

For admission control, obviously all of that only works for QoS data frames, otherwise we cannot even access the QoS field in the header.

Syzbot reported (see below) an uninitialized value here due to a status of a non-QoS nullfunc packet, which isn't even long enough to contain the QoS header.

Fix this to only do anything for QoS data packets.(CVE-2021-47602)

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

scsi: bnx2fc: Make bnx2fc_recv_frame() mp safe

Running tests with a debug kernel shows that bnx2fc_recv_frame() is modifying the per_cpu lport stats counters in a non-mpsafe way. Just boot a debug kernel and run the bnx2fc driver with the hardware enabled.

[ 1391.699147] BUG: using smp_processor_id() in preemptible [00000000] code: bnx2fc_ [ 1391.699160] caller is bnx2fc_recv_frame+0xbf9/0x1760 [bnx2fc] [ 1391.699174] CPU: 2 PID: 4355 Comm: bnx2fc_l2_threa Kdump: loaded Tainted: G B [ 1391.699180] Hardware name: HP ProLiant DL120 G7, BIOS J01 07/01/2013 [ 1391.699183] Call Trace: [ 1391.699188] dump_stack_lvl+0x57/0x7d [ 1391.699198] check_preemption_disabled+0xc8/0xd0 [ 1391.699205] bnx2fc_recv_frame+0xbf9/0x1760 [bnx2fc] [ 1391.699215] ? do_raw_spin_trylock+0xb5/0x180 [ 1391.699221] ? bnx2fc_npiv_create_vports.isra.0+0x4e0/0x4e0 [bnx2fc] [ 1391.699229] ? bnx2fc_l2_rcv_thread+0xb7/0x3a0 [bnx2fc] [ 1391.699240] bnx2fc_l2_rcv_thread+0x1af/0x3a0 [bnx2fc] [ 1391.699250] ? bnx2fc_ulp_init+0xc0/0xc0 [bnx2fc] [ 1391.699258] kthread+0x364/0x420 [ 1391.699263] ? _raw_spin_unlock_irq+0x24/0x50 [ 1391.699268] ? set_kthread_struct+0x100/0x100 [ 1391.699273] ret_from_fork+0x22/0x30

Restore the old get_cpu/put_cpu code with some modifications to reduce the size of the critical section.(CVE-2022-48715)

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

rpmsg: char: Fix race between the release of rpmsg_ctrldev and cdev

struct rpmsg_ctrldev contains a struct cdev. The current code frees the rpmsg_ctrldev struct in rpmsg_ctrldev_release_device(), but the cdev is a managed object, therefore its release is not predictable and the rpmsg_ctrldev could be freed before the cdev is entirely released, as in the backtrace below.

[ 93.625603] ODEBUG: free active (active state 0) object type: timer_list hint: delayed_work_timer_fn+0x0/0x7c [ 93.636115] WARNING: CPU: 0 PID: 12 at lib/debugobjects.c:488 debug_print_object+0x13c/0x1b0 [ 93.644799] Modules linked in: veth xt_cgroup xt_MASQUERADE rfcomm algif_hash algif_skcipher af_alg uinput ip6table_nat fuse uvcvideo videobuf2_vmalloc venus_enc venus_dec videobuf2_dma_contig hci_uart btandroid btqca snd_soc_rt5682_i2c bluetooth qcom_spmi_temp_alarm snd_soc_rt5682v [ 93.715175] CPU: 0 PID: 12 Comm: kworker/0:1 Tainted: G B 5.4.163-lockdep #26 [ 93.723855] Hardware name: Google Lazor (rev3 - 8) with LTE (DT) [ 93.730055] Workqueue: events kobject_delayed_cleanup [ 93.735271] pstate: 60c00009 (nZCv daif +PAN +UAO) [ 93.740216] pc : debug_print_object+0x13c/0x1b0 [ 93.744890] lr :…

The Linux Kernel, the operating system core itself.

Security Fix(es):

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

ubifs: Set page uptodate in the correct place

Page cache reads are lockless, so setting the freshly allocated page uptodate before we've overwritten it with the data it's supposed to have in it will allow a simultaneous reader to see old data. Move the call to SetPageUptodate into ubifs_write_end(), which is after we copied the new data into the page.(CVE-2024-35821)

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

kprobes: Fix possible use-after-free issue on kprobe registration

When unloading a module, its state is changing MODULE_STATE_LIVE -> MODULE_STATE_GOING -> MODULE_STATE_UNFORMED. Each change will take a time. is_module_text_address() and __module_text_address() works with MODULE_STATE_LIVE and MODULE_STATE_GOING. If we use is_module_text_address() and __module_text_address() separately, there is a chance that the first one is succeeded but the next one is failed because module->state becomes MODULE_STATE_UNFORMED between those operations.

In check_kprobe_address_safe(), if the second __module_text_address() is failed, that is ignored because it expected a kernel_text address. But it may have failed simply because module->state has been changed to MODULE_STATE_UNFORMED. In this case, arm_kprobe() will try to modify non-exist module text address (use-after-free).

To fix this problem, we should not use separated is_module_text_address() and __module_text_address(), but use only __module_text_address() once and do try_module_get(module) which is only available with MODULE_STATE_LIVE.(CVE-2024-35955)

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

net/sched: taprio: always validate TCA_TAPRIO_ATTR_PRIOMAP

If one TCA_TAPRIO_ATTR_PRIOMAP attribute has been provided, taprio_parse_mqprio_opt() must validate it, or userspace can inject arbitrary data to the kernel, the second time taprio_change() is called.

First call (with valid attributes) sets dev->num_tc to a non zero value.

Second call (with arbitrary mqprio attributes) returns early from taprio_parse_mqprio_opt() and bad things can happen.(CVE-2024-36974)

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

tcp: Fix shift-out-of-bounds in dctcp_update_alpha().

In dctcp_update_alpha(), we use a module parameter dctcp_shift_g as follows:

alpha -= min_not_zero(alpha, alpha >> dctcp_shift_g); ... delivered_ce <<= (10 - dctcp_shift_g);

It seems syzkaller started fuzzing module parameters and triggered shift-out-of-bounds [0] by setting 100 to dctcp_shift_g:

memcpy((void*)0x20000080, "/sys/module/tcp_dctcp/parameters/dctcp_shift_g\000", 47); res = syscall(__NR_openat, /fd=/0xffffffffffffff9cul, /file=/0x20000080ul, /flags=/2ul, /mode=/0ul); memcpy((void*)0x20000000, "100\000", 4); syscall(__NR_write, /fd=/r[0], /val=/0x20000000ul, /len=/4ul);

Let's limit the max value of dctcp_shift_g by param_set_uint_minmax().

With this patch:

echo 10 > /sys/module/tcp_dctcp/parameters/dctcp_shift_g

cat /sys/module/tcp_dctcp/parameters/dctcp_shift_g

10

echo 11 > /sys/module/tcp_dctcp/parameters/dctcp_shift_g

-bash: echo: write error: Invalid argument

[0]: UBSAN: shift-out-of-bounds in net/ipv4/tcp_dctcp.c:143:12 shift exponent 100 is too large for 32-bit type 'u32' (aka 'unsigned int') CPU: 0 PID: 8083 Comm: syz-executor345 Not tainted 6.9.0-05151-g1b294a1f3561 #2 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1.1 04/01/2014 Call Trace: <TASK> __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x201/0x300 lib/dump_stack.c:114 ubsan_epilogue lib/ubsan.c:231 [inline] __ubsan_handle_shift_out_of_bounds+0x346/0x3a0…

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…

The Linux Kernel, the operating system core itself.

Security Fix(es):

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:

Bluetooth: L2CAP: Fix slab-use-after-free in l2cap_connect()

Extend a critical section to prevent chan from early freeing. Also make the l2cap_connect() return type void. Nothing is using the returned value but it is ugly to return a potentially freed pointer. Making it void will help with backports because earlier kernels did use the return value. Now the compile will break for kernels where this patch is not a complete fix.

Call stack summary:

[use] l2cap_bredr_sig_cmd l2cap_connect ┌ mutex_lock(&conn->chan_lock); │ chan = pchan->ops->new_connection(pchan); <- alloc chan │ __l2cap_chan_add(conn, chan); │ l2cap_chan_hold(chan); │ list_add(&chan->list, &conn->chan_l); ... (1) └ mutex_unlock(&conn->chan_lock); chan->conf_state ... (4) <- use after free

[free] l2cap_conn_del ┌ mutex_lock(&conn->chan_lock); │ foreach chan in conn->chan_l: ... (2) │ l2cap_chan_put(chan); │ l2cap_chan_destroy │ kfree(chan) ... (3) <- chan freed └ mutex_unlock(&conn->chan_lock);

================================================================== BUG: KASAN: slab-use-after-free in instrument_atomic_read include/linux/instrumented.h:68 [inline] BUG: KASAN: slab-use-after-free in _test_bit include/asm-generic/bitops/instrumented-non-atomic.h:141 [inline] BUG: KASAN: slab-use-after-free in l2cap_connect+0xa67/0x11a0 net/bluetooth/l2cap_core.c:4260 Read of size 8 at addr ffff88810bf040a0 by task kworker/u3:1/311(CVE-2024-36013)

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

net: hns3: fix kernel crash when devlink reload during pf initialization

The devlink reload process will access the hardware resources, but the register operation is done before the hardware is initialized. So, processing the devlink reload during initialization may lead to kernel crash. This patch fixes this by taking devl_lock during initialization.(CVE-2024-36021)

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

bnxt_re: avoid shift undefined behavior in bnxt_qplib_alloc_init_hwq

Undefined behavior is triggered when bnxt_qplib_alloc_init_hwq is called with hwq_attr->aux_depth != 0 and hwq_attr->aux_stride == 0. In that case, "roundup_pow_of_two(hwq_attr->aux_stride)" gets called. roundup_pow_of_two is documented as undefined for 0.

Fix it in the one caller that had this combination.

The undefined behavior was detected by UBSAN: UBSAN: shift-out-of-bounds in ./include/linux/log2.h:57:13 shift exponent 64 is too large for 64-bit type 'long unsigned int' CPU: 24 PID: 1075 Comm: (udev-worker) Not tainted 6.9.0-rc6+ #4 Hardware name: Abacus electric, s.r.o. - [email protected] Super Server/H12SSW-iN, BIOS 2.7 10/25/2023 Call Trace: <TASK> dump_stack_lvl+0x5d/0x80 ubsan_epilogue+0x5/0x30 __ubsan_handle_shift_out_of_bounds.cold+0x61/0xec …

In the Linux kernel, the following vulnerability has been resolved: um: Add winch to winch_handlers before registering winch IRQ Registering a winch IRQ is racy, an interrupt may occur before the winch is added to the winch_handlers list. If that happens, register_winch_irq() adds to that list a winch that is scheduled to be (or has already been) freed, causing a panic later in winch_cleanup(). Avoid the race by adding the winch to the winch_handlers list before registering the IRQ, and rolling back if um_request_irq() fails.

• CVE-url: https://ubuntu.com/security/CVE-2024-39467
  • f2fs: fix to do sanity check on i_xattr_nid in sanity_check_inode()
• CVE-url: https://ubuntu.com/security/CVE-2024-36940
  • pinctrl: core: delete incorrect free in pinctrl_enable()
• CVE-url: https://ubuntu.com/security/CVE-2024-38659
  • enic: Validate length of nl attributes in enic_set_vf_port
• CVE-url: https://ubuntu.com/security/CVE-2024-38560
  • scsi: bfa: Ensure the copied buf is NUL terminated
• CVE-url: https://ubuntu.com/security/CVE-2024-36941
  • wifi: nl80211: don't free NULL coalescing rule
• CVE-url: https://ubuntu.com/security/CVE-2024-27401
  • firewire: nosy: ensure user_length is taken into account when fetching packet contents
• CVE-url: https://ubuntu.com/security/CVE-2024-39276
  • ext4: fix mb_cache_entry's e_refcnt leak in ext4_xattr_block_cache_find()
• CVE-url: https://ubuntu.com/security/CVE-2024-27398
  • Bluetooth: Fix use-after-free bugs caused by sco_sock_timeout
• CVE-url: https://ubuntu.com/security/CVE-2024-36964
  • fs/9p: only translate RWX permissions for plain 9P2000
• CVE-url: https://ubuntu.com/security/CVE-2024-38601
  • ring-buffer: Fix a race between readers and resize checks
• CVE-url: https://ubuntu.com/security/CVE-2024-39475
  • fbdev: savage: Handle err return when savagefb_check_var failed
• CVE-url: https://ubuntu.com/security/CVE-2024-38578
  • ecryptfs: Fix buffer size for tag 66 packet
• CVE-url: https://ubuntu.com/security/CVE-2024-36950
  • firewire: ohci: mask bus reset interrupts between ISR and bottom half
• CVE-url: https://ubuntu.com/security/CVE-2024-38589
  • netrom: fix possible dead-lock in nr_rt_ioctl()
• CVE-url: https://ubuntu.com/security/CVE-2024-38627
  • stm class: Fix a double free in stm_register_device()
• CVE-url: https://ubuntu.com/security/CVE-2024-38612
  • ipv6: sr: fix invalid unregister error path
• CVE-url: https://ubuntu.com/security/CVE-2024-36905
  • tcp: defer shutdown(SEND_SHUTDOWN) for TCP_SYN_RECV sockets
• CVE-url: https://ubuntu.com/security/CVE-2024-38559
  • scsi: qedf: Ensure the copied buf is NUL terminated
• CVE-url: https://ubuntu.com/security/CVE-2024-33621
  • ipvlan: Dont Use skb->sk in ipvlan_process_v{4,6}_outbound
• CVE-url: https://ubuntu.com/security/CVE-2024-38637
  • greybus: lights: check return of get_channel_from_mode
• CVE-url: https://ubuntu.com/security/CVE-2024-38567
  • wifi: carl9170: add a proper sanity check for endpoints
• CVE-url: https://ubuntu.com/security/CVE-2024-39301
  • net/9p: fix uninit-value in p9_client_rpc()
• CVE-url: https://ubuntu.com/security/CVE-2024-36919
  • scsi: bnx2fc: Remove spin_lock_bh while releasing resources after upload
• CVE-url: https://ubuntu.com/security/CVE-2022-48772
  • media: lgdt3306a: Add a check against null-pointer-def
• CVE-url: https://ubuntu.com/security/CVE-2024-36017
  • rtnetlink: Correct nested IFLA_VF_VLAN_LIST attribute validation
• CVE-url: https://ubuntu.com/security/CVE-2024-36934
  • bna: ensure the copied buf is NUL terminated
• CVE-url: https://ubuntu.com/security/CVE-2024-38558
  • net: openvswitch: fix overwriting ct original tuple for ICMPv6
• CVE-url: https://ubuntu.com/security/CVE-2024-38565
  • USB: core: Add routines for endpoint checks in old drivers
  • wifi: ar5523: enable proper endpoint verification
• CVE-url: https://ubuntu.com/security/CVE-2024-38600
  • ALSA: control: Add verification for kctl accesses
  • ALSA: control: Track in-flight control read/write/tlv accesses
  • ALSA: Fix deadlocks with kctl removals at disconnection
• CVE-url: https://ubuntu.com/security/CVE-2024-31076
  • genirq/cpuhotplug, x86/vector: Prevent vector leak during CPU offline
• CVE-url: https://ubuntu.com/security/CVE-2024-36015
  • ida: Add new API
  • ppdev: Remove usage of the deprecated…

• CVE-url: https://ubuntu.com/security/CVE-2024-39467
  • f2fs: fix to do sanity check on i_xattr_nid in sanity_check_inode()
• CVE-url: https://ubuntu.com/security/CVE-2024-36940
  • pinctrl: core: delete incorrect free in pinctrl_enable()
• CVE-url: https://ubuntu.com/security/CVE-2024-38659
  • enic: Validate length of nl attributes in enic_set_vf_port
• CVE-url: https://ubuntu.com/security/CVE-2024-38560
  • scsi: bfa: Ensure the copied buf is NUL terminated
• CVE-url: https://ubuntu.com/security/CVE-2024-36941
  • wifi: nl80211: don't free NULL coalescing rule
• CVE-url: https://ubuntu.com/security/CVE-2024-27401
  • firewire: nosy: ensure user_length is taken into account when fetching packet contents
• CVE-url: https://ubuntu.com/security/CVE-2024-39276
  • ext4: fix mb_cache_entry's e_refcnt leak in ext4_xattr_block_cache_find()
• CVE-url: https://ubuntu.com/security/CVE-2024-27398
  • Bluetooth: Fix use-after-free bugs caused by sco_sock_timeout
• CVE-url: https://ubuntu.com/security/CVE-2024-36964
  • fs/9p: only translate RWX permissions for plain 9P2000
• CVE-url: https://ubuntu.com/security/CVE-2024-38601
  • ring-buffer: Fix a race between readers and resize checks
• CVE-url: https://ubuntu.com/security/CVE-2024-39475
  • fbdev: savage: Handle err return when savagefb_check_var failed
• CVE-url: https://ubuntu.com/security/CVE-2024-38578
  • ecryptfs: Fix buffer size for tag 66 packet
• CVE-url: https://ubuntu.com/security/CVE-2024-36950
  • firewire: ohci: mask bus reset interrupts between ISR and bottom half
• CVE-url: https://ubuntu.com/security/CVE-2024-38589
  • netrom: fix possible dead-lock in nr_rt_ioctl()
• CVE-url: https://ubuntu.com/security/CVE-2024-38627
  • stm class: Fix a double free in stm_register_device()
• CVE-url: https://ubuntu.com/security/CVE-2024-38612
  • ipv6: sr: fix invalid unregister error path
• CVE-url: https://ubuntu.com/security/CVE-2024-36905
  • tcp: defer shutdown(SEND_SHUTDOWN) for TCP_SYN_RECV sockets
• CVE-url: https://ubuntu.com/security/CVE-2024-38559
  • scsi: qedf: Ensure the copied buf is NUL terminated
• CVE-url: https://ubuntu.com/security/CVE-2024-33621
  • ipvlan: Dont Use skb->sk in ipvlan_process_v{4,6}_outbound
• CVE-url: https://ubuntu.com/security/CVE-2024-38637
  • greybus: lights: check return of get_channel_from_mode
• CVE-url: https://ubuntu.com/security/CVE-2024-38567
  • wifi: carl9170: add a proper sanity check for endpoints
• CVE-url: https://ubuntu.com/security/CVE-2024-39301
  • net/9p: fix uninit-value in p9_client_rpc()
• CVE-url: https://ubuntu.com/security/CVE-2024-36919
  • scsi: bnx2fc: Remove spin_lock_bh while releasing resources after upload
• CVE-url: https://ubuntu.com/security/CVE-2022-48772
  • media: lgdt3306a: Add a check against null-pointer-def
• CVE-url: https://ubuntu.com/security/CVE-2024-36017
  • rtnetlink: Correct nested IFLA_VF_VLAN_LIST attribute validation
• CVE-url: https://ubuntu.com/security/CVE-2024-36934
  • bna: ensure the copied buf is NUL terminated
• CVE-url: https://ubuntu.com/security/CVE-2024-38558
  • net: openvswitch: fix overwriting ct original tuple for ICMPv6
• CVE-url: https://ubuntu.com/security/CVE-2024-38565
  • USB: core: Add routines for endpoint checks in old drivers
  • wifi: ar5523: enable proper endpoint verification
• CVE-url: https://ubuntu.com/security/CVE-2024-38600
  • ALSA: control: Add verification for kctl accesses
  • ALSA: control: Track in-flight control read/write/tlv accesses
  • ALSA: Fix deadlocks with kctl removals at disconnection
• CVE-url: https://ubuntu.com/security/CVE-2024-31076
  • genirq/cpuhotplug, x86/vector: Prevent vector leak during CPU offline
• CVE-url: https://ubuntu.com/security/CVE-2024-36015
  • ida: Add new API
  • ppdev: Remove usage of the deprecated…

• CVE-url: https://ubuntu.com/security/CVE-2024-36939
  • NFS: Cleanup - add nfs_clients_exit to mirror nfs_clients_init
  • nfs: expose /proc/net/sunrpc/nfs in net namespaces
  • sunrpc: add a struct rpc_stats arg to rpc_create_args
  • nfs: make the rpc_stat per net namespace
  • nfs: Handle error of rpc_proc_register() in nfs_net_init().
• CVE-url: https://ubuntu.com/security/CVE-2024-38600
  • ALSA: Fix deadlocks with kctl removals at disconnection
• CVE-url: https://ubuntu.com/security/CVE-2024-36270
  • netfilter: tproxy: bail out if IP has been disabled on the device
• CVE-url: https://ubuntu.com/security/CVE-2024-38659
  • enic: Validate length of nl attributes in enic_set_vf_port
• CVE-url: https://ubuntu.com/security/CVE-2024-38560
  • scsi: bfa: Ensure the copied buf is NUL terminated
• CVE-url: https://ubuntu.com/security/CVE-2024-36941
  • wifi: nl80211: don't free NULL coalescing rule
• CVE-url: https://ubuntu.com/security/CVE-2024-27401
  • firewire: nosy: ensure user_length is taken into account when fetching packet contents
• CVE-url: https://ubuntu.com/security/CVE-2024-36964
  • fs/9p: only translate RWX permissions for plain 9P2000
• CVE-url: https://ubuntu.com/security/CVE-2024-38601
  • ring-buffer: Fix a race between readers and resize checks
• CVE-url: https://ubuntu.com/security/CVE-2024-39475
  • fbdev: savage: Handle err return when savagefb_check_var failed
• CVE-url: https://ubuntu.com/security/CVE-2024-38578
  • ecryptfs: Fix buffer size for tag 66 packet
• CVE-url: https://ubuntu.com/security/CVE-2024-36950
  • firewire: ohci: mask bus reset interrupts between ISR and bottom half
• CVE-url: https://ubuntu.com/security/CVE-2024-38589
  • netrom: fix possible dead-lock in nr_rt_ioctl()
• CVE-url: https://ubuntu.com/security/CVE-2024-38627
  • stm class: Fix a double free in stm_register_device()
• CVE-url: https://ubuntu.com/security/CVE-2024-36905
  • tcp: suppress too verbose messages in tcp_send_ack()
  • tcp: defer shutdown(SEND_SHUTDOWN) for TCP_SYN_RECV sockets
• CVE-url: https://ubuntu.com/security/CVE-2024-33621
  • ipvlan: Dont Use skb->sk in ipvlan_process_v{4,6}_outbound
• CVE-url: https://ubuntu.com/security/CVE-2024-38567
  • wifi: carl9170: add a proper sanity check for endpoints
• CVE-url: https://ubuntu.com/security/CVE-2024-39301
  • net/9p: fix uninit-value in p9_client_rpc()
• CVE-url: https://ubuntu.com/security/CVE-2024-36919
  • scsi: bnx2fc: Remove spin_lock_bh while releasing resources after upload
• CVE-url: https://ubuntu.com/security/CVE-2024-36934
  • new helper: memdup_user_nul()
  • bna: ensure the copied buf is NUL terminated
• CVE-url: https://ubuntu.com/security/CVE-2024-38558
  • net: openvswitch: fix overwriting ct original tuple for ICMPv6
• CVE-url: https://ubuntu.com/security/CVE-2024-38565
  • USB: core: Add routines for endpoint checks in old drivers
  • wifi: ar5523: enable proper endpoint verification
• CVE-url: https://ubuntu.com/security/CVE-2024-38621
  • media: stk1160: fix bounds checking in stk1160_copy_video()
• CVE-url: https://ubuntu.com/security/CVE-2024-35947
  • dyndbg: fix old BUG_ON in >control parser
• CVE-url: https://ubuntu.com/security/CVE-2024-27399
  • Bluetooth: l2cap: fix null-ptr-deref in l2cap_chan_timeout
• CVE-url: https://ubuntu.com/security/CVE-2024-38618
  • ALSA: timer: Simplify timer hw resolution calls
  • ALSA: timer: Set lower bound of start tick time
• CVE-url: https://ubuntu.com/security/CVE-2024-36286
  • netfilter: nfnetlink_queue: acquire rcu_read_lock() in instance_destroy_rcu()
• CVE-url: https://ubuntu.com/security/CVE-2024-38607
  • macintosh/via-macii: Fix "BUG: sleeping function called from invalid context"
• CVE-url: https://ubuntu.com/security/CVE-2024-37356
  • params: lift…

• CVE-url: https://ubuntu.com/security/CVE-2024-36939
  • NFS: Cleanup - add nfs_clients_exit to mirror nfs_clients_init
  • nfs: expose /proc/net/sunrpc/nfs in net namespaces
  • sunrpc: add a struct rpc_stats arg to rpc_create_args
  • nfs: make the rpc_stat per net namespace
  • nfs: Handle error of rpc_proc_register() in nfs_net_init().
• CVE-url: https://ubuntu.com/security/CVE-2024-38600
  • ALSA: Fix deadlocks with kctl removals at disconnection
• CVE-url: https://ubuntu.com/security/CVE-2024-36270
  • netfilter: tproxy: bail out if IP has been disabled on the device
• CVE-url: https://ubuntu.com/security/CVE-2024-38659
  • enic: Validate length of nl attributes in enic_set_vf_port
• CVE-url: https://ubuntu.com/security/CVE-2024-38560
  • scsi: bfa: Ensure the copied buf is NUL terminated
• CVE-url: https://ubuntu.com/security/CVE-2024-36941
  • wifi: nl80211: don't free NULL coalescing rule
• CVE-url: https://ubuntu.com/security/CVE-2024-27401
  • firewire: nosy: ensure user_length is taken into account when fetching packet contents
• CVE-url: https://ubuntu.com/security/CVE-2024-36964
  • fs/9p: only translate RWX permissions for plain 9P2000
• CVE-url: https://ubuntu.com/security/CVE-2024-38601
  • ring-buffer: Fix a race between readers and resize checks
• CVE-url: https://ubuntu.com/security/CVE-2024-39475
  • fbdev: savage: Handle err return when savagefb_check_var failed
• CVE-url: https://ubuntu.com/security/CVE-2024-38578
  • ecryptfs: Fix buffer size for tag 66 packet
• CVE-url: https://ubuntu.com/security/CVE-2024-36950
  • firewire: ohci: mask bus reset interrupts between ISR and bottom half
• CVE-url: https://ubuntu.com/security/CVE-2024-38589
  • netrom: fix possible dead-lock in nr_rt_ioctl()
• CVE-url: https://ubuntu.com/security/CVE-2024-38627
  • stm class: Fix a double free in stm_register_device()
• CVE-url: https://ubuntu.com/security/CVE-2024-36905
  • tcp: suppress too verbose messages in tcp_send_ack()
  • tcp: defer shutdown(SEND_SHUTDOWN) for TCP_SYN_RECV sockets
• CVE-url: https://ubuntu.com/security/CVE-2024-33621
  • ipvlan: Dont Use skb->sk in ipvlan_process_v{4,6}_outbound
• CVE-url: https://ubuntu.com/security/CVE-2024-38567
  • wifi: carl9170: add a proper sanity check for endpoints
• CVE-url: https://ubuntu.com/security/CVE-2024-39301
  • net/9p: fix uninit-value in p9_client_rpc()
• CVE-url: https://ubuntu.com/security/CVE-2024-36919
  • scsi: bnx2fc: Remove spin_lock_bh while releasing resources after upload
• CVE-url: https://ubuntu.com/security/CVE-2024-36934
  • new helper: memdup_user_nul()
  • bna: ensure the copied buf is NUL terminated
• CVE-url: https://ubuntu.com/security/CVE-2024-38558
  • net: openvswitch: fix overwriting ct original tuple for ICMPv6
• CVE-url: https://ubuntu.com/security/CVE-2024-38565
  • USB: core: Add routines for endpoint checks in old drivers
  • wifi: ar5523: enable proper endpoint verification
• CVE-url: https://ubuntu.com/security/CVE-2024-38621
  • media: stk1160: fix bounds checking in stk1160_copy_video()
• CVE-url: https://ubuntu.com/security/CVE-2024-35947
  • dyndbg: fix old BUG_ON in >control parser
• CVE-url: https://ubuntu.com/security/CVE-2024-27399
  • Bluetooth: l2cap: fix null-ptr-deref in l2cap_chan_timeout
• CVE-url: https://ubuntu.com/security/CVE-2024-38618
  • ALSA: timer: Simplify timer hw resolution calls
  • ALSA: timer: Set lower bound of start tick time
• CVE-url: https://ubuntu.com/security/CVE-2024-36286
  • netfilter: nfnetlink_queue: acquire rcu_read_lock() in instance_destroy_rcu()
• CVE-url: https://ubuntu.com/security/CVE-2024-38607
  • macintosh/via-macii: Fix "BUG: sleeping function called from invalid context"
• CVE-url: https://ubuntu.com/security/CVE-2024-37356
  • params: lift…

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

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

Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:

• ARM64 architecture;
• M68K architecture;
• User-Mode Linux (UML);
• x86 architecture;
• Accessibility subsystem;
• Character device driver;
• Clock framework and drivers;
• CPU frequency scaling framework;
• Hardware crypto device drivers;
• Buffer Sharing and Synchronization framework;
• FireWire subsystem;
• GPU drivers;
• HW tracing;
• Macintosh device drivers;
• Multiple devices driver;
• Media drivers;
• Network drivers;
• Pin controllers subsystem;
• S/390 drivers;
• SCSI drivers;
• SoundWire subsystem;
• Greybus lights staging drivers;
• TTY drivers;
• Framebuffer layer;
• Virtio drivers;
• 9P distributed file system;
• eCrypt file system;
• EROFS file system;
• Ext4 file system;
• F2FS file system;
• JFFS2 file system;
• Network file system client;
• NILFS2 file system;
• SMB network file system;
• Kernel debugger infrastructure;
• IRQ subsystem;
• Tracing infrastructure;
• Dynamic debug library;
• 9P file system network protocol;
• Bluetooth subsystem;
• Networking core;
• IPv4 networking;
• IPv6 networking;
• Netfilter;
• NET/ROM layer;
• NFC subsystem;
• NSH protocol;
• Open vSwitch;
• Phonet protocol;
• TIPC protocol;
• Unix domain sockets;
• Wireless networking;
• eXpress Data Path;
• XFRM subsystem;
• ALSA framework; (CVE-2024-36934, CVE-2024-38578, CVE-2024-38600, CVE-2024-27399, CVE-2024-39276, CVE-2024-38596, CVE-2024-36933, CVE-2024-36919, CVE-2024-35976, CVE-2024-37356, CVE-2023-52585, CVE-2024-38558, CVE-2024-38560, CVE-2024-38634, CVE-2024-36959, CVE-2024-38633, CVE-2024-36886, CVE-2024-27398, CVE-2024-39493, CVE-2024-26886, CVE-2024-31076, CVE-2024-38559, CVE-2024-38615, CVE-2024-36971, CVE-2024-38627, CVE-2024-36964, CVE-2024-38780, CVE-2024-37353, CVE-2024-38621, CVE-2024-36883, CVE-2024-39488, CVE-2024-38661, CVE-2024-36939, CVE-2024-38589, CVE-2024-38565, CVE-2024-38381, CVE-2024-35947, CVE-2024-36905, CVE-2022-48772, CVE-2024-36017, CVE-2024-36946, CVE-2024-27401, CVE-2024-38579, CVE-2024-38612, CVE-2024-38598, CVE-2024-38635, CVE-2024-38587, CVE-2024-38567, CVE-2024-38549, CVE-2024-36960, CVE-2023-52752, CVE-2024-27019, CVE-2024-38601, CVE-2024-39489, CVE-2024-39467, CVE-2023-52882, CVE-2024-38583, CVE-2024-39480, CVE-2024-38607, CVE-2024-36940, CVE-2024-38659, CVE-2023-52434, CVE-2024-36015, CVE-2024-38582, CVE-2024-36950, CVE-2024-38552, CVE-2024-33621, CVE-2024-36954, CVE-2024-39475, CVE-2024-39301, CVE-2024-38599, CVE-2024-36902, CVE-2024-36286, CVE-2024-38613, CVE-2024-38637, CVE-2024-36941, CVE-2024-36014, CVE-2024-38618, CVE-2024-36904, CVE-2024-36270, CVE-2024-39292, CVE-2024-39471, CVE-2022-48674)

Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:

• ARM64 architecture;
• M68K architecture;
• User-Mode Linux (UML);
• x86 architecture;
• Accessibility subsystem;
• Character device driver;
• Clock framework and drivers;
• CPU frequency scaling framework;
• Hardware crypto device drivers;
• Buffer Sharing and Synchronization framework;
• FireWire subsystem;
• GPU drivers;
• HW tracing;
• Macintosh device drivers;
• Multiple devices driver;
• Media drivers;
• Network drivers;
• Pin controllers subsystem;
• S/390 drivers;
• SCSI drivers;
• SoundWire subsystem;
• Greybus lights staging drivers;
• TTY drivers;
• Framebuffer layer;
• Virtio drivers;
• 9P distributed file system;
• eCrypt file system;
• EROFS file system;
• Ext4 file system;
• F2FS file system;
• JFFS2 file system;
• Network file system client;
• NILFS2 file system;
• SMB network file system;
• Kernel debugger infrastructure;
• IRQ subsystem;
• Tracing infrastructure;
• Dynamic debug library;
• 9P file system network protocol;
• Bluetooth subsystem;
• Networking core;
• IPv4 networking;
• IPv6 networking;
• Netfilter;
• NET/ROM layer;
• NFC subsystem;
• NSH protocol;
• Open vSwitch;
• Phonet protocol;
• TIPC protocol;
• Unix domain sockets;
• Wireless networking;
• eXpress Data Path;
• XFRM subsystem;
• ALSA framework; (CVE-2024-36934, CVE-2024-38578, CVE-2024-38600, CVE-2024-27399, CVE-2024-39276, CVE-2024-38596, CVE-2024-36933, CVE-2024-36919, CVE-2024-35976, CVE-2024-37356, CVE-2023-52585, CVE-2024-38558, CVE-2024-38560, CVE-2024-38634, CVE-2024-36959, CVE-2024-38633, CVE-2024-36886, CVE-2024-27398, CVE-2024-39493, CVE-2024-26886, CVE-2024-31076, CVE-2024-38559, CVE-2024-38615, CVE-2024-36971, CVE-2024-38627, CVE-2024-36964, CVE-2024-38780, CVE-2024-37353, CVE-2024-38621, CVE-2024-36883, CVE-2024-39488, CVE-2024-38661, CVE-2024-36939, CVE-2024-38589, CVE-2024-38565, CVE-2024-38381, CVE-2024-35947, CVE-2024-36905, CVE-2022-48772, CVE-2024-36017, CVE-2024-36946, CVE-2024-27401, CVE-2024-38579, CVE-2024-38612, CVE-2024-38598, CVE-2024-38635, CVE-2024-38587, CVE-2024-38567, CVE-2024-38549, CVE-2024-36960, CVE-2023-52752, CVE-2024-27019, CVE-2024-38601, CVE-2024-39489, CVE-2024-39467, CVE-2023-52882, CVE-2024-38583, CVE-2024-39480, CVE-2024-38607, CVE-2024-36940, CVE-2024-38659, CVE-2023-52434, CVE-2024-36015, CVE-2024-38582, CVE-2024-36950, CVE-2024-38552, CVE-2024-33621, CVE-2024-36954, CVE-2024-39475, CVE-2024-39301, CVE-2024-38599, CVE-2024-36902, CVE-2024-36286, CVE-2024-38613, CVE-2024-38637, CVE-2024-36941, CVE-2024-36014, CVE-2024-38618, CVE-2024-36904, CVE-2024-36270, CVE-2024-39292, CVE-2024-39471, CVE-2022-48674)

Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:

• ARM64 architecture;
• M68K architecture;
• User-Mode Linux (UML);
• x86 architecture;
• Accessibility subsystem;
• Character device driver;
• Clock framework and drivers;
• CPU frequency scaling framework;
• Hardware crypto device drivers;
• Buffer Sharing and Synchronization framework;
• FireWire subsystem;
• GPU drivers;
• HW tracing;
• Macintosh device drivers;
• Multiple devices driver;
• Media drivers;
• Network drivers;
• Pin controllers subsystem;
• S/390 drivers;
• SCSI drivers;
• SoundWire subsystem;
• Greybus lights staging drivers;
• TTY drivers;
• Framebuffer layer;
• Virtio drivers;
• 9P distributed file system;
• eCrypt file system;
• EROFS file system;
• Ext4 file system;
• F2FS file system;
• JFFS2 file system;
• Network file system client;
• NILFS2 file system;
• SMB network file system;
• Kernel debugger infrastructure;
• IRQ subsystem;
• Tracing infrastructure;
• Dynamic debug library;
• 9P file system network protocol;
• Bluetooth subsystem;
• Networking core;
• IPv4 networking;
• IPv6 networking;
• Netfilter;
• NET/ROM layer;
• NFC subsystem;
• NSH protocol;
• Open vSwitch;
• Phonet protocol;
• TIPC protocol;
• Unix domain sockets;
• Wireless networking;
• eXpress Data Path;
• XFRM subsystem;
• ALSA framework; (CVE-2024-36934, CVE-2024-38578, CVE-2024-38600, CVE-2024-27399, CVE-2024-39276, CVE-2024-38596, CVE-2024-36933, CVE-2024-36919, CVE-2024-35976, CVE-2024-37356, CVE-2023-52585, CVE-2024-38558, CVE-2024-38560, CVE-2024-38634, CVE-2024-36959, CVE-2024-38633, CVE-2024-36886, CVE-2024-27398, CVE-2024-39493, CVE-2024-26886, CVE-2024-31076, CVE-2024-38559, CVE-2024-38615, CVE-2024-36971, CVE-2024-38627, CVE-2024-36964, CVE-2024-38780, CVE-2024-37353, CVE-2024-38621, CVE-2024-36883, CVE-2024-39488, CVE-2024-38661, CVE-2024-36939, CVE-2024-38589, CVE-2024-38565, CVE-2024-38381, CVE-2024-35947, CVE-2024-36905, CVE-2022-48772, CVE-2024-36017, CVE-2024-36946, CVE-2024-27401, CVE-2024-38579, CVE-2024-38612, CVE-2024-38598, CVE-2024-38635, CVE-2024-38587, CVE-2024-38567, CVE-2024-38549, CVE-2024-36960, CVE-2023-52752, CVE-2024-27019, CVE-2024-38601, CVE-2024-39489, CVE-2024-39467, CVE-2023-52882, CVE-2024-38583, CVE-2024-39480, CVE-2024-38607, CVE-2024-36940, CVE-2024-38659, CVE-2023-52434, CVE-2024-36015, CVE-2024-38582, CVE-2024-36950, CVE-2024-38552, CVE-2024-33621, CVE-2024-36954, CVE-2024-39475, CVE-2024-39301, CVE-2024-38599, CVE-2024-36902, CVE-2024-36286, CVE-2024-38613, CVE-2024-38637, CVE-2024-36941, CVE-2024-36014, CVE-2024-38618, CVE-2024-36904, CVE-2024-36270, CVE-2024-39292, CVE-2024-39471, CVE-2022-48674)

Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:

• ARM64 architecture;
• M68K architecture;
• User-Mode Linux (UML);
• x86 architecture;
• Accessibility subsystem;
• Character device driver;
• Clock framework and drivers;
• CPU frequency scaling framework;
• Hardware crypto device drivers;
• Buffer Sharing and Synchronization framework;
• FireWire subsystem;
• GPU drivers;
• HW tracing;
• Macintosh device drivers;
• Multiple devices driver;
• Media drivers;
• Network drivers;
• Pin controllers subsystem;
• S/390 drivers;
• SCSI drivers;
• SoundWire subsystem;
• Greybus lights staging drivers;
• TTY drivers;
• Framebuffer layer;
• Virtio drivers;
• 9P distributed file system;
• eCrypt file system;
• EROFS file system;
• Ext4 file system;
• F2FS file system;
• JFFS2 file system;
• Network file system client;
• NILFS2 file system;
• SMB network file system;
• Kernel debugger infrastructure;
• IRQ subsystem;
• Tracing infrastructure;
• Dynamic debug library;
• 9P file system network protocol;
• Bluetooth subsystem;
• Networking core;
• IPv4 networking;
• IPv6 networking;
• Netfilter;
• NET/ROM layer;
• NFC subsystem;
• NSH protocol;
• Open vSwitch;
• Phonet protocol;
• TIPC protocol;
• Unix domain sockets;
• Wireless networking;
• eXpress Data Path;
• XFRM subsystem;
• ALSA framework; (CVE-2024-36934, CVE-2024-38578, CVE-2024-38600, CVE-2024-27399, CVE-2024-39276, CVE-2024-38596, CVE-2024-36933, CVE-2024-36919, CVE-2024-35976, CVE-2024-37356, CVE-2023-52585, CVE-2024-38558, CVE-2024-38560, CVE-2024-38634, CVE-2024-36959, CVE-2024-38633, CVE-2024-36886, CVE-2024-27398, CVE-2024-39493, CVE-2024-26886, CVE-2024-31076, CVE-2024-38559, CVE-2024-38615, CVE-2024-36971, CVE-2024-38627, CVE-2024-36964, CVE-2024-38780, CVE-2024-37353, CVE-2024-38621, CVE-2024-36883, CVE-2024-39488, CVE-2024-38661, CVE-2024-36939, CVE-2024-38589, CVE-2024-38565, CVE-2024-38381, CVE-2024-35947, CVE-2024-36905, CVE-2022-48772, CVE-2024-36017, CVE-2024-36946, CVE-2024-27401, CVE-2024-38579, CVE-2024-38612, CVE-2024-38598, CVE-2024-38635, CVE-2024-38587, CVE-2024-38567, CVE-2024-38549, CVE-2024-36960, CVE-2023-52752, CVE-2024-27019, CVE-2024-38601, CVE-2024-39489, CVE-2024-39467, CVE-2023-52882, CVE-2024-38583, CVE-2024-39480, CVE-2024-38607, CVE-2024-36940, CVE-2024-38659, CVE-2023-52434, CVE-2024-36015, CVE-2024-38582, CVE-2024-36950, CVE-2024-38552, CVE-2024-33621, CVE-2024-36954, CVE-2024-39475, CVE-2024-39301, CVE-2024-38599, CVE-2024-36902, CVE-2024-36286, CVE-2024-38613, CVE-2024-38637, CVE-2024-36941, CVE-2024-36014, CVE-2024-38618, CVE-2024-36904, CVE-2024-36270, CVE-2024-39292, CVE-2024-39471, CVE-2022-48674)

Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:

• ARM64 architecture;
• M68K architecture;
• User-Mode Linux (UML);
• x86 architecture;
• Accessibility subsystem;
• Character device driver;
• Clock framework and drivers;
• CPU frequency scaling framework;
• Hardware crypto device drivers;
• Buffer Sharing and Synchronization framework;
• FireWire subsystem;
• ARM SCMI message protocol;
• GPU drivers;
• HW tracing;
• InfiniBand drivers;
• Macintosh device drivers;
• Multiple devices driver;
• Media drivers;
• Network drivers;
• Pin controllers subsystem;
• S/390 drivers;
• SCSI drivers;
• SoundWire subsystem;
• Greybus lights staging drivers;
• TTY drivers;
• Framebuffer layer;
• Virtio drivers;
• 9P distributed file system;
• eCrypt file system;
• EROFS file system;
• Ext4 file system;
• F2FS file system;
• JFFS2 file system;
• Network file system client;
• NILFS2 file system;
• SMB network file system;
• Mellanox drivers;
• Kernel debugger infrastructure;
• IRQ subsystem;
• Tracing infrastructure;
• Dynamic debug library;
• 9P file system network protocol;
• Bluetooth subsystem;
• Networking core;
• IPv4 networking;
• IPv6 networking;
• Netfilter;
• NET/ROM layer;
• NFC subsystem;
• NSH protocol;
• Open vSwitch;
• Phonet protocol;
• TIPC protocol;
• TLS protocol;
• Unix domain sockets;
• Wireless networking;
• eXpress Data Path;
• XFRM subsystem;
• ALSA framework; (CVE-2024-26584, CVE-2023-52434, CVE-2024-36933, CVE-2024-36286, CVE-2024-36886, CVE-2024-38579, CVE-2022-48772, CVE-2024-39493, CVE-2024-38637, CVE-2024-36016, CVE-2023-52752, CVE-2024-38558, CVE-2024-39488, CVE-2024-38559, CVE-2024-36919, CVE-2024-36905, CVE-2024-39489, CVE-2024-39475, CVE-2021-47131, CVE-2024-26585, CVE-2024-38578, CVE-2024-38567, CVE-2024-38596, CVE-2024-38598, CVE-2024-36940, CVE-2024-38552, CVE-2024-37356, CVE-2024-38780, CVE-2024-38589, CVE-2024-36959, CVE-2024-27399, CVE-2024-36017, CVE-2024-38661, CVE-2024-36939, CVE-2024-36904, CVE-2024-36902, CVE-2024-38381, CVE-2024-36883, CVE-2024-37353, CVE-2024-38560, CVE-2024-39292, CVE-2024-36934, CVE-2024-38621, CVE-2024-38599, CVE-2024-36941, CVE-2022-48655, CVE-2024-26886, CVE-2024-36014, CVE-2024-38613, CVE-2024-27398, CVE-2024-27019, CVE-2024-36954, CVE-2024-39471, CVE-2024-26583, CVE-2024-35947, CVE-2024-31076, CVE-2024-38659, CVE-2024-38549, CVE-2024-38618, CVE-2024-38565, CVE-2024-27401, CVE-2022-48674, CVE-2024-38582, CVE-2024-38634, CVE-2024-38627, CVE-2024-39480, CVE-2024-36015, CVE-2023-52585, CVE-2024-36270, CVE-2024-26907, CVE-2024-38615, CVE-2024-38600, CVE-2024-38612, CVE-2024-36946, CVE-2024-39301, CVE-2024-38601, CVE-2024-38635, CVE-2024-33621, CVE-2024-36964, CVE-2024-38633, CVE-2024-39467, CVE-2024-38607, CVE-2024-36971, CVE-2024-35976, CVE-2024-38587, CVE-2023-52882, CVE-2024-36950, CVE-2024-39276, CVE-2024-36960, CVE-2024-38583)

Yuxuan Hu discovered that the Bluetooth RFCOMM protocol driver in the Linux Kernel contained a race condition, leading to a NULL pointer dereference. An attacker could possibly use this to cause a denial of service (system crash). (CVE-2024-22099)

It was discovered that a race condition existed in the Bluetooth subsystem in the Linux kernel, leading to a null pointer dereference vulnerability. A privileged local attacker could use this to possibly cause a denial of service (system crash). (CVE-2024-24860)

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:

• SuperH RISC architecture;
• User-Mode Linux (UML);
• GPU drivers;
• MMC subsystem;
• Network drivers;
• PHY drivers;
• Pin controllers subsystem;
• Xen hypervisor drivers;
• GFS2 file system;
• Core kernel;
• Bluetooth subsystem;
• IPv4 networking;
• IPv6 networking;
• HD-audio driver;
• ALSA SH drivers; (CVE-2024-26903, CVE-2024-35835, CVE-2023-52644, CVE-2024-39292, CVE-2024-36940, CVE-2024-26600, CVE-2023-52629, CVE-2024-35955, CVE-2023-52760, CVE-2023-52806, CVE-2024-39484, CVE-2024-26679, CVE-2024-26654, CVE-2024-36901, CVE-2024-26687, CVE-2023-52470)

Yuxuan Hu discovered that the Bluetooth RFCOMM protocol driver in the Linux Kernel contained a race condition, leading to a NULL pointer dereference. An attacker could possibly use this to cause a denial of service (system crash). (CVE-2024-22099)

It was discovered that a race condition existed in the Bluetooth subsystem in the Linux kernel, leading to a null pointer dereference vulnerability. A privileged local attacker could use this to possibly cause a denial of service (system crash). (CVE-2024-24860)

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:

• SuperH RISC architecture;
• User-Mode Linux (UML);
• GPU drivers;
• MMC subsystem;
• Network drivers;
• PHY drivers;
• Pin controllers subsystem;
• Xen hypervisor drivers;
• GFS2 file system;
• Core kernel;
• Bluetooth subsystem;
• IPv4 networking;
• IPv6 networking;
• HD-audio driver;
• ALSA SH drivers; (CVE-2024-26903, CVE-2024-35835, CVE-2023-52644, CVE-2024-39292, CVE-2024-36940, CVE-2024-26600, CVE-2023-52629, CVE-2024-35955, CVE-2023-52760, CVE-2023-52806, CVE-2024-39484, CVE-2024-26679, CVE-2024-26654, CVE-2024-36901, CVE-2024-26687, CVE-2023-52470)

Yuxuan Hu discovered that the Bluetooth RFCOMM protocol driver in the Linux Kernel contained a race condition, leading to a NULL pointer dereference. An attacker could possibly use this to cause a denial of service (system crash). (CVE-2024-22099)

It was discovered that a race condition existed in the Bluetooth subsystem in the Linux kernel, leading to a null pointer dereference vulnerability. A privileged local attacker could use this to possibly cause a denial of service (system crash). (CVE-2024-24860)

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:

• SuperH RISC architecture;
• User-Mode Linux (UML);
• GPU drivers;
• MMC subsystem;
• Network drivers;
• PHY drivers;
• Pin controllers subsystem;
• Xen hypervisor drivers;
• GFS2 file system;
• Core kernel;
• Bluetooth subsystem;
• IPv4 networking;
• IPv6 networking;
• HD-audio driver;
• ALSA SH drivers; (CVE-2024-26903, CVE-2024-35835, CVE-2023-52644, CVE-2024-39292, CVE-2024-36940, CVE-2024-26600, CVE-2023-52629, CVE-2024-35955, CVE-2023-52760, CVE-2023-52806, CVE-2024-39484, CVE-2024-26679, CVE-2024-26654, CVE-2024-36901, CVE-2024-26687, CVE-2023-52470)

Yuxuan Hu discovered that the Bluetooth RFCOMM protocol driver in the Linux Kernel contained a race condition, leading to a NULL pointer dereference. An attacker could possibly use this to cause a denial of service (system crash). (CVE-2024-22099)

It was discovered that a race condition existed in the Bluetooth subsystem in the Linux kernel, leading to a null pointer dereference vulnerability. A privileged local attacker could use this to possibly cause a denial of service (system crash). (CVE-2024-24860)

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:

• SuperH RISC architecture;
• User-Mode Linux (UML);
• GPU drivers;
• MMC subsystem;
• Network drivers;
• PHY drivers;
• Pin controllers subsystem;
• Xen hypervisor drivers;
• GFS2 file system;
• Core kernel;
• Bluetooth subsystem;
• IPv4 networking;
• IPv6 networking;
• HD-audio driver;
• ALSA SH drivers; (CVE-2024-26903, CVE-2024-35835, CVE-2023-52644, CVE-2024-39292, CVE-2024-36940, CVE-2024-26600, CVE-2023-52629, CVE-2024-35955, CVE-2023-52760, CVE-2023-52806, CVE-2024-39484, CVE-2024-26679, CVE-2024-26654, CVE-2024-36901, CVE-2024-26687, CVE-2023-52470)

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:

• SuperH RISC architecture;
• User-Mode Linux (UML);
• MMC subsystem;
• Network drivers;
• GFS2 file system;
• IPv4 networking;
• IPv6 networking; (CVE-2024-26921, CVE-2023-52629, CVE-2024-26680, CVE-2024-26830, CVE-2024-39484, CVE-2024-39292, CVE-2024-36901, CVE-2023-52760)

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:

• SuperH RISC architecture;
• User-Mode Linux (UML);
• MMC subsystem;
• Network drivers;
• GFS2 file system;
• IPv4 networking;
• IPv6 networking; (CVE-2024-26921, CVE-2023-52629, CVE-2024-26680, CVE-2024-26830, CVE-2024-39484, CVE-2024-39292, CVE-2024-36901, CVE-2023-52760)

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:

• User-Mode Linux (UML);
• MMC subsystem; (CVE-2024-39292, CVE-2024-39484)

Yuxuan Hu discovered that the Bluetooth RFCOMM protocol driver in the Linux Kernel contained a race condition, leading to a NULL pointer dereference. An attacker could possibly use this to cause a denial of service (system crash). (CVE-2024-22099)

It was discovered that a race condition existed in the Bluetooth subsystem in the Linux kernel, leading to a null pointer dereference vulnerability. A privileged local attacker could use this to possibly cause a denial of service (system crash). (CVE-2024-24860)

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:

• SuperH RISC architecture;
• User-Mode Linux (UML);
• GPU drivers;
• HID subsystem;
• MMC subsystem;
• Network drivers;
• PHY drivers;
• SCSI drivers;
• USB subsystem;
• Xen hypervisor drivers;
• GFS2 file system;
• Memory management;
• Bluetooth subsystem;
• IPv4 networking;
• IPv6 networking;
• NFC subsystem;
• HD-audio driver;
• ALSA SH drivers; (CVE-2023-52806, CVE-2021-46924, CVE-2021-47521, CVE-2021-47542, CVE-2024-26903, CVE-2024-26654, CVE-2024-27013, CVE-2024-26600, CVE-2021-47518, CVE-2021-47171, CVE-2023-52629, CVE-2023-52644, CVE-2021-46904, CVE-2023-52470, CVE-2024-36901, CVE-2021-46906, CVE-2024-39292, CVE-2022-48659, CVE-2021-47173, CVE-2021-47571, CVE-2024-26929, CVE-2024-39484, CVE-2024-26687, CVE-2024-26679, CVE-2023-52760)

Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:

• ARM64 architecture;
• M68K architecture;
• User-Mode Linux (UML);
• x86 architecture;
• Accessibility subsystem;
• Character device driver;
• Clock framework and drivers;
• CPU frequency scaling framework;
• Hardware crypto device drivers;
• Buffer Sharing and Synchronization framework;
• FireWire subsystem;
• ARM SCMI message protocol;
• GPU drivers;
• HW tracing;
• InfiniBand drivers;
• Macintosh device drivers;
• Multiple devices driver;
• Media drivers;
• Network drivers;
• Pin controllers subsystem;
• S/390 drivers;
• SCSI drivers;
• SoundWire subsystem;
• Greybus lights staging drivers;
• TTY drivers;
• Framebuffer layer;
• Virtio drivers;
• 9P distributed file system;
• eCrypt file system;
• EROFS file system;
• Ext4 file system;
• F2FS file system;
• JFFS2 file system;
• Network file system client;
• NILFS2 file system;
• SMB network file system;
• Mellanox drivers;
• Kernel debugger infrastructure;
• IRQ subsystem;
• Tracing infrastructure;
• Dynamic debug library;
• 9P file system network protocol;
• Bluetooth subsystem;
• Networking core;
• IPv4 networking;
• IPv6 networking;
• Netfilter;
• NET/ROM layer;
• NFC subsystem;
• NSH protocol;
• Open vSwitch;
• Phonet protocol;
• TIPC protocol;
• TLS protocol;
• Unix domain sockets;
• Wireless networking;
• eXpress Data Path;
• XFRM subsystem;
• ALSA framework; (CVE-2022-48674, CVE-2024-36016, CVE-2024-36934, CVE-2024-39471, CVE-2024-38381, CVE-2024-26584, CVE-2024-38635, CVE-2024-36902, CVE-2022-48772, CVE-2024-38600, CVE-2024-39475, CVE-2024-26886, CVE-2024-39301, CVE-2024-36919, CVE-2024-35947, CVE-2024-38559, CVE-2024-38637, CVE-2024-36014, CVE-2024-36960, CVE-2024-35976, CVE-2024-27399, CVE-2024-38607, CVE-2024-38558, CVE-2024-38578, CVE-2024-36015, CVE-2024-39488, CVE-2024-38780, CVE-2024-36940, CVE-2024-38621, CVE-2024-38659, CVE-2024-26585, CVE-2024-27019, CVE-2024-38615, CVE-2024-38661, CVE-2024-37353, CVE-2024-38549, CVE-2024-38579, CVE-2024-27401, CVE-2024-38589, CVE-2024-38565, CVE-2022-48655, CVE-2024-38567, CVE-2024-38587, CVE-2024-37356, CVE-2024-36959, CVE-2024-39493, CVE-2024-38627, CVE-2024-36939, CVE-2024-31076, CVE-2024-36971, CVE-2024-38560, CVE-2024-39467, CVE-2024-36286, CVE-2024-39480, CVE-2024-26907, CVE-2024-36017, CVE-2024-38634, CVE-2023-52585, CVE-2024-38582, CVE-2023-52752, CVE-2024-38583, CVE-2024-38618, CVE-2024-36946, CVE-2024-39292, CVE-2024-36950, CVE-2024-36886, CVE-2024-39489, CVE-2024-36933, CVE-2024-27398, CVE-2023-52434, CVE-2024-36905, CVE-2024-38596, CVE-2021-47131, CVE-2024-38601, CVE-2024-38552, CVE-2024-26583, CVE-2024-38633, CVE-2024-36964, CVE-2024-39276, CVE-2024-36270, CVE-2024-38613, CVE-2024-36904, CVE-2024-38598, CVE-2024-38612, CVE-2024-36941, CVE-2024-36954, CVE-2024-38599, CVE-2024-36883, CVE-2023-52882, CVE-2024-33621)

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

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

Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:

• ARM64 architecture;
• MIPS architecture;
• PA-RISC architecture;
• PowerPC architecture;
• RISC-V architecture;
• User-Mode Linux (UML);
• x86 architecture;
• Block layer subsystem;
• ACPI drivers;
• Drivers core;
• Null block device driver;
• Character device driver;
• TPM device driver;
• Clock framework and drivers;
• CPU frequency scaling framework;
• Hardware crypto device drivers;
• CXL (Compute Express Link) drivers;
• Buffer Sharing and Synchronization framework;
• DMA engine subsystem;
• EFI core;
• FPGA Framework;
• GPU drivers;
• Greybus drivers;
• HID subsystem;
• HW tracing;
• I2C subsystem;
• IIO subsystem;
• InfiniBand drivers;
• Input Device (Mouse) drivers;
• Mailbox framework;
• Media drivers;
• Microchip PCI driver;
• VMware VMCI Driver;
• MMC subsystem;
• Network drivers;
• PCI subsystem;
• x86 platform drivers;
• PTP clock framework;
• S/390 drivers;
• SCSI drivers;
• SoundWire subsystem;
• Sonic Silicon Backplane drivers;
• Greybus lights staging drivers;
• Thermal drivers;
• TTY drivers;
• USB subsystem;
• VFIO drivers;
• Framebuffer layer;
• Watchdog drivers;
• 9P distributed file system;
• BTRFS file system;
• File systems infrastructure;
• Ext4 file system;
• F2FS file system;
• JFS file system;
• Network file system server daemon;
• NILFS2 file system;
• NTFS3 file system;
• SMB network file system;
• Tracing file system;
• IOMMU subsystem;
• Tracing infrastructure;
• io_uring subsystem;
• Core kernel;
• BPF subsystem;
• Kernel debugger infrastructure;
• DMA mapping infrastructure;
• IRQ subsystem;
• Memory management;
• 9P file system network protocol;
• Amateur Radio drivers;
• B.A.T.M.A.N. meshing protocol;
• Ethernet bridge;
• Networking core;
• Ethtool driver;
• IPv4 networking;
• IPv6 networking;
• MAC80211 subsystem;
• Multipath TCP;
• Netfilter;
• NET/ROM layer;
• NFC subsystem;
• Network traffic control;
• Sun RPC protocol;
• TIPC protocol;
• TLS protocol;
• Unix domain sockets;
• Wireless networking;
• XFRM subsystem;
• AppArmor security module;
• Integrity Measurement Architecture(IMA) framework;
• Landlock security;
• Linux Security Modules (LSM) Framework;
• SELinux security module;
• Simplified Mandatory Access Control Kernel framework;
• ALSA framework;
• HD-audio driver;
• SOF drivers;
• KVM core; (CVE-2024-38623, CVE-2024-38662, CVE-2024-39484, CVE-2024-42148, CVE-2024-39493, CVE-2024-38637, CVE-2024-40962, CVE-2024-36281, CVE-2024-40922, CVE-2024-40958, CVE-2024-40920, CVE-2024-40986, CVE-2024-40929, CVE-2024-40967, CVE-2024-39296, CVE-2024-40900, CVE-2024-40995, CVE-2024-40974, CVE-2024-40942, CVE-2024-39464, CVE-2024-40916, CVE-2024-40952, CVE-2024-40997, CVE-2024-41004, CVE-2024-40970, CVE-2024-40911, CVE-2024-40972, CVE-2024-36477, CVE-2024-40996, CVE-2024-40988, CVE-2024-38619, CVE-2024-40998, CVE-2024-38627, CVE-2024-36971, CVE-2024-37021, CVE-2024-40989, CVE-2024-40947, CVE-2024-40957, CVE-2024-39508, CVE-2024-41005, CVE-2024-40931, CVE-2024-34777, CVE-2024-38633, CVE-2024-38663, CVE-2024-36288, CVE-2024-40955, CVE-2024-40973, CVE-2024-39483, CVE-2024-38388, CVE-2024-40976, CVE-2024-38622, CVE-2024-40915, CVE-2024-38661, CVE-2024-38306,…

Ziming Zhang discovered that the DRM driver for VMware Virtual GPU did not properly handle certain error conditions, leading to a NULL pointer dereference. A local attacker could possibly trigger this vulnerability to cause a denial of service. (CVE-2022-38096)

Gui-Dong Han discovered that the software RAID driver in the Linux kernel contained a race condition, leading to an integer overflow vulnerability. A privileged attacker could possibly use this to cause a denial of service (system crash). (CVE-2024-23307)

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

It was discovered that a race condition existed in the Bluetooth subsystem in the Linux kernel when modifying certain settings values through debugfs. A privileged local attacker could use this to cause a denial of service. (CVE-2024-24857, CVE-2024-24858, CVE-2024-24859)

Bai Jiaju discovered that the Xceive XC4000 silicon tuner device driver in the Linux kernel contained a race condition, leading to an integer overflow vulnerability. An attacker could possibly use this to cause a denial of service (system crash). (CVE-2024-24861)

Chenyuan Yang discovered that the Unsorted Block Images (UBI) flash device volume management subsystem did not properly validate logical eraseblock sizes in certain situations. An attacker could possibly use this to cause a denial of service (system crash). (CVE-2024-25739)

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)

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

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

Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:

• ARM32 architecture;
• ARM64 architecture;
• M68K architecture;
• MIPS architecture;
• PowerPC architecture;
• RISC-V architecture;
• SuperH RISC architecture;
• User-Mode Linux (UML);
• x86 architecture;
• Block layer subsystem;
• Cryptographic API;
• Accessibility subsystem;
• ACPI drivers;
• Android drivers;
• Serial ATA and Parallel ATA drivers;
• Drivers core;
• Bluetooth drivers;
• Character device driver;
• Clock framework and drivers;
• Data acquisition framework and drivers;
• CPU frequency scaling framework;
• Hardware crypto device drivers;
• Buffer Sharing and Synchronization framework;
• DMA engine subsystem;
• FireWire subsystem;
• FPGA Framework;
• GPIO subsystem;
• GPU drivers;
• Greybus drivers;
• HID subsystem;
• HW tracing;
• I2C subsystem;
• IIO subsystem;
• InfiniBand drivers;
• Input Device (Mouse) drivers;
• IRQ chip drivers;
• Macintosh device drivers;
• Multiple devices driver;
• Media drivers;
• EEPROM drivers;
• VMware VMCI Driver;
• MMC subsystem;
• Network drivers;
• Near Field Communication (NFC) drivers;
• NVME drivers;
• Device tree and open firmware driver;
• PCI subsystem;
• Pin controllers subsystem;
• PTP clock framework;
• Remote Processor subsystem;
• S/390 drivers;
• SCSI drivers;
• Freescale SoC…

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

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

Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:

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