It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2023-2024-549 advisory.

    2024-07-03: CVE-2024-26629 was added to this advisory.

    2024-07-03: CVE-2024-0841 was added to this advisory.

    2024-07-03: CVE-2023-52616 was added to this advisory.

    2024-05-23: CVE-2024-26665 was added to this advisory.

    2024-04-25: CVE-2024-26601 was added to this advisory.

    2024-04-25: CVE-2024-26602 was added to this advisory.

    2024-04-10: CVE-2024-26603 was added to this advisory.

    2024-03-27: CVE-2024-2193 was added to this advisory.

    2024-03-27: CVE-2024-26581 was added to this advisory.

    dm_table_create in drivers/md/dm-table.c in the Linux kernel through 6.7.4 can attempt to (in     alloc_targets) allocate more than INT_MAX bytes, and crash, because of a missing check for struct     dm_ioctl.target_count. (CVE-2023-52429)

    A flaw was found in the smb client in the Linux kernel. A potential out-of-bounds error was seen in the     smb2_parse_contexts() function. Validate offsets and lengths before dereferencing create contexts in     smb2_parse_contexts(). (CVE-2023-52434)

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

    net: prevent mss overflow in skb_segment()

    Once again syzbot is able to crash the kernel in skb_segment() [1]

    GSO_BY_FRAGS is a forbidden value, but unfortunately the followingcomputation in skb_segment() can reach     it quite easily :

    mss = mss * partial_segs;

    65535 = 3 * 5 * 17 * 257, so many initial values of mss can lead toa bad final result.

    Make sure to limit segmentation so that the new mss value is smallerthan GSO_BY_FRAGS.

    [1]

    general protection fault, probably for non-canonical address 0xdffffc000000000e: 0000 [#1] PREEMPT SMP     KASANKASAN: null-ptr-deref in range [0x0000000000000070-0x0000000000000077]CPU: 1 PID: 5079 Comm: syz-     executor993 Not tainted 6.7.0-rc4-syzkaller-00141-g1ae4cd3cbdd0 #0Hardware name: Google Google Compute     Engine/Google Compute Engine, BIOS Google 11/10/2023RIP: 0010:skb_segment+0x181d/0x3f30     net/core/skbuff.c:4551Code: 83 e3 02 e9 fb ed ff ff e8 90 68 1c f9 48 8b 84 24 f8 00 00 00 48 8d 78 70 48     b8 00 00 00 00 00 fc ff df 48 89 fa 48 c1 ea 03 <0f> b6 04 02 84 c0 74 08 3c 03 0f 8e 8a 21 00 00 48 8b 84     24 f8 00RSP: 0018:ffffc900043473d0 EFLAGS: 00010202RAX: dffffc0000000000 RBX: 0000000000010046 RCX:
    ffffffff886b1597RDX: 000000000000000e RSI: ffffffff886b2520 RDI: 0000000000000070RBP: ffffc90004347578     R08: 0000000000000005 R09: 000000000000ffffR10: 000000000000ffff R11: 0000000000000002 R12:
    ffff888063202ac0R13: 0000000000010000 R14: 000000000000ffff R15: 0000000000000046FS:
    0000555556e7e380(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000CS: 0010 DS: 0000 ES: 0000 CR0:
    0000000080050033CR2: 0000000020010000 CR3: 0000000027ee2000 CR4: 00000000003506f0DR0: 0000000000000000     DR1: 0000000000000000 DR2: 0000000000000000DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7:
    0000000000000400Call Trace:<TASK>udp6_ufo_fragment+0xa0e/0xd00     net/ipv6/udp_offload.c:109ipv6_gso_segment+0x534/0x17e0     net/ipv6/ip6_offload.c:120skb_mac_gso_segment+0x290/0x610 net/core/gso.c:53__skb_gso_segment+0x339/0x710     net/core/gso.c:124skb_gso_segment include/net/gso.h:83 [inline]validate_xmit_skb+0x36c/0xeb0     net/core/dev.c:3626__dev_queue_xmit+0x6f3/0x3d60 net/core/dev.c:4338dev_queue_xmit     include/linux/netdevice.h:3134 [inline]packet_xmit+0x257/0x380 net/packet/af_packet.c:276packet_snd     net/packet/af_packet.c:3087 [inline]packet_sendmsg+0x24c6/0x5220     net/packet/af_packet.c:3119sock_sendmsg_nosec net/socket.c:730 [inline]__sock_sendmsg+0xd5/0x180     net/socket.c:745__sys_sendto+0x255/0x340 net/socket.c:2190__do_sys_sendto net/socket.c:2202     [inline]__se_sys_sendto net/socket.c:2198 [inline]__x64_sys_sendto+0xe0/0x1b0     net/socket.c:2198do_syscall_x64 arch/x86/entry/common.c:52 [inline]do_syscall_64+0x40/0x110     arch/x86/entry/common.c:83entry_SYSCALL_64_after_hwframe+0x63/0x6bRIP: 0033:0x7f8692032aa9Code: 28 00 00     00 75 05 48 83 c4 28 c3 e8 d1 19 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c     24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48RSP: 002b:00007fff8d685418     EFLAGS: 00000246 ORIG_RAX: 000000000000002cRAX: ffffffffffffffda RBX: 0000000000000003 RCX:
    00007f8692032aa9RDX: 0000000000010048 RSI: 00000000200000c0 RDI: 0000000000000003RBP: 00000000000f4240     R08: 0000000020000540 R09: 0000000000000014R10: 0000000000000000 R11: 0000000000000246 R12:
    00007fff8d685480R13: 0000000000000001 R14: 00007fff8d685480 R15: 0000000000000003</TASK>Modules linked     in:---[ end trace 0000000000000000 ]---RIP: 0010:skb_segment+0x181d/0x3f30 net/core/skbuff.c:4551Code: 83     e3 02 e9 fb ed ff ff e8 90 68 1c f9 48 8b 84 24 f8 00 00 00 48 8d 78 70 48 b8 00 00 00 00 00 fc ff df 48     89 fa 48 c1 ea 03 <0f> b6 04 02 84 c0 74 08 3c 03 0f 8e 8a 21 00 00 48 8b 84 24 f8 00RSP:
    0018:ffffc900043473d0 EFLAGS: 00010202RAX: dffffc0000000000 RBX: 0000000000010046 RCX:
    ffffffff886b1597RDX: 000000000000000e RSI: ffffffff886b2520 RDI: 0000000000000070RBP: ffffc90004347578 R0
    ---truncated--- (CVE-2023-52435)

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

    crypto: lib/mpi - Fix unexpected pointer access in mpi_ec_init (CVE-2023-52616)

    A vulnerability was found in vhost_new_msg in drivers/vhost/vhost.c in the Linux kernel, which does not     properly initialize memory in messages passed between virtual guests and the host operating system in the     vhost/vhost.c:vhost_new_msg() function. This issue can allow local privileged users to read some kernel     memory contents when reading from the /dev/vhost-net device file. (CVE-2024-0340)

    A null pointer dereference flaw was found in the hugetlbfs_fill_super function in the Linux kernel     hugetlbfs (HugeTLB pages) functionality. This issue may allow a local user to crash the system or     potentially escalate their privileges on the system. (CVE-2024-0841)

    A vulnerability was reported in the Open vSwitch sub-component in the Linux Kernel. The flaw occurs when a     recursive operation of code push recursively calls into the code block. The OVS module does not validate     the stack depth, pushing too many frames and causing a stack overflow. As a result, this can lead to a     crash or other related issues. (CVE-2024-1151)

    A Speculative Race Condition (SRC) vulnerability that impacts modern CPU architectures supporting     speculative execution (related to Spectre V1) has been disclosed. An unauthenticated attacker can exploit     this vulnerability to disclose arbitrary data from the CPU using race conditions to access the speculative     executable code paths. (CVE-2024-2193)

    In btrfs_get_root_ref in fs/btrfs/disk-io.c in the Linux kernel through 6.7.1, there can be an assertion     failure and crash because a subvolume can be read out too soon after its root item is inserted upon     subvolume creation. (CVE-2024-23850)

    copy_params in drivers/md/dm-ioctl.c in the Linux kernel through 6.7.1 can attempt to allocate more than     INT_MAX bytes, and crash, because of a missing param_kernel->data_size check. This is related to     ctl_ioctl. (CVE-2024-23851)

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

    netfilter: nft_set_rbtree: skip end interval element from gc

    rbtree lazy gc on insert might collect an end interval element that hasbeen just added in this     transactions, skip end interval elements thatare not yet active. (CVE-2024-26581)

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

    net: tls: fix use-after-free with partial reads and async decrypt

    tls_decrypt_sg doesn't take a reference on the pages from clear_skb,so the put_page() in tls_decrypt_done     releases them, and we triggera use-after-free in process_rx_list when we try to read from thepartially-     read skb. (CVE-2024-26582)

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

    tls: fix race between async notify and socket close

    The submitting thread (one which called recvmsg/sendmsg)may exit as soon as the async crypto handler calls     complete()so any code past that point risks touching already freed data.

    Try to avoid the locking and extra flags altogether.Have the main thread hold an extra reference, this     waywe can depend solely on the atomic ref counter forsynchronization.

    Don't futz with reiniting the completion, either, we are nowtightly controlling when completion fires.
    (CVE-2024-26583)

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

    ext4: regenerate buddy after block freeing failed if under fc replay

    This mostly reverts commit 6bd97bf273bd (ext4: remove redundantmb_regenerate_buddy()) and reintroduces     mb_regenerate_buddy(). Based oncode in mb_free_blocks(), fast commit replay can end up marking as     freeblocks that are already marked as such. This causes corruption of thebuddy bitmap so we need to     regenerate it in that case. (CVE-2024-26601)

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

    sched/membarrier: reduce the ability to hammer on sys_membarrier

    On some systems, sys_membarrier can be very expensive, causing overallslowdowns for everything.  So put a     lock on the path in order toserialize the accesses to prevent the ability for this to be called attoo high     of a frequency and saturate the machine. (CVE-2024-26602)

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

    x86/fpu: Stop relying on userspace for info to fault in xsave buffer

    Before this change, the expected size of the user space buffer wastaken from fx_sw->xstate_size.
    fx_sw->xstate_size can be changedfrom user-space, so it is possible construct a sigreturn frame where:

    * fx_sw->xstate_size is smaller than the size required by valid bits infx_sw->xfeatures.* user-space     unmaps parts of the sigrame fpu buffer so that not all ofthe buffer required by xrstor is accessible.

    In this case, xrstor tries to restore and accesses the unmapped areawhich results in a fault. But     fault_in_readable succeeds because buf +fx_sw->xstate_size is within the still mapped area, so it goes     back andtries xrstor again. It will spin in this loop forever.

    Instead, fault in the maximum size which can be touched by XRSTOR (takenfrom fpstate->user_size).

    [ dhansen: tweak subject / changelog ] (CVE-2024-26603)

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

    nfsd: fix RELEASE_LOCKOWNER (CVE-2024-26629)

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

    tunnels: fix out of bounds access when building IPv6 PMTU error (CVE-2024-26665)

Tenable has extracted the preceding description block directly from the tested product security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

Detections

Analytics

Amazon Linux 2023 : bpftool, kernel, kernel-devel (ALAS2023-2024-549)

high Nessus Plugin ID 191609

Version 1.11