In the Linux kernel, the following vulnerability has been resolved: rxrpc: fix a race in rxrpc_exit_net() Current code can lead to the following race: CPU0 CPU1 rxrpc_exit_net() rxrpc_peer_keepalive_worker() if (rxnet->live) rxnet->live = false; del_timer_sync(&rxnet->peer_keepalive_timer); timer_reduce(&rxnet->peer_keepalive_timer, jiffies + delay); cancel_work_sync(&rxnet->peer_keepalive_work); rxrpc_exit_net() exits while peer_keepalive_timer is still armed, leading to use-after-free. syzbot report was: ODEBUG: free active (active state 0) object type: timer_list hint: rxrpc_peer_keepalive_timeout+0x0/0xb0 WARNING: CPU: 0 PID: 3660 at lib/debugobjects.c:505 debug_print_object+0x16e/0x250 lib/debugobjects.c:505 Modules linked in: CPU: 0 PID: 3660 Comm: kworker/u4:6 Not tainted 5.17.0-syzkaller-13993-g88e6c0207623 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Workqueue: netns cleanup_net RIP: 0010:debug_print_object+0x16e/0x250 lib/debugobjects.c:505 Code: ff df 48 89 fa 48 c1 ea 03 80 3c 02 00 0f 85 af 00 00 00 48 8b 14 dd 00 1c 26 8a 4c 89 ee 48 c7 c7 00 10 26 8a e8 b1 e7 28 05 <0f> 0b 83 05 15 eb c5 09 01 48 83 c4 18 5b 5d 41 5c 41 5d 41 5e c3 RSP: 0018:ffffc9000353fb00 EFLAGS: 00010082 RAX: 0000000000000000 RBX: 0000000000000003 RCX: 0000000000000000 RDX: ffff888029196140 RSI: ffffffff815efad8 RDI: fffff520006a7f52 RBP: 0000000000000001 R08: 0000000000000000 R09: 0000000000000000 R10: ffffffff815ea4ae R11: 0000000000000000 R12: ffffffff89ce23e0 R13: ffffffff8a2614e0 R14: ffffffff816628c0 R15: dffffc0000000000 FS: 0000000000000000(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fe1f2908924 CR3: 0000000043720000 CR4: 00000000003506f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> __debug_check_no_obj_freed lib/debugobjects.c:992 [inline] debug_check_no_obj_freed+0x301/0x420 lib/debugobjects.c:1023 kfree+0xd6/0x310 mm/slab.c:3809 ops_free_list.part.0+0x119/0x370 net/core/net_namespace.c:176 ops_free_list net/core/net_namespace.c:174 [inline] cleanup_net+0x591/0xb00 net/core/net_namespace.c:598 process_one_work+0x996/0x1610 kernel/workqueue.c:2289 worker_thread+0x665/0x1080 kernel/workqueue.c:2436 kthread+0x2e9/0x3a0 kernel/kthread.c:376 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298 </TASK>

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

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

    rxrpc: fix a race in rxrpc_exit_net()

    Current code can lead to the following race:

    CPU0                                                 CPU1

    rxrpc_exit_net()                                                          rxrpc_peer_keepalive_worker()                                                            if (rxnet->live)

      rxnet->live = false;
      del_timer_sync(&rxnet->peer_keepalive_timer);

                                                                 timer_reduce(&rxnet->peer_keepalive_timer,     jiffies + delay);

      cancel_work_sync(&rxnet->peer_keepalive_work);

    rxrpc_exit_net() exits while peer_keepalive_timer is still armed,     leading to use-after-free.

    syzbot report was:

    ODEBUG: free active (active state 0) object type: timer_list hint: rxrpc_peer_keepalive_timeout+0x0/0xb0     WARNING: CPU: 0 PID: 3660 at lib/debugobjects.c:505 debug_print_object+0x16e/0x250 lib/debugobjects.c:505     Modules linked in:
    CPU: 0 PID: 3660 Comm: kworker/u4:6 Not tainted 5.17.0-syzkaller-13993-g88e6c0207623 #0     Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011     Workqueue: netns cleanup_net     RIP: 0010:debug_print_object+0x16e/0x250 lib/debugobjects.c:505     Code: ff df 48 89 fa 48 c1 ea 03 80 3c 02 00 0f 85 af 00 00 00 48 8b 14 dd 00 1c 26 8a 4c 89 ee 48 c7 c7     00 10 26 8a e8 b1 e7 28 05 <0f> 0b 83 05 15 eb c5 09 01 48 83 c4 18 5b 5d 41 5c 41 5d 41 5e c3     RSP: 0018:ffffc9000353fb00 EFLAGS: 00010082     RAX: 0000000000000000 RBX: 0000000000000003 RCX: 0000000000000000     RDX: ffff888029196140 RSI: ffffffff815efad8 RDI: fffff520006a7f52     RBP: 0000000000000001 R08: 0000000000000000 R09: 0000000000000000     R10: ffffffff815ea4ae R11: 0000000000000000 R12: ffffffff89ce23e0     R13: ffffffff8a2614e0 R14: ffffffff816628c0 R15: dffffc0000000000     FS:  0000000000000000(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000     CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033     CR2: 00007fe1f2908924 CR3: 0000000043720000 CR4: 00000000003506f0     DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000     DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400     Call Trace:
     <TASK>
     __debug_check_no_obj_freed lib/debugobjects.c:992 [inline]      debug_check_no_obj_freed+0x301/0x420 lib/debugobjects.c:1023      kfree+0xd6/0x310 mm/slab.c:3809      ops_free_list.part.0+0x119/0x370 net/core/net_namespace.c:176      ops_free_list net/core/net_namespace.c:174 [inline]      cleanup_net+0x591/0xb00 net/core/net_namespace.c:598      process_one_work+0x996/0x1610 kernel/workqueue.c:2289      worker_thread+0x665/0x1080 kernel/workqueue.c:2436      kthread+0x2e9/0x3a0 kernel/kthread.c:376      ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298      </TASK>

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-986721 advisory.

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

    rxrpc: fix a race in rxrpc_exit_net()

    Current code can lead to the following race:

    CPU0                                                 CPU1

    rxrpc_exit_net()                                                          rxrpc_peer_keepalive_worker()                                                            if (rxnet->live)

      rxnet->live = false;
      del_timer_sync(&rxnet->peer_keepalive_timer);

                                                                 timer_reduce(&rxnet->peer_keepalive_timer,     jiffies + delay);

      cancel_work_sync(&rxnet->peer_keepalive_work);

    rxrpc_exit_net() exits while peer_keepalive_timer is still armed,     leading to use-after-free.

    syzbot report was:

    ODEBUG: free active (active state 0) object type: timer_list hint: rxrpc_peer_keepalive_timeout+0x0/0xb0     WARNING: CPU: 0 PID: 3660 at lib/debugobjects.c:505 debug_print_object+0x16e/0x250 lib/debugobjects.c:505     Modules linked in:
    CPU: 0 PID: 3660 Comm: kworker/u4:6 Not tainted 5.17.0-syzkaller-13993-g88e6c0207623 #0     Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011     Workqueue: netns cleanup_net     RIP: 0010:debug_print_object+0x16e/0x250 lib/debugobjects.c:505     Code: ff df 48 89 fa 48 c1 ea 03 80 3c 02 00 0f 85 af 00 00 00 48 8b 14 dd 00 1c 26 8a 4c 89 ee 48 c7 c7     00 10 26 8a e8 b1 e7 28 05 <0f> 0b 83 05 15 eb c5 09 01 48 83 c4 18 5b 5d 41 5c 41 5d 41 5e c3     RSP: 0018:ffffc9000353fb00 EFLAGS: 00010082     RAX: 0000000000000000 RBX: 0000000000000003 RCX: 0000000000000000     RDX: ffff888029196140 RSI: ffffffff815efad8 RDI: fffff520006a7f52     RBP: 0000000000000001 R08: 0000000000000000 R09: 0000000000000000     R10: ffffffff815ea4ae R11: 0000000000000000 R12: ffffffff89ce23e0     R13: ffffffff8a2614e0 R14: ffffffff816628c0 R15: dffffc0000000000     FS:  0000000000000000(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000     CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033     CR2: 00007fe1f2908924 CR3: 0000000043720000 CR4: 00000000003506f0     DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000     DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400     Call Trace:
     <TASK>
     __debug_check_no_obj_freed lib/debugobjects.c:992 [inline]      debug_check_no_obj_freed+0x301/0x420 lib/debugobjects.c:1023      kfree+0xd6/0x310 mm/slab.c:3809      ops_free_list.part.0+0x119/0x370 net/core/net_namespace.c:176      ops_free_list net/core/net_namespace.c:174 [inline]      cleanup_net+0x591/0xb00 net/core/net_namespace.c:598      process_one_work+0x996/0x1610 kernel/workqueue.c:2289      worker_thread+0x665/0x1080 kernel/workqueue.c:2436      kthread+0x2e9/0x3a0 kernel/kthread.c:376      ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298      </TASK>

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 Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - In the Linux kernel, the following vulnerability has been resolved: rxrpc: fix a race in rxrpc_exit_net()     Current code can lead to the following race: CPU0 CPU1 rxrpc_exit_net() rxrpc_peer_keepalive_worker() if     (rxnet->live) rxnet->live = false; del_timer_sync(&rxnet->peer_keepalive_timer);
    timer_reduce(&rxnet->peer_keepalive_timer, jiffies + delay);
    cancel_work_sync(&rxnet->peer_keepalive_work); rxrpc_exit_net() exits while peer_keepalive_timer is still     armed, leading to use-after-free. syzbot report was: ODEBUG: free active (active state 0) object type:
    timer_list hint: rxrpc_peer_keepalive_timeout+0x0/0xb0 WARNING: CPU: 0 PID: 3660 at lib/debugobjects.c:505     debug_print_object+0x16e/0x250 lib/debugobjects.c:505 Modules linked in: CPU: 0 PID: 3660 Comm:
    kworker/u4:6 Not tainted 5.17.0-syzkaller-13993-g88e6c0207623 #0 Hardware name: Google Google Compute     Engine/Google Compute Engine, BIOS Google 01/01/2011 Workqueue: netns cleanup_net RIP:
    0010:debug_print_object+0x16e/0x250 lib/debugobjects.c:505 Code: ff df 48 89 fa 48 c1 ea 03 80 3c 02 00 0f     85 af 00 00 00 48 8b 14 dd 00 1c 26 8a 4c 89 ee 48 c7 c7 00 10 26 8a e8 b1 e7 28 05 <0f> 0b 83 05 15 eb c5     09 01 48 83 c4 18 5b 5d 41 5c 41 5d 41 5e c3 RSP: 0018:ffffc9000353fb00 EFLAGS: 00010082 RAX:
    0000000000000000 RBX: 0000000000000003 RCX: 0000000000000000 RDX: ffff888029196140 RSI: ffffffff815efad8     RDI: fffff520006a7f52 RBP: 0000000000000001 R08: 0000000000000000 R09: 0000000000000000 R10:
    ffffffff815ea4ae R11: 0000000000000000 R12: ffffffff89ce23e0 R13: ffffffff8a2614e0 R14: ffffffff816628c0     R15: dffffc0000000000 FS: 0000000000000000(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000 CS: 0010     DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fe1f2908924 CR3: 0000000043720000 CR4: 00000000003506f0     DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6:
    00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> __debug_check_no_obj_freed     lib/debugobjects.c:992 [inline] debug_check_no_obj_freed+0x301/0x420 lib/debugobjects.c:1023     kfree+0xd6/0x310 mm/slab.c:3809 ops_free_list.part.0+0x119/0x370 net/core/net_namespace.c:176     ops_free_list net/core/net_namespace.c:174 [inline] cleanup_net+0x591/0xb00 net/core/net_namespace.c:598     process_one_work+0x996/0x1610 kernel/workqueue.c:2289 worker_thread+0x665/0x1080 kernel/workqueue.c:2436     kthread+0x2e9/0x3a0 kernel/kthread.c:376 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298 </TASK>     (CVE-2022-49087)

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.190-107.353. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2KERNEL-5.4-2024-076 advisory.

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

    ubi: Fix race condition between ctrl_cdev_ioctl and ubi_cdev_ioctl (CVE-2021-47634)

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

    Revert Revert block, bfq: honor already-setup queue merges (CVE-2021-47646)

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

    ASoC: soc-compress: prevent the potentially use of null pointer (CVE-2021-47650)

    When the KVM updates the guest's page table entry, it will first use get_user_pages_fast() to pin the     page, and when it fails (e.g. the vma->flags has VM_IO or VM_PFNMAP), it will get corresponding VMA where     the page lies in through find_vma_intersection(), calculate the physical address, and map the page to the     kernel virtual address through memremap(), and finally, write the update.The problem is that when we get     the vma through find_vma_intersection(), only VM_PFNMAP is checked, not both VM_IO and VM_PFNMAP. In the     reproducer below, after the KVM_SET_USER_MEMORY_REGION is completed, we replace the guest's memory mapping     with the kernel-user shared region of io_uring and then perform the KVM_TRANSLATE operation, which finally     triggers the page table entry update. Now, memremap() will return page_offset_base (direct mapping of all     physical memory) + vaddr (the linear address of KVM_TRANSLATE) + vm_pgoff (the offset when io_uring     performs mmap(2)), and use the return value as the base address for CMPXCHG (write 0x21 in this case).
    Since both vaddr and vm_pgoff are controllable by the user-mode process, writing may exceed the previously     mapped guest memory space and trigger exceptions such as UAF. The vulnerability shares similarities with     CVE-2021-22543. (CVE-2022-1158)

    A vulnerability was found in the pfkey_register function in net/key/af_key.c in the Linux kernel. This     flaw allows a local, unprivileged user to gain access to kernel memory, leading to a system crash or a     leak of internal kernel information. (CVE-2022-1353)

    A flaw was found in the Linux kernel implementation of proxied virtualized TPM devices. On a system where     virtualized TPM devices are configured (this is not the default) a local attacker can create a use-after-     free and create a situation where it may be possible to escalate privileges on the system. (CVE-2022-2977)

    A flaw was found in the Linux kernel. A NULL pointer dereference may occur while a slip driver is in     progress to detach in sl_tx_timeout in drivers/net/slip/slip.c. This issue could allow an attacker to     crash the system or leak internal kernel information. (CVE-2022-41858)

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

    swiotlb: fix info leak with DMA_FROM_DEVICE (CVE-2022-48853)

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

    dm integrity: fix memory corruption when tag_size is less than digest size (CVE-2022-49044)

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

    ipv6: fix panic when forwarding a pkt with no in6 dev (CVE-2022-49048)

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

    scsi: target: tcmu: Fix possible page UAF (CVE-2022-49053)

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

    cifs: potential buffer overflow in handling symlinks (CVE-2022-49058)

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

    veth: Ensure eth header is in skb's linear part (CVE-2022-49066)

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

    ata: sata_dwc_460ex: Fix crash due to OOB write (CVE-2022-49073)

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

    irqchip/gic-v3: Fix GICR_CTLR.RWP polling (CVE-2022-49074)

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

    btrfs: fix qgroup reserve overflow the qgroup limit (CVE-2022-49075)

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

    mmmremap.c: avoid pointless invalidate_range_start/end on mremap(old_size=0) (CVE-2022-49077)

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

    lz4: fix LZ4_decompress_safe_partial read out of bound (CVE-2022-49078)

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

    mm/mempolicy: fix mpol_new leak in shared_policy_replace (CVE-2022-49080)

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

    qede: confirm skb is allocated before using (CVE-2022-49084)

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

    drbd: Fix five use after free bugs in get_initial_state (CVE-2022-49085)

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

    rxrpc: fix a race in rxrpc_exit_net() (CVE-2022-49087)

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

    net: ipv4: fix route with nexthop object delete warning (CVE-2022-49092)

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

    net/tls: fix slab-out-of-bounds bug in decrypt_internal (CVE-2022-49094)

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

    Drivers: hv: vmbus: Fix potential crash on module unload (CVE-2022-49098)

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

    virtio_console: eliminate anonymous module_init & module_exit (CVE-2022-49100)

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

    scsi: libfc: Fix use after free in fc_exch_abts_resp() (CVE-2022-49114)

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

    dm ioctl: prevent potential spectre v1 gadget (CVE-2022-49122)

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

    ACPI: CPPC: Avoid out of bounds access when parsing _CPC data (CVE-2022-49145)

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

    scsi: qla2xxx: Suppress a kernel complaint in qla_create_qpair() (CVE-2022-49155)

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

    ntfs: add sanity check on allocation size (CVE-2022-49166)

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

    ext4: don't BUG if someone dirty pages without asking ext4 first (CVE-2022-49171)

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

    PM: core: keep irq flags in device_pm_check_callbacks() (CVE-2022-49175)

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

    bfq: fix use-after-free in bfq_dispatch_request (CVE-2022-49176)

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

    block, bfq: don't move oom_bfqq (CVE-2022-49179)

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

    LSM: general protection fault in legacy_parse_param (CVE-2022-49180)

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

    af_netlink: Fix shift out of bounds in group mask calculation (CVE-2022-49197)

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

    bpf, sockmap: Fix more uncharged while msg has more_data (CVE-2022-49204)

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

    bpf, sockmap: Fix double uncharge the mem of sk_msg (CVE-2022-49205)

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

    RDMA/mlx5: Fix memory leak in error flow for subscribe event routine (CVE-2022-49206)

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

    bpf, sockmap: Fix memleak in tcp_bpf_sendmsg while sk msg is full (CVE-2022-49209)

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

    dax: make sure inodes are flushed before destroy cache (CVE-2022-49220)

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

    power: supply: ab8500: Fix memory leak in ab8500_fg_sysfs_init (CVE-2022-49224)

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

    block: don't delete queue kobject before its children (CVE-2022-49259)

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

    NFSD: prevent integer overflow on 32 bit systems (CVE-2022-49279)

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

    NFSD: prevent underflow in nfssvc_decode_writeargs() (CVE-2022-49280)

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

    tpm: fix reference counting for struct tpm_chip (CVE-2022-49287)

    A flaw that boot CPU could be vulnerable for the speculative execution behavior kind of attacks in the     Linux kernel X86 CPU Power management options functionality was found in the way user resuming CPU from     suspend-to-RAM. A local user could use this flaw to potentially get unauthorized access to some memory of     the CPU similar to the speculative execution behavior kind of attacks. (CVE-2023-1637)

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.112-108.499. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2KERNEL-5.10-2023-036 advisory.

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

    ubi: Fix race condition between ctrl_cdev_ioctl and ubi_cdev_ioctl (CVE-2021-47634)

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

    Revert Revert block, bfq: honor already-setup queue merges (CVE-2021-47646)

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

    ASoC: soc-compress: prevent the potentially use of null pointer (CVE-2021-47650)

    A denial of service (DOS) issue was found in the Linux kernel's smb2_ioctl_query_info function in     the fs/cifs/smb2ops.c Common Internet File System (CIFS) due to an incorrect return from the memdup_user     function. This flaw allows a local, privileged (CAP_SYS_ADMIN) attacker to crash the system.
    (CVE-2022-0168)

    When the KVM updates the guest's page table entry, it will first use get_user_pages_fast() to pin the     page, and when it fails (e.g. the vma->flags has VM_IO or VM_PFNMAP), it will get corresponding VMA where     the page lies in through find_vma_intersection(), calculate the physical address, and map the page to the     kernel virtual address through memremap(), and finally, write the update.The problem is that when we get     the vma through find_vma_intersection(), only VM_PFNMAP is checked, not both VM_IO and VM_PFNMAP. In the     reproducer below, after the KVM_SET_USER_MEMORY_REGION is completed, we replace the guest's memory mapping     with the kernel-user shared region of io_uring and then perform the KVM_TRANSLATE operation, which finally     triggers the page table entry update. Now, memremap() will return page_offset_base (direct mapping of all     physical memory) + vaddr (the linear address of KVM_TRANSLATE) + vm_pgoff (the offset when io_uring     performs mmap(2)), and use the return value as the base address for CMPXCHG (write 0x21 in this case).
    Since both vaddr and vm_pgoff are controllable by the user-mode process, writing may exceed the previously     mapped guest memory space and trigger exceptions such as UAF. The vulnerability shares similarities with     CVE-2021-22543. (CVE-2022-1158)

    A vulnerability was found in the pfkey_register function in net/key/af_key.c in the Linux kernel. This     flaw allows a local, unprivileged user to gain access to kernel memory, leading to a system crash or a     leak of internal kernel information. (CVE-2022-1353)

    A use-after-free flaw was found in the Linux kernel's io_uring interface subsystem in the way a user     triggers a race condition between timeout flush and removal. This flaw allows a local user to crash or     escalate their privileges on the system. (CVE-2022-29582)

    A flaw was found in the Linux kernel implementation of proxied virtualized TPM devices. On a system where     virtualized TPM devices are configured (this is not the default) a local attacker can create a use-after-     free and create a situation where it may be possible to escalate privileges on the system. (CVE-2022-2977)

    A flaw was found in the Linux kernel. A NULL pointer dereference may occur while a slip driver is in     progress to detach in sl_tx_timeout in drivers/net/slip/slip.c. This issue could allow an attacker to     crash the system or leak internal kernel information. (CVE-2022-41858)

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

    swiotlb: fix info leak with DMA_FROM_DEVICE (CVE-2022-48853)

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

    dm integrity: fix memory corruption when tag_size is less than digest size (CVE-2022-49044)

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

    ipv6: fix panic when forwarding a pkt with no in6 dev (CVE-2022-49048)

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

    mm: fix unexpected zeroed page mapping with zram swap (CVE-2022-49052)

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

    scsi: target: tcmu: Fix possible page UAF (CVE-2022-49053)

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

    cifs: potential buffer overflow in handling symlinks (CVE-2022-49058)

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

    SUNRPC: Fix the svc_deferred_event trace class (CVE-2022-49065)

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

    veth: Ensure eth header is in skb's linear part (CVE-2022-49066)

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

    gpio: Restrict usage of GPIO chip irq members before initialization (CVE-2022-49072)

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

    ata: sata_dwc_460ex: Fix crash due to OOB write (CVE-2022-49073)

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

    irqchip/gic-v3: Fix GICR_CTLR.RWP polling (CVE-2022-49074)

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

    btrfs: fix qgroup reserve overflow the qgroup limit (CVE-2022-49075)

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

    mmmremap.c: avoid pointless invalidate_range_start/end on mremap(old_size=0) (CVE-2022-49077)

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

    lz4: fix LZ4_decompress_safe_partial read out of bound (CVE-2022-49078)

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

    mm/mempolicy: fix mpol_new leak in shared_policy_replace (CVE-2022-49080)

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

    qede: confirm skb is allocated before using (CVE-2022-49084)

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

    drbd: Fix five use after free bugs in get_initial_state (CVE-2022-49085)

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

    net: openvswitch: fix leak of nested actions (CVE-2022-49086)

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

    rxrpc: fix a race in rxrpc_exit_net() (CVE-2022-49087)

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

    net: ipv4: fix route with nexthop object delete warning (CVE-2022-49092)

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

    net/tls: fix slab-out-of-bounds bug in decrypt_internal (CVE-2022-49094)

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

    NFS: Avoid writeback threads getting stuck in mempool_alloc() (CVE-2022-49097)

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

    Drivers: hv: vmbus: Fix potential crash on module unload (CVE-2022-49098)

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

    virtio_console: eliminate anonymous module_init & module_exit (CVE-2022-49100)

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

    NFSv4.2: fix reference count leaks in _nfs42_proc_copy_notify() (CVE-2022-49103)

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

    ceph: fix memory leak in ceph_readdir when note_last_dentry returns error (CVE-2022-49107)

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

    scsi: libfc: Fix use after free in fc_exch_abts_resp() (CVE-2022-49114)

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

    dm ioctl: prevent potential spectre v1 gadget (CVE-2022-49122)

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

    io_uring: fix memory leak of uid in files registration (CVE-2022-49144)

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

    ACPI: CPPC: Avoid out of bounds access when parsing _CPC data (CVE-2022-49145)

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

    watch_queue: Free the page array when watch_queue is dismantled (CVE-2022-49148)

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

    rxrpc: Fix call timer start racing with call destruction (CVE-2022-49149)

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

    wireguard: socket: free skb in send6 when ipv6 is disabled (CVE-2022-49153)

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

    KVM: SVM: fix panic on out-of-bounds guest IRQ (CVE-2022-49154)

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

    scsi: qla2xxx: Suppress a kernel complaint in qla_create_qpair() (CVE-2022-49155)

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

    scsi: qla2xxx: Fix scheduling while atomic (CVE-2022-49156)

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

    ext4: don't BUG if someone dirty pages without asking ext4 first (CVE-2022-49171)

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

    ext4: fix ext4_mb_mark_bb() with flex_bg with fast_commit (CVE-2022-49174)

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

    PM: core: keep irq flags in device_pm_check_callbacks() (CVE-2022-49175)

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

    bfq: fix use-after-free in bfq_dispatch_request (CVE-2022-49176)

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

    block, bfq: don't move oom_bfqq (CVE-2022-49179)

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

    LSM: general protection fault in legacy_parse_param (CVE-2022-49180)

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

    af_netlink: Fix shift out of bounds in group mask calculation (CVE-2022-49197)

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

    bpf, sockmap: Fix more uncharged while msg has more_data (CVE-2022-49204)

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

    bpf, sockmap: Fix double uncharge the mem of sk_msg (CVE-2022-49205)

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

    RDMA/mlx5: Fix memory leak in error flow for subscribe event routine (CVE-2022-49206)

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

    bpf, sockmap: Fix memleak in tcp_bpf_sendmsg while sk msg is full (CVE-2022-49209)

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

    MIPS: pgalloc: fix memory leak caused by pgd_free() (CVE-2022-49210)

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

    dax: make sure inodes are flushed before destroy cache (CVE-2022-49220)

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

    power: supply: ab8500: Fix memory leak in ab8500_fg_sysfs_init (CVE-2022-49224)

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

    watch_queue: Actually free the watch (CVE-2022-49256)

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

    watch_queue: Fix NULL dereference in error cleanup (CVE-2022-49257)

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

    block: don't delete queue kobject before its children (CVE-2022-49259)

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

    drm/i915/gem: add missing boundary check in vm_access (CVE-2022-49261)

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

    exec: Force single empty string when argv is empty (CVE-2022-49264)

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

    cifs: prevent bad output lengths in smb2_ioctl_query_info() (CVE-2022-49271)

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

    ALSA: pcm: Fix potential AB/BA lock with buffer_mutex and mmap_lock (CVE-2022-49272)

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

    NFSD: prevent integer overflow on 32 bit systems (CVE-2022-49279)

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

    NFSD: prevent underflow in nfssvc_decode_writeargs() (CVE-2022-49280)

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

    tpm: fix reference counting for struct tpm_chip (CVE-2022-49287)

    A use-after-free flaw was found in the Linux kernel's core dump subsystem. This flaw could allow a local     user to crash the system. (CVE-2023-1249)

    A flaw that boot CPU could be vulnerable for the speculative execution behavior kind of attacks in the     Linux kernel X86 CPU Power management options functionality was found in the way user resuming CPU from     suspend-to-RAM. A local user could use this flaw to potentially get unauthorized access to some memory of     the CPU similar to the speculative execution behavior kind of attacks. (CVE-2023-1637)

    Improper restriction of operations within the bounds of a memory buffer in some Intel(R) i915 Graphics     drivers for linux before kernel version 6.2.10 may allow an authenticated user to potentially enable     escalation of privilege via local access. (CVE-2023-28410)

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 remote Redhat Enterprise Linux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2023:2458 advisory.

    The kernel packages contain the Linux kernel, the core of any Linux operating system.

    Security Fix(es):

    * use-after-free in l2cap_connect and l2cap_le_connect_req in net/bluetooth/l2cap_core.c (CVE-2022-42896)

    * net/ulp: use-after-free in listening ULP sockets (CVE-2023-0461)

    * cpu: AMD CPUs may transiently execute beyond unconditional direct branch (CVE-2021-26341)

    * malicious data for FBIOPUT_VSCREENINFO ioctl may cause OOB write memory (CVE-2021-33655)

    * possible race condition in drivers/tty/tty_buffers.c (CVE-2022-1462)

    * KVM: NULL pointer dereference in kvm_mmu_invpcid_gva (CVE-2022-1789)

    * use-after-free in free_pipe_info() could lead to privilege escalation (CVE-2022-1882)

    * KVM: nVMX: missing IBPB when exiting from nested guest can lead to Spectre v2 attacks (CVE-2022-2196)

    * netfilter: nf_conntrack_irc message handling issue (CVE-2022-2663)

    * race condition in xfrm_probe_algs can lead to OOB read/write (CVE-2022-3028)

    * out-of-bounds read in fib_nh_match of the file net/ipv4/fib_semantics.c (CVE-2022-3435)

    * race condition in hugetlb_no_page() in mm/hugetlb.c (CVE-2022-3522)

    * memory leak in ipv6_renew_options() (CVE-2022-3524)

    * data races around icsk->icsk_af_ops in do_ipv6_setsockopt (CVE-2022-3566)

    * data races around sk->sk_prot (CVE-2022-3567)

    * memory leak in l2cap_recv_acldata of the file net/bluetooth/l2cap_core.c (CVE-2022-3619)

    * denial of service in follow_page_pte in mm/gup.c due to poisoned pte entry (CVE-2022-3623)

    * use-after-free after failed devlink reload in devlink_param_get (CVE-2022-3625)

    * USB-accessible buffer overflow in brcmfmac (CVE-2022-3628)

    * use after free flaw in l2cap_conn_del in net/bluetooth/l2cap_core.c (CVE-2022-3640)

    * Double-free in split_2MB_gtt_entry when function intel_gvt_dma_map_guest_page failed (CVE-2022-3707)

    * mptcp: NULL pointer dereference in subflow traversal at disconnect time (CVE-2022-4128)

    * l2tp: missing lock when clearing sk_user_data can lead to NULL pointer dereference (CVE-2022-4129)

    * igmp: use-after-free in ip_check_mc_rcu when opening and closing inet sockets (CVE-2022-20141)

    * lockdown bypass using IMA (CVE-2022-21505)

    * double free in usb_8dev_start_xmit in drivers/net/can/usb/usb_8dev.c (CVE-2022-28388)

    * network backend may cause Linux netfront to use freed SKBs (XSA-405) (CVE-2022-33743)

    * unmap_mapping_range() race with munmap() on VM_PFNMAP mappings leads to stale TLB entry (CVE-2022-39188)

    * TLB flush operations are mishandled in certain KVM_VCPU_PREEMPTED leading to guest malfunctioning     (CVE-2022-39189)

    * u8 overflow problem in cfg80211_update_notlisted_nontrans() (CVE-2022-41674)

    * use-after-free related to leaf anon_vma double reuse (CVE-2022-42703)

    * use-after-free in bss_ref_get in net/wireless/scan.c (CVE-2022-42720)

    * BSS list corruption in cfg80211_add_nontrans_list in net/wireless/scan.c (CVE-2022-42721)

    * Denial of service in beacon protection for P2P-device (CVE-2022-42722)

    * memory corruption in usbmon driver (CVE-2022-43750)

    * NULL pointer dereference in traffic control subsystem (CVE-2022-47929)

    * NULL pointer dereference in rawv6_push_pending_frames (CVE-2023-0394)

    * use-after-free due to race condition in qdisc_graft() (CVE-2023-0590)

    * use-after-free caused by invalid pointer hostname in fs/cifs/connect.c (CVE-2023-1195)

    * denial of service in tipc_conn_close (CVE-2023-1382)

    For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and     other related information, refer to the CVE page(s) listed in the References section.

    Additional Changes:

    For detailed information on changes in this release, see the Red Hat Enterprise Linux 9.2 Release Notes     linked from the References section.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux 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
272828	Unity Linux 20.1070a Security Update: kernel (UTSA-2025-989107)	Nessus	Unity Linux Local Security Checks	high
269132	Unity Linux 20.1070e Security Update: kernel (UTSA-2025-986721)	Nessus	Unity Linux Local Security Checks	high
225297	Linux Distros Unpatched Vulnerability : CVE-2022-49087	Nessus	Misc.	high
206247	Amazon Linux 2 : kernel (ALASKERNEL-5.4-2024-076)	Nessus	Amazon Linux Local Security Checks	high
180564	Amazon Linux 2 : kernel (ALASKERNEL-5.10-2023-036)	Nessus	Amazon Linux Local Security Checks	high
175477	RHEL 9 : kernel (RHSA-2023:2458)	Nessus	Red Hat Local Security Checks	high

Detections

Analytics

CVE-2022-49087

high

Tenable Plugins

high

high

high

high

high

high