In the Linux kernel, the following vulnerability has been resolved: xen/gntdev: Accommodate VMA splitting Prior to this commit, the gntdev driver code did not handle the following scenario correctly with paravirtualized (PV) Xen domains: * User process sets up a gntdev mapping composed of two grant mappings (i.e., two pages shared by another Xen domain). * User process munmap()s one of the pages. * User process munmap()s the remaining page. * User process exits. In the scenario above, the user process would cause the kernel to log the following messages in dmesg for the first munmap(), and the second munmap() call would result in similar log messages: BUG: Bad page map in process doublemap.test pte:... pmd:... page:0000000057c97bff refcount:1 mapcount:-1 \ mapping:0000000000000000 index:0x0 pfn:... ... page dumped because: bad pte ... file:gntdev fault:0x0 mmap:gntdev_mmap [xen_gntdev] readpage:0x0 ... Call Trace: <TASK> dump_stack_lvl+0x46/0x5e print_bad_pte.cold+0x66/0xb6 unmap_page_range+0x7e5/0xdc0 unmap_vmas+0x78/0xf0 unmap_region+0xa8/0x110 __do_munmap+0x1ea/0x4e0 __vm_munmap+0x75/0x120 __x64_sys_munmap+0x28/0x40 do_syscall_64+0x38/0x90 entry_SYSCALL_64_after_hwframe+0x61/0xcb ... For each munmap() call, the Xen hypervisor (if built with CONFIG_DEBUG) would print out the following and trigger a general protection fault in the affected Xen PV domain: (XEN) d0v... Attempt to implicitly unmap d0's grant PTE ... (XEN) d0v... Attempt to implicitly unmap d0's grant PTE ... As of this writing, gntdev_grant_map structure's vma field (referred to as map->vma below) is mainly used for checking the start and end addresses of mappings. However, with split VMAs, these may change, and there could be more than one VMA associated with a gntdev mapping. Hence, remove the use of map->vma and rely on map->pages_vm_start for the original start address and on (map->count << PAGE_SHIFT) for the original mapping size. Let the invalidate() and find_special_page() hooks use these. Also, given that there can be multiple VMAs associated with a gntdev mapping, move the "mmu_interval_notifier_remove(&map->notifier)" call to the end of gntdev_put_map, so that the MMU notifier is only removed after the closing of the last remaining VMA. Finally, use an atomic to prevent inadvertent gntdev mapping re-use, instead of using the map->live_grants atomic counter and/or the map->vma pointer (the latter of which is now removed). This prevents the userspace from mmap()'ing (with MAP_FIXED) a gntdev mapping over the same address range as a previously set up gntdev mapping. This scenario can be summarized with the following call-trace, which was valid prior to this commit: mmap gntdev_mmap mmap (repeat mmap with MAP_FIXED over the same address range) gntdev_invalidate unmap_grant_pages (sets 'being_removed' entries to true) gnttab_unmap_refs_async unmap_single_vma gntdev_mmap (maps the shared pages again) munmap gntdev_invalidate unmap_grant_pages (no-op because 'being_removed' entries are true) unmap_single_vma (For PV domains, Xen reports that a granted page is being unmapped and triggers a general protection fault in the affected domain, if Xen was built with CONFIG_DEBUG) The fix for this last scenario could be worth its own commit, but we opted for a single commit, because removing the gntdev_grant_map structure's vma field requires guarding the entry to gntdev_mmap(), and the live_grants atomic counter is not sufficient on its own to prevent the mmap() over a pre-existing mapping.

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

  - xen/gntdev: Accommodate VMA splitting Prior to this commit, the gntdev driver code did not handle the     following scenario correctly with paravirtualized (PV) Xen domains: * User process sets up a gntdev     mapping composed of two grant mappings (i.e., two pages shared by another Xen domain). * User process     munmap()s one of the pages. * User process munmap()s the remaining page. * User process exits. In the     scenario above, the user process would cause the kernel to log the following messages in dmesg for the     first munmap(), and the second munmap() call would result in similar log messages: BUG: Bad page map in     process doublemap.test pte:... pmd:... page:0000000057c97bff refcount:1 mapcount:-1 \     mapping:0000000000000000 index:0x0 pfn:... ... page dumped because: bad pte ... file:gntdev fault:0x0     mmap:gntdev_mmap [xen_gntdev] readpage:0x0 ... Call Trace: <TASK> dump_stack_lvl+0x46/0x5e     print_bad_pte.cold+0x66/0xb6 unmap_page_range+0x7e5/0xdc0 unmap_vmas+0x78/0xf0 unmap_region+0xa8/0x110
    __do_munmap+0x1ea/0x4e0 __vm_munmap+0x75/0x120 __x64_sys_munmap+0x28/0x40 do_syscall_64+0x38/0x90     entry_SYSCALL_64_after_hwframe+0x61/0xcb ... For each munmap() call, the Xen hypervisor (if built with     CONFIG_DEBUG) would print out the following and trigger a general protection fault in the affected Xen PV     domain: (XEN) d0v... Attempt to implicitly unmap d0's grant PTE ... (XEN) d0v... Attempt to implicitly     unmap d0's grant PTE ... As of this writing, gntdev_grant_map structure's vma field (referred to as     map->vma below) is mainly used for checking the start and end addresses of mappings. However, with split     VMAs, these may change, and there could be more than one VMA associated with a gntdev mapping. Hence,     remove the use of map->vma and rely on map->pages_vm_start for the original start address and on     (map->count << PAGE_SHIFT) for the original mapping size. Let the invalidate() and find_special_page()     hooks use these. Also, given that there can be multiple VMAs associated with a gntdev mapping, move the     mmu_interval_notifier_remove(&map->notifier) call to the end of gntdev_put_map, so that the MMU notifier     is only removed after the closing of the last remaining VMA. Finally, use an atomic to prevent inadvertent     gntdev mapping re-use, instead of using the map->live_grants atomic counter and/or the map->vma pointer     (the latter of which is now removed). This prevents the userspace from mmap()'ing (with MAP_FIXED) a     gntdev mapping over the same address range as a previously set up gntdev mapping. This scenario can be     summarized with the following call-trace, which was valid prior to this commit: mmap gntdev_mmap mmap     (repeat mmap with MAP_FIXED over the same address range) gntdev_invalidate unmap_grant_pages (sets     'being_removed' entries to true) gnttab_unmap_refs_async unmap_single_vma gntdev_mmap (maps the shared     pages again) munmap gntdev_invalidate unmap_grant_pages (no-op because 'being_removed' entries are true)     unmap_single_vma (For PV domains, Xen reports that a granted page is being unmapped and triggers a general     protection fault in the affected domain, if Xen was built with CONFIG_DEBUG) The fix for this last     scenario could be worth its own commit, but we opted for a single commit, because removing the     gntdev_grant_map structure's vma field requires guarding the entry to gntdev_mmap(), and the live_grants     atomic counter is not sufficient on its own to prevent the mmap() over a pre-existing mapping.
    (CVE-2022-50471)

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.15.75-48.135. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2KERNEL-5.15-2025-090 advisory.

    A vulnerability, which was classified as problematic, has been found in Linux Kernel. This issue affects     the function nilfs_attach_log_writer of the file fs/nilfs2/segment.c of the component BPF. The     manipulation leads to memory leak. The attack may be initiated remotely. It is recommended to apply a     patch to fix this issue. The identifier VDB-211961 was assigned to this vulnerability. (CVE-2022-3646)

    drivers/scsi/stex.c in the Linux kernel through 5.19.9 allows local users to obtain sensitive information     from kernel memory because stex_queuecommand_lck lacks a memset for the PASSTHRU_CMD case.
    (CVE-2022-40768)

    The Linux kernel NFSD implementation prior to versions 5.19.17 and 6.0.2 are vulnerable to buffer     overflow. NFSD tracks the number of pages held by each NFSD thread by combining the receive and send     buffers of a remote procedure call (RPC) into a single array of pages. A client can force the send buffer     to shrink by sending an RPC message over TCP with garbage data added at the end of the message. The RPC     message with garbage data is still correctly formed according to the specification and is passed forward     to handlers. Vulnerable code in NFSD is not expecting the oversized request and writes beyond the     allocated buffer space. CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H (CVE-2022-43945)

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

    NFSD: Protect against send buffer overflow in NFSv2 READDIR (CVE-2022-50235)

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

    NFSD: fix use-after-free on source server when doing inter-server copy (CVE-2022-50241)

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

    sctp: handle the error returned from sctp_auth_asoc_init_active_key (CVE-2022-50243)

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

    xen/gntdev: Prevent leaking grants (CVE-2022-50257)

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

    vhost/vsock: Use kvmalloc/kvfree for larger packets. (CVE-2022-50271)

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

    md: Replace snprintf with scnprintf (CVE-2022-50299)

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

    nbd: Fix hung when signal interrupts nbd_start_device_ioctl() (CVE-2022-50314)

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

    jbd2: fix potential use-after-free in jbd2_fc_wait_bufs (CVE-2022-50328)

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

    ext4: fix null-ptr-deref in ext4_write_info (CVE-2022-50344)

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

    NFSD: Protect against send buffer overflow in NFSv3 READ (CVE-2022-50345)

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

    nfsd: Fix a memory leak in an error handling path (CVE-2022-50348)

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

    btrfs: fix race between quota enable and quota rescan ioctl (CVE-2022-50379)

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

    net/ieee802154: reject zero-sized raw_sendmsg() (CVE-2022-50397)

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

    net: If sock is dead don't access sock's sk_wq in sk_stream_wait_memory (CVE-2022-50409)

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

    NFSD: Protect against send buffer overflow in NFSv2 READ (CVE-2022-50410)

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

    scsi: libsas: Fix use-after-free bug in smp_execute_task_sg() (CVE-2022-50422)

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

    ext4: avoid crash when inline data creation follows DIO write (CVE-2022-50435)

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

    xfrm: Reinject transport-mode packets through workqueue (CVE-2022-50445)

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

    xen/gntdev: Accommodate VMA splitting (CVE-2022-50471)

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

    drm/mipi-dsi: Detach devices when removing the host (CVE-2022-50489)

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

    bpf: Propagate error from htab_lock_bucket() to userspace (CVE-2022-50490)

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

    ext4: fix potential memory leak in ext4_fc_record_regions() (CVE-2022-50512)

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

    usb: host: xhci: Fix potential memory leak in xhci_alloc_stream_info() (CVE-2022-50544)

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.155-138.670. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2KERNEL-5.10-2022-023 advisory.

    A memory overflow vulnerability was found in the Linux kernel's ipc functionality of the memcg subsystem,     in the way a user calls the semget function multiple times, creating semaphores. This flaw allows a local     user to starve the resources, causing a denial of service. The highest threat from this vulnerability is     to system availability. (CVE-2021-3759)

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

    inet: fully convert sk->sk_rx_dst to RCU rules (CVE-2021-47103)

    A vulnerability was found in Linux Kernel. It has been declared as problematic. Affected by this     vulnerability is the function ipv6_renew_options of the component IPv6 Handler. The manipulation leads to     memory leak. The attack can be launched remotely. It is recommended to apply a patch to fix this issue.
    The identifier VDB-211021 was assigned to this vulnerability. (CVE-2022-3524)

    A vulnerability classified as problematic was found in Linux Kernel. This vulnerability affects the     function bnx2x_tpa_stop of the file drivers/net/ethernet/broadcom/bnx2x/bnx2x_cmn.c of the component BPF.
    The manipulation leads to memory leak. It is recommended to apply a patch to fix this issue. VDB-211042 is     the identifier assigned to this vulnerability. (CVE-2022-3542)

    A vulnerability classified as critical was found in Linux Kernel. Affected by this vulnerability is the     function l2cap_reassemble_sdu of the file net/bluetooth/l2cap_core.c of the component Bluetooth. The     manipulation leads to use after free. It is recommended to apply a patch to fix this issue. The associated     identifier of this vulnerability is VDB-211087. (CVE-2022-3564)

    A vulnerability was found in Linux Kernel. It has been declared as problematic. Affected by this     vulnerability is the function intr_callback of the file drivers/net/usb/r8152.c of the component BPF. The     manipulation leads to logging of excessive data. The attack can be launched remotely. It is recommended to     apply a patch to fix this issue. The associated identifier of this vulnerability is VDB-211363.
    (CVE-2022-3594)

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

    arm64: topology: fix possible overflow in amu_fie_setup() (CVE-2022-48657)

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

    nilfs2: fix use-after-free bug of ns_writer on remount (CVE-2022-49834)

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

    can: j1939: j1939_send_one(): fix missing CAN header initialization (CVE-2022-49845)

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

    udf: Fix a slab-out-of-bounds write bug in udf_find_entry() (CVE-2022-49846)

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

    nilfs2: fix deadlock in nilfs_count_free_blocks() (CVE-2022-49850)

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

    net: macvlan: fix memory leaks of macvlan_common_newlink (CVE-2022-49853)

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

    tipc: fix the msg->req tlv len check in tipc_nl_compat_name_table_dump_header (CVE-2022-49862)

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

    can: af_can: fix NULL pointer dereference in can_rx_register() (CVE-2022-49863)

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

    ipv6: addrlabel: fix infoleak when sending struct ifaddrlblmsg to network (CVE-2022-49865)

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

    bnxt_en: Fix possible crash in bnxt_hwrm_set_coal() (CVE-2022-49869)

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

    capabilities: fix undefined behavior in bit shift for CAP_TO_MASK (CVE-2022-49870)

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

    net: tun: Fix memory leaks of napi_get_frags (CVE-2022-49871)

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

    net: gso: fix panic on frag_list with mixed head alloc types (CVE-2022-49872)

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

    bpf: Fix wrong reg type conversion in release_reference() (CVE-2022-49873)

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

    HID: hyperv: fix possible memory leak in mousevsc_probe() (CVE-2022-49874)

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

    bpftool: Fix NULL pointer dereference when pin {PROG, MAP, LINK} without FILE (CVE-2022-49875)

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

    bpf, sockmap: Fix the sk->sk_forward_alloc warning of sk_stream_kill_queues (CVE-2022-49877)

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

    ext4: fix BUG_ON() when directory entry has invalid rec_len (CVE-2022-49879)

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

    ext4: fix warning in 'ext4_da_release_space' (CVE-2022-49880)

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

    ACPI: APEI: Fix integer overflow in ghes_estatus_pool_init() (CVE-2022-49885)

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

    capabilities: fix potential memleak on error path from vfs_getxattr_alloc() (CVE-2022-49890)

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

    ftrace: Fix use-after-free for dynamic ftrace_ops (CVE-2022-49892)

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

    fscrypt: stop using keyrings subsystem for fscrypt_master_key (CVE-2022-49899)

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

    ipv6: fix WARNING in ip6_route_net_exit_late() (CVE-2022-49903)

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

    net, neigh: Fix null-ptr-deref in neigh_table_clear() (CVE-2022-49904)

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

    net: mdio: fix undefined behavior in bit shift for __mdiobus_register (CVE-2022-49907)

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

    btrfs: fix ulist leaks in error paths of qgroup self tests (CVE-2022-49912)

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

    btrfs: fix inode list leak during backref walking at find_parent_nodes() (CVE-2022-49913)

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

    btrfs: fix inode list leak during backref walking at resolve_indirect_refs() (CVE-2022-49914)

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

    mISDN: fix possible memory leak in mISDN_register_device() (CVE-2022-49915)

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

    ipvs: fix WARNING in ip_vs_app_net_cleanup() (CVE-2022-49917)

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

    ipvs: fix WARNING in __ip_vs_cleanup_batch() (CVE-2022-49918)

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

    netfilter: nf_tables: release flow rule object from commit path (CVE-2022-49919)

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

    net: sched: Fix use after free in red_enqueue() (CVE-2022-49921)

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

    RDMA/core: Fix null-ptr-deref in ib_core_cleanup() (CVE-2022-49925)

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

    nfs4: Fix kmemleak when allocate slot failed (CVE-2022-49927)

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

    binder: fix UAF of alloc->vma in race with munmap() (CVE-2022-50240)

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

    NFSD: fix use-after-free on source server when doing inter-server copy (CVE-2022-50241)

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

    sctp: handle the error returned from sctp_auth_asoc_init_active_key (CVE-2022-50243)

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

    xen/gntdev: Prevent leaking grants (CVE-2022-50257)

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

    kcm: annotate data-races around kcm->rx_wait (CVE-2022-50265)

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

    vhost/vsock: Use kvmalloc/kvfree for larger packets. (CVE-2022-50271)

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

    mm,hugetlb: take hugetlb_lock before decrementing h->resv_huge_pages (CVE-2022-50285)

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

    kcm: annotate data-races around kcm->rx_psock (CVE-2022-50291)

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

    md: Replace snprintf with scnprintf (CVE-2022-50299)

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

    nbd: Fix hung when signal interrupts nbd_start_device_ioctl() (CVE-2022-50314)

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

    ata: ahci: Match EM_MAX_SLOTS with SATA_PMP_MAX_PORTS (CVE-2022-50315)

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

    jbd2: fix potential use-after-free in jbd2_fc_wait_bufs (CVE-2022-50328)

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

    crypto: cavium - prevent integer overflow loading firmware (CVE-2022-50330)

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

    binder: fix UAF of alloc->vma in race with munmap() (CVE-2022-50338)

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

    ext4: fix null-ptr-deref in ext4_write_info (CVE-2022-50344)

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

    nfsd: Fix a memory leak in an error handling path (CVE-2022-50348)

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

    net: hns: fix possible memory leak in hnae_ae_register() (CVE-2022-50352)

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

    net: sched: sfb: fix null pointer access issue when sfb_init() fails (CVE-2022-50356)

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

    btrfs: fix race between quota enable and quota rescan ioctl (CVE-2022-50379)

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

    mm: /proc/pid/smaps_rollup: fix no vma's null-deref (CVE-2022-50380)

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

    net/ieee802154: reject zero-sized raw_sendmsg() (CVE-2022-50397)

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

    net: If sock is dead don't access sock's sk_wq in sk_stream_wait_memory (CVE-2022-50409)

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

    scsi: libsas: Fix use-after-free bug in smp_execute_task_sg() (CVE-2022-50422)

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

    kernfs: fix use-after-free in __kernfs_remove (CVE-2022-50432)

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

    ext4: avoid crash when inline data creation follows DIO write (CVE-2022-50435)

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

    net: sched: cake: fix null pointer access issue when cake_init() fails (CVE-2022-50452)

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

    scsi: iscsi: iscsi_tcp: Fix null-ptr-deref while calling getpeername() (CVE-2022-50459)

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

    cifs: Fix xid leak in cifs_flock() (CVE-2022-50460)

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

    fs/binfmt_elf: Fix memory leak in load_elf_binary() (CVE-2022-50466)

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

    xhci: Remove device endpoints from bandwidth list when freeing the device (CVE-2022-50470)

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

    xen/gntdev: Accommodate VMA splitting (CVE-2022-50471)

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

    iommu/vt-d: Clean up si_domain in the init_dmars() error path (CVE-2022-50482)

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

    ext4: fix potential memory leak in ext4_fc_record_regions() (CVE-2022-50512)

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

    tipc: fix an information leak in tipc_topsrv_kern_subscr (CVE-2022-50531)

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

    usb: host: xhci: Fix potential memory leak in xhci_alloc_stream_info() (CVE-2022-50544)

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

    tipc: fix a null-ptr-deref in tipc_topsrv_accept (CVE-2022-50555)

    A use-after-free flaw was found in qdisc_graft in net/sched/sch_api.c in the Linux Kernel due to a race     problem. This flaw leads to a denial of service issue. (CVE-2023-0590)

    An out-of-bounds memory access flaw was found in the Linux kernel's TUN/TAP device driver functionality in     how a user generates a malicious (too big) networking packet when napi frags is enabled. This flaw allows     a local user to crash or potentially escalate their privileges on the system. (CVE-2023-3812)

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.

An update of the linux package has been released.

ID	Name	Product	Family	Severity
269312	Linux Distros Unpatched Vulnerability : CVE-2022-50471	Nessus	Misc.	high
266163	Amazon Linux 2 : kernel, --advisory ALAS2KERNEL-5.15-2025-090 (ALASKERNEL-5.15-2025-090)	Nessus	Amazon Linux Local Security Checks	medium
168520	Amazon Linux 2 : kernel, --advisory ALAS2KERNEL-5.10-2022-023 (ALASKERNEL-5.10-2022-023)	Nessus	Amazon Linux Local Security Checks	high
153035	Photon OS 4.0: Linux PHSA-2021-4.0-0095	Nessus	PhotonOS Local Security Checks	high

Detections

Analytics

CVE-2022-50471

high

Tenable Plugins

high

medium

high

high