In the Linux kernel, the following vulnerability has been resolved: mlxsw: spectrum_acl_tcam: Fix stack corruption When tc filters are first added to a net device, the corresponding local port gets bound to an ACL group in the device. The group contains a list of ACLs. In turn, each ACL points to a different TCAM region where the filters are stored. During forwarding, the ACLs are sequentially evaluated until a match is found. One reason to place filters in different regions is when they are added with decreasing priorities and in an alternating order so that two consecutive filters can never fit in the same region because of their key usage. In Spectrum-2 and newer ASICs the firmware started to report that the maximum number of ACLs in a group is more than 16, but the layout of the register that configures ACL groups (PAGT) was not updated to account for that. It is therefore possible to hit stack corruption [1] in the rare case where more than 16 ACLs in a group are required. Fix by limiting the maximum ACL group size to the minimum between what the firmware reports and the maximum ACLs that fit in the PAGT register. Add a test case to make sure the machine does not crash when this condition is hit. [1] Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: mlxsw_sp_acl_tcam_group_update+0x116/0x120 [...] dump_stack_lvl+0x36/0x50 panic+0x305/0x330 __stack_chk_fail+0x15/0x20 mlxsw_sp_acl_tcam_group_update+0x116/0x120 mlxsw_sp_acl_tcam_group_region_attach+0x69/0x110 mlxsw_sp_acl_tcam_vchunk_get+0x492/0xa20 mlxsw_sp_acl_tcam_ventry_add+0x25/0xe0 mlxsw_sp_acl_rule_add+0x47/0x240 mlxsw_sp_flower_replace+0x1a9/0x1d0 tc_setup_cb_add+0xdc/0x1c0 fl_hw_replace_filter+0x146/0x1f0 fl_change+0xc17/0x1360 tc_new_tfilter+0x472/0xb90 rtnetlink_rcv_msg+0x313/0x3b0 netlink_rcv_skb+0x58/0x100 netlink_unicast+0x244/0x390 netlink_sendmsg+0x1e4/0x440 ____sys_sendmsg+0x164/0x260 ___sys_sendmsg+0x9a/0xe0 __sys_sendmsg+0x7a/0xc0 do_syscall_64+0x40/0xe0 entry_SYSCALL_64_after_hwframe+0x63/0x6b

The version of kernel installed on the remote host is prior to 5.4.275-189.375. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2KERNEL-5.4-2024-065 advisory.

  - In the Linux kernel, the following vulnerability has been resolved: smb: client: fix potential OOBs in     smb2_parse_contexts() Validate offsets and lengths before dereferencing create contexts in     smb2_parse_contexts(). This fixes following oops when accessing invalid create contexts from server: BUG:
    unable to handle page fault for address: ffff8881178d8cc3 #PF: supervisor read access in kernel mode #PF:
    error_code(0x0000) - not-present page PGD 4a01067 P4D 4a01067 PUD 0 Oops: 0000 [#1] PREEMPT SMP NOPTI CPU:
    3 PID: 1736 Comm: mount.cifs Not tainted 6.7.0-rc4 #1 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009),     BIOS rel-1.16.2-3-gd478f380-rebuilt.opensuse.org 04/01/2014 RIP: 0010:smb2_parse_contexts+0xa0/0x3a0     [cifs] Code: f8 10 75 13 48 b8 93 ad 25 50 9c b4 11 e7 49 39 06 0f 84 d2 00 00 00 8b 45 00 85 c0 74 61 41     29 c5 48 01 c5 41 83 fd 0f 76 55 <0f> b7 7d 04 0f b7 45 06 4c 8d 74 3d 00 66 83 f8 04 75 bc ba 04 00 RSP:
    0018:ffffc900007939e0 EFLAGS: 00010216 RAX: ffffc90000793c78 RBX: ffff8880180cc000 RCX: ffffc90000793c90     RDX: ffffc90000793cc0 RSI: ffff8880178d8cc0 RDI: ffff8880180cc000 RBP: ffff8881178d8cbf R08:
    ffffc90000793c22 R09: 0000000000000000 R10: ffff8880180cc000 R11: 0000000000000024 R12: 0000000000000000     R13: 0000000000000020 R14: 0000000000000000 R15: ffffc90000793c22 FS: 00007f873753cbc0(0000)     GS:ffff88806bc00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2:
    ffff8881178d8cc3 CR3: 00000000181ca000 CR4: 0000000000750ef0 PKRU: 55555554 Call Trace: <TASK> ?
    __die+0x23/0x70 ? page_fault_oops+0x181/0x480 ? search_module_extables+0x19/0x60 ?     srso_alias_return_thunk+0x5/0xfbef5 ? exc_page_fault+0x1b6/0x1c0 ? asm_exc_page_fault+0x26/0x30 ?     smb2_parse_contexts+0xa0/0x3a0 [cifs] SMB2_open+0x38d/0x5f0 [cifs] ? smb2_is_path_accessible+0x138/0x260     [cifs] smb2_is_path_accessible+0x138/0x260 [cifs] cifs_is_path_remote+0x8d/0x230 [cifs]     cifs_mount+0x7e/0x350 [cifs] cifs_smb3_do_mount+0x128/0x780 [cifs] smb3_get_tree+0xd9/0x290 [cifs]     vfs_get_tree+0x2c/0x100 ? capable+0x37/0x70 path_mount+0x2d7/0xb80 ? srso_alias_return_thunk+0x5/0xfbef5 ?
    _raw_spin_unlock_irqrestore+0x44/0x60 __x64_sys_mount+0x11a/0x150 do_syscall_64+0x47/0xf0     entry_SYSCALL_64_after_hwframe+0x6f/0x77 RIP: 0033:0x7f8737657b1e (CVE-2023-52434)

  - 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 way we can depend     solely on the atomic ref counter for synchronization. Don't futz with reiniting the completion, either, we     are now tightly controlling when completion fires. (CVE-2024-26583)

  - In the Linux kernel, the following vulnerability has been resolved: net: tls: handle backlogging of crypto     requests Since we're setting the CRYPTO_TFM_REQ_MAY_BACKLOG flag on our requests to the crypto API,     crypto_aead_{encrypt,decrypt} can return -EBUSY instead of -EINPROGRESS in valid situations. For example,     when the cryptd queue for AESNI is full (easy to trigger with an artificially low     cryptd.cryptd_max_cpu_qlen), requests will be enqueued to the backlog but still processed. In that case,     the async callback will also be called twice: first with err == -EINPROGRESS, which it seems we can just     ignore, then with err == 0. Compared to Sabrina's original patch this version uses the new     tls_*crypt_async_wait() helpers and converts the EBUSY to EINPROGRESS to avoid having to modify all the     error handling paths. The handling is identical. (CVE-2024-26584)

  - In the Linux kernel, the following vulnerability has been resolved: mlxsw: spectrum_acl_tcam: Fix stack     corruption When tc filters are first added to a net device, the corresponding local port gets bound to an     ACL group in the device. The group contains a list of ACLs. In turn, each ACL points to a different TCAM     region where the filters are stored. During forwarding, the ACLs are sequentially evaluated until a match     is found. One reason to place filters in different regions is when they are added with decreasing     priorities and in an alternating order so that two consecutive filters can never fit in the same region     because of their key usage. In Spectrum-2 and newer ASICs the firmware started to report that the maximum     number of ACLs in a group is more than 16, but the layout of the register that configures ACL groups     (PAGT) was not updated to account for that. It is therefore possible to hit stack corruption [1] in the     rare case where more than 16 ACLs in a group are required. Fix by limiting the maximum ACL group size to     the minimum between what the firmware reports and the maximum ACLs that fit in the PAGT register. Add a     test case to make sure the machine does not crash when this condition is hit. [1] Kernel panic - not     syncing: stack-protector: Kernel stack is corrupted in: mlxsw_sp_acl_tcam_group_update+0x116/0x120 [...]     dump_stack_lvl+0x36/0x50 panic+0x305/0x330 __stack_chk_fail+0x15/0x20     mlxsw_sp_acl_tcam_group_update+0x116/0x120 mlxsw_sp_acl_tcam_group_region_attach+0x69/0x110     mlxsw_sp_acl_tcam_vchunk_get+0x492/0xa20 mlxsw_sp_acl_tcam_ventry_add+0x25/0xe0     mlxsw_sp_acl_rule_add+0x47/0x240 mlxsw_sp_flower_replace+0x1a9/0x1d0 tc_setup_cb_add+0xdc/0x1c0     fl_hw_replace_filter+0x146/0x1f0 fl_change+0xc17/0x1360 tc_new_tfilter+0x472/0xb90     rtnetlink_rcv_msg+0x313/0x3b0 netlink_rcv_skb+0x58/0x100 netlink_unicast+0x244/0x390     netlink_sendmsg+0x1e4/0x440 ____sys_sendmsg+0x164/0x260 ___sys_sendmsg+0x9a/0xe0 __sys_sendmsg+0x7a/0xc0     do_syscall_64+0x40/0xe0 entry_SYSCALL_64_after_hwframe+0x63/0x6b (CVE-2024-26586)

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

The remote Redhat Enterprise Linux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2024:2674 advisory.

  - kernel: off-path attacker may inject data or terminate victim's TCP session (CVE-2020-36516)

  - kernel: mlxsw: spectrum_acl_tcam: Fix stack corruption (CVE-2024-26586)

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

The remote Redhat Enterprise Linux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2024:2582 advisory.

  - In the Linux kernel, the following vulnerability has been resolved: netfilter: nft_limit: avoid possible     divide error in nft_limit_init div_u64() divides u64 by u32. nft_limit_init() wants to divide u64 by u64,     use the appropriate math function (div64_u64) divide error: 0000 [#1] PREEMPT SMP KASAN CPU: 1 PID: 8390     Comm: syz-executor188 Not tainted 5.12.0-rc4-syzkaller #0 Hardware name: Google Google Compute     Engine/Google Compute Engine, BIOS Google 01/01/2011 RIP: 0010:div_u64_rem include/linux/math64.h:28     [inline] RIP: 0010:div_u64 include/linux/math64.h:127 [inline] RIP: 0010:nft_limit_init+0x2a2/0x5e0     net/netfilter/nft_limit.c:85 Code: ef 4c 01 eb 41 0f 92 c7 48 89 de e8 38 a5 22 fa 4d 85 ff 0f 85 97 02 00     00 e8 ea 9e 22 fa 4c 0f af f3 45 89 ed 31 d2 4c 89 f0 <49> f7 f5 49 89 c6 e8 d3 9e 22 fa 48 8d 7d 48 48 b8     00 00 00 00 00 RSP: 0018:ffffc90009447198 EFLAGS: 00010246 RAX: 0000000000000000 RBX: 0000200000000000     RCX: 0000000000000000 RDX: 0000000000000000 RSI: ffffffff875152e6 RDI: 0000000000000003 RBP:
    ffff888020f80908 R08: 0000200000000000 R09: 0000000000000000 R10: ffffffff875152d8 R11: 0000000000000000     R12: ffffc90009447270 R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 FS:
    000000000097a300(0000) GS:ffff8880b9d00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0:
    0000000080050033 CR2: 00000000200001c4 CR3: 0000000026a52000 CR4: 00000000001506e0 DR0: 0000000000000000     DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7:
    0000000000000400 Call Trace: nf_tables_newexpr net/netfilter/nf_tables_api.c:2675 [inline]     nft_expr_init+0x145/0x2d0 net/netfilter/nf_tables_api.c:2713 nft_set_elem_expr_alloc+0x27/0x280     net/netfilter/nf_tables_api.c:5160 nf_tables_newset+0x1997/0x3150 net/netfilter/nf_tables_api.c:4321     nfnetlink_rcv_batch+0x85a/0x21b0 net/netfilter/nfnetlink.c:456 nfnetlink_rcv_skb_batch     net/netfilter/nfnetlink.c:580 [inline] nfnetlink_rcv+0x3af/0x420 net/netfilter/nfnetlink.c:598     netlink_unicast_kernel net/netlink/af_netlink.c:1312 [inline] netlink_unicast+0x533/0x7d0     net/netlink/af_netlink.c:1338 netlink_sendmsg+0x856/0xd90 net/netlink/af_netlink.c:1927 sock_sendmsg_nosec     net/socket.c:654 [inline] sock_sendmsg+0xcf/0x120 net/socket.c:674 ____sys_sendmsg+0x6e8/0x810     net/socket.c:2350 ___sys_sendmsg+0xf3/0x170 net/socket.c:2404 __sys_sendmsg+0xe5/0x1b0 net/socket.c:2433     do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46 entry_SYSCALL_64_after_hwframe+0x44/0xae     (CVE-2021-46915)

  - An issue was discovered in l2cap_sock_release in net/bluetooth/l2cap_sock.c in the Linux kernel before     6.4.10. There is a use-after-free because the children of an sk are mishandled. (CVE-2023-40283)

  - In the Linux kernel, the following vulnerability has been resolved: mlxsw: spectrum_acl_tcam: Fix stack     corruption When tc filters are first added to a net device, the corresponding local port gets bound to an     ACL group in the device. The group contains a list of ACLs. In turn, each ACL points to a different TCAM     region where the filters are stored. During forwarding, the ACLs are sequentially evaluated until a match     is found. One reason to place filters in different regions is when they are added with decreasing     priorities and in an alternating order so that two consecutive filters can never fit in the same region     because of their key usage. In Spectrum-2 and newer ASICs the firmware started to report that the maximum     number of ACLs in a group is more than 16, but the layout of the register that configures ACL groups     (PAGT) was not updated to account for that. It is therefore possible to hit stack corruption [1] in the     rare case where more than 16 ACLs in a group are required. Fix by limiting the maximum ACL group size to     the minimum between what the firmware reports and the maximum ACLs that fit in the PAGT register. Add a     test case to make sure the machine does not crash when this condition is hit. [1] Kernel panic - not     syncing: stack-protector: Kernel stack is corrupted in: mlxsw_sp_acl_tcam_group_update+0x116/0x120 [...]     dump_stack_lvl+0x36/0x50 panic+0x305/0x330 __stack_chk_fail+0x15/0x20     mlxsw_sp_acl_tcam_group_update+0x116/0x120 mlxsw_sp_acl_tcam_group_region_attach+0x69/0x110     mlxsw_sp_acl_tcam_vchunk_get+0x492/0xa20 mlxsw_sp_acl_tcam_ventry_add+0x25/0xe0     mlxsw_sp_acl_rule_add+0x47/0x240 mlxsw_sp_flower_replace+0x1a9/0x1d0 tc_setup_cb_add+0xdc/0x1c0     fl_hw_replace_filter+0x146/0x1f0 fl_change+0xc17/0x1360 tc_new_tfilter+0x472/0xb90     rtnetlink_rcv_msg+0x313/0x3b0 netlink_rcv_skb+0x58/0x100 netlink_unicast+0x244/0x390     netlink_sendmsg+0x1e4/0x440 ____sys_sendmsg+0x164/0x260 ___sys_sendmsg+0x9a/0xe0 __sys_sendmsg+0x7a/0xc0     do_syscall_64+0x40/0xe0 entry_SYSCALL_64_after_hwframe+0x63/0x6b (CVE-2024-26586)

  - 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 overall     slowdowns for everything. So put a lock on the path in order to serialize the accesses to prevent the     ability for this to be called at too high of a frequency and saturate the machine. (CVE-2024-26602)

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

The remote Redhat Enterprise Linux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2024:2585 advisory.

  - In the Linux kernel, the following vulnerability has been resolved: netfilter: nft_limit: avoid possible     divide error in nft_limit_init div_u64() divides u64 by u32. nft_limit_init() wants to divide u64 by u64,     use the appropriate math function (div64_u64) divide error: 0000 [#1] PREEMPT SMP KASAN CPU: 1 PID: 8390     Comm: syz-executor188 Not tainted 5.12.0-rc4-syzkaller #0 Hardware name: Google Google Compute     Engine/Google Compute Engine, BIOS Google 01/01/2011 RIP: 0010:div_u64_rem include/linux/math64.h:28     [inline] RIP: 0010:div_u64 include/linux/math64.h:127 [inline] RIP: 0010:nft_limit_init+0x2a2/0x5e0     net/netfilter/nft_limit.c:85 Code: ef 4c 01 eb 41 0f 92 c7 48 89 de e8 38 a5 22 fa 4d 85 ff 0f 85 97 02 00     00 e8 ea 9e 22 fa 4c 0f af f3 45 89 ed 31 d2 4c 89 f0 <49> f7 f5 49 89 c6 e8 d3 9e 22 fa 48 8d 7d 48 48 b8     00 00 00 00 00 RSP: 0018:ffffc90009447198 EFLAGS: 00010246 RAX: 0000000000000000 RBX: 0000200000000000     RCX: 0000000000000000 RDX: 0000000000000000 RSI: ffffffff875152e6 RDI: 0000000000000003 RBP:
    ffff888020f80908 R08: 0000200000000000 R09: 0000000000000000 R10: ffffffff875152d8 R11: 0000000000000000     R12: ffffc90009447270 R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 FS:
    000000000097a300(0000) GS:ffff8880b9d00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0:
    0000000080050033 CR2: 00000000200001c4 CR3: 0000000026a52000 CR4: 00000000001506e0 DR0: 0000000000000000     DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7:
    0000000000000400 Call Trace: nf_tables_newexpr net/netfilter/nf_tables_api.c:2675 [inline]     nft_expr_init+0x145/0x2d0 net/netfilter/nf_tables_api.c:2713 nft_set_elem_expr_alloc+0x27/0x280     net/netfilter/nf_tables_api.c:5160 nf_tables_newset+0x1997/0x3150 net/netfilter/nf_tables_api.c:4321     nfnetlink_rcv_batch+0x85a/0x21b0 net/netfilter/nfnetlink.c:456 nfnetlink_rcv_skb_batch     net/netfilter/nfnetlink.c:580 [inline] nfnetlink_rcv+0x3af/0x420 net/netfilter/nfnetlink.c:598     netlink_unicast_kernel net/netlink/af_netlink.c:1312 [inline] netlink_unicast+0x533/0x7d0     net/netlink/af_netlink.c:1338 netlink_sendmsg+0x856/0xd90 net/netlink/af_netlink.c:1927 sock_sendmsg_nosec     net/socket.c:654 [inline] sock_sendmsg+0xcf/0x120 net/socket.c:674 ____sys_sendmsg+0x6e8/0x810     net/socket.c:2350 ___sys_sendmsg+0xf3/0x170 net/socket.c:2404 __sys_sendmsg+0xe5/0x1b0 net/socket.c:2433     do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46 entry_SYSCALL_64_after_hwframe+0x44/0xae     (CVE-2021-46915)

  - An issue was discovered in l2cap_sock_release in net/bluetooth/l2cap_sock.c in the Linux kernel before     6.4.10. There is a use-after-free because the children of an sk are mishandled. (CVE-2023-40283)

  - In the Linux kernel, the following vulnerability has been resolved: mlxsw: spectrum_acl_tcam: Fix stack     corruption When tc filters are first added to a net device, the corresponding local port gets bound to an     ACL group in the device. The group contains a list of ACLs. In turn, each ACL points to a different TCAM     region where the filters are stored. During forwarding, the ACLs are sequentially evaluated until a match     is found. One reason to place filters in different regions is when they are added with decreasing     priorities and in an alternating order so that two consecutive filters can never fit in the same region     because of their key usage. In Spectrum-2 and newer ASICs the firmware started to report that the maximum     number of ACLs in a group is more than 16, but the layout of the register that configures ACL groups     (PAGT) was not updated to account for that. It is therefore possible to hit stack corruption [1] in the     rare case where more than 16 ACLs in a group are required. Fix by limiting the maximum ACL group size to     the minimum between what the firmware reports and the maximum ACLs that fit in the PAGT register. Add a     test case to make sure the machine does not crash when this condition is hit. [1] Kernel panic - not     syncing: stack-protector: Kernel stack is corrupted in: mlxsw_sp_acl_tcam_group_update+0x116/0x120 [...]     dump_stack_lvl+0x36/0x50 panic+0x305/0x330 __stack_chk_fail+0x15/0x20     mlxsw_sp_acl_tcam_group_update+0x116/0x120 mlxsw_sp_acl_tcam_group_region_attach+0x69/0x110     mlxsw_sp_acl_tcam_vchunk_get+0x492/0xa20 mlxsw_sp_acl_tcam_ventry_add+0x25/0xe0     mlxsw_sp_acl_rule_add+0x47/0x240 mlxsw_sp_flower_replace+0x1a9/0x1d0 tc_setup_cb_add+0xdc/0x1c0     fl_hw_replace_filter+0x146/0x1f0 fl_change+0xc17/0x1360 tc_new_tfilter+0x472/0xb90     rtnetlink_rcv_msg+0x313/0x3b0 netlink_rcv_skb+0x58/0x100 netlink_unicast+0x244/0x390     netlink_sendmsg+0x1e4/0x440 ____sys_sendmsg+0x164/0x260 ___sys_sendmsg+0x9a/0xe0 __sys_sendmsg+0x7a/0xc0     do_syscall_64+0x40/0xe0 entry_SYSCALL_64_after_hwframe+0x63/0x6b (CVE-2024-26586)

  - 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 overall     slowdowns for everything. So put a lock on the path in order to serialize the accesses to prevent the     ability for this to be called at too high of a frequency and saturate the machine. (CVE-2024-26602)

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

The remote Redhat Enterprise Linux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2024:2394 advisory.

  - kernel: Bluetooth BR/EDR PIN Pairing procedure is vulnerable to an impersonation attack (CVE-2020-26555)

  - kernel: memcg does not limit the number of POSIX file locks allowing memory exhaustion (CVE-2022-0480)

  - kernel: vmwgfx: NULL pointer dereference in vmw_cmd_dx_define_query (CVE-2022-38096)

  - kernel: integer overflow in l2cap_config_req() in net/bluetooth/l2cap_core.c (CVE-2022-45934)

  - kernel: use after free in vcs_read in drivers/tty/vt/vc_screen.c due to race (CVE-2023-3567)

  - kernel: cxgb4: use-after-free in ch_flower_stats_cb() (CVE-2023-4133)

  - kernel: netfilter: nf_tables: out-of-bounds access in nf_tables_newtable() (CVE-2023-6040)

  - kernel: NVMe: info leak due to out-of-bounds read in nvmet_ctrl_find_get (CVE-2023-6121)

  - kernel: local dos vulnerability in scatterwalk_copychunks (CVE-2023-6176)

  - kernel: GC's deletion of an SKB races with unix_stream_read_generic()  leading to UAF (CVE-2023-6531)

  - kernel: GSM multiplexing race condition leads to privilege escalation (CVE-2023-6546)

  - kernel: null pointer dereference vulnerability in nft_dynset_init() (CVE-2023-6622)

  - kernel: Null Pointer Dereference vulnerability in ida_free in lib/idr.c (CVE-2023-6915)

  - kernel: Out of boundary write in perf_read_group() as result of overflow a perf_event's read_size     (CVE-2023-6931)

  - kernel: use-after-free in IPv4 IGMP (CVE-2023-6932)

  - kernel: Bluetooth Forward and Future Secrecy Attacks and Defenses (CVE-2023-24023)

  - kernel: irdma: Improper access control (CVE-2023-25775)

  - Kernel: double free in hci_conn_cleanup of the bluetooth subsystem (CVE-2023-28464)

  - kernel: Bluetooth: HCI: global out-of-bounds access in net/bluetooth/hci_sync.c (CVE-2023-28866)

  - kernel: race condition between HCIUARTSETPROTO and HCIUARTGETPROTO in hci_uart_tty_ioctl (CVE-2023-31083)

  - kernel: usb: out-of-bounds read in read_descriptors (CVE-2023-37453)

  - kernel: netfilter: nftables out-of-bounds read in nf_osf_match_one() (CVE-2023-39189)

  - kernel: netfilter: xtables sctp out-of-bounds read in match_flags() (CVE-2023-39193)

  - kernel: xfrm: out-of-bounds read in __xfrm_state_filter_match() (CVE-2023-39194)

  - kernel: QXL: race condition leading to use-after-free in qxl_mode_dumb_create() (CVE-2023-39198)

  - kernel: ipv4: NULL pointer dereference in ipv4_send_dest_unreach() (CVE-2023-42754)

  - kernel: netfilter: race condition between IPSET_CMD_ADD and IPSET_CMD_SWAP (CVE-2023-42756)

  - kernel: lib/kobject.c vulnerable to fill_kobj_path out-of-bounds write (CVE-2023-45863)

  - kernel: NULL pointer dereference vulnerability in io_uring_show_fdinfo (CVE-2023-46862)

  - kernel: use-after-free during a race condition between a nonblocking atomic commit and a driver unload in     drivers/gpu/drm/drm_atomic.c (CVE-2023-51043)

  - kernel: bluetooth: bt_sock_ioctl race condition leads to use-after-free in bt_sock_recvmsg     (CVE-2023-51779)

  - kernel: use-after-free in net/atm/ioctl.c (CVE-2023-51780)

  - kernel: smb: client: fix potential OOBs in smb2_parse_contexts() (CVE-2023-52434)

  - kernel: gfs2: Fix kernel NULL pointer dereference in gfs2_rgrp_dump (CVE-2023-52448)

  - kernel: perf/x86/lbr: Filter vsyscall addresses (CVE-2023-52476)

  - kernel: mm/sparsemem: fix race in accessing memory_section->usage (CVE-2023-52489)

  - kernel: net: fix possible store tearing in neigh_periodic_work() (CVE-2023-52522)

  - kernel: HID: sony: Fix a potential memory leak in sony_probe() (CVE-2023-52529)

  - kernel: team: NULL pointer dereference when team device type is changed (CVE-2023-52574)

  - kernel: net: bridge: data races indata-races in br_handle_frame_finish() (CVE-2023-52578)

  - kernel: net/core: kernel crash in ETH_P_1588 flow dissector (CVE-2023-52580)

  - kernel: netfilter: nf_tables: memory leak when more than 255 elements expired (CVE-2023-52581)

  - kernel: net/sched: act_ct: fix skb leak and crash on ooo frags (CVE-2023-52610)

  - kernel: netfilter: nf_tables: disallow timeout for anonymous sets (CVE-2023-52620)

  - kernel: CIFS Filesystem Decryption Improper Input Validation Remote Code Execution Vulnerability in     function receive_encrypted_standard of client (CVE-2024-0565)

  - kernel: hugetlbfs: Null pointer dereference in hugetlbfs_fill_super function (CVE-2024-0841)

  - kernel: nf_tables: use-after-free vulnerability in the nft_setelem_catchall_deactivate() function     (CVE-2024-1085)

  - kernel: nf_tables: use-after-free vulnerability in the nft_verdict_init() function (CVE-2024-1086)

  - kernel: tls: use-after-free with partial reads and async decrypt (CVE-2024-26582)

  - kernel: tls: race between async notify and socket close (CVE-2024-26583)

  - kernel: tls: handle backlogging of crypto requests (CVE-2024-26584)

  - kernel: tls: race between tx work scheduling and socket close (CVE-2024-26585)

  - kernel: mlxsw: spectrum_acl_tcam: Fix stack corruption (CVE-2024-26586)

  - kernel: i2c: i801: Fix block process call transactions (CVE-2024-26593)

  - kernel: sched/membarrier: reduce the ability to hammer on sys_membarrier (CVE-2024-26602)

  - kernel: netfilter: nf_tables: reject QUEUE/DROP verdict parameters (CVE-2024-26609)

  - kernel: ip6_tunnel: fix NEXTHDR_FRAGMENT handling in ip6_tnl_parse_tlv_enc_lim() (CVE-2024-26633)

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

The remote Redhat Enterprise Linux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2024:2008 advisory.

  - kernel: netfilter: divide error in nft_limit_init (CVE-2021-46915)

  - kernel: use-after-free in smb2_is_status_io_timeout() (CVE-2023-1192)

  - kernel: tun: bugs for oversize packet when napi frags enabled in tun_napi_alloc_frags (CVE-2023-3812)

  - kernel: vmxnet3: NULL pointer dereference in vmxnet3_rq_cleanup() (CVE-2023-4459)

  - kernel: refcount leak in ctnetlink_create_conntrack() (CVE-2023-7192)

  - kernel: mlxsw: spectrum_acl_tcam: Fix stack corruption (CVE-2024-26586)

  - kernel: sched/membarrier: reduce the ability to hammer on sys_membarrier (CVE-2024-26602)

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

The remote Redhat Enterprise Linux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2024:2006 advisory.

  - kernel: netfilter: divide error in nft_limit_init (CVE-2021-46915)

  - kernel: use-after-free in smb2_is_status_io_timeout() (CVE-2023-1192)

  - kernel: tun: bugs for oversize packet when napi frags enabled in tun_napi_alloc_frags (CVE-2023-3812)

  - kernel: vmxnet3: NULL pointer dereference in vmxnet3_rq_cleanup() (CVE-2023-4459)

  - kernel: refcount leak in ctnetlink_create_conntrack() (CVE-2023-7192)

  - kernel: mlxsw: spectrum_acl_tcam: Fix stack corruption (CVE-2024-26586)

  - kernel: sched/membarrier: reduce the ability to hammer on sys_membarrier (CVE-2024-26602)

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

The remote Redhat Enterprise Linux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2024:1882 advisory.

  - kernel: Marvin vulnerability side-channel leakage in the RSA decryption operation (CVE-2023-6240)

  - kernel: tls: use-after-free with partial reads and async decrypt (CVE-2024-26582)

  - kernel: tls: handle backlogging of crypto requests (CVE-2024-26584)

  - kernel: mlxsw: spectrum_acl_tcam: Fix stack corruption (CVE-2024-26586)

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

The remote Redhat Enterprise Linux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2024:1881 advisory.

  - kernel: Marvin vulnerability side-channel leakage in the RSA decryption operation (CVE-2023-6240)

  - kernel: tls: use-after-free with partial reads and async decrypt (CVE-2024-26582)

  - kernel: tls: handle backlogging of crypto requests (CVE-2024-26584)

  - kernel: mlxsw: spectrum_acl_tcam: Fix stack corruption (CVE-2024-26586)

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

The version of kernel installed on the remote host is prior to 5.10.209-198.812. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2KERNEL-5.10-2024-048 advisory.

  - Transmit requests in Xen's virtual network protocol can consist of multiple parts. While not really     useful, except for the initial part any of them may be of zero length, i.e. carry no data at all. Besides     a certain initial portion of the to be transferred data, these parts are directly translated into what     Linux calls SKB fragments. Such converted request parts can, when for a particular SKB they are all of     length zero, lead to a de-reference of NULL in core networking code. (CVE-2023-46838)

  - In the Linux kernel, the following vulnerability has been resolved: uio: Fix use-after-free in uio_open     core-1 core-2 ------------------------------------------------------- uio_unregister_device uio_open idev     = idr_find() device_unregister(&idev->dev) put_device(&idev->dev) uio_device_release     get_device(&idev->dev) kfree(idev) uio_free_minor(minor) uio_release put_device(&idev->dev) kfree(idev)
    ------------------------------------------------------- In the core-1 uio_unregister_device(), the     device_unregister will kfree idev when the idev->dev kobject ref is 1. But after core-1 device_unregister,     put_device and before doing kfree, the core-2 may get_device. Then: 1. After core-1 kfree idev, the core-2     will do use-after-free for idev. 2. When core-2 do uio_release and put_device, the idev will be double     freed. To address this issue, we can get idev atomic & inc idev reference with minor_lock.
    (CVE-2023-52439)

  - In the Linux kernel, the following vulnerability has been resolved: gfs2: Fix kernel NULL pointer     dereference in gfs2_rgrp_dump Syzkaller has reported a NULL pointer dereference when accessing rgd->rd_rgl     in gfs2_rgrp_dump(). This can happen when creating rgd->rd_gl fails in read_rindex_entry(). Add a NULL     pointer check in gfs2_rgrp_dump() to prevent that. (CVE-2023-52448)

  - In the Linux kernel, the following vulnerability has been resolved: bpf: fix check for attempt to corrupt     spilled pointer When register is spilled onto a stack as a 1/2/4-byte register, we set     slot_type[BPF_REG_SIZE - 1] (plus potentially few more below it, depending on actual spill size). So to     check if some stack slot has spilled register we need to consult slot_type[7], not slot_type[0]. To avoid     the need to remember and double-check this in the future, just use is_spilled_reg() helper.
    (CVE-2023-52462)

  - In the Linux kernel, the following vulnerability has been resolved: efivarfs: force RO when remounting if     SetVariable is not supported If SetVariable at runtime is not supported by the firmware we never assign a     callback for that function. At the same time mount the efivarfs as RO so no one can call that. However, we     never check the permission flags when someone remounts the filesystem as RW. As a result this leads to a     crash looking like this: $ mount -o remount,rw /sys/firmware/efi/efivars $ efi-updatevar -f PK.auth PK [     303.279166] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000 [     303.280482] Mem abort info: [ 303.280854] ESR = 0x0000000086000004 [ 303.281338] EC = 0x21: IABT (current     EL), IL = 32 bits [ 303.282016] SET = 0, FnV = 0 [ 303.282414] EA = 0, S1PTW = 0 [ 303.282821] FSC = 0x04:
    level 0 translation fault [ 303.283771] user pgtable: 4k pages, 48-bit VAs, pgdp=000000004258c000 [     303.284913] [0000000000000000] pgd=0000000000000000, p4d=0000000000000000 [ 303.286076] Internal error:
    Oops: 0000000086000004 [#1] PREEMPT SMP [ 303.286936] Modules linked in: qrtr tpm_tis tpm_tis_core     crct10dif_ce arm_smccc_trng rng_core drm fuse ip_tables x_tables ipv6 [ 303.288586] CPU: 1 PID: 755 Comm:
    efi-updatevar Not tainted 6.3.0-rc1-00108-gc7d0c4695c68 #1 [ 303.289748] Hardware name: Unknown Unknown     Product/Unknown Product, BIOS 2023.04-00627-g88336918701d 04/01/2023 [ 303.291150] pstate: 60400005 (nZCv     daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 303.292123] pc : 0x0 [ 303.292443] lr :
    efivar_set_variable_locked+0x74/0xec [ 303.293156] sp : ffff800008673c10 [ 303.293619] x29:
    ffff800008673c10 x28: ffff0000037e8000 x27: 0000000000000000 [ 303.294592] x26: 0000000000000800 x25:
    ffff000002467400 x24: 0000000000000027 [ 303.295572] x23: ffffd49ea9832000 x22: ffff0000020c9800 x21:
    ffff000002467000 [ 303.296566] x20: 0000000000000001 x19: 00000000000007fc x18: 0000000000000000 [     303.297531] x17: 0000000000000000 x16: 0000000000000000 x15: 0000aaaac807ab54 [ 303.298495] x14:
    ed37489f673633c0 x13: 71c45c606de13f80 x12: 47464259e219acf4 [ 303.299453] x11: ffff000002af7b01 x10:
    0000000000000003 x9 : 0000000000000002 [ 303.300431] x8 : 0000000000000010 x7 : ffffd49ea8973230 x6 :
    0000000000a85201 [ 303.301412] x5 : 0000000000000000 x4 : ffff0000020c9800 x3 : 00000000000007fc [     303.302370] x2 : 0000000000000027 x1 : ffff000002467400 x0 : ffff000002467000 [ 303.303341] Call trace: [     303.303679] 0x0 [ 303.303938] efivar_entry_set_get_size+0x98/0x16c [ 303.304585]     efivarfs_file_write+0xd0/0x1a4 [ 303.305148] vfs_write+0xc4/0x2e4 [ 303.305601] ksys_write+0x70/0x104 [     303.306073] __arm64_sys_write+0x1c/0x28 [ 303.306622] invoke_syscall+0x48/0x114 [ 303.307156]     el0_svc_common.constprop.0+0x44/0xec [ 303.307803] do_el0_svc+0x38/0x98 [ 303.308268] el0_svc+0x2c/0x84 [     303.308702] el0t_64_sync_handler+0xf4/0x120 [ 303.309293] el0t_64_sync+0x190/0x194 [ 303.309794] Code:
    ???????? ???????? ???????? ???????? (????????) [ 303.310612] ---[ end trace 0000000000000000 ]--- Fix this     by adding a .reconfigure() function to the fs operations which we can use to check the requested flags and     deny anything that's not RO if the firmware doesn't implement SetVariable at runtime. (CVE-2023-52463)

  - In the Linux kernel, the following vulnerability has been resolved: mfd: syscon: Fix null pointer     dereference in of_syscon_register() kasprintf() returns a pointer to dynamically allocated memory which     can be NULL upon failure. (CVE-2023-52467)

  - In the Linux kernel, the following vulnerability has been resolved: drivers/amd/pm: fix a use-after-free     in kv_parse_power_table When ps allocated by kzalloc equals to NULL, kv_parse_power_table frees     adev->pm.dpm.ps that allocated before. However, after the control flow goes through the following call     chains: kv_parse_power_table |-> kv_dpm_init |-> kv_dpm_sw_init |-> kv_dpm_fini The adev->pm.dpm.ps is     used in the for loop of kv_dpm_fini after its first free in kv_parse_power_table and causes a use-after-     free bug. (CVE-2023-52469)

  - An out-of-bounds access vulnerability involving netfilter was reported and fixed as: f1082dd31fe4     (netfilter: nf_tables: Reject tables of unsupported family); While creating a new netfilter table, lack of     a safeguard against invalid nf_tables family (pf) values within `nf_tables_newtable` function enables an     attacker to achieve out-of-bounds access. (CVE-2023-6040)

  - A Null pointer dereference problem was found in ida_free in lib/idr.c in the Linux Kernel. This issue may     allow an attacker using this library to cause a denial of service problem due to a missing check at a     function return. (CVE-2023-6915)

  - An out-of-bounds memory read flaw was found in receive_encrypted_standard in fs/smb/client/smb2ops.c in     the SMB Client sub-component in the Linux Kernel. This issue occurs due to integer underflow on the memcpy     length, leading to a denial of service. (CVE-2024-0565)

  - A flaw was found in the Netfilter subsystem in the Linux kernel. The issue is in the nft_byteorder_eval()     function, where the code iterates through a loop and writes to the `dst` array. On each iteration, 8 bytes     are written, but `dst` is an array of u32, so each element only has space for 4 bytes. That means every     iteration overwrites part of the previous element corrupting this array of u32. This flaw allows a local     user to cause a denial of service or potentially break NetFilter functionality. (CVE-2024-0607)

  - An out-of-bounds memory write flaw was found in the Linux kernel's Transport Layer Security functionality     in how a user calls a function splice with a ktls socket as the destination. This flaw allows a local user     to crash or potentially escalate their privileges on the system. (CVE-2024-0646)

  - In rds_recv_track_latency in net/rds/af_rds.c in the Linux kernel through 6.7.1, there is an off-by-one     error for an RDS_MSG_RX_DGRAM_TRACE_MAX comparison, resulting in out-of-bounds access. (CVE-2024-23849)

  - In the Linux kernel, the following vulnerability has been resolved: mlxsw: spectrum_acl_tcam: Fix stack     corruption When tc filters are first added to a net device, the corresponding local port gets bound to an     ACL group in the device. The group contains a list of ACLs. In turn, each ACL points to a different TCAM     region where the filters are stored. During forwarding, the ACLs are sequentially evaluated until a match     is found. One reason to place filters in different regions is when they are added with decreasing     priorities and in an alternating order so that two consecutive filters can never fit in the same region     because of their key usage. In Spectrum-2 and newer ASICs the firmware started to report that the maximum     number of ACLs in a group is more than 16, but the layout of the register that configures ACL groups     (PAGT) was not updated to account for that. It is therefore possible to hit stack corruption [1] in the     rare case where more than 16 ACLs in a group are required. Fix by limiting the maximum ACL group size to     the minimum between what the firmware reports and the maximum ACLs that fit in the PAGT register. Add a     test case to make sure the machine does not crash when this condition is hit. [1] Kernel panic - not     syncing: stack-protector: Kernel stack is corrupted in: mlxsw_sp_acl_tcam_group_update+0x116/0x120 [...]     dump_stack_lvl+0x36/0x50 panic+0x305/0x330 __stack_chk_fail+0x15/0x20     mlxsw_sp_acl_tcam_group_update+0x116/0x120 mlxsw_sp_acl_tcam_group_region_attach+0x69/0x110     mlxsw_sp_acl_tcam_vchunk_get+0x492/0xa20 mlxsw_sp_acl_tcam_ventry_add+0x25/0xe0     mlxsw_sp_acl_rule_add+0x47/0x240 mlxsw_sp_flower_replace+0x1a9/0x1d0 tc_setup_cb_add+0xdc/0x1c0     fl_hw_replace_filter+0x146/0x1f0 fl_change+0xc17/0x1360 tc_new_tfilter+0x472/0xb90     rtnetlink_rcv_msg+0x313/0x3b0 netlink_rcv_skb+0x58/0x100 netlink_unicast+0x244/0x390     netlink_sendmsg+0x1e4/0x440 ____sys_sendmsg+0x164/0x260 ___sys_sendmsg+0x9a/0xe0 __sys_sendmsg+0x7a/0xc0     do_syscall_64+0x40/0xe0 entry_SYSCALL_64_after_hwframe+0x63/0x6b (CVE-2024-26586)

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

The version of kernel installed on the remote host is prior to 5.15.148-97.158. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2KERNEL-5.15-2024-036 advisory.

  - Transmit requests in Xen's virtual network protocol can consist of multiple parts. While not really     useful, except for the initial part any of them may be of zero length, i.e. carry no data at all. Besides     a certain initial portion of the to be transferred data, these parts are directly translated into what     Linux calls SKB fragments. Such converted request parts can, when for a particular SKB they are all of     length zero, lead to a de-reference of NULL in core networking code. (CVE-2023-46838)

  - In the Linux kernel, the following vulnerability has been resolved: uio: Fix use-after-free in uio_open     core-1 core-2 ------------------------------------------------------- uio_unregister_device uio_open idev     = idr_find() device_unregister(&idev->dev) put_device(&idev->dev) uio_device_release     get_device(&idev->dev) kfree(idev) uio_free_minor(minor) uio_release put_device(&idev->dev) kfree(idev)
    ------------------------------------------------------- In the core-1 uio_unregister_device(), the     device_unregister will kfree idev when the idev->dev kobject ref is 1. But after core-1 device_unregister,     put_device and before doing kfree, the core-2 may get_device. Then: 1. After core-1 kfree idev, the core-2     will do use-after-free for idev. 2. When core-2 do uio_release and put_device, the idev will be double     freed. To address this issue, we can get idev atomic & inc idev reference with minor_lock.
    (CVE-2023-52439)

  - In the Linux kernel, the following vulnerability has been resolved: bpf: fix check for attempt to corrupt     spilled pointer When register is spilled onto a stack as a 1/2/4-byte register, we set     slot_type[BPF_REG_SIZE - 1] (plus potentially few more below it, depending on actual spill size). So to     check if some stack slot has spilled register we need to consult slot_type[7], not slot_type[0]. To avoid     the need to remember and double-check this in the future, just use is_spilled_reg() helper.
    (CVE-2023-52462)

  - In the Linux kernel, the following vulnerability has been resolved: efivarfs: force RO when remounting if     SetVariable is not supported If SetVariable at runtime is not supported by the firmware we never assign a     callback for that function. At the same time mount the efivarfs as RO so no one can call that. However, we     never check the permission flags when someone remounts the filesystem as RW. As a result this leads to a     crash looking like this: $ mount -o remount,rw /sys/firmware/efi/efivars $ efi-updatevar -f PK.auth PK [     303.279166] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000 [     303.280482] Mem abort info: [ 303.280854] ESR = 0x0000000086000004 [ 303.281338] EC = 0x21: IABT (current     EL), IL = 32 bits [ 303.282016] SET = 0, FnV = 0 [ 303.282414] EA = 0, S1PTW = 0 [ 303.282821] FSC = 0x04:
    level 0 translation fault [ 303.283771] user pgtable: 4k pages, 48-bit VAs, pgdp=000000004258c000 [     303.284913] [0000000000000000] pgd=0000000000000000, p4d=0000000000000000 [ 303.286076] Internal error:
    Oops: 0000000086000004 [#1] PREEMPT SMP [ 303.286936] Modules linked in: qrtr tpm_tis tpm_tis_core     crct10dif_ce arm_smccc_trng rng_core drm fuse ip_tables x_tables ipv6 [ 303.288586] CPU: 1 PID: 755 Comm:
    efi-updatevar Not tainted 6.3.0-rc1-00108-gc7d0c4695c68 #1 [ 303.289748] Hardware name: Unknown Unknown     Product/Unknown Product, BIOS 2023.04-00627-g88336918701d 04/01/2023 [ 303.291150] pstate: 60400005 (nZCv     daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 303.292123] pc : 0x0 [ 303.292443] lr :
    efivar_set_variable_locked+0x74/0xec [ 303.293156] sp : ffff800008673c10 [ 303.293619] x29:
    ffff800008673c10 x28: ffff0000037e8000 x27: 0000000000000000 [ 303.294592] x26: 0000000000000800 x25:
    ffff000002467400 x24: 0000000000000027 [ 303.295572] x23: ffffd49ea9832000 x22: ffff0000020c9800 x21:
    ffff000002467000 [ 303.296566] x20: 0000000000000001 x19: 00000000000007fc x18: 0000000000000000 [     303.297531] x17: 0000000000000000 x16: 0000000000000000 x15: 0000aaaac807ab54 [ 303.298495] x14:
    ed37489f673633c0 x13: 71c45c606de13f80 x12: 47464259e219acf4 [ 303.299453] x11: ffff000002af7b01 x10:
    0000000000000003 x9 : 0000000000000002 [ 303.300431] x8 : 0000000000000010 x7 : ffffd49ea8973230 x6 :
    0000000000a85201 [ 303.301412] x5 : 0000000000000000 x4 : ffff0000020c9800 x3 : 00000000000007fc [     303.302370] x2 : 0000000000000027 x1 : ffff000002467400 x0 : ffff000002467000 [ 303.303341] Call trace: [     303.303679] 0x0 [ 303.303938] efivar_entry_set_get_size+0x98/0x16c [ 303.304585]     efivarfs_file_write+0xd0/0x1a4 [ 303.305148] vfs_write+0xc4/0x2e4 [ 303.305601] ksys_write+0x70/0x104 [     303.306073] __arm64_sys_write+0x1c/0x28 [ 303.306622] invoke_syscall+0x48/0x114 [ 303.307156]     el0_svc_common.constprop.0+0x44/0xec [ 303.307803] do_el0_svc+0x38/0x98 [ 303.308268] el0_svc+0x2c/0x84 [     303.308702] el0t_64_sync_handler+0xf4/0x120 [ 303.309293] el0t_64_sync+0x190/0x194 [ 303.309794] Code:
    ???????? ???????? ???????? ???????? (????????) [ 303.310612] ---[ end trace 0000000000000000 ]--- Fix this     by adding a .reconfigure() function to the fs operations which we can use to check the requested flags and     deny anything that's not RO if the firmware doesn't implement SetVariable at runtime. (CVE-2023-52463)

  - In the Linux kernel, the following vulnerability has been resolved: mfd: syscon: Fix null pointer     dereference in of_syscon_register() kasprintf() returns a pointer to dynamically allocated memory which     can be NULL upon failure. (CVE-2023-52467)

  - An out-of-bounds access vulnerability involving netfilter was reported and fixed as: f1082dd31fe4     (netfilter: nf_tables: Reject tables of unsupported family); While creating a new netfilter table, lack of     a safeguard against invalid nf_tables family (pf) values within `nf_tables_newtable` function enables an     attacker to achieve out-of-bounds access. (CVE-2023-6040)

  - A Null pointer dereference problem was found in ida_free in lib/idr.c in the Linux Kernel. This issue may     allow an attacker using this library to cause a denial of service problem due to a missing check at a     function return. (CVE-2023-6915)

  - An out-of-bounds memory read flaw was found in receive_encrypted_standard in fs/smb/client/smb2ops.c in     the SMB Client sub-component in the Linux Kernel. This issue occurs due to integer underflow on the memcpy     length, leading to a denial of service. (CVE-2024-0565)

  - An out-of-bounds memory write flaw was found in the Linux kernel's Transport Layer Security functionality     in how a user calls a function splice with a ktls socket as the destination. This flaw allows a local user     to crash or potentially escalate their privileges on the system. (CVE-2024-0646)

  - A use-after-free vulnerability in the Linux kernel's netfilter: nf_tables component can be exploited to     achieve local privilege escalation. The nft_setelem_catchall_deactivate() function checks whether the     catch-all set element is active in the current generation instead of the next generation before freeing     it, but only flags it inactive in the next generation, making it possible to free the element multiple     times, leading to a double free vulnerability. We recommend upgrading past commit     b1db244ffd041a49ecc9618e8feb6b5c1afcdaa7. (CVE-2024-1085)

  - In the Linux kernel, the following vulnerability has been resolved: mlxsw: spectrum_acl_tcam: Fix stack     corruption When tc filters are first added to a net device, the corresponding local port gets bound to an     ACL group in the device. The group contains a list of ACLs. In turn, each ACL points to a different TCAM     region where the filters are stored. During forwarding, the ACLs are sequentially evaluated until a match     is found. One reason to place filters in different regions is when they are added with decreasing     priorities and in an alternating order so that two consecutive filters can never fit in the same region     because of their key usage. In Spectrum-2 and newer ASICs the firmware started to report that the maximum     number of ACLs in a group is more than 16, but the layout of the register that configures ACL groups     (PAGT) was not updated to account for that. It is therefore possible to hit stack corruption [1] in the     rare case where more than 16 ACLs in a group are required. Fix by limiting the maximum ACL group size to     the minimum between what the firmware reports and the maximum ACLs that fit in the PAGT register. Add a     test case to make sure the machine does not crash when this condition is hit. [1] Kernel panic - not     syncing: stack-protector: Kernel stack is corrupted in: mlxsw_sp_acl_tcam_group_update+0x116/0x120 [...]     dump_stack_lvl+0x36/0x50 panic+0x305/0x330 __stack_chk_fail+0x15/0x20     mlxsw_sp_acl_tcam_group_update+0x116/0x120 mlxsw_sp_acl_tcam_group_region_attach+0x69/0x110     mlxsw_sp_acl_tcam_vchunk_get+0x492/0xa20 mlxsw_sp_acl_tcam_ventry_add+0x25/0xe0     mlxsw_sp_acl_rule_add+0x47/0x240 mlxsw_sp_flower_replace+0x1a9/0x1d0 tc_setup_cb_add+0xdc/0x1c0     fl_hw_replace_filter+0x146/0x1f0 fl_change+0xc17/0x1360 tc_new_tfilter+0x472/0xb90     rtnetlink_rcv_msg+0x313/0x3b0 netlink_rcv_skb+0x58/0x100 netlink_unicast+0x244/0x390     netlink_sendmsg+0x1e4/0x440 ____sys_sendmsg+0x164/0x260 ___sys_sendmsg+0x9a/0xe0 __sys_sendmsg+0x7a/0xc0     do_syscall_64+0x40/0xe0 entry_SYSCALL_64_after_hwframe+0x63/0x6b (CVE-2024-26586)

  - In the Linux kernel, the following vulnerability has been resolved: bpf: Fix re-attachment branch in     bpf_tracing_prog_attach The following case can cause a crash due to missing attach_btf: 1) load rawtp     program 2) load fentry program with rawtp as target_fd 3) create tracing link for fentry program with     target_fd = 0 4) repeat 3 In the end we have: - prog->aux->dst_trampoline == NULL - tgt_prog == NULL     (because we did not provide target_fd to link_create) - prog->aux->attach_btf == NULL (the program was     loaded with attach_prog_fd=X) - the program was loaded for tgt_prog but we have no way to find out which     one BUG: kernel NULL pointer dereference, address: 0000000000000058 Call Trace: <TASK> ? __die+0x20/0x70 ?     page_fault_oops+0x15b/0x430 ? fixup_exception+0x22/0x330 ? exc_page_fault+0x6f/0x170 ?     asm_exc_page_fault+0x22/0x30 ? bpf_tracing_prog_attach+0x279/0x560 ? btf_obj_id+0x5/0x10     bpf_tracing_prog_attach+0x439/0x560 __sys_bpf+0x1cf4/0x2de0 __x64_sys_bpf+0x1c/0x30     do_syscall_64+0x41/0xf0 entry_SYSCALL_64_after_hwframe+0x6e/0x76 Return -EINVAL in this situation.
    (CVE-2024-26591)

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

ID	Name	Product	Family	Severity
197523	Amazon Linux 2 : kernel (ALASKERNEL-5.4-2024-065)	Nessus	Amazon Linux Local Security Checks	high
195267	EulerOS 2.0 SP10 : kernel (EulerOS-SA-2024-1592)	Nessus	Huawei Local Security Checks	high
195118	Ubuntu 22.04 LTS : Linux kernel (OEM) vulnerabilities (USN-6765-1)	Nessus	Ubuntu Local Security Checks	high
195036	Oracle Linux 9 : kernel (ELSA-2024-2394)	Nessus	Oracle Linux Local Security Checks	critical
194946	RHEL 8 : kernel (RHSA-2024:2674)	Nessus	Red Hat Local Security Checks	medium
194841	RHEL 8 : kernel (RHSA-2024:2582)	Nessus	Red Hat Local Security Checks	high
194836	RHEL 8 : kernel-rt (RHSA-2024:2585)	Nessus	Red Hat Local Security Checks	high
194794	RHEL 9 : kernel (RHSA-2024:2394)	Nessus	Red Hat Local Security Checks	critical
193786	RHEL 8 : kernel-rt (RHSA-2024:2008)	Nessus	Red Hat Local Security Checks	high
193784	RHEL 8 : kernel (RHSA-2024:2006)	Nessus	Red Hat Local Security Checks	high
193475	RHEL 9 : kernel-rt (RHSA-2024:1882)	Nessus	Red Hat Local Security Checks	high
193474	RHEL 9 : kernel (RHSA-2024:1881)	Nessus	Red Hat Local Security Checks	high
193375	Ubuntu 20.04 LTS / 22.04 LTS : Linux kernel (AWS) vulnerabilities (USN-6725-2)	Nessus	Ubuntu Local Security Checks	critical
193309	Debian dsa-5658 : affs-modules-6.1.0-11-4kc-malta-di - security update	Nessus	Debian Local Security Checks	high
193084	Ubuntu 20.04 LTS / 22.04 LTS : Linux kernel vulnerabilities (USN-6725-1)	Nessus	Ubuntu Local Security Checks	critical
192490	SUSE SLES15 Security Update : kernel (SUSE-SU-2024:0977-1)	Nessus	SuSE Local Security Checks	high
192487	SUSE SLES15 Security Update : kernel (SUSE-SU-2024:0926-1)	Nessus	SuSE Local Security Checks	high
192180	SUSE SLES15 / openSUSE 15 Security Update : kernel (SUSE-SU-2024:0910-1)	Nessus	SuSE Local Security Checks	high
192178	SUSE SLES15 Security Update : kernel (SUSE-SU-2024:0900-2)	Nessus	SuSE Local Security Checks	high
192141	SUSE SLES15 Security Update : kernel (SUSE-SU-2024:0900-1)	Nessus	SuSE Local Security Checks	high
192014	SUSE SLES15 Security Update : kernel (SUSE-SU-2024:0857-1)	Nessus	SuSE Local Security Checks	high
192011	SUSE SLED15 / SLES15 / openSUSE 15 Security Update : kernel (SUSE-SU-2024:0858-1)	Nessus	SuSE Local Security Checks	high
192006	SUSE SLES15 / openSUSE 15 Security Update : kernel (SUSE-SU-2024:0855-1)	Nessus	SuSE Local Security Checks	high
190029	Amazon Linux 2 : kernel (ALASKERNEL-5.10-2024-048)	Nessus	Amazon Linux Local Security Checks	high
190021	Amazon Linux 2 : kernel (ALASKERNEL-5.15-2024-036)	Nessus	Amazon Linux Local Security Checks	high

Detections

Analytics

CVE-2024-26586

medium

Tenable Plugins

high

high

high

critical

medium

high

high

critical

high

high

high

high

critical

high

critical

high

high

high

high

high

high

high

high

high

high