In the Linux kernel, the following vulnerability has been resolved: pnode: terminate at peers of source The propagate_mnt() function handles mount propagation when creating mounts and propagates the source mount tree @source_mnt to all applicable nodes of the destination propagation mount tree headed by @dest_mnt. Unfortunately it contains a bug where it fails to terminate at peers of @source_mnt when looking up copies of the source mount that become masters for copies of the source mount tree mounted on top of slaves in the destination propagation tree causing a NULL dereference. Once the mechanics of the bug are understood it's easy to trigger. Because of unprivileged user namespaces it is available to unprivileged users. While fixing this bug we've gotten confused multiple times due to unclear terminology or missing concepts. So let's start this with some clarifications: * The terms "master" or "peer" denote a shared mount. A shared mount belongs to a peer group. * A peer group is a set of shared mounts that propagate to each other. They are identified by a peer group id. The peer group id is available in @shared_mnt->mnt_group_id. Shared mounts within the same peer group have the same peer group id. The peers in a peer group can be reached via @shared_mnt->mnt_share. * The terms "slave mount" or "dependent mount" denote a mount that receives propagation from a peer in a peer group. IOW, shared mounts may have slave mounts and slave mounts have shared mounts as their master. Slave mounts of a given peer in a peer group are listed on that peers slave list available at @shared_mnt->mnt_slave_list. * The term "master mount" denotes a mount in a peer group. IOW, it denotes a shared mount or a peer mount in a peer group. The term "master mount" - or "master" for short - is mostly used when talking in the context of slave mounts that receive propagation from a master mount. A master mount of a slave identifies the closest peer group a slave mount receives propagation from. The master mount of a slave can be identified via @slave_mount->mnt_master. Different slaves may point to different masters in the same peer group. * Multiple peers in a peer group can have non-empty ->mnt_slave_lists. Non-empty ->mnt_slave_lists of peers don't intersect. Consequently, to ensure all slave mounts of a peer group are visited the ->mnt_slave_lists of all peers in a peer group have to be walked. * Slave mounts point to a peer in the closest peer group they receive propagation from via @slave_mnt->mnt_master (see above). Together with these peers they form a propagation group (see below). The closest peer group can thus be identified through the peer group id @slave_mnt->mnt_master->mnt_group_id of the peer/master that a slave mount receives propagation from. * A shared-slave mount is a slave mount to a peer group pg1 while also a peer in another peer group pg2. IOW, a peer group may receive propagation from another peer group. If a peer group pg1 is a slave to another peer group pg2 then all peers in peer group pg1 point to the same peer in peer group pg2 via ->mnt_master. IOW, all peers in peer group pg1 appear on the same ->mnt_slave_list. IOW, they cannot be slaves to different peer groups. * A pure slave mount is a slave mount that is a slave to a peer group but is not a peer in another peer group. * A propagation group denotes the set of mounts consisting of a single peer group pg1 and all slave mounts and shared-slave mounts that point to a peer in that peer group via ->mnt_master. IOW, all slave mounts such that @slave_mnt->mnt_master->mnt_group_id is equal to @shared_mnt->mnt_group_id. The concept of a propagation group makes it easier to talk about a single propagation level in a propagation tree. For example, in propagate_mnt() the immediate peers of @dest_mnt and all slaves of @dest_mnt's peer group form a propagation group pr ---truncated---

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - pnode: terminate at peers of source The propagate_mnt() function handles mount propagation when creating     mounts and propagates the source mount tree @source_mnt to all applicable nodes of the destination     propagation mount tree headed by @dest_mnt. Unfortunately it contains a bug where it fails to terminate at     peers of @source_mnt when looking up copies of the source mount that become masters for copies of the     source mount tree mounted on top of slaves in the destination propagation tree causing a NULL dereference.
    Once the mechanics of the bug are understood it's easy to trigger. Because of unprivileged user namespaces     it is available to unprivileged users. While fixing this bug we've gotten confused multiple times due to     unclear terminology or missing concepts. So let's start this with some clarifications: * The terms     master or peer denote a shared mount. A shared mount belongs to a peer group. * A peer group is a set     of shared mounts that propagate to each other. They are identified by a peer group id. The peer group id     is available in @shared_mnt->mnt_group_id. Shared mounts within the same peer group have the same peer     group id. The peers in a peer group can be reached via @shared_mnt->mnt_share. * The terms slave mount     or dependent mount denote a mount that receives propagation from a peer in a peer group. IOW, shared     mounts may have slave mounts and slave mounts have shared mounts as their master. Slave mounts of a given     peer in a peer group are listed on that peers slave list available at @shared_mnt->mnt_slave_list. * The     term master mount denotes a mount in a peer group. IOW, it denotes a shared mount or a peer mount in a     peer group. The term master mount - or master for short - is mostly used when talking in the context     of slave mounts that receive propagation from a master mount. A master mount of a slave identifies the     closest peer group a slave mount receives propagation from. The master mount of a slave can be identified     via @slave_mount->mnt_master. Different slaves may point to different masters in the same peer group. *     Multiple peers in a peer group can have non-empty ->mnt_slave_lists. Non-empty ->mnt_slave_lists of peers     don't intersect. Consequently, to ensure all slave mounts of a peer group are visited the
    ->mnt_slave_lists of all peers in a peer group have to be walked. * Slave mounts point to a peer in the     closest peer group they receive propagation from via @slave_mnt->mnt_master (see above). Together with     these peers they form a propagation group (see below). The closest peer group can thus be identified     through the peer group id @slave_mnt->mnt_master->mnt_group_id of the peer/master that a slave mount     receives propagation from. * A shared-slave mount is a slave mount to a peer group pg1 while also a peer     in another peer group pg2. IOW, a peer group may receive propagation from another peer group. If a peer     group pg1 is a slave to another peer group pg2 then all peers in peer group pg1 point to the same peer in     peer group pg2 via ->mnt_master. IOW, all peers in peer group pg1 appear on the same ->mnt_slave_list.
    IOW, they cannot be slaves to different peer groups. * A pure slave mount is a slave mount that is a slave     to a peer group but is not a peer in another peer group. * A propagation group denotes the set of mounts     consisting of a single peer group pg1 and all slave mounts and shared-slave mounts that point to a peer in     that peer group via ->mnt_master. IOW, all slave mounts such that @slave_mnt->mnt_master->mnt_group_id is     equal to @shared_mnt->mnt_group_id. The concept of a propagation group makes it easier to talk about a     single propagation level in a propagation tree. For example, in propagate_mnt() the immediate peers of     @dest_mnt and all slaves of @dest_mnt's peer group form a propagation group pr ---truncated---     (CVE-2022-50280)

Note that Nessus relies on the presence of the package as reported by the vendor.

The version of kernel installed on the remote host is prior to 5.4.231-137.341. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2KERNEL-5.4-2023-042 advisory.

    A flaw was found in the Linux kernel's Layer 2 Tunneling Protocol (L2TP). A missing lock when clearing     sk_user_data can lead to a race condition and NULL pointer dereference. A local user could use this flaw     to potentially crash the system causing a denial of service. (CVE-2022-4129)

    In the Linux kernel before 6.1.6, a NULL pointer dereference bug in the traffic control subsystem allows     an unprivileged user to trigger a denial of service (system crash) via a crafted traffic control     configuration that is set up with tc qdisc and tc class commands. This affects qdisc_graft in     net/sched/sch_api.c. (CVE-2022-47929)

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

    udf: Fix preallocation discarding at indirect extent boundary (CVE-2022-48946)

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

    igb: Initialize mailbox message for VF reset (CVE-2022-48949)

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

    perf/x86/amd: fix potential integer overflow on shift of a int (CVE-2022-49748)

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

    dmaengine: Fix double increment of client_count in dma_chan_get() (CVE-2022-49753)

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

    igb: Do not free q_vector unless new one was allocated (CVE-2022-50252)

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

    power: supply: fix null pointer dereferencing in power_supply_get_battery_info (CVE-2022-50276)

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

    pnode: terminate at peers of source (CVE-2022-50280)

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

    chardev: fix error handling in cdev_device_add() (CVE-2022-50282)

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

    qlcnic: prevent ->dcb use-after-free on qlcnic_dcb_enable() failure (CVE-2022-50288)

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

    fs: jfs: fix shift-out-of-bounds in dbDiscardAG (CVE-2022-50333)

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

    hugetlbfs: fix null-ptr-deref in hugetlbfs_parse_param() (CVE-2022-50334)

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

    cifs: fix oops during encryption (CVE-2022-50341)

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

    ext4: init quota for 'old.inode' in 'ext4_rename' (CVE-2022-50346)

    The Linux kernel does not correctly mitigate SMT attacks, as discovered through a strange pattern in the     kernel API using STIBP as a mitigation, leaving the process exposed for a short period of time after a     syscall. The kernel also does not issue an IBPB immediately during the syscall. (CVE-2023-0045)

    A NULL pointer dereference flaw was found in rawv6_push_pending_frames in net/ipv6/raw.c in the network     subcomponent in the Linux kernel. This flaw causes the system to crash. (CVE-2023-0394)

    Detected a few exploitable gadgets that could leak secret memory through a side-channel such as MDS as     well as insufficient hardening of the usercopy functions against spectre-v1. (CVE-2023-0459)

    There is a use-after-free vulnerability in the Linux Kernel which can be exploited to achieve local     privilege escalation. To reach the vulnerability kernel configuration flag CONFIG_TLS or     CONFIG_XFRM_ESPINTCP has to be configured, but the operation does not require any privilege.

    There is a use-after-free bug of icsk_ulp_data of a struct inet_connection_sock.

    When CONFIG_TLS is enabled, user can install a tls context (struct tls_context) on a connected tcp socket.
    The context is not cleared if this socket is disconnected and reused as a listener. If a new socket is     created from the listener, the context is inherited and vulnerable.

    The setsockopt TCP_ULP operation does not require any privilege.

    We recommend upgrading past commit 2c02d41d71f90a5168391b6a5f2954112ba2307c (CVE-2023-0461)

    A memory corruption flaw was found in the Linux kernel's human interface device (HID) subsystem in how a     user inserts a malicious USB device. This flaw allows a local user to crash or potentially escalate their     privileges on the system. (CVE-2023-1073)

    cbq_classify in net/sched/sch_cbq.c in the Linux kernel through 6.1.4 allows attackers to cause a denial     of service (slab-out-of-bounds read) because of type confusion (non-negative numbers can sometimes     indicate a TC_ACT_SHOT condition rather than valid classification results). (CVE-2023-23454)

    atm_tc_enqueue in net/sched/sch_atm.c in the Linux kernel through 6.1.4 allows attackers to cause a denial     of service because of type confusion (non-negative numbers can sometimes indicate a TC_ACT_SHOT condition     rather than valid classification results). (CVE-2023-23455)

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

    net/sched: act_mpls: Fix warning during failed attribute validation (CVE-2023-52906)

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

    bpf: Skip task with pid=1 in send_signal_common() (CVE-2023-52992)

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

    x86/i8259: Mark legacy PIC interrupts with IRQ_LEVEL (CVE-2023-52993)

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

    ipv4: prevent potential spectre v1 gadget in fib_metrics_match() (CVE-2023-52996)

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

    ipv4: prevent potential spectre v1 gadget in ip_metrics_convert() (CVE-2023-52997)

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

    net: fix UaF in netns ops registration error path (CVE-2023-52999)

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

    netlink: prevent potential spectre v1 gadgets (CVE-2023-53000)

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

    cifs: Fix oops due to uncleared server->smbd_conn in reconnect (CVE-2023-53006)

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

    tracing: Make sure trace_printk() can output as soon as it can be used (CVE-2023-53007)

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

    HID: betop: check shape of output reports (CVE-2023-53015)

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

    net: mdio: validate parameter addr in mdiobus_get_phy() (CVE-2023-53019)

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

    net/sched: sch_taprio: fix possible use-after-free (CVE-2023-53021)

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

    bpf: Fix pointer-leak due to insufficient speculative store bypass mitigation (CVE-2023-53024)

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

    RDMA/core: Fix ib block iterator counter overflow (CVE-2023-53026)

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

    netfilter: ipset: Fix overflow before widen in the bitmap_ip_create() function. (CVE-2023-53032)

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.

The version of kernel installed on the remote host is prior to 4.14.304-226.531. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2-2023-1932 advisory.

    Guests can trigger NIC interface reset/abort/crash via netback It is possible for a guest to trigger a NIC     interface reset/abort/crash in a Linux based network backend by sending certain kinds of packets. It     appears to be an (unwritten?) assumption in the rest of the Linux network stack that packet protocol     headers are all contained within the linear section of the SKB and some NICs behave badly if this is not     the case. This has been reported to occur with Cisco (enic) and Broadcom NetXtrem II BCM5780 (bnx2x)     though it may be an issue with other NICs/drivers as well. In case the frontend is sending requests with     split headers, netback will forward those violating above mentioned assumption to the networking core,     resulting in said misbehavior. (CVE-2022-3643)

    Guests can trigger deadlock in Linux netback driver T[his CNA information record relates to multiple CVEs;
    the text explains which aspects/vulnerabilities correspond to which CVE.] The patch for XSA-392 introduced     another issue which might result in a deadlock when trying to free the SKB of a packet dropped due to the     XSA-392 handling (CVE-2022-42328). Additionally when dropping packages for other reasons the same deadlock     could occur in case of netpoll being active for the interface the xen-netback driver is connected to     (CVE-2022-42329). (CVE-2022-42328)

    Guests can trigger deadlock in Linux netback driver T[his CNA information record relates to multiple CVEs;
    the text explains which aspects/vulnerabilities correspond to which CVE.] The patch for XSA-392 introduced     another issue which might result in a deadlock when trying to free the SKB of a packet dropped due to the     XSA-392 handling (CVE-2022-42328). Additionally when dropping packages for other reasons the same deadlock     could occur in case of netpoll being active for the interface the xen-netback driver is connected to     (CVE-2022-42329). (CVE-2022-42329)

    An issue was discovered in the Linux kernel through 6.0.10. l2cap_config_req in net/bluetooth/l2cap_core.c     has an integer wraparound via L2CAP_CONF_REQ packets. (CVE-2022-45934)

    In the Linux kernel before 6.1.6, a NULL pointer dereference bug in the traffic control subsystem allows     an unprivileged user to trigger a denial of service (system crash) via a crafted traffic control     configuration that is set up with tc qdisc and tc class commands. This affects qdisc_graft in     net/sched/sch_api.c. (CVE-2022-47929)

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

    udf: Fix preallocation discarding at indirect extent boundary (CVE-2022-48946)

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

    Bluetooth: L2CAP: Fix u8 overflow (CVE-2022-48947)

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

    igb: Initialize mailbox message for VF reset (CVE-2022-48949)

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

    ipv6: avoid use-after-free in ip6_fragment() (CVE-2022-48956)

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

    mac802154: fix missing INIT_LIST_HEAD in ieee802154_if_add() (CVE-2022-48972)

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

    HID: core: fix shift-out-of-bounds in hid_report_raw_event (CVE-2022-48978)

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

    media: v4l2-dv-timings.c: fix too strict blanking sanity checks (CVE-2022-48987)

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

    memcg: fix possible use-after-free in memcg_write_event_control() (CVE-2022-48988)

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

    mm/khugepaged: invoke MMU notifiers in shmem/file collapse paths (CVE-2022-48991)

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

    igb: Do not free q_vector unless new one was allocated (CVE-2022-50252)

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

    pnode: terminate at peers of source (CVE-2022-50280)

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

    chardev: fix error handling in cdev_device_add() (CVE-2022-50282)

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

    fs: jfs: fix shift-out-of-bounds in dbDiscardAG (CVE-2022-50333)

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

    ext4: init quota for 'old.inode' in 'ext4_rename' (CVE-2022-50346)

    The Linux kernel does not correctly mitigate SMT attacks, as discovered through a strange pattern in the     kernel API using STIBP as a mitigation, leaving the process exposed for a short period of time after a     syscall. The kernel also does not issue an IBPB immediately during the syscall. (CVE-2023-0045)

    A NULL pointer dereference flaw was found in rawv6_push_pending_frames in net/ipv6/raw.c in the network     subcomponent in the Linux kernel. This flaw causes the system to crash. (CVE-2023-0394)

    Detected a few exploitable gadgets that could leak secret memory through a side-channel such as MDS as     well as insufficient hardening of the usercopy functions against spectre-v1. (CVE-2023-0459)

    There is a use-after-free vulnerability in the Linux Kernel which can be exploited to achieve local     privilege escalation. To reach the vulnerability kernel configuration flag CONFIG_TLS or     CONFIG_XFRM_ESPINTCP has to be configured, but the operation does not require any privilege.

    There is a use-after-free bug of icsk_ulp_data of a struct inet_connection_sock.

    When CONFIG_TLS is enabled, user can install a tls context (struct tls_context) on a connected tcp socket.
    The context is not cleared if this socket is disconnected and reused as a listener. If a new socket is     created from the listener, the context is inherited and vulnerable.

    The setsockopt TCP_ULP operation does not require any privilege.

    We recommend upgrading past commit 2c02d41d71f90a5168391b6a5f2954112ba2307c (CVE-2023-0461)

    atm_tc_enqueue in net/sched/sch_atm.c in the Linux kernel through 6.1.4 allows attackers to cause a denial     of service because of type confusion (non-negative numbers can sometimes indicate a TC_ACT_SHOT condition     rather than valid classification results). (CVE-2023-23455)

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

    netfilter: ipset: Fix overflow before widen in the bitmap_ip_create() function. (CVE-2023-53032)

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.

The version of kernel installed on the remote host is prior to 5.15.90-54.138. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2KERNEL-5.15-2023-013 advisory.

    In the Linux kernel before 6.1.6, a NULL pointer dereference bug in the traffic control subsystem allows     an unprivileged user to trigger a denial of service (system crash) via a crafted traffic control     configuration that is set up with tc qdisc and tc class commands. This affects qdisc_graft in     net/sched/sch_api.c. (CVE-2022-47929)

    A flaw NULL Pointer Dereference in the Linux kernel NTFS3 driver function attr_punch_hole() was found. A     local user could use this flaw to crash the system. (CVE-2022-4842)

    In the Linux kernel before 6.1.3, fs/ntfs3/inode.c does not validate the attribute name offset. An     unhandled page fault may occur. (CVE-2022-48424)

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

    sched/core: Fix use-after-free bug in dup_user_cpus_ptr() (CVE-2022-48892)

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

    pnode: terminate at peers of source (CVE-2022-50280)

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

    ext4: fix potential out of bound read in ext4_fc_replay_scan() (CVE-2022-50306)

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

    cifs: fix oops during encryption (CVE-2022-50341)

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

    ext4: init quota for 'old.inode' in 'ext4_rename' (CVE-2022-50346)

    The Linux kernel does not correctly mitigate SMT attacks, as discovered through a strange pattern in the     kernel API using STIBP as a mitigation, leaving the process exposed for a short period of time after a     syscall. The kernel also does not issue an IBPB immediately during the syscall. (CVE-2023-0045)

    A buffer overflow vulnerability was found in the Netfilter subsystem in the Linux Kernel. This issue could     allow the leakage of both stack and heap addresses, and potentially allow Local Privilege Escalation to     the root user via arbitrary code execution. (CVE-2023-0179)

    A NULL pointer dereference flaw was found in rawv6_push_pending_frames in net/ipv6/raw.c in the network     subcomponent in the Linux kernel. This flaw causes the system to crash. (CVE-2023-0394)

    Detected a few exploitable gadgets that could leak secret memory through a side-channel such as MDS as     well as insufficient hardening of the usercopy functions against spectre-v1. (CVE-2023-0459)

    There is a use-after-free vulnerability in the Linux Kernel which can be exploited to achieve local     privilege escalation. To reach the vulnerability kernel configuration flag CONFIG_TLS or     CONFIG_XFRM_ESPINTCP has to be configured, but the operation does not require any privilege.

    There is a use-after-free bug of icsk_ulp_data of a struct inet_connection_sock.

    When CONFIG_TLS is enabled, user can install a tls context (struct tls_context) on a connected tcp socket.
    The context is not cleared if this socket is disconnected and reused as a listener. If a new socket is     created from the listener, the context is inherited and vulnerable.

    The setsockopt TCP_ULP operation does not require any privilege.

    We recommend upgrading past commit 2c02d41d71f90a5168391b6a5f2954112ba2307c (CVE-2023-0461)

    cbq_classify in net/sched/sch_cbq.c in the Linux kernel through 6.1.4 allows attackers to cause a denial     of service (slab-out-of-bounds read) because of type confusion (non-negative numbers can sometimes     indicate a TC_ACT_SHOT condition rather than valid classification results). (CVE-2023-23454)

    atm_tc_enqueue in net/sched/sch_atm.c in the Linux kernel through 6.1.4 allows attackers to cause a denial     of service because of type confusion (non-negative numbers can sometimes indicate a TC_ACT_SHOT condition     rather than valid classification results). (CVE-2023-23455)

    In the Linux kernel 6.0.8, there is a use-after-free in run_unpack in fs/ntfs3/run.c, related to a     difference between NTFS sector size and media sector size. (CVE-2023-26544)

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

    net/sched: act_mpls: Fix warning during failed attribute validation (CVE-2023-52906)

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

    netfilter: ipset: Fix overflow before widen in the bitmap_ip_create() function. (CVE-2023-53032)

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

    netfilter: nft_payload: incorrect arithmetics when fetching VLAN header bits (CVE-2023-53033)

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.

The version of kernel installed on the remote host is prior to 5.10.165-143.735. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2KERNEL-5.10-2023-026 advisory.

    In the Linux kernel before 6.1.6, a NULL pointer dereference bug in the traffic control subsystem allows     an unprivileged user to trigger a denial of service (system crash) via a crafted traffic control     configuration that is set up with tc qdisc and tc class commands. This affects qdisc_graft in     net/sched/sch_api.c. (CVE-2022-47929)

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

    rtc: cmos: Fix event handler registration ordering issue (CVE-2022-48953)

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

    igb: Do not free q_vector unless new one was allocated (CVE-2022-50252)

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

    power: supply: fix null pointer dereferencing in power_supply_get_battery_info (CVE-2022-50276)

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

    pnode: terminate at peers of source (CVE-2022-50280)

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

    chardev: fix error handling in cdev_device_add() (CVE-2022-50282)

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

    qlcnic: prevent ->dcb use-after-free on qlcnic_dcb_enable() failure (CVE-2022-50288)

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

    fs: jfs: fix shift-out-of-bounds in dbDiscardAG (CVE-2022-50333)

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

    hugetlbfs: fix null-ptr-deref in hugetlbfs_parse_param() (CVE-2022-50334)

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

    cifs: fix oops during encryption (CVE-2022-50341)

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

    ext4: init quota for 'old.inode' in 'ext4_rename' (CVE-2022-50346)

    The Linux kernel does not correctly mitigate SMT attacks, as discovered through a strange pattern in the     kernel API using STIBP as a mitigation, leaving the process exposed for a short period of time after a     syscall. The kernel also does not issue an IBPB immediately during the syscall. (CVE-2023-0045)

    A buffer overflow vulnerability was found in the Netfilter subsystem in the Linux Kernel. This issue could     allow the leakage of both stack and heap addresses, and potentially allow Local Privilege Escalation to     the root user via arbitrary code execution. (CVE-2023-0179)

    There is a logic error in io_uring's implementation which can be used to trigger a use-after-free     vulnerability leading to privilege escalation. In the io_prep_async_work function the assumption that the     last io_grab_identity call cannot return false is not true, and in this case the function will use the     init_cred or the previous linked requests identity to do operations instead of using the current identity.
    This can lead to reference counting issues causing use-after-free. We recommend upgrading past version     5.10.161. (CVE-2023-0240)

    A NULL pointer dereference flaw was found in rawv6_push_pending_frames in net/ipv6/raw.c in the network     subcomponent in the Linux kernel. This flaw causes the system to crash. (CVE-2023-0394)

    Detected a few exploitable gadgets that could leak secret memory through a side-channel such as MDS as     well as insufficient hardening of the usercopy functions against spectre-v1. (CVE-2023-0459)

    There is a use-after-free vulnerability in the Linux Kernel which can be exploited to achieve local     privilege escalation. To reach the vulnerability kernel configuration flag CONFIG_TLS or     CONFIG_XFRM_ESPINTCP has to be configured, but the operation does not require any privilege.

    There is a use-after-free bug of icsk_ulp_data of a struct inet_connection_sock.

    When CONFIG_TLS is enabled, user can install a tls context (struct tls_context) on a connected tcp socket.
    The context is not cleared if this socket is disconnected and reused as a listener. If a new socket is     created from the listener, the context is inherited and vulnerable.

    The setsockopt TCP_ULP operation does not require any privilege.

    We recommend upgrading past commit 2c02d41d71f90a5168391b6a5f2954112ba2307c (CVE-2023-0461)

    efi: rt-wrapper: Add missing include (CVE-2023-21102)

    cbq_classify in net/sched/sch_cbq.c in the Linux kernel through 6.1.4 allows attackers to cause a denial     of service (slab-out-of-bounds read) because of type confusion (non-negative numbers can sometimes     indicate a TC_ACT_SHOT condition rather than valid classification results). (CVE-2023-23454)

    atm_tc_enqueue in net/sched/sch_atm.c in the Linux kernel through 6.1.4 allows attackers to cause a denial     of service because of type confusion (non-negative numbers can sometimes indicate a TC_ACT_SHOT condition     rather than valid classification results). (CVE-2023-23455)

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

    net/sched: act_mpls: Fix warning during failed attribute validation (CVE-2023-52906)

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

    netfilter: ipset: Fix overflow before widen in the bitmap_ip_create() function. (CVE-2023-53032)

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

    netfilter: nft_payload: incorrect arithmetics when fetching VLAN header bits (CVE-2023-53033)

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.

ID	Name	Product	Family	Severity
265146	Linux Distros Unpatched Vulnerability : CVE-2022-50280	Nessus	Misc.	low
171848	Amazon Linux 2 : kernel, --advisory ALAS2KERNEL-5.4-2023-042 (ALASKERNEL-5.4-2023-042)	Nessus	Amazon Linux Local Security Checks	high
171229	Amazon Linux 2 : kernel, --advisory ALAS2-2023-1932 (ALAS-2023-1932)	Nessus	Amazon Linux Local Security Checks	high
171227	Amazon Linux 2 : kernel, --advisory ALAS2KERNEL-5.15-2023-013 (ALASKERNEL-5.15-2023-013)	Nessus	Amazon Linux Local Security Checks	high
171216	Amazon Linux 2 : kernel, --advisory ALAS2KERNEL-5.10-2023-026 (ALASKERNEL-5.10-2023-026)	Nessus	Amazon Linux Local Security Checks	high

Detections

Analytics

CVE-2022-50280

high

Tenable Plugins

low

high

high

high

high