CVE-2024-36971

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

net: fix __dst_negative_advice() race

__dst_negative_advice() does not enforce proper RCU rules when sk->dst_cache must be cleared, leading to possible UAF.

RCU rules are that we must first clear sk->sk_dst_cache, then call dst_release(old_dst).

Note that sk_dst_reset(sk) is implementing this protocol correctly, while __dst_negative_advice() uses the wrong order.

Given that ip6_negative_advice() has special logic against RTF_CACHE, this means each of the three ->negative_advice() existing methods must perform the sk_dst_reset() themselves.

Note the check against NULL dst is centralized in __dst_negative_advice(), there is no need to duplicate it in various callbacks.

Many thanks to Clement Lecigne for tracking this issue.

This old bug became visible after the blamed commit, using UDP sockets.

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

net: fix __dst_negative_advice() race

__dst_negative_advice() does not enforce proper RCU rules when sk->dst_cache must be cleared, leading to possible UAF.

RCU rules are that we must first clear sk->sk_dst_cache, then call dst_release(old_dst).

Note that sk_dst_reset(sk) is implementing this protocol correctly, while __dst_negative_advice() uses the wrong order.

Given that ip6_negative_advice() has special logic against RTF_CACHE, this means each of the three ->negative_advice() existing methods must perform the sk_dst_reset() themselves.

Note the check against NULL dst is centralized in __dst_negative_advice(), there is no need to duplicate it in various callbacks.

Many thanks to Clement Lecigne for tracking this issue.

This old bug became visible after the blamed commit, using UDP sockets.

In the Linux kernel, the following vulnerability has been resolved: net: fix __dst_negative_advice() race __dst_negative_advice() does not enforce proper RCU rules when sk->dst_cache must be cleared, leading to possible UAF. RCU rules are that we must first clear sk->sk_dst_cache, then call dst_release(old_dst). Note that sk_dst_reset(sk) is implementing this protocol correctly, while __dst_negative_advice() uses the wrong order. Given that ip6_negative_advice() has special logic against RTF_CACHE, this means each of the three ->negative_advice() existing methods must perform the sk_dst_reset() themselves. Note the check against NULL dst is centralized in __dst_negative_advice(), there is no need to duplicate it in various callbacks. Many thanks to Clement Lecigne for tracking this issue. This old bug became visible after the blamed commit, using UDP sockets.

The Linux Kernel, the operating system core itself.

Security Fix(es):

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

afs: Fix corruption in reads at fpos 2G-4G from an OpenAFS server

AFS-3 has two data fetch RPC variants, FS.FetchData and FS.FetchData64, and Linux's afs client switches between them when talking to a non-YFS server if the read size, the file position or the sum of the two have the upper 32 bits set of the 64-bit value.

This is a problem, however, since the file position and length fields of FS.FetchData are signed 32-bit values.

Fix this by capturing the capability bits obtained from the fileserver when it's sent an FS.GetCapabilities RPC, rather than just discarding them, and then picking out the VICED_CAPABILITY_64BITFILES flag. This can then be used to decide whether to use FS.FetchData or FS.FetchData64 - and also FS.StoreData or FS.StoreData64 - rather than using upper_32_bits() to switch on the parameter values.

This capabilities flag could also be used to limit the maximum size of the file, but all servers must be checked for that.

Note that the issue does not exist with FS.StoreData - that uses unsigned 32-bit values. It's also not a problem with Auristor servers as its YFS.FetchData64 op uses unsigned 64-bit values.

This can be tested by cloning a git repo through an OpenAFS client to an OpenAFS server and then doing "git status" on it from a Linux afs client[1]. Provided the clone has a pack file that's in the 2G-4G range, the git status will show errors like:

error: packfile .git/objects/pack/pack-5e813c51d12b6847bbc0fcd97c2bca66da50079c.pack does not match index
error: packfile .git/objects/pack/pack-5e813c51d12b6847bbc0fcd97c2bca66da50079c.pack does not match index

This can be observed in the server's FileLog with something like the following appearing:

Sun Aug 29 19:31:39 2021 SRXAFS_FetchData, Fid = 2303380852.491776.3263114, Host 192.168.11.201:7001, Id 1001 Sun Aug 29 19:31:39 2021 CheckRights: len=0, for host=192.168.11.201:7001 Sun Aug 29 19:31:39 2021 FetchData_RXStyle: Pos 18446744071815340032, Len 3154 Sun Aug 29 19:31:39 2021 FetchData_RXStyle: file size 2400758866 ... Sun Aug 29 19:31:40 2021 SRXAFS_FetchData returns 5

Note the file position of 18446744071815340032. This is the requested file position sign-extended.(CVE-2021-47366)

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

net/smc: Fix possible access to freed memory in link clear

After modifying the QP to the Error state, all RX WR would be completed with WC in IB_WC_WR_FLUSH_ERR status. Current implementation does not wait for it is done, but destroy the QP and free the link group directly. So there is a risk that accessing the freed memory in tasklet context.

Here is a crash example:

BUG: unable to handle page fault for address: ffffffff8f220860 #PF: supervisor write access in kernel mode #PF: error_code(0x0002) - not-present page PGD f7300e067 P4D f7300e067 PUD f7300f063 PMD 8c4e45063 PTE 800ffff08c9df060 Oops: 0002 [#1] SMP PTI CPU: 1 PID: 0 Comm: swapper/1 Kdump: loaded Tainted: G S OE 5.10.0-0607+ #23 Hardware name: Inspur NF5280M4/YZMB-00689-101, BIOS 4.1.20 07/09/2018 RIP: 0010:native_queued_spin_lock_slowpath+0x176/0x1b0 Code: f3 90 48 8b 32 48 85 f6 74 f6 eb d5 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 c8 02 00 48 03 04 f5 00 09 98 8e <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 74 f7 48 8b 32 RSP: 0018:ffffb3b6c001ebd8 EFLAGS: 00010086 RAX: ffffffff8f220860 RBX: 0000000000000246 RCX: 0000000000080000 RDX: ffff91db1f86c800 RSI: 000000000000173c RDI: ffff91db62bace00 RBP: ffff91db62bacc00 R08: 0000000000000000 R09: c00000010000028b R10: 0000000000055198 R11: ffffb3b6c001ea58 R12: ffff91db80e05010 R13: 000000000000000a R14: 0000000000000006 R15: 0000000000000040 FS: 0000000000000000(0000) GS:ffff91db1f840000(0000)…

The Linux Kernel, the operating system core itself.

Security Fix(es):

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

afs: Fix corruption in reads at fpos 2G-4G from an OpenAFS server

AFS-3 has two data fetch RPC variants, FS.FetchData and FS.FetchData64, and Linux's afs client switches between them when talking to a non-YFS server if the read size, the file position or the sum of the two have the upper 32 bits set of the 64-bit value.

This is a problem, however, since the file position and length fields of FS.FetchData are signed 32-bit values.

Fix this by capturing the capability bits obtained from the fileserver when it's sent an FS.GetCapabilities RPC, rather than just discarding them, and then picking out the VICED_CAPABILITY_64BITFILES flag. This can then be used to decide whether to use FS.FetchData or FS.FetchData64 - and also FS.StoreData or FS.StoreData64 - rather than using upper_32_bits() to switch on the parameter values.

This capabilities flag could also be used to limit the maximum size of the file, but all servers must be checked for that.

Note that the issue does not exist with FS.StoreData - that uses unsigned 32-bit values. It's also not a problem with Auristor servers as its YFS.FetchData64 op uses unsigned 64-bit values.

This can be tested by cloning a git repo through an OpenAFS client to an OpenAFS server and then doing "git status" on it from a Linux afs client[1]. Provided the clone has a pack file that's in the 2G-4G range, the git status will show errors like:

error: packfile .git/objects/pack/pack-5e813c51d12b6847bbc0fcd97c2bca66da50079c.pack does not match index
error: packfile .git/objects/pack/pack-5e813c51d12b6847bbc0fcd97c2bca66da50079c.pack does not match index

This can be observed in the server's FileLog with something like the following appearing:

Sun Aug 29 19:31:39 2021 SRXAFS_FetchData, Fid = 2303380852.491776.3263114, Host 192.168.11.201:7001, Id 1001 Sun Aug 29 19:31:39 2021 CheckRights: len=0, for host=192.168.11.201:7001 Sun Aug 29 19:31:39 2021 FetchData_RXStyle: Pos 18446744071815340032, Len 3154 Sun Aug 29 19:31:39 2021 FetchData_RXStyle: file size 2400758866 ... Sun Aug 29 19:31:40 2021 SRXAFS_FetchData returns 5

Note the file position of 18446744071815340032. This is the requested file position sign-extended.(CVE-2021-47366)

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

net/smc: Fix possible access to freed memory in link clear

After modifying the QP to the Error state, all RX WR would be completed with WC in IB_WC_WR_FLUSH_ERR status. Current implementation does not wait for it is done, but destroy the QP and free the link group directly. So there is a risk that accessing the freed memory in tasklet context.

Here is a crash example:

BUG: unable to handle page fault for address: ffffffff8f220860 #PF: supervisor write access in kernel mode #PF: error_code(0x0002) - not-present page PGD f7300e067 P4D f7300e067 PUD f7300f063 PMD 8c4e45063 PTE 800ffff08c9df060 Oops: 0002 [#1] SMP PTI CPU: 1 PID: 0 Comm: swapper/1 Kdump: loaded Tainted: G S OE 5.10.0-0607+ #23 Hardware name: Inspur NF5280M4/YZMB-00689-101, BIOS 4.1.20 07/09/2018 RIP: 0010:native_queued_spin_lock_slowpath+0x176/0x1b0 Code: f3 90 48 8b 32 48 85 f6 74 f6 eb d5 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 c8 02 00 48 03 04 f5 00 09 98 8e <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 74 f7 48 8b 32 RSP: 0018:ffffb3b6c001ebd8 EFLAGS: 00010086 RAX: ffffffff8f220860 RBX: 0000000000000246 RCX: 0000000000080000 RDX: ffff91db1f86c800 RSI: 000000000000173c RDI: ffff91db62bace00 RBP: ffff91db62bacc00 R08: 0000000000000000 R09: c00000010000028b R10: 0000000000055198 R11: ffffb3b6c001ea58 R12: ffff91db80e05010 R13: 000000000000000a R14: 0000000000000006 R15: 0000000000000040 FS: 0000000000000000(0000) GS:ffff91db1f840000(0000)…

The Linux Kernel, the operating system core itself.

Security Fix(es):

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

can: mcba_usb: fix memory leak in mcba_usb

Syzbot reported memory leak in SocketCAN driver for Microchip CAN BUS Analyzer Tool. The problem was in unfreed usb_coherent.

In mcba_usb_start() 20 coherent buffers are allocated and there is nothing, that frees them:

1. In callback function the urb is resubmitted and that's all
2. In disconnect function urbs are simply killed, but URB_FREE_BUFFER is not set (see mcba_usb_start) and this flag cannot be used with coherent buffers.

Fail log: | [ 1354.053291][ T8413] mcba_usb 1-1:0.0 can0: device disconnected | [ 1367.059384][ T8420] kmemleak: 20 new suspected memory leaks (see /sys/kernel/debug/kmem)

So, all allocated buffers should be freed with usb_free_coherent() explicitly

NOTE: The same pattern for allocating and freeing coherent buffers is used in drivers/net/can/usb/kvaser_usb/kvaser_usb_core.c(CVE-2021-47231)

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

can: j1939: fix Use-after-Free, hold skb ref while in use

This patch fixes a Use-after-Free found by the syzbot.

The problem is that a skb is taken from the per-session skb queue, without incrementing the ref count. This leads to a Use-after-Free if the skb is taken concurrently from the session queue due to a CTS.(CVE-2021-47232)

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

batman-adv: Avoid WARN_ON timing related checks

The soft/batadv interface for a queued OGM can be changed during the time the OGM was queued for transmission and when the OGM is actually transmitted by the worker.

But WARN_ON must be used to denote kernel bugs and not to print simple warnings. A warning can simply be printed using pr_warn.(CVE-2021-47252)

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

media: ngene: Fix out-of-bounds bug in ngene_command_config_free_buf()

Fix an 11-year old bug in ngene_command_config_free_buf() while addressing the following warnings caught with -Warray-bounds:

arch/alpha/include/asm/string.h:22:16: warning: '__builtin_memcpy' offset [12, 16] from the object at 'com' is out of the bounds of referenced subobject 'config' with type 'unsigned char' at offset 10 [-Warray-bounds] arch/x86/include/asm/string_32.h:182:25: warning: '__builtin_memcpy' offset [12, 16] from the object at 'com' is out of the bounds of referenced subobject 'config' with type 'unsigned char' at offset 10 [-Warray-bounds]

The problem is that the original code is trying to copy 6 bytes of data into a one-byte size member config of the wrong structue FW_CONFIGURE_BUFFERS, in a single call to memcpy(). This causes a legitimate compiler warning because memcpy() overruns the length of &com.cmd.ConfigureBuffers.config. It seems that the right structure is FW_CONFIGURE_FREE_BUFFERS, instead, because it contains 6 more members apart from the header hdr. Also, the name of the function ngene_command_config_free_buf() suggests that the actual intention is to ConfigureFreeBuffers, instead of ConfigureBuffers (which takes place in the function ngene_command_config_buf(), above).

Fix this by enclosing those 6 members of struct FW_CONFIGURE_FREE_BUFFERS into new struct config, and use &com.cmd.ConfigureFreeBuffers.config as the destination address, instead of &com.cmd.ConfigureBuffers.config, when calling memcpy().

This also helps with the ongoing efforts to globally enable -Warray-bounds and get us closer to being able to tighten the FORTIFY_SOURCE routines on memcpy().(CVE-2021-47288)

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

coresight: tmc-etf: Fix global-out-of-bounds in tmc_update_etf_buffer()

commit 6f755e85c332 ("coresight: Add helper for…

The Linux Kernel, the operating system core itself.

Security Fix(es):

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

apparmor: Fix null pointer deref when receiving skb during sock creation

The panic below is observed when receiving ICMP packets with secmark set while an ICMP raw socket is being created. SK_CTX(sk)->label is updated in apparmor_socket_post_create(), but the packet is delivered to the socket before that, causing the null pointer dereference. Drop the packet if label context is not set.

BUG: kernel NULL pointer dereference, address: 000000000000004c
#PF: supervisor read access in kernel mode
#PF: error_code(0x0000) - not-present page
PGD 0 P4D 0
Oops: 0000 [#1] PREEMPT SMP NOPTI
CPU: 0 PID: 407 Comm: a.out Not tainted 6.4.12-arch1-1 #1 3e6fa2753a2d75925c34ecb78e22e85a65d083df
Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 05/28/2020
RIP: 0010:aa_label_next_confined+0xb/0x40
Code: 00 00 48 89 ef e8 d5 25 0c 00 e9 66 ff ff ff 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 66 0f 1f 00 0f 1f 44 00 00 89 f0 <8b> 77 4c 39 c6 7e 1f 48 63 d0 48 8d 14 d7 eb 0b 83 c0 01 48 83 c2
RSP: 0018:ffffa92940003b08 EFLAGS: 00010246
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 000000000000000e
RDX: ffffa92940003be8 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffff8b57471e7800 R08: ffff8b574c642400 R09: 0000000000000002
R10: ffffffffbd820eeb R11: ffffffffbeb7ff00 R12: ffff8b574c642400
R13: 0000000000000001 R14: 0000000000000001 R15: 0000000000000000
FS:  00007fb092ea7640(0000) GS:ffff8b577bc00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000000000004c CR3: 00000001020f2005 CR4: 00000000007706f0
PKRU: 55555554
Call Trace:
 <IRQ>
 ? __die+0x23/0x70
 ? page_fault_oops+0x171/0x4e0
 ? exc_page_fault+0x7f/0x180
 ? asm_exc_page_fault+0x26/0x30
 ? aa_label_next_confined+0xb/0x40
 apparmor_secmark_check+0xec/0x330
 security_sock_rcv_skb+0x35/0x50
 sk_filter_trim_cap+0x47/0x250
 sock_queue_rcv_skb_reason+0x20/0x60
 raw_rcv+0x13c/0x210
 raw_local_deliver+0x1f3/0x250
 ip_protocol_deliver_rcu+0x4f/0x2f0
 ip_local_deliver_finish+0x76/0xa0
 __netif_receive_skb_one_core+0x89/0xa0
 netif_receive_skb+0x119/0x170
 ? __netdev_alloc_skb+0x3d/0x140
 vmxnet3_rq_rx_complete+0xb23/0x1010 [vmxnet3 56a84f9c97178c57a43a24ec073b45a9d6f01f3a]
 vmxnet3_poll_rx_only+0x36/0xb0 [vmxnet3 56a84f9c97178c57a43a24ec073b45a9d6f01f3a]
 __napi_poll+0x28/0x1b0
 net_rx_action+0x2a4/0x380
 __do_softirq+0xd1/0x2c8
 __irq_exit_rcu+0xbb/0xf0
 common_interrupt+0x86/0xa0
 </IRQ>
 <TASK>
 asm_common_interrupt+0x26/0x40
RIP: 0010:apparmor_socket_post_create+0xb/0x200
Code: 08 48 85 ff 75 a1 eb b1 0f 1f 80 00 00 00 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 f3 0f 1e fa 0f 1f 44 00 00 41 54 <55> 48 89 fd 53 45 85 c0 0f 84 b2 00 00 00 48 8b 1d 80 56 3f 02 48
RSP: 0018:ffffa92940ce7e50 EFLAGS: 00000286
RAX: ffffffffbc756440 RBX: 0000000000000000 RCX: 0000000000000001
RDX: 0000000000000003 RSI: 0000000000000002 RDI: ffff8b574eaab740
RBP: 0000000000000001 R08: 0000000000000000 R09: 0000000000000000
R10: ffff8b57444cec70 R11: 0000000000000000 R12: 0000000000000003
R13: 0000000000000002 R14: ffff8b574eaab740 R15: ffffffffbd8e4748
 ? __pfx_apparmor_socket_post_create+0x10/0x10
 security_socket_post_create+0x4b/0x80
 __sock_create+0x176/0x1f0
 __sys_socket+0x89/0x100
 __x64_sys_socket+0x17/0x20
 do_syscall_64+0x5d/0x90
 ? do_syscall_64+0x6c/0x90
 ? do_syscall_64+0x6c/0x90
 ? do_syscall_64+0x6c/0x90
 entry_SYSCALL_64_after_hwframe+0x72/0xdc(CVE-2023-52889)

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

netfilter: nf_tables: use…

In the Linux kernel, the following vulnerability has been resolved: net: fix __dst_negative_advice() race __dst_negative_advice() does not enforce proper RCU rules when sk->dst_cache must be cleared, leading to possible UAF. RCU rules are that we must first clear sk->sk_dst_cache, then call dst_release(old_dst). Note that sk_dst_reset(sk) is implementing this protocol correctly, while __dst_negative_advice() uses the wrong order. Given that ip6_negative_advice() has special logic against RTF_CACHE, this means each of the three ->negative_advice() existing methods must perform the sk_dst_reset() themselves. Note the check against NULL dst is centralized in __dst_negative_advice(), there is no need to duplicate it in various callbacks. Many thanks to Clement Lecigne for tracking this issue. This old bug became visible after the blamed commit, using UDP sockets.

The kernel packages contain the Linux kernel, the core of any Linux operating system.

Security Fix(es):

• kernel: powerpc: Fix access beyond end of drmem array (CVE-2023-52451)
• kernel: efivarfs: force RO when remounting if SetVariable is not supported (CVE-2023-52463)
• kernel: tracing: Restructure trace_clock_global() to never block (CVE-2021-46939)
• kernel: ext4: avoid online resizing failures due to oversized flex bg (CVE-2023-52622)
• kernel: net/sched: flower: Fix chain template offload (CVE-2024-26669)
• kernel: stmmac: Clear variable when destroying workqueue (CVE-2024-26802)
• kernel: efi: runtime: Fix potential overflow of soft-reserved region size (CVE-2024-26843)
• kernel: quota: Fix potential NULL pointer dereference (CVE-2024-26878)
• kernel: TIPC message reassembly use-after-free remote code execution vulnerability (CVE-2024-36886)
• kernel: SUNRPC: fix a memleak in gss_import_v2_context (CVE-2023-52653)
• kernel: dmaengine/idxd: hardware erratum allows potential security problem with direct access by untrusted application (CVE-2024-21823)
• kernel: Revert "net/mlx5: Block entering switchdev mode with ns inconsistency" (CVE-2023-52658)
• kernel: ext4: fix corruption during on-line resize (CVE-2024-35807)
• kernel: x86/fpu: Keep xfd_state in sync with MSR_IA32_XFD (CVE-2024-35801)
• kernel: dyndbg: fix old BUG_ON in >control parser (CVE-2024-35947)
• kernel: net/sched: act_skbmod: prevent kernel-infoleak (CVE-2024-35893)
• kernel: x86/mce: Make sure to grab mce_sysfs_mutex in set_bank() (CVE-2024-35876)
• kernel: platform/x86: wmi: Fix opening of char device (CVE-2023-52864)
• kernel: tipc: Change nla_policy for bearer-related names to NLA_NUL_STRING (CVE-2023-52845)
• (CVE-2023-28746)
• (CVE-2023-52847)
• (CVE-2021-47548)
• (CVE-2024-36921)
• (CVE-2024-26921)
• (CVE-2021-47579)
• (CVE-2024-36927)
• (CVE-2024-39276)
• (CVE-2024-33621)
• (CVE-2024-27010)
• (CVE-2024-26960)
• (CVE-2024-38596)
• (CVE-2022-48743)
• (CVE-2024-26733)
• (CVE-2024-26586)
• (CVE-2024-26698)
• (CVE-2023-52619)

Bug Fix(es):

• AlmaLinux8.6 - Spinlock statistics may show negative elapsed time and incorrectly formatted output (JIRA:AlmaLinux-17678)
• [AWS][8.9]There are call traces found when booting debug-kernel for Amazon EC2 r8g.metal-24xl instance (JIRA:AlmaLinux-23841)
• [almalinux8] gfs2: Fix glock shrinker (JIRA:AlmaLinux-32941)
• lan78xx: Microchip LAN7800 never comes up after unplug and replug (JIRA:AlmaLinux-33437)
• [Hyper-V][AlmaLinux-8.10.z] Update hv_netvsc driver to TOT (JIRA:AlmaLinux-39074)
• Use-after-free on proc inode-i_sb triggered by fsnotify (JIRA:AlmaLinux-40167)
• blk-cgroup: Properly propagate the iostat update up the hierarchy [almalinux-8.10.z] (JIRA:AlmaLinux-40939)
• (JIRA:AlmaLinux-31798)
• (JIRA:AlmaLinux-10263)
• (JIRA:AlmaLinux-40901)
• (JIRA:AlmaLinux-43547)
• (JIRA:AlmaLinux-34876)

Enhancement(s):

• [RFE] Add module parameters 'soft_reboot_cmd' and 'soft_active_on_boot' for customizing softdog configuration (JIRA:AlmaLinux-19723)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer the CVE page(s) listed in the References section.

The kernel-rt packages provide the Real Time Linux Kernel, which enables fine-tuning for systems with extremely high determinism requirements.

Security Fix(es):

• kernel: efivarfs: force RO when remounting if SetVariable is not supported (CVE-2023-52463)
• kernel: tracing: Restructure trace_clock_global() to never block (CVE-2021-46939)
• kernel: ext4: avoid online resizing failures due to oversized flex bg (CVE-2023-52622)
• kernel: net/sched: flower: Fix chain template offload (CVE-2024-26669)
• kernel: stmmac: Clear variable when destroying workqueue (CVE-2024-26802)
• kernel: efi: runtime: Fix potential overflow of soft-reserved region size (CVE-2024-26843)
• kernel: quota: Fix potential NULL pointer dereference (CVE-2024-26878)
• kernel: TIPC message reassembly use-after-free remote code execution vulnerability (CVE-2024-36886)
• kernel: SUNRPC: fix a memleak in gss_import_v2_context (CVE-2023-52653)
• kernel: dmaengine/idxd: hardware erratum allows potential security problem with direct access by untrusted application (CVE-2024-21823)
• kernel: ext4: fix corruption during on-line resize (CVE-2024-35807)
• kernel: x86/fpu: Keep xfd_state in sync with MSR_IA32_XFD (CVE-2024-35801)
• kernel: dyndbg: fix old BUG_ON in >control parser (CVE-2024-35947)
• kernel: net/sched: act_skbmod: prevent kernel-infoleak (CVE-2024-35893)
• kernel: x86/mce: Make sure to grab mce_sysfs_mutex in set_bank() (CVE-2024-35876)
• kernel: platform/x86: wmi: Fix opening of char device (CVE-2023-52864)
• kernel: tipc: Change nla_policy for bearer-related names to NLA_NUL_STRING (CVE-2023-52845)
• kernel: Revert "net/mlx5: Block entering switchdev mode with ns inconsistency" (CVE-2023-52658)
• kernel: crash due to a missing check for leb_size (CVE-2024-25739)
• kernel: tcp: make sure init the accept_queue's spinlocks once (CVE-2024-26614)
• kernel: tcp: add sanity checks to rx zerocopy (CVE-2024-26640)
• kernel: NFSv4.2: fix nfs4_listxattr kernel BUG at mm/usercopy.c:102 (CVE-2024-26870)
• kernel: nfs: fix UAF in direct writes (CVE-2024-26958)
• kernel: SUNRPC: fix some memleaks in gssx_dec_option_array (CVE-2024-27388)
• kernel: wifi: iwlwifi: mvm: don't set the MFP flag for the GTK (CVE-2024-27434)
• kernel: of: Fix double free in of_parse_phandle_with_args_map (CVE-2023-52679)
• kernel: scsi: lpfc: Fix possible memory leak in lpfc_rcv_padisc() (CVE-2024-35930)
• kernel: wifi: iwlwifi: mvm: rfi: fix potential response leaks (CVE-2024-35912)
• kernel: block: prevent division by zero in blk_rq_stat_sum() (CVE-2024-35925)
• kernel: wifi: ath11k: decrease MHI channel buffer length to 8KB (CVE-2024-35938)
• kernel: wifi: cfg80211: check A-MSDU format more carefully (CVE-2024-35937)
• kernel: wifi: rtw89: fix null pointer access when abort scan (CVE-2024-35946)
• kernel: netfilter: nf_tables: honor table dormant flag from netdev release event path (CVE-2024-36005)
• kernel: mm/hugetlb: fix missing hugetlb_lock for resv uncharge (CVE-2024-36000)
• kernel: mlxsw: spectrum_acl_tcam: Fix incorrect list API usage (CVE-2024-36006)
• kernel: net: ieee802154: fix null deref in parse dev addr (CVE-2021-47257)
• kernel: mmc: sdio: fix possible resource leaks in some error paths (CVE-2023-52730)
• kernel: wifi: ath11k: fix gtk offload status event locking (CVE-2023-52777)
• (CVE-2023-52832)
• (CVE-2023-52803)
• (CVE-2023-52756)
• (CVE-2023-52834)
• (CVE-2023-52791)
• (CVE-2023-52764)
• (CVE-2021-47468)
• (CVE-2021-47284)
• (CVE-2024-36025)
• (CVE-2024-36941)
• (CVE-2024-36940)
• (CVE-2024-36904)
• (CVE-2024-36896)
• (CVE-2024-36954)
• (CVE-2024-36950)
• (CVE-2024-38575)
• (CVE-2024-36917)
• (CVE-2024-36016)
• (CVE-2023-52762)
• (CVE-2024-27025)
• (CVE-2021-47548)
• (CVE-2023-52619)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer the CVE page(s) listed in the References section.

The kernel packages contain the Linux kernel, the core of any Linux operating system.
Security Fix(es):

• kernel: phy: (CVE-2024-26600)
• kernel: netfilter: multiple flaws (CVE-2024-26808, CVE-2024-27065, CVE-2024-35899, CVE-2024-36005)
• kernel: cifs: (CVE-2024-26828)
• kernel: wifi: multiple flaws (CVE-2024-26897, CVE-2024-27052, CVE-2024-27049, CVE-2023-52651, CVE-2024-35789, CVE-2024-27434, CVE-2024-35845, CVE-2024-35937, CVE-2024-36941, CVE-2024-36922, CVE-2024-36921, CVE-2024-38575)
• kernel: nfs: (CVE-2024-26868)
• kernel: igc: (CVE-2024-26853)
• kernel: dmaengine/idxd: (CVE-2024-21823)
• kernel: ipv6: multiple flaws (CVE-2024-27417, CVE-2024-35969, CVE-2024-36903, CVE-2024-40961)
• kernel: vt: (CVE-2024-35823)
• kernel: efi: (CVE-2024-35800)
• kernel: mlxsw: (CVE-2024-35852)
• kernel: eeprom: (CVE-2024-35848)
• kernel: ice: (CVE-2024-35911)
• kernel: platform/x86: (CVE-2023-52864)
• kernel: i40e: (CVE-2024-36020)
• kernel: rtnetlink: (CVE-2024-36017)
• kernel: net: multiple flaws (CVE-2024-36929, CVE-2024-36971, CVE-2021-47606, CVE-2024-38558, CVE-2024-40928, CVE-2024-40954)
• kernel: ipvlan: (CVE-2024-33621)
• kernel: tcp: (CVE-2024-37356)
• kernel: virtio: (CVE-2024-37353)
• kernel: tls: (CVE-2024-36489)
• kernel: cxl/region: (CVE-2024-38391)
• kernel: bonding: (CVE-2024-39487)
• kernel: netns: (CVE-2024-40958)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

In __dst_negative_advice of sock.h, there is a possible failure to clear sk->sk_dst_cache in the correct order resulting in a use after free. This could lead to remote code execution with System execution privileges needed. User interaction is not needed for exploitation.

• CVE-url: https://ubuntu.com/security/CVE-2024-26764
  • aio: remove an outdated BUG_ON and comment in aio_complete
  • aio: remove the extra get_file/fput pair in io_submit_one
  • aio: refactor read/write iocb setup
  • fs/aio: Restrict kiocb_set_cancel_fn() to I/O submitted via libaio
• CVE-url: https://ubuntu.com/security/CVE-2024-36971
  • net: fix __dst_negative_advice() race
• CVE-url: https://ubuntu.com/security/CVE-2024-26840
  • cachefiles: fix memory leak in cachefiles_add_cache()
• CVE-url: https://ubuntu.com/security/CVE-2021-47543
  • perf report: Fix memory leaks around perf_tip()
• CVE-url: https://ubuntu.com/security/CVE-2024-27405
  • usb: gadget: ncm: Handle decoding of multiple NTB's in unwrap call
  • usb: gadget: ncm: Avoid dropping datagrams of properly parsed NTBs
• CVE-url: https://ubuntu.com/security/CVE-2024-26779
  • wifi: mac80211: fix race condition on enabling fast-xmit
• CVE-url: https://ubuntu.com/security/CVE-2024-26772
  • ext4: avoid allocating blocks from corrupted group in ext4_mb_find_by_goal()
• CVE-url: https://ubuntu.com/security/CVE-2024-26845
  • scsi: target: core: Add TMF to tmr_list handling
• CVE-url: https://ubuntu.com/security/CVE-2021-47063
  • drm: bridge/panel: Cleanup connector on bridge detach
• CVE-url: https://ubuntu.com/security/CVE-2024-26804
  • net: ip_tunnel: prevent perpetual headroom growth
• CVE-url: https://ubuntu.com/security/CVE-2024-27410
  • wifi: nl80211: reject iftype change with mesh ID change
• CVE-url: https://ubuntu.com/security/CVE-2024-26793
  • gtp: fix use-after-free and null-ptr-deref in gtp_newlink()
• CVE-url: https://ubuntu.com/security/CVE-2024-26754
  • gtp: fix use-after-free and null-ptr-deref in gtp_genl_dump_pdp()
• CVE-url: https://ubuntu.com/security/CVE-2024-26839
  • IB/hfi1: Fix a memleak in init_credit_return
• CVE-url: https://ubuntu.com/security/CVE-2024-26773
  • ext4: avoid allocating blocks from corrupted group in ext4_mb_try_best_found()
• CVE-url: https://ubuntu.com/security/CVE-2024-27413
  • efi/capsule-loader: fix incorrect allocation size
• CVE-url: https://ubuntu.com/security/CVE-2024-26736
  • afs: Increase buffer size in afs_update_volume_status()
• CVE-url: https://ubuntu.com/security/CVE-2024-26777
  • fbdev: sis: Error out if pixclock equals zero
• CVE-url: https://ubuntu.com/security/CVE-2024-26778
  • fbdev: savage: Error out if pixclock equals zero
• CVE-url: https://ubuntu.com/security/CVE-2024-26763
  • dm-crypt: don't modify the data when using authenticated encryption
• CVE-url: https://ubuntu.com/security/CVE-2024-26733
  • arp: Prevent overflow in arp_req_get().
• CVE-url: https://ubuntu.com/security/CVE-2024-26791
  • btrfs: dev-replace: properly validate device names

• CVE-url: https://ubuntu.com/security/CVE-2024-26764
  • aio: remove an outdated BUG_ON and comment in aio_complete
  • aio: remove the extra get_file/fput pair in io_submit_one
  • aio: refactor read/write iocb setup
  • fs/aio: Restrict kiocb_set_cancel_fn() to I/O submitted via libaio
• CVE-url: https://ubuntu.com/security/CVE-2024-36971
  • net: fix __dst_negative_advice() race
• CVE-url: https://ubuntu.com/security/CVE-2024-26840
  • cachefiles: fix memory leak in cachefiles_add_cache()
• CVE-url: https://ubuntu.com/security/CVE-2021-47543
  • perf report: Fix memory leaks around perf_tip()
• CVE-url: https://ubuntu.com/security/CVE-2024-27405
  • usb: gadget: ncm: Handle decoding of multiple NTB's in unwrap call
  • usb: gadget: ncm: Avoid dropping datagrams of properly parsed NTBs
• CVE-url: https://ubuntu.com/security/CVE-2024-26779
  • wifi: mac80211: fix race condition on enabling fast-xmit
• CVE-url: https://ubuntu.com/security/CVE-2024-26772
  • ext4: avoid allocating blocks from corrupted group in ext4_mb_find_by_goal()
• CVE-url: https://ubuntu.com/security/CVE-2024-26845
  • scsi: target: core: Add TMF to tmr_list handling
• CVE-url: https://ubuntu.com/security/CVE-2021-47063
  • drm: bridge/panel: Cleanup connector on bridge detach
• CVE-url: https://ubuntu.com/security/CVE-2024-26804
  • net: ip_tunnel: prevent perpetual headroom growth
• CVE-url: https://ubuntu.com/security/CVE-2024-27410
  • wifi: nl80211: reject iftype change with mesh ID change
• CVE-url: https://ubuntu.com/security/CVE-2024-26793
  • gtp: fix use-after-free and null-ptr-deref in gtp_newlink()
• CVE-url: https://ubuntu.com/security/CVE-2024-26754
  • gtp: fix use-after-free and null-ptr-deref in gtp_genl_dump_pdp()
• CVE-url: https://ubuntu.com/security/CVE-2024-26839
  • IB/hfi1: Fix a memleak in init_credit_return
• CVE-url: https://ubuntu.com/security/CVE-2024-26773
  • ext4: avoid allocating blocks from corrupted group in ext4_mb_try_best_found()
• CVE-url: https://ubuntu.com/security/CVE-2024-27413
  • efi/capsule-loader: fix incorrect allocation size
• CVE-url: https://ubuntu.com/security/CVE-2024-26736
  • afs: Increase buffer size in afs_update_volume_status()
• CVE-url: https://ubuntu.com/security/CVE-2024-26777
  • fbdev: sis: Error out if pixclock equals zero
• CVE-url: https://ubuntu.com/security/CVE-2024-26778
  • fbdev: savage: Error out if pixclock equals zero
• CVE-url: https://ubuntu.com/security/CVE-2024-26763
  • dm-crypt: don't modify the data when using authenticated encryption
• CVE-url: https://ubuntu.com/security/CVE-2024-26733
  • arp: Prevent overflow in arp_req_get().
• CVE-url: https://ubuntu.com/security/CVE-2024-26791
  • btrfs: dev-replace: properly validate device names

• ima: Fix use-after-free on a dentry's dname.name {CVE-2024-39494}
• ima: define ima_max_digest_data struct without a flexible array variable
• ima: detect changes to the backing overlay file
• tcp: Use refcount_inc_not_zero() in tcp_twsk_unique(). {CVE-2024-36904}
• af_unix: Fix garbage collector racing against connect() {CVE-2024-26923}
• net/ipv6: avoid possible UAF in ip6_route_mpath_notify() {CVE-2024-26852}
• net/mlx5: Fix a race on command flush flow {CVE-2022-48858}
• sctp: fix kernel-infoleak for SCTP sockets {CVE-2022-48855}
• libbpf: Fix use-after-free in btf_dump_name_dups {CVE-2022-3534}
• net: fix __dst_negative_advice() race {CVE-2024-36971}
• ext4: fix kernel BUG in 'ext4_write_inline_data_end()' {CVE-2021-33631}
• tipc: fix UAF in error path {CVE-2024-36886}
• smb: client: fix parsing of SMB3.1.1 POSIX create context {CVE-2023-52434}
• smb: client: fix potential OOBs in smb2_parse_contexts() {CVE-2023-52434}
• perf: Disallow mis-matched inherited group reads {CVE-2023-5717}
• af_unix: Fix null-ptr-deref in unix_stream_sendpage(). {CVE-2023-4622}
• sched/rt: pick_next_rt_entity(): check list_entry {CVE-2023-1077}
• i2c: Fix a potential use after free {CVE-2019-25162}

• ima: Fix use-after-free on a dentry's dname.name {CVE-2024-39494}
• ima: define ima_max_digest_data struct without a flexible array variable
• ima: detect changes to the backing overlay file
• tcp: Use refcount_inc_not_zero() in tcp_twsk_unique(). {CVE-2024-36904}
• af_unix: Fix garbage collector racing against connect() {CVE-2024-26923}
• net/ipv6: avoid possible UAF in ip6_route_mpath_notify() {CVE-2024-26852}
• net/mlx5: Fix a race on command flush flow {CVE-2022-48858}
• sctp: fix kernel-infoleak for SCTP sockets {CVE-2022-48855}
• bpf: Add MEM_RDONLY for helper args that are pointers to rdonly mem. {CVE-2022-0500}
• bpf: Make per_cpu_ptr return rdonly PTR_TO_MEM. {CVE-2022-0500}
• bpf: Introduce MEM_RDONLY flag {CVE-2022-0500}
• bpf: Replace PTR_TO_XXX_OR_NULL with PTR_TO_XXX | PTR_MAYBE_NULL {CVE-2022-0500}
• bpf: Replace RET_XXX_OR_NULL with RET_XXX | PTR_MAYBE_NULL {CVE-2022-0500}
• bpf: Replace ARG_XXX_OR_NULL with ARG_XXX | PTR_MAYBE_NULL {CVE-2022-0500}
• bpf: Introduce composable reg, ret and arg types. {CVE-2022-0500}
• bpf: Extract nullable reg type conversion into a helper function {CVE-2022-0500}
• bpf: Rename bpf_reg_state variables {CVE-2022-0500}
• libbpf: Fix use-after-free in btf_dump_name_dups {CVE-2022-3534}
• net: fix __dst_negative_advice() race {CVE-2024-36971}
• ext4: fix kernel BUG in 'ext4_write_inline_data_end()' {CVE-2021-33631}
• tipc: fix UAF in error path {CVE-2024-36886}
• smb: client: fix parsing of SMB3.1.1 POSIX create context {CVE-2023-52434}
• smb: client: fix potential OOBs in smb2_parse_contexts() {CVE-2023-52434}
• perf: Disallow mis-matched inherited group reads {CVE-2023-5717}
• af_unix: Fix null-ptr-deref in unix_stream_sendpage(). {CVE-2023-4622}
• sched/rt: pick_next_rt_entity(): check list_entry {CVE-2023-1077}
• i2c: Fix a potential use after free {CVE-2019-25162}

• net: fix __dst_negative_advice() race {CVE-2024-36971}
• spec: update shim Conflicts, Provides keys
• ipv6: fib6_rules: avoid possible NULL dereference in fib6_rule_action() {CVE-2024-36902}
• ipv6: prevent NULL dereference in ip6_output() {CVE-2024-36901}
• drm/amd/display: Atom Integrated System Info v2_2 for DCN35 {CVE-2024-36897}
• i2c: smbus: fix NULL function pointer dereference {CVE-2024-35984}
• Bluetooth: Fix memory leak in hci_req_sync_complete() {CVE-2024-35978}
• net/mlx5: Properly link new fs rules into the tree {CVE-2024-35960}
• net: ena: Fix incorrect descriptor free behavior {CVE-2024-35958}
• tun: limit printing rate when illegal packet received by tun dev {CVE-2024-27013}
• Bluetooth: rfcomm: Fix null-ptr-deref in rfcomm_check_security {CVE-2024-26903}
• bpf: Fix re-attachment branch in bpf_tracing_prog_attach {CVE-2024-26591}
• ubi: Check for too small LEB size in VTBL code {CVE-2024-25739}
• Bluetooth: Fix atomicity violation in {min,max}_key_size_set {CVE-2024-24860}
• dm: limit the number of targets and parameter size area {CVE-2024-23851}
• netfilter: nf_tables: Fix potential data-race in __nft_expr_type_get() {CVE-2024-27020}
• netfilter: nf_tables: __nft_expr_type_get() selects specific family type
• scsi: qla2xxx: Fix double free of the ha->vp_map pointer {CVE-2024-26930}
• scsi: qla2xxx: Fix double free of fcport {CVE-2024-26929}
• net: ip_tunnel: make sure to pull inner header in ip_tunnel_rcv() {CVE-2024-26882}
• ext4: improve error recovery code paths in __ext4_remount() {CVE-2024-0775}
• netfilter: nf_tables: Reject tables of unsupported family {CVE-2023-6040}

• tun: add missing verification for short frame {CVE-2024-41091}
• tap: add missing verification for short frame {CVE-2024-41090}
• drm/amd/display: Fix potential index out of bounds in color transformation function {CVE-2024-38552}
• net: fix __dst_negative_advice() race {CVE-2024-36971}
• net: annotate data-races around sk->sk_dst_pending_confirm {CVE-2024-36971}
• net: fix out-of-bounds access in ops_init {CVE-2024-36883}
• net/sched: flower: Fix chain template offload {CVE-2024-26669}
• netfilter: nf_tables: use timestamp to check for set element timeout {CVE-2024-27397}
• netfilter: nft_set_rbtree: Remove unused variable nft_net {CVE-2024-27397}
• netfilter: nft_set_rbtree: prefer sync gc to async worker {CVE-2024-27397}
• netfilter: nft_set_rbtree: rename gc deactivate+erase function {CVE-2024-27397}
• netfilter: nf_tables: de-constify set commit ops function argument {CVE-2024-27397}
• netfilter: nft_set_rbtree: .deactivate fails if element has expired {CVE-2024-27397}
• sched/membarrier: reduce the ability to hammer on sys_membarrier {CVE-2024-26602}
• drm/vmwgfx: Fix possible null pointer derefence with invalid contexts {CVE-2022-38096}
• sched/psi: Fix use-after-free in ep_remove_wait_queue() {CVE-2023-52707}
• wait: add wake_up_pollfree() {CVE-2023-52707}
• x86/sev: Check for user-space IOIO pointing to kernel space {CVE-2023-46813}
• x86/sev: Check IOBM for IOIO exceptions from user-space {CVE-2023-46813}
• x86/sev: Disable MMIO emulation from user mode {CVE-2023-46813}
• tcp: Fix shift-out-of-bounds in dctcp_update_alpha(). {CVE-2024-37356}
• blk-cgroup: fix list corruption from reorder of WRITE ->lqueued {CVE-2024-38384}
• netfilter: complete validation of user input {CVE-2024-35962}
• SUNRPC: Fix UAF in svc_tcp_listen_data_ready() {CVE-2023-52885}
• PM / devfreq: Synchronize devfreq_monitor_[start/stop] {CVE-2023-52635}
• netfilter: validate user input for expected length {CVE-2024-35896}
• virtio: delete vq in vp_find_vqs_msix() when request_irq() fails {CVE-2024-37353}
• bnxt: prevent skb UAF after handing over to PTP worker {CVE-2022-48637}
• net: openvswitch: fix overwriting ct original tuple for ICMPv6 {CVE-2024-38558}
• net: core: reject skb_copy(_expand) for fraglist GSO skbs {CVE-2024-36929}
• rtnetlink: Correct nested IFLA_VF_VLAN_LIST attribute validation {CVE-2024-36017}
• ipvlan: Dont Use skb->sk in ipvlan_process_v{4,6}_outbound {CVE-2024-33621}
• drm/vmwgfx: Fix invalid reads in fence signaled events {CVE-2024-36960}
• gro: fix ownership transfer {CVE-2024-35890}
• mlxbf_gige: stop interface during shutdown {CVE-2024-35885}
• scsi: libfc: Fix potential NULL pointer dereference in fc_lport_ptp_setup() {CVE-2023-52809}
• wifi: mt76: replace skb_put with skb_put_zero {CVE-2024-42225}
• drm/amdgpu: Using uninitialized value *size when calling amdgpu_vce_cs_reloc {CVE-2024-42228}
• scsi: mpi3mr: Sanitise num_phys {CVE-2024-42159}
• bpf: Avoid uninitialized value in BPF_CORE_READ_BITFIELD {CVE-2024-42161}
• drm/amdgpu/mes: fix use-after-free issue {CVE-2024-38581}
• i40e: fix vf may be used uninitialized in this function warning {CVE-2024-36020}
• vt: fix unicode buffer corruption when deleting characters {CVE-2024-35823}
• ata: libata-core: Fix double free on error {CVE-2024-41087}
• netfilter: nf_tables: release mutex after nft_gc_seq_end from abort path {CVE-2024-26925}
• tcp_metrics: validate source addr length {CVE-2024-42154}

• media: dvb-core: Fix use-after-free due on race condition at dvb_net {CVE-2022-45886}
• media: dvb-core: Fix use-after-free due to race condition at dvb_ca_en50221 {CVE-2022-45919}
• bonding: Fix out-of-bounds read in bond_option_arp_ip_targets_set() {CVE-2024-39487}
• net: fix __dst_negative_advice() race {CVE-2024-36971}

The kernel packages contain the Linux kernel, the core of any Linux operating system.

Security Fix(es):

• kernel: powerpc: Fix access beyond end of drmem array (CVE-2023-52451)

• kernel: efivarfs: force RO when remounting if SetVariable is not supported (CVE-2023-52463)

• kernel: tracing: Restructure trace_clock_global() to never block (CVE-2021-46939)

• kernel: ext4: avoid online resizing failures due to oversized flex bg (CVE-2023-52622)

• kernel: net/sched: flower: Fix chain template offload (CVE-2024-26669)

• kernel: stmmac: Clear variable when destroying workqueue (CVE-2024-26802)

• kernel: efi: runtime: Fix potential overflow of soft-reserved region size (CVE-2024-26843)

• kernel: quota: Fix potential NULL pointer dereference (CVE-2024-26878)

• kernel: TIPC message reassembly use-after-free remote code execution vulnerability (CVE-2024-36886)

• kernel: SUNRPC: fix a memleak in gss_import_v2_context (CVE-2023-52653)

• kernel: dmaengine/idxd: hardware erratum allows potential security problem with direct access by untrusted application (CVE-2024-21823)

• kernel: Revert "net/mlx5: Block entering switchdev mode with ns inconsistency" (CVE-2023-52658)

• kernel: ext4: fix corruption during on-line resize (CVE-2024-35807)

• kernel: x86/fpu: Keep xfd_state in sync with MSR_IA32_XFD (CVE-2024-35801)

• kernel: dyndbg: fix old BUG_ON in >control parser (CVE-2024-35947)

• kernel: net/sched: act_skbmod: prevent kernel-infoleak (CVE-2024-35893)

• kernel: x86/mce: Make sure to grab mce_sysfs_mutex in set_bank() (CVE-2024-35876)

• kernel: platform/x86: wmi: Fix opening of char device (CVE-2023-52864)

• kernel: tipc: Change nla_policy for bearer-related names to NLA_NUL_STRING (CVE-2023-52845)

• (CVE-2023-28746)

• (CVE-2023-52847)

• (CVE-2021-47548)

• (CVE-2024-36921)

• (CVE-2024-26921)

• (CVE-2021-47579)

• (CVE-2024-36927)

• (CVE-2024-39276)

• (CVE-2024-33621)

• (CVE-2024-27010)

• (CVE-2024-26960)

• (CVE-2024-38596)

• (CVE-2022-48743)

• (CVE-2024-26733)

• (CVE-2024-26586)

• (CVE-2024-26698)

• (CVE-2023-52619)

Bug Fix(es):

• Rocky Linux8.6 - Spinlock statistics may show negative elapsed time and incorrectly formatted output (JIRA:Rocky Linux-17678)

• [AWS][8.9]There are call traces found when booting debug-kernel for Amazon EC2 r8g.metal-24xl instance (JIRA:Rocky Linux-23841)

• [rhel8] gfs2: Fix glock shrinker (JIRA:Rocky Linux-32941)

• lan78xx: Microchip LAN7800 never comes up after unplug and replug (JIRA:Rocky Linux-33437)

• [Hyper-V][Rocky Linux-8.10.z] Update hv_netvsc driver to TOT (JIRA:Rocky Linux-39074)

• Use-after-free on proc inode-i_sb triggered by fsnotify (JIRA:Rocky Linux-40167)

• blk-cgroup: Properly propagate the iostat update up the hierarchy [rhel-8.10.z] (JIRA:Rocky Linux-40939)

• (JIRA:Rocky Linux-31798)

• (JIRA:Rocky Linux-10263)

• (JIRA:Rocky Linux-40901)

• (JIRA:Rocky Linux-43547)

• (JIRA:Rocky Linux-34876)

Enhancement(s):

• [RFE] Add module parameters 'soft_reboot_cmd' and 'soft_active_on_boot' for customizing softdog configuration (JIRA:Rocky Linux-19723)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer the CVE page(s) listed in the References section.

The kernel-rt packages provide the Real Time Linux Kernel, which enables fine-tuning for systems with extremely high determinism requirements.

Security Fix(es):

• kernel: efivarfs: force RO when remounting if SetVariable is not supported (CVE-2023-52463)

• kernel: tracing: Restructure trace_clock_global() to never block (CVE-2021-46939)

• kernel: ext4: avoid online resizing failures due to oversized flex bg (CVE-2023-52622)

• kernel: net/sched: flower: Fix chain template offload (CVE-2024-26669)

• kernel: stmmac: Clear variable when destroying workqueue (CVE-2024-26802)

• kernel: efi: runtime: Fix potential overflow of soft-reserved region size (CVE-2024-26843)

• kernel: quota: Fix potential NULL pointer dereference (CVE-2024-26878)

• kernel: TIPC message reassembly use-after-free remote code execution vulnerability (CVE-2024-36886)

• kernel: SUNRPC: fix a memleak in gss_import_v2_context (CVE-2023-52653)

• kernel: dmaengine/idxd: hardware erratum allows potential security problem with direct access by untrusted application (CVE-2024-21823)

• kernel: ext4: fix corruption during on-line resize (CVE-2024-35807)

• kernel: x86/fpu: Keep xfd_state in sync with MSR_IA32_XFD (CVE-2024-35801)

• kernel: dyndbg: fix old BUG_ON in >control parser (CVE-2024-35947)

• kernel: net/sched: act_skbmod: prevent kernel-infoleak (CVE-2024-35893)

• kernel: x86/mce: Make sure to grab mce_sysfs_mutex in set_bank() (CVE-2024-35876)

• kernel: platform/x86: wmi: Fix opening of char device (CVE-2023-52864)

• kernel: tipc: Change nla_policy for bearer-related names to NLA_NUL_STRING (CVE-2023-52845)

• kernel: Revert "net/mlx5: Block entering switchdev mode with ns inconsistency" (CVE-2023-52658)

• kernel: crash due to a missing check for leb_size (CVE-2024-25739)

• kernel: tcp: make sure init the accept_queue's spinlocks once (CVE-2024-26614)

• kernel: tcp: add sanity checks to rx zerocopy (CVE-2024-26640)

• kernel: NFSv4.2: fix nfs4_listxattr kernel BUG at mm/usercopy.c:102 (CVE-2024-26870)

• kernel: nfs: fix UAF in direct writes (CVE-2024-26958)

• kernel: SUNRPC: fix some memleaks in gssx_dec_option_array (CVE-2024-27388)

• kernel: wifi: iwlwifi: mvm: don't set the MFP flag for the GTK (CVE-2024-27434)

• kernel: of: Fix double free in of_parse_phandle_with_args_map (CVE-2023-52679)

• kernel: scsi: lpfc: Fix possible memory leak in lpfc_rcv_padisc() (CVE-2024-35930)

• kernel: wifi: iwlwifi: mvm: rfi: fix potential response leaks (CVE-2024-35912)

• kernel: block: prevent division by zero in blk_rq_stat_sum() (CVE-2024-35925)

• kernel: wifi: ath11k: decrease MHI channel buffer length to 8KB (CVE-2024-35938)

• kernel: wifi: cfg80211: check A-MSDU format more carefully (CVE-2024-35937)

• kernel: wifi: rtw89: fix null pointer access when abort scan (CVE-2024-35946)

• kernel: netfilter: nf_tables: honor table dormant flag from netdev release event path (CVE-2024-36005)

• kernel: mm/hugetlb: fix missing hugetlb_lock for resv uncharge (CVE-2024-36000)

• kernel: mlxsw: spectrum_acl_tcam: Fix incorrect list API usage (CVE-2024-36006)

• kernel: net: ieee802154: fix null deref in parse dev addr (CVE-2021-47257)

• kernel: mmc: sdio: fix possible resource leaks in some error paths (CVE-2023-52730)

• kernel: wifi: ath11k: fix gtk offload status event locking (CVE-2023-52777)

• (CVE-2023-52832)

• (CVE-2023-52803)

• (CVE-2023-52756)

• (CVE-2023-52834)

• (CVE-2023-52791)

• (CVE-2023-52764)

• (CVE-2021-47468)

• (CVE-2021-47284)

• (CVE-2024-36025)

• (CVE-2024-36941)

• (CVE-2024-36940)

• (CVE-2024-36904)

• (CVE-2024-36896)

• (CVE-2024-36954)

• (CVE-2024-36950)

• (CVE-2024-38575)

• (CVE-2024-36917)

• (CVE-2024-36016)

• (CVE-2023-52762)

• (CVE-2024-27025)

• (CVE-2021-47548)

• (CVE-2023-52619)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer the CVE page(s) listed in the References section.

Errata Tool Automation could not update the description because it is longer (4803) than ET limit of 4000 characters. (OSCI-6058) Please update the description manually.

The kernel packages contain the Linux kernel, the core of any Linux operating system.

Security Fix(es):

• kernel: powerpc: Fix access beyond end of drmem array (CVE-2023-52451)

• kernel: efivarfs: force RO when remounting if SetVariable is not supported (CVE-2023-52463)

• kernel: tracing: Restructure trace_clock_global() to never block (CVE-2021-46939)

• kernel: ext4: avoid online resizing failures due to oversized flex bg (CVE-2023-52622)

• kernel: net/sched: flower: Fix chain template offload (CVE-2024-26669)

• kernel: stmmac: Clear variable when destroying workqueue (CVE-2024-26802)

• kernel: efi: runtime: Fix potential overflow of soft-reserved region size (CVE-2024-26843)

• kernel: quota: Fix potential NULL pointer dereference (CVE-2024-26878)

• kernel: TIPC message reassembly use-after-free remote code execution vulnerability (CVE-2024-36886)

• kernel: SUNRPC: fix a memleak in gss_import_v2_context (CVE-2023-52653)

• kernel: dmaengine/idxd: hardware erratum allows potential security problem with direct access by untrusted application (CVE-2024-21823)

• kernel: Revert "net/mlx5: Block entering switchdev mode with ns inconsistency" (CVE-2023-52658)

• kernel: ext4: fix corruption during on-line resize (CVE-2024-35807)

• kernel: x86/fpu: Keep xfd_state in sync with MSR_IA32_XFD (CVE-2024-35801)

• kernel: dyndbg: fix old BUG_ON in >control parser (CVE-2024-35947)

• kernel: net/sched: act_skbmod: prevent kernel-infoleak (CVE-2024-35893)

• kernel: x86/mce: Make sure to grab mce_sysfs_mutex in set_bank() (CVE-2024-35876)

• kernel: platform/x86: wmi: Fix opening of char device (CVE-2023-52864)

• kernel: tipc: Change nla_policy for bearer-related names to NLA_NUL_STRING (CVE-2023-52845)

• (CVE-2023-28746)

• (CVE-2023-52847)

• (CVE-2021-47548)

• (CVE-2024-36921)

• (CVE-2024-26921)

• (CVE-2021-47579)

• (CVE-2024-36927)

• (CVE-2024-39276)

• (CVE-2024-33621)

• (CVE-2024-27010)

• (CVE-2024-26960)

• (CVE-2024-38596)

• (CVE-2022-48743)

• (CVE-2024-26733)

• (CVE-2024-26586)

• (CVE-2024-26698)

• (CVE-2023-52619)

Bug Fix(es):

• Rocky Linux SIG Cloud8.6 - Spinlock statistics may show negative elapsed time and incorrectly formatted output (JIRA:Rocky Linux SIG Cloud-17678)

• [AWS][8.9]There are call traces found when booting debug-kernel for Amazon EC2 r8g.metal-24xl instance (JIRA:Rocky Linux SIG Cloud-23841)

• [rhel8] gfs2: Fix glock shrinker (JIRA:Rocky Linux SIG Cloud-32941)

• lan78xx: Microchip LAN7800 never comes up after unplug and replug (JIRA:Rocky Linux SIG Cloud-33437)

• [Hyper-V][Rocky Linux SIG Cloud-8.10.z] Update hv_netvsc driver to TOT (JIRA:Rocky Linux SIG Cloud-39074)

• Use-after-free on proc inode-i_sb triggered by fsnotify (JIRA:Rocky Linux SIG Cloud-40167)

• blk-cgroup: Properly propagate the iostat update up the hierarchy [rhel-8.10.z] (JIRA:Rocky Linux SIG Cloud-40939)

• (JIRA:Rocky Linux SIG Cloud-31798)

• (JIRA:Rocky Linux SIG Cloud-10263)

• (JIRA:Rocky Linux SIG Cloud-40901)

• (JIRA:Rocky Linux SIG Cloud-43547)

• (JIRA:Rocky Linux SIG Cloud-34876)

Enhancement(s):

• [RFE] Add module parameters 'soft_reboot_cmd' and 'soft_active_on_boot' for customizing softdog configuration (JIRA:Rocky Linux SIG Cloud-19723)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer the CVE page(s) listed in the References section.

The SUSE Linux Enterprise 15 SP5 Azure kernel was updated to receive various security bugfixes.

The following security bugs were fixed:

• CVE-2021-47089: kfence: fix memory leak when cat kfence objects (bsc#1220958.
• CVE-2021-47432: lib/generic-radix-tree.c: Do not overflow in peek() (bsc#1225391).
• CVE-2021-47515: seg6: fix the iif in the IPv6 socket control block (bsc#1225426).
• CVE-2021-47538: rxrpc: Fix rxrpc_local leak in rxrpc_lookup_peer() (bsc#1225448).
• CVE-2021-47539: rxrpc: Fix rxrpc_peer leak in rxrpc_look_up_bundle() (bsc#1225452).
• CVE-2021-47555: net: vlan: fix underflow for the real_dev refcnt (bsc#1225467).
• CVE-2021-47566: Fix clearing user buffer by properly using clear_user() (bsc#1225514).
• CVE-2021-47571: staging: rtl8192e: Fix use after free in _rtl92e_pci_disconnect() (bsc#1225518).
• CVE-2021-47572: net: nexthop: fix null pointer dereference when IPv6 is not enabled (bsc#1225389).
• CVE-2022-48716: ASoC: codecs: wcd938x: fix incorrect used of portid (bsc#1226678).
• CVE-2023-24023: Bluetooth: Add more enc key size check (bsc#1218148).
• CVE-2023-52622: ext4: avoid online resizing failures due to oversized flex bg (bsc#1222080).
• CVE-2023-52658: Revert 'net/mlx5: Block entering switchdev mode with ns inconsistency' (bsc#1224719).
• CVE-2023-52667: net/mlx5e: fix a potential double-free in fs_any_create_groups (bsc#1224603).
• CVE-2023-52670: rpmsg: virtio: Free driver_override when rpmsg_remove() (bsc#1224696).
• CVE-2023-52672: pipe: wakeup wr_wait after setting max_usage (bsc#1224614).
• CVE-2023-52675: powerpc/imc-pmu: Add a null pointer check in update_events_in_group() (bsc#1224504).
• CVE-2023-52735: bpf, sockmap: Don't let sock_map_{close,destroy,unhash} call itself (bsc#1225475).
• CVE-2023-52737: btrfs: lock the inode in shared mode before starting fiemap (bsc#1225484).
• CVE-2023-52752: smb: client: fix use-after-free bug in cifs_debug_data_proc_show() (bsc#1225487).
• CVE-2023-52784: bonding: stop the device in bond_setup_by_slave() (bsc#1224946).
• CVE-2023-52787: blk-mq: make sure active queue usage is held for bio_integrity_prep() (bsc#1225105).
• CVE-2023-52835: perf/core: Bail out early if the request AUX area is out of bound (bsc#1225602).
• CVE-2023-52837: nbd: fix uaf in nbd_open (bsc#1224935).
• CVE-2023-52843: llc: verify mac len before reading mac header (bsc#1224951).
• CVE-2023-52845: tipc: Change nla_policy for bearer-related names to NLA_NUL_STRING (bsc#1225585).
• CVE-2023-52846: hsr: Prevent use after free in prp_create_tagged_frame() (bsc#1225098).
• CVE-2023-52869: pstore/platform: Add check for kstrdup (bsc#1225050).
• CVE-2023-52881: tcp: do not accept ACK of bytes we never sent (bsc#1225611).
• CVE-2023-52882: clk: sunxi-ng: h6: Reparent CPUX during PLL CPUX rate change (bsc#1225692).
• CVE-2024-26625: Call sock_orphan() at release time (bsc#1221086)
• CVE-2024-26644: btrfs: do not abort filesystem when attempting to snapshot deleted subvolume (bsc#1221282bsc#1222072).
• CVE-2024-26720: mm: Avoid overflows in dirty throttling logic (bsc#1222364).
• CVE-2024-26923: Fixed false-positive lockdep splat for spin_lock() in __unix_gc() (bsc#1223384).
• CVE-2024-26973: fat: fix uninitialized field in nostale filehandles (git-fixesbsc#1223641).
• CVE-2024-27432: net: ethernet: mtk_eth_soc: fix PPE hanging issue (bsc#1224716).
• CVE-2024-35247: fpga: region: add owner module and take its refcount (bsc#1226948).
• CVE-2024-35789: Check fast rx for non-4addr sta VLAN changes (bsc#1224749).
• CVE-2024-35790: usb: typec: altmodes/displayport: create sysfs nodes as driver's default device attribute group (bsc#1224712).
• CVE-2024-35807: ext4: fix corruption during on-line resize (bsc#1224735).
• CVE-2024-35835: net/mlx5e: fix a double-free in arfs_create_groups (bsc#1224605).
• CVE-2024-35848: eeprom: at24: fix memory corruption race condition (bsc#1224612).
• CVE-2024-35857: icmp: prevent possible NULL dereferences from icmp_build_probe() (bsc#1224619).
• CVE-2024-35861:…

The SUSE Linux Enterprise 15 SP4 RT kernel was updated to receive various security bugfixes.

The following security bugs were fixed:

• CVE-2021-47555: net: vlan: fix underflow for the real_dev refcnt (bsc#1225467).
• CVE-2021-47571: staging: rtl8192e: Fix use after free in _rtl92e_pci_disconnect() (bsc#1225518).
• CVE-2023-24023: Bluetooth: Add more enc key size check (bsc#1218148).
• CVE-2023-52670: rpmsg: virtio: Free driver_override when rpmsg_remove() (bsc#1224696).
• CVE-2023-52752: smb: client: fix use-after-free bug in cifs_debug_data_proc_show() (bsc#1225487).
• CVE-2023-52837: nbd: fix uaf in nbd_open (bsc#1224935).
• CVE-2023-52846: hsr: Prevent use after free in prp_create_tagged_frame() (bsc#1225098).
• CVE-2023-52881: tcp: do not accept ACK of bytes we never sent (bsc#1225611).
• CVE-2024-35789: Check fast rx for non-4addr sta VLAN changes (bsc#1224749).
• CVE-2024-35861: Fixed potential UAF in cifs_signal_cifsd_for_reconnect() (bsc#1224766).
• CVE-2024-35862: Fixed potential UAF in smb2_is_network_name_deleted() (bsc#1224764).
• CVE-2024-35864: Fixed potential UAF in smb2_is_valid_lease_break() (bsc#1224765).
• CVE-2024-35950: drm/client: Fully protect modes with dev->mode_config.mutex (bsc#1224703).
• CVE-2024-36894: usb: gadget: f_fs: Fix race between aio_cancel() and AIO request complete (bsc#1225749).
• CVE-2024-36899: gpiolib: cdev: Fix use after free in lineinfo_changed_notify (bsc#1225737).
• CVE-2024-36904: tcp: Use refcount_inc_not_zero() in tcp_twsk_unique() (bsc#1225732).
• CVE-2024-36940: pinctrl: core: delete incorrect free in pinctrl_enable() (bsc#1225840).
• CVE-2024-36964: fs/9p: only translate RWX permissions for plain 9P2000 (bsc#1225866).
• CVE-2024-36971: net: fix __dst_negative_advice() race (bsc#1226145).
• CVE-2024-38541: of: module: add buffer overflow check in of_modalias() (bsc#1226587).
• CVE-2024-38545: RDMA/hns: Fix UAF for cq async event (bsc#1226595).
• CVE-2024-38559: scsi: qedf: Ensure the copied buf is NUL terminated (bsc#1226785).
• CVE-2024-38560: scsi: bfa: Ensure the copied buf is NUL terminated (bsc#1226786).
• CVE-2024-38564: bpf: Add BPF_PROG_TYPE_CGROUP_SKB attach type enforcement in BPF_LINK_CREATE (bsc#1226789).
• CVE-2024-38578: ecryptfs: Fix buffer size for tag 66 packet (bsc#1226634).

The following non-security bugs were fixed:

• Revert 'build initrd without systemd' (bsc#1195775)
• cgroup: Add annotation for holding namespace_sem in current_cgns_cgroup_from_root() (bsc#1222254).
• cgroup: Eliminate the need for cgroup_mutex in proc_cgroup_show() (bsc#1222254).
• cgroup: Make operations on the cgroup root_list RCU safe (bsc#1222254).
• cgroup: Remove unnecessary list_empty() (bsc#1222254).
• cgroup: preserve KABI of cgroup_root (bsc#1222254).
• mkspec-dtb: add toplevel symlinks also on arm
• ocfs2: adjust enabling place for la window (bsc#1219224).
• ocfs2: fix sparse warnings (bsc#1219224).
• ocfs2: improve write IO performance when fragmentation is high (bsc#1219224).
• ocfs2: speed up chain-list searching (bsc#1219224).
• random: treat bootloader trust toggle the same way as cpu trust toggle (bsc#1226953).
• rpm/kernel-obs-build.spec.in: Add iso9660 (bsc#1226212) Some builds do not just create an iso9660 image, but also mount it during build.
• rpm/kernel-obs-build.spec.in: Add networking modules for docker (bsc#1226211) docker needs more networking modules, even legacy iptable_nat and _filter.
• rpm/kernel-obs-build.spec.in: Include algif_hash, aegis128 and xts modules afgif_hash is needed by some packages (e.g. iwd) for tests, xts is used for LUKS2 volumes by default and aegis128 is useful as AEAD cipher for LUKS2. Wrap the long line to make it readable.
• rpm/mkspec-dtb: dtbs have moved to vendor sub-directories in 6.5 By commit 724ba6751532 ('ARM: dts: Move .dts files to vendor sub-directories'). So switch to them.
• scsi: lpfc: Remove IRQF_ONESHOT flag from threaded IRQ handling (bsc#1216124).
• smb: client: ensure to try all targets when finding…