In the Linux kernel, the following vulnerability has been resolved: fscrypt: stop using keyrings subsystem for fscrypt_master_key The approach of fs/crypto/ internally managing the fscrypt_master_key structs as the payloads of "struct key" objects contained in a "struct key" keyring has outlived its usefulness. The original idea was to simplify the code by reusing code from the keyrings subsystem. However, several issues have arisen that can't easily be resolved: - When a master key struct is destroyed, blk_crypto_evict_key() must be called on any per-mode keys embedded in it. (This started being the case when inline encryption support was added.) Yet, the keyrings subsystem can arbitrarily delay the destruction of keys, even past the time the filesystem was unmounted. Therefore, currently there is no easy way to call blk_crypto_evict_key() when a master key is destroyed. Currently, this is worked around by holding an extra reference to the filesystem's request_queue(s). But it was overlooked that the request_queue reference is *not* guaranteed to pin the corresponding blk_crypto_profile too; for device-mapper devices that support inline crypto, it doesn't. This can cause a use-after-free. - When the last inode that was using an incompletely-removed master key is evicted, the master key removal is completed by removing the key struct from the keyring. Currently this is done via key_invalidate(). Yet, key_invalidate() takes the key semaphore. This can deadlock when called from the shrinker, since in fscrypt_ioctl_add_key(), memory is allocated with GFP_KERNEL under the same semaphore. - More generally, the fact that the keyrings subsystem can arbitrarily delay the destruction of keys (via garbage collection delay, or via random processes getting temporary key references) is undesirable, as it means we can't strictly guarantee that all secrets are ever wiped. - Doing the master key lookups via the keyrings subsystem results in the key_permission LSM hook being called. fscrypt doesn't want this, as all access control for encrypted files is designed to happen via the files themselves, like any other files. The workaround which SELinux users are using is to change their SELinux policy to grant key search access to all domains. This works, but it is an odd extra step that shouldn't really have to be done. The fix for all these issues is to change the implementation to what I should have done originally: don't use the keyrings subsystem to keep track of the filesystem's fscrypt_master_key structs. Instead, just store them in a regular kernel data structure, and rework the reference counting, locking, and lifetime accordingly. Retain support for RCU-mode key lookups by using a hash table. Replace fscrypt_sb_free() with fscrypt_sb_delete(), which releases the keys synchronously and runs a bit earlier during unmount, so that block devices are still available. A side effect of this patch is that neither the master keys themselves nor the filesystem keyrings will be listed in /proc/keys anymore. ("Master key users" and the master key users keyrings will still be listed.) However, this was mostly an implementation detail, and it was intended just for debugging purposes. I don't know of anyone using it. This patch does *not* change how "master key users" (->mk_users) works; that still uses the keyrings subsystem. That is still needed for key quotas, and changing that isn't necessary to solve the issues listed above. If we decide to change that too, it would be a separate patch. I've marked this as fixing the original commit that added the fscrypt keyring, but as noted above the most important issue that this patch fixes wasn't introduced until the addition of inline encryption support.

The Unity Linux 20 host has a package installed that is affected by a vulnerability as referenced in the UTSA-2025-989619 advisory.

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

    fscrypt: stop using keyrings subsystem for fscrypt_master_key

    The approach of fs/crypto/ internally managing the fscrypt_master_key     structs as the payloads of struct key objects contained in a     struct key keyring has outlived its usefulness.  The original idea was     to simplify the code by reusing code from the keyrings subsystem.
    However, several issues have arisen that can't easily be resolved:

    - When a master key struct is destroyed, blk_crypto_evict_key() must be       called on any per-mode keys embedded in it.  (This started being the       case when inline encryption support was added.)  Yet, the keyrings       subsystem can arbitrarily delay the destruction of keys, even past the       time the filesystem was unmounted.  Therefore, currently there is no       easy way to call blk_crypto_evict_key() when a master key is       destroyed.  Currently, this is worked around by holding an extra       reference to the filesystem's request_queue(s).  But it was overlooked       that the request_queue reference is *not* guaranteed to pin the       corresponding blk_crypto_profile too; for device-mapper devices that       support inline crypto, it doesn't.  This can cause a use-after-free.

    - When the last inode that was using an incompletely-removed master key       is evicted, the master key removal is completed by removing the key       struct from the keyring.  Currently this is done via key_invalidate().
      Yet, key_invalidate() takes the key semaphore.  This can deadlock when       called from the shrinker, since in fscrypt_ioctl_add_key(), memory is       allocated with GFP_KERNEL under the same semaphore.

    - More generally, the fact that the keyrings subsystem can arbitrarily       delay the destruction of keys (via garbage collection delay, or via       random processes getting temporary key references) is undesirable, as       it means we can't strictly guarantee that all secrets are ever wiped.

    - Doing the master key lookups via the keyrings subsystem results in the       key_permission LSM hook being called.  fscrypt doesn't want this, as       all access control for encrypted files is designed to happen via the       files themselves, like any other files.  The workaround which SELinux       users are using is to change their SELinux policy to grant key search       access to all domains.  This works, but it is an odd extra step that       shouldn't really have to be done.

    The fix for all these issues is to change the implementation to what I     should have done originally: don't use the keyrings subsystem to keep     track of the filesystem's fscrypt_master_key structs.  Instead, just     store them in a regular kernel data structure, and rework the reference     counting, locking, and lifetime accordingly.  Retain support for     RCU-mode key lookups by using a hash table.  Replace fscrypt_sb_free()     with fscrypt_sb_delete(), which releases the keys synchronously and runs     a bit earlier during unmount, so that block devices are still available.

    A side effect of this patch is that neither the master keys themselves     nor the filesystem keyrings will be listed in /proc/keys anymore.
    (Master key users and the master key users keyrings will still be     listed.)  However, this was mostly an implementation detail, and it was     intended just for debugging purposes.  I don't know of anyone using it.

    This patch does *not* change how master key users (->mk_users) works;
    that still uses the keyrings subsystem.  That is still needed for key     quotas, and changing that isn't necessary to solve the issues listed     above.  If we decide to change that too, it would be a separate patch.

    I've marked this as fixing the original commit that added the fscrypt     keyring, but as noted above the most important issue that this patch     fixes wasn't introduced until the addition of inline encryption support.

Tenable has extracted the preceding description block directly from the Unity Linux security advisory.

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

The Unity Linux 20 host has a package installed that is affected by a vulnerability as referenced in the UTSA-2025-987032 advisory.

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

    fscrypt: stop using keyrings subsystem for fscrypt_master_key

    The approach of fs/crypto/ internally managing the fscrypt_master_key     structs as the payloads of struct key objects contained in a     struct key keyring has outlived its usefulness.  The original idea was     to simplify the code by reusing code from the keyrings subsystem.
    However, several issues have arisen that can't easily be resolved:

    - When a master key struct is destroyed, blk_crypto_evict_key() must be       called on any per-mode keys embedded in it.  (This started being the       case when inline encryption support was added.)  Yet, the keyrings       subsystem can arbitrarily delay the destruction of keys, even past the       time the filesystem was unmounted.  Therefore, currently there is no       easy way to call blk_crypto_evict_key() when a master key is       destroyed.  Currently, this is worked around by holding an extra       reference to the filesystem's request_queue(s).  But it was overlooked       that the request_queue reference is *not* guaranteed to pin the       corresponding blk_crypto_profile too; for device-mapper devices that       support inline crypto, it doesn't.  This can cause a use-after-free.

    - When the last inode that was using an incompletely-removed master key       is evicted, the master key removal is completed by removing the key       struct from the keyring.  Currently this is done via key_invalidate().
      Yet, key_invalidate() takes the key semaphore.  This can deadlock when       called from the shrinker, since in fscrypt_ioctl_add_key(), memory is       allocated with GFP_KERNEL under the same semaphore.

    - More generally, the fact that the keyrings subsystem can arbitrarily       delay the destruction of keys (via garbage collection delay, or via       random processes getting temporary key references) is undesirable, as       it means we can't strictly guarantee that all secrets are ever wiped.

    - Doing the master key lookups via the keyrings subsystem results in the       key_permission LSM hook being called.  fscrypt doesn't want this, as       all access control for encrypted files is designed to happen via the       files themselves, like any other files.  The workaround which SELinux       users are using is to change their SELinux policy to grant key search       access to all domains.  This works, but it is an odd extra step that       shouldn't really have to be done.

    The fix for all these issues is to change the implementation to what I     should have done originally: don't use the keyrings subsystem to keep     track of the filesystem's fscrypt_master_key structs.  Instead, just     store them in a regular kernel data structure, and rework the reference     counting, locking, and lifetime accordingly.  Retain support for     RCU-mode key lookups by using a hash table.  Replace fscrypt_sb_free()     with fscrypt_sb_delete(), which releases the keys synchronously and runs     a bit earlier during unmount, so that block devices are still available.

    A side effect of this patch is that neither the master keys themselves     nor the filesystem keyrings will be listed in /proc/keys anymore.
    (Master key users and the master key users keyrings will still be     listed.)  However, this was mostly an implementation detail, and it was     intended just for debugging purposes.  I don't know of anyone using it.

    This patch does *not* change how master key users (->mk_users) works;
    that still uses the keyrings subsystem.  That is still needed for key     quotas, and changing that isn't necessary to solve the issues listed     above.  If we decide to change that too, it would be a separate patch.

    I've marked this as fixing the original commit that added the fscrypt     keyring, but as noted above the most important issue that this patch     fixes wasn't introduced until the addition of inline encryption support.

Tenable has extracted the preceding description block directly from the Unity Linux security advisory.

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

According to the versions of the kernel packages installed, the EulerOS installation on the remote host is affected by the following vulnerabilities :

    RDMA/core: Silence oversized kvmalloc() warning(CVE-2025-37867)

    igb: revert rtnl_lock() that causes deadlock(CVE-2023-53060)

    bnxt_en: Avoid order-5 memory allocation for TPA data(CVE-2023-53134)

    net_sched: sch_sfq: move the limit validation(CVE-2025-37752)

    ftrace: Add cond_resched() to ftrace_graph_set_hash().(CVE-2025-37940)

    net: annotate races around sk-sk_bound_dev_if(CVE-2022-49420)

    ext4: fix off-by-one error in do_split(CVE-2025-23150)

    jbd2: remove wrong sb-s_sequence check(CVE-2025-37839)

    ext4: update s_journal_inum if it changes after journal replay(CVE-2023-53091)

    udp: Fix memory accounting leak.(CVE-2025-22058)

    netem: Update sch-q.qlen before qdisc_tree_reduce_backlog().(CVE-2025-21703)

    net: fix memory leak in tcp_conn_request().(CVE-2024-57841)

    xfrm: state: fix out-of-bounds read during lookup(CVE-2024-57982)

    Insufficient control flow management for the Intel(R) 82599 Ethernet Controllers and Adapters may allow an     authenticated user to potentially enable denial of service via local access.(CVE-2021-33061)

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

    nvmet: avoid potential UAF in nvmet_req_complete().(CVE-2023-53116)

    ata: libata-transport: fix error handling in ata_tport_add().(CVE-2022-49825)

    ata: libata-transport: fix double ata_host_put() in ata_tport_add().(CVE-2022-49826)

    bpf: track changes_pkt_data property for global functions(CVE-2024-58098)

    pinctrl: devicetree: fix null pointer dereferencing in pinctrl_dt_to_map(CVE-2022-49832)

    scsi: core: Fix a procfs host directory removal regression(CVE-2023-53118)

    bpf, verifier: Fix memory leak in array reallocation for stack state(CVE-2022-49878)

    kprobes: Skip clearing aggrprobe's post_handler in kprobe-on-ftrace case(CVE-2022-49779)

    i2c: piix4: Fix adapter not be removed in piix4_remove().(CVE-2022-49900)

    bpf: Fix kmemleak warning for percpu hashmap(CVE-2025-37807)

    drm: Fix potential null-ptr-deref in drm_vblank_destroy_worker().(CVE-2022-49827)

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

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

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

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

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

    bpf, test_run: Fix alignment problem in bpf_prog_test_run_skb().(CVE-2022-49840)

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

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

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

    ftrace: Fix null pointer dereference in ftrace_add_mod().(CVE-2022-49802)

    tracing: Do not let histogram values have some modifiers(CVE-2023-53093)

    ftrace: Fix invalid address access in lookup_rec() when index is 0(CVE-2023-53075)

    iavf: Fix handling of dummy receive descriptors(CVE-2022-49583)

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

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

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

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

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

    scsi: scsi_transport_sas: Fix error handling in sas_phy_add().(CVE-2022-49839)

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

    blk-mq: Fix kmemleak in blk_mq_init_allocated_queue(CVE-2022-49901)

    bpf: Fix memory leaks in __check_func_call(CVE-2022-49837)

    ext4: ignore xattrs past end(CVE-2025-37738)

    ext4: fix another off-by-one fsmap error on 1k block filesystems(CVE-2023-53143)

    ext4: fix WARNING in ext4_update_inline_data(CVE-2023-53100)

    ext4: Fix possible corruption when moving a directory(CVE-2023-53137)

    ext4: zero i_disksize when initializing the bootloader inode(CVE-2023-53101)

    ata: libata-transport: fix error handling in ata_tdev_add().(CVE-2022-49823)

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

    ext4: fix task hung in ext4_xattr_delete_inode(CVE-2023-53089)

    scsi: target: tcm_loop: Fix possible name leak in tcm_loop_setup_hba_bus().(CVE-2022-49780)

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

    ring-buffer: Check for NULL cpu_buffer in ring_buffer_wake_waiters().(CVE-2022-49889)

    netlabel: Fix NULL pointer exception caused by CALIPSO on IPv4 sockets.(CVE-2025-22063)

    clk: samsung: Fix UBSAN panic in samsung_clk_init().(CVE-2025-39728)

    x86/mm/pat: Fix VM_PAT handling when fork() fails in copy_page_range().(CVE-2025-22090)

    misc/vmw_vmci: fix an infoleak in vmci_host_do_receive_datagram().(CVE-2022-49788)

    scsi: mpt3sas: Fix NULL pointer access in mpt3sas_transport_port_add().(CVE-2023-53124)

    tracing: Fix wild-memory-access in register_synth_event().(CVE-2022-49799)

    hrtimers: Handle CPU state correctly on hotplug(CVE-2024-57951)

    block, bfq: fix uaf for bfqq in bic_set_bfqq().(CVE-2023-52983)

    tcp: Fix data-races around sysctl_tcp_max_reordering.(CVE-2022-49571)

    tcp: Fix data-races around sysctl_tcp_slow_start_after_idle.(CVE-2022-49572)

    tcp: Fix a data-race around sysctl_tcp_early_retrans.(CVE-2022-49573)

    kthread: unpark only parked kthread(CVE-2024-50019)

    media: streamzap: fix race between device disconnection and urb callback(CVE-2025-22027)

    net: openvswitch: fix flow memory leak in ovs_flow_cmd_new(CVE-2023-52977)

    efi: Do not import certificates from UEFI Secure Boot for T2 Macs(CVE-2022-49357)

    Bluetooth: fix dangling sco_conn and use-after-free in sco_sock_timeout(CVE-2022-49474)

    mmc: core: use sysfs_emit() instead of sprintf().(CVE-2022-49267)

    ext4: fix OOB read when checking dotdot dir(CVE-2025-37785)

    tcp: Fix data-races around sysctl_tcp_fastopen.(CVE-2022-49586)

    tcp: Fix a data-race around sysctl_tcp_thin_linear_timeouts.(CVE-2022-49575)

    ipv6: Fix signed integer overflow in l2tp_ip6_sendmsg(CVE-2022-49727)

    tcp: Fix a data-race around sysctl_tcp_notsent_lowat.(CVE-2022-49587)

    dlm: prevent NPD when writing a positive value to event_done(CVE-2025-23131)

    thermal: int340x: Add NULL check for adev(CVE-2025-23136)

    nfsd: don't ignore the return code of svc_proc_register().(CVE-2025-22026)

    ext4: fix out-of-bound read in ext4_xattr_inode_dec_ref_all().(CVE-2025-22121)

    ext4: avoid journaling sb update on error if journal is destroying(CVE-2025-22113)

Tenable has extracted the preceding description block directly from the EulerOS kernel 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 Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - fscrypt: stop using keyrings subsystem for fscrypt_master_key The approach of fs/crypto/ internally     managing the fscrypt_master_key structs as the payloads of struct key objects contained in a struct     key keyring has outlived its usefulness. The original idea was to simplify the code by reusing code from     the keyrings subsystem. However, several issues have arisen that can't easily be resolved: - When a master     key struct is destroyed, blk_crypto_evict_key() must be called on any per-mode keys embedded in it. (This     started being the case when inline encryption support was added.) Yet, the keyrings subsystem can     arbitrarily delay the destruction of keys, even past the time the filesystem was unmounted. Therefore,     currently there is no easy way to call blk_crypto_evict_key() when a master key is destroyed. Currently,     this is worked around by holding an extra reference to the filesystem's request_queue(s). But it was     overlooked that the request_queue reference is *not* guaranteed to pin the corresponding     blk_crypto_profile too; for device-mapper devices that support inline crypto, it doesn't. This can cause a     use-after-free. - When the last inode that was using an incompletely-removed master key is evicted, the     master key removal is completed by removing the key struct from the keyring. Currently this is done via     key_invalidate(). Yet, key_invalidate() takes the key semaphore. This can deadlock when called from the     shrinker, since in fscrypt_ioctl_add_key(), memory is allocated with GFP_KERNEL under the same semaphore.
    - More generally, the fact that the keyrings subsystem can arbitrarily delay the destruction of keys (via     garbage collection delay, or via random processes getting temporary key references) is undesirable, as it     means we can't strictly guarantee that all secrets are ever wiped. - Doing the master key lookups via the     keyrings subsystem results in the key_permission LSM hook being called. fscrypt doesn't want this, as all     access control for encrypted files is designed to happen via the files themselves, like any other files.
    The workaround which SELinux users are using is to change their SELinux policy to grant key search access     to all domains. This works, but it is an odd extra step that shouldn't really have to be done. The fix for     all these issues is to change the implementation to what I should have done originally: don't use the     keyrings subsystem to keep track of the filesystem's fscrypt_master_key structs. Instead, just store them     in a regular kernel data structure, and rework the reference counting, locking, and lifetime accordingly.
    Retain support for RCU-mode key lookups by using a hash table. Replace fscrypt_sb_free() with     fscrypt_sb_delete(), which releases the keys synchronously and runs a bit earlier during unmount, so that     block devices are still available. A side effect of this patch is that neither the master keys themselves     nor the filesystem keyrings will be listed in /proc/keys anymore. (Master key users and the master key     users keyrings will still be listed.) However, this was mostly an implementation detail, and it was     intended just for debugging purposes. I don't know of anyone using it. This patch does *not* change how     master key users (->mk_users) works; that still uses the keyrings subsystem. That is still needed for     key quotas, and changing that isn't necessary to solve the issues listed above. If we decide to change     that too, it would be a separate patch. I've marked this as fixing the original commit that added the     fscrypt keyring, but as noted above the most important issue that this patch fixes wasn't introduced until     the addition of inline encryption support. (CVE-2022-49899)

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.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)

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

    xfrm: Update ipcomp_scratches with NULL when freed (CVE-2022-50569)

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

    arm64: ftrace: fix module PLTs with mcount (CVE-2022-50579)

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

    blk-throttle: prevent overflow while calculating wait time (CVE-2022-50580)

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

    regulator: core: Prevent integer underflow (CVE-2022-50582)

    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.

The version of kernel installed on the remote host is prior to 5.15.79-51.138. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2KERNEL-5.15-2022-011 advisory.

    A vulnerability classified as problematic has been found in Linux Kernel. This affects the function     fib_nh_match of the file net/ipv4/fib_semantics.c of the component IPv4 Handler. The manipulation leads to     out-of-bounds read. It is possible to initiate the attack remotely. It is recommended to apply a patch to     fix this issue. The identifier VDB-210357 was assigned to this vulnerability. (CVE-2022-3435)

    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, which was classified as problematic, has been found in Linux Kernel. This issue affects     the function unix_sock_destructor/unix_release_sock of the file net/unix/af_unix.c of the component BPF.
    The manipulation leads to memory leak. It is recommended to apply a patch to fix this issue. The     associated identifier of this vulnerability is VDB-211043. (CVE-2022-3543)

    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 has been found in Linux Kernel and classified as problematic. This vulnerability affects     the function l2cap_recv_acldata of the file net/bluetooth/l2cap_core.c of the component Bluetooth. The     manipulation leads to memory leak. It is recommended to apply a patch to fix this issue. VDB-211918 is the     identifier assigned to this vulnerability. (CVE-2022-3619)

    A vulnerability was found in Linux Kernel. It has been declared as problematic. Affected by this     vulnerability is the function follow_page_pte of the file mm/gup.c of the component BPF. The manipulation     leads to race condition. The attack can be launched remotely. It is recommended to apply a patch to fix     this issue. The identifier VDB-211921 was assigned to this vulnerability. (CVE-2022-3623)

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

    btrfs: zoned: initialize device's zone info for seeding (CVE-2022-49831)

    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:

    btrfs: fix match incorrectly in dev_args_match_device (CVE-2022-49849)

    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:

    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:

    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:

    bpf, verifier: Fix memory leak in array reallocation for stack state (CVE-2022-49878)

    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:

    arm64: entry: avoid kprobe recursion (CVE-2022-49888)

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

    ring-buffer: Check for NULL cpu_buffer in ring_buffer_wake_waiters() (CVE-2022-49889)

    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:

    btrfs: fix tree mod log mishandling of reallocated nodes (CVE-2022-49898)

    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:

    block: Fix possible memory leak for rq_wb on add_disk failure (CVE-2022-49902)

    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/smc: Fix possible leaked pernet namespace in smc_init() (CVE-2022-49905)

    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:

    netfilter: ipset: enforce documented limit to prevent allocating huge memory (CVE-2022-49911)

    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:

    netfilter: nf_tables: netlink notifier might race to release objects (CVE-2022-49920)

    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:

    SUNRPC: Fix null-ptr-deref when xps sysfs alloc failed (CVE-2022-49928)

    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:

    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:

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

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

    net: do not sense pfmemalloc status in skb_append_pagefrags() (CVE-2022-50323)

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

    cifs: Fix xid leak in cifs_create() (CVE-2022-50351)

    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:

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

    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:

    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:

    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:

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

    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.

ID	Name	Product	Family	Severity
273529	Unity Linux 20.1070a Security Update: kernel (UTSA-2025-989619)	Nessus	Unity Linux Local Security Checks	medium
268758	Unity Linux 20.1070e Security Update: kernel (UTSA-2025-987032)	Nessus	Unity Linux Local Security Checks	medium
265114	EulerOS Virtualization 2.13.1 : kernel (EulerOS-SA-2025-2168)	Nessus	Huawei Local Security Checks	high
265107	EulerOS Virtualization 2.13.0 : kernel (EulerOS-SA-2025-2169)	Nessus	Huawei Local Security Checks	high
249320	EulerOS 2.0 SP13 : kernel (EulerOS-SA-2025-1979)	Nessus	Huawei Local Security Checks	high
249192	EulerOS 2.0 SP13 : kernel (EulerOS-SA-2025-1993)	Nessus	Huawei Local Security Checks	high
244671	Linux Distros Unpatched Vulnerability : CVE-2022-49899	Nessus	Misc.	medium
168520	Amazon Linux 2 : kernel, --advisory ALAS2KERNEL-5.10-2022-023 (ALASKERNEL-5.10-2022-023)	Nessus	Amazon Linux Local Security Checks	high
168507	Amazon Linux 2 : kernel, --advisory ALAS2KERNEL-5.15-2022-011 (ALASKERNEL-5.15-2022-011)	Nessus	Amazon Linux Local Security Checks	high

Detections

Analytics

CVE-2022-49899

medium

Tenable Plugins

medium

medium

high

high

high

high

medium

high

high