In the Linux kernel, the following vulnerability has been resolved: ext4: fix bug_on in __es_tree_search caused by bad quota inode We got a issue as fllows: ================================================================== kernel BUG at fs/ext4/extents_status.c:202! invalid opcode: 0000 [#1] PREEMPT SMP CPU: 1 PID: 810 Comm: mount Not tainted 6.1.0-rc1-next-g9631525255e3 #352 RIP: 0010:__es_tree_search.isra.0+0xb8/0xe0 RSP: 0018:ffffc90001227900 EFLAGS: 00010202 RAX: 0000000000000000 RBX: 0000000077512a0f RCX: 0000000000000000 RDX: 0000000000000002 RSI: 0000000000002a10 RDI: ffff8881004cd0c8 RBP: ffff888177512ac8 R08: 47ffffffffffffff R09: 0000000000000001 R10: 0000000000000001 R11: 00000000000679af R12: 0000000000002a10 R13: ffff888177512d88 R14: 0000000077512a10 R15: 0000000000000000 FS: 00007f4bd76dbc40(0000)GS:ffff88842fd00000(0000)knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00005653bf993cf8 CR3: 000000017bfdf000 CR4: 00000000000006e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> ext4_es_cache_extent+0xe2/0x210 ext4_cache_extents+0xd2/0x110 ext4_find_extent+0x5d5/0x8c0 ext4_ext_map_blocks+0x9c/0x1d30 ext4_map_blocks+0x431/0xa50 ext4_getblk+0x82/0x340 ext4_bread+0x14/0x110 ext4_quota_read+0xf0/0x180 v2_read_header+0x24/0x90 v2_check_quota_file+0x2f/0xa0 dquot_load_quota_sb+0x26c/0x760 dquot_load_quota_inode+0xa5/0x190 ext4_enable_quotas+0x14c/0x300 __ext4_fill_super+0x31cc/0x32c0 ext4_fill_super+0x115/0x2d0 get_tree_bdev+0x1d2/0x360 ext4_get_tree+0x19/0x30 vfs_get_tree+0x26/0xe0 path_mount+0x81d/0xfc0 do_mount+0x8d/0xc0 __x64_sys_mount+0xc0/0x160 do_syscall_64+0x35/0x80 entry_SYSCALL_64_after_hwframe+0x63/0xcd </TASK> ================================================================== Above issue may happen as follows: ------------------------------------- ext4_fill_super ext4_orphan_cleanup ext4_enable_quotas ext4_quota_enable ext4_iget --> get error inode <5> ext4_ext_check_inode --> Wrong imode makes it escape inspection make_bad_inode(inode) --> EXT4_BOOT_LOADER_INO set imode dquot_load_quota_inode vfs_setup_quota_inode --> check pass dquot_load_quota_sb v2_check_quota_file v2_read_header ext4_quota_read ext4_bread ext4_getblk ext4_map_blocks ext4_ext_map_blocks ext4_find_extent ext4_cache_extents ext4_es_cache_extent __es_tree_search.isra.0 ext4_es_end --> Wrong extents trigger BUG_ON In the above issue, s_usr_quota_inum is set to 5, but inode<5> contains incorrect imode and disordered extents. Because 5 is EXT4_BOOT_LOADER_INO, the ext4_ext_check_inode check in the ext4_iget function can be bypassed, finally, the extents that are not checked trigger the BUG_ON in the __es_tree_search function. To solve this issue, check whether the inode is bad_inode in vfs_setup_quota_inode().

The AlmaLinux 9.2 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare ALMALINUX9.2:CLSA-2025:1762171389 advisory.

  - In the Linux kernel, the following vulnerability has been resolved: ext4: add EXT4_IGET_BAD flag to     prevent unexpected bad inode There are many places that will get unhappy (and crash) when ext4_iget()     returns a bad inode. However, if iget the boot loader inode, allows a bad inode to be returned, because     the inode may not be initialized. This mechanism can be used to bypass some checks and cause panic. To     solve this problem, we add a special iget flag EXT4_IGET_BAD. Only with this flag we'd be returning bad     inode from ext4_iget(), otherwise we always return the error code if the inode is bad inode.(suggested by     Jan Kara) (CVE-2022-50485)

  - In the Linux kernel, the following vulnerability has been resolved: ext4: fix bug_on in __es_tree_search     caused by bad boot loader inode We got a issue as fllows:
    ================================================================== kernel BUG at     fs/ext4/extents_status.c:203! invalid opcode: 0000 [#1] PREEMPT SMP CPU: 1 PID: 945 Comm: cat Not tainted     6.0.0-next-20221007-dirty #349 RIP: 0010:ext4_es_end.isra.0+0x34/0x42 RSP: 0018:ffffc9000143b768 EFLAGS:
    00010203 RAX: 0000000000000000 RBX: ffff8881769cd0b8 RCX: 0000000000000000 RDX: 0000000000000000 RSI:
    ffffffff8fc27cf7 RDI: 00000000ffffffff RBP: ffff8881769cd0bc R08: 0000000000000000 R09: ffffc9000143b5f8     R10: 0000000000000001 R11: 0000000000000001 R12: ffff8881769cd0a0 R13: ffff8881768e5668 R14:
    00000000768e52f0 R15: 0000000000000000 FS:
    00007f359f7f05c0(0000)GS:ffff88842fd00000(0000)knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0:
    0000000080050033 CR2: 00007f359f5a2000 CR3: 000000017130c000 CR4: 00000000000006e0 DR0: 0000000000000000     DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7:
    0000000000000400 Call Trace: <TASK> __es_tree_search.isra.0+0x6d/0xf5 ext4_es_cache_extent+0xfa/0x230     ext4_cache_extents+0xd2/0x110 ext4_find_extent+0x5d5/0x8c0 ext4_ext_map_blocks+0x9c/0x1d30     ext4_map_blocks+0x431/0xa50 ext4_mpage_readpages+0x48e/0xe40 ext4_readahead+0x47/0x50     read_pages+0x82/0x530 page_cache_ra_unbounded+0x199/0x2a0 do_page_cache_ra+0x47/0x70     page_cache_ra_order+0x242/0x400 ondemand_readahead+0x1e8/0x4b0 page_cache_sync_ra+0xf4/0x110     filemap_get_pages+0x131/0xb20 filemap_read+0xda/0x4b0 generic_file_read_iter+0x13a/0x250     ext4_file_read_iter+0x59/0x1d0 vfs_read+0x28f/0x460 ksys_read+0x73/0x160 __x64_sys_read+0x1e/0x30     do_syscall_64+0x35/0x80 entry_SYSCALL_64_after_hwframe+0x63/0xcd </TASK>     ================================================================== In the above issue, ioctl invokes the     swap_inode_boot_loader function to swap inode<5> and inode<12>. However, inode<5> contain incorrect imode     and disordered extents, and i_nlink is set to 1. The extents check for inode in the ext4_iget function can     be bypassed bacause 5 is EXT4_BOOT_LOADER_INO. While links_count is set to 1, the extents are not     initialized in swap_inode_boot_loader. After the ioctl command is executed successfully, the extents are     swapped to inode<12>, in this case, run the `cat` command to view inode<12>. And Bug_ON is triggered due     to the incorrect extents. When the boot loader inode is not initialized, its imode can be one of the     following: 1) the imode is a bad type, which is marked as bad_inode in ext4_iget and set to S_IFREG. 2)     the imode is good type but not S_IFREG. 3) the imode is S_IFREG. The BUG_ON may be triggered by bypassing     the check in cases 1 and 2. Therefore, when the boot loader inode is bad_inode or its imode is not     S_IFREG, initialize the inode to avoid triggering the BUG. (CVE-2022-50638)

  - In the Linux kernel, the following vulnerability has been resolved: ext4: fix bug_on in __es_tree_search     caused by bad quota inode We got a issue as fllows:
    ================================================================== kernel BUG at     fs/ext4/extents_status.c:202! invalid opcode: 0000 [#1] PREEMPT SMP CPU: 1 PID: 810 Comm: mount Not     tainted 6.1.0-rc1-next-g9631525255e3 #352 RIP: 0010:__es_tree_search.isra.0+0xb8/0xe0 RSP:
    0018:ffffc90001227900 EFLAGS: 00010202 RAX: 0000000000000000 RBX: 0000000077512a0f RCX: 0000000000000000     RDX: 0000000000000002 RSI: 0000000000002a10 RDI: ffff8881004cd0c8 RBP: ffff888177512ac8 R08:
    47ffffffffffffff R09: 0000000000000001 R10: 0000000000000001 R11: 00000000000679af R12: 0000000000002a10     R13: ffff888177512d88 R14: 0000000077512a10 R15: 0000000000000000 FS:
    00007f4bd76dbc40(0000)GS:ffff88842fd00000(0000)knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0:
    0000000080050033 CR2: 00005653bf993cf8 CR3: 000000017bfdf000 CR4: 00000000000006e0 DR0: 0000000000000000     DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7:
    0000000000000400 Call Trace: <TASK> ext4_es_cache_extent+0xe2/0x210 ext4_cache_extents+0xd2/0x110     ext4_find_extent+0x5d5/0x8c0 ext4_ext_map_blocks+0x9c/0x1d30 ext4_map_blocks+0x431/0xa50     ext4_getblk+0x82/0x340 ext4_bread+0x14/0x110 ext4_quota_read+0xf0/0x180 v2_read_header+0x24/0x90     v2_check_quota_file+0x2f/0xa0 dquot_load_quota_sb+0x26c/0x760 dquot_load_quota_inode+0xa5/0x190     ext4_enable_quotas+0x14c/0x300 __ext4_fill_super+0x31cc/0x32c0 ext4_fill_super+0x115/0x2d0     get_tree_bdev+0x1d2/0x360 ext4_get_tree+0x19/0x30 vfs_get_tree+0x26/0xe0 path_mount+0x81d/0xfc0     do_mount+0x8d/0xc0 __x64_sys_mount+0xc0/0x160 do_syscall_64+0x35/0x80     entry_SYSCALL_64_after_hwframe+0x63/0xcd </TASK>     ================================================================== Above issue may happen as follows:
    ------------------------------------- ext4_fill_super ext4_orphan_cleanup ext4_enable_quotas     ext4_quota_enable ext4_iget --> get error inode <5> ext4_ext_check_inode --> Wrong imode makes it escape     inspection make_bad_inode(inode) --> EXT4_BOOT_LOADER_INO set imode dquot_load_quota_inode     vfs_setup_quota_inode --> check pass dquot_load_quota_sb v2_check_quota_file v2_read_header     ext4_quota_read ext4_bread ext4_getblk ext4_map_blocks ext4_ext_map_blocks ext4_find_extent     ext4_cache_extents ext4_es_cache_extent __es_tree_search.isra.0 ext4_es_end --> Wrong extents trigger     BUG_ON In the above issue, s_usr_quota_inum is set to 5, but inode<5> contains incorrect imode and     disordered extents. Because 5 is EXT4_BOOT_LOADER_INO, the ext4_ext_check_inode check in the ext4_iget     function can be bypassed, finally, the extents that are not checked trigger the BUG_ON in the
    __es_tree_search function. To solve this issue, check whether the inode is bad_inode in     vfs_setup_quota_inode(). (CVE-2022-50782)

  - In the Linux kernel, the following vulnerability has been resolved: crypto: seqiv - Handle EBUSY correctly     As it is seqiv only handles the special return value of EINPROGERSS, which means that in all other cases     it will free data related to the request. However, as the caller of seqiv may specify MAY_BACKLOG, we also     need to expect EBUSY and treat it in the same way. Otherwise backlogged requests will trigger a use-after-     free. (CVE-2023-53373)

  - In the Linux kernel, the following vulnerability has been resolved: drm/radeon: free iio for atombios when     driver shutdown Fix below kmemleak when unload radeon driver: unreferenced object 0xffff9f8608ede200 (size     512): comm systemd-udevd, pid 326, jiffies 4294682822 (age 716.338s) hex dump (first 32 bytes): 00 00 00     00 c4 aa ec aa 14 ab 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00     ................ backtrace: [<0000000062fadebe>] kmem_cache_alloc_trace+0x2f1/0x500 [<00000000b6883cea>]     atom_parse+0x117/0x230 [radeon] [<00000000158c23fd>] radeon_atombios_init+0xab/0x170 [radeon]     [<00000000683f672e>] si_init+0x57/0x750 [radeon] [<00000000566cc31f>] radeon_device_init+0x559/0x9c0     [radeon] [<0000000046efabb3>] radeon_driver_load_kms+0xc1/0x1a0 [radeon] [<00000000b5155064>]     drm_dev_register+0xdd/0x1d0 [<0000000045fec835>] radeon_pci_probe+0xbd/0x100 [radeon] [<00000000e69ecca3>]     pci_device_probe+0xe1/0x160 [<0000000019484b76>] really_probe.part.0+0xc1/0x2c0 [<000000003f2649da>]
    __driver_probe_device+0x96/0x130 [<00000000231c5bb1>] driver_probe_device+0x24/0xf0 [<0000000000a42377>]
    __driver_attach+0x77/0x190 [<00000000d7574da6>] bus_for_each_dev+0x7f/0xd0 [<00000000633166d2>]     driver_attach+0x1e/0x30 [<00000000313b05b8>] bus_add_driver+0x12c/0x1e0 iio was allocated in     atom_index_iio() called by atom_parse(), but it doesn't got released when the dirver is shutdown. Fix this     kmemleak by free it in radeon_atombios_fini(). (CVE-2023-53453)

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

The Rocky Linux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the CIQ crxsa-2024_3138 advisory.

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

    Security Fix(es):

    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 Rocky Linux SIG Cloud 8.10 Release Notes     linked from the References section.

    This advisory is provided by Ctrl IQ, Inc for Rocky Linux systems. For more information about CIQ security     practices, visit https://ciq.com/security.

Tenable has extracted the preceding description block directly from the CIQ 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 Unity Linux 20 host has a package installed that is affected by a vulnerability as referenced in the UTSA-2026-013629 advisory.

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

    ext4: fix bug_on in __es_tree_search caused by bad quota inode

    We got a issue as fllows:
    ==================================================================      kernel BUG at fs/ext4/extents_status.c:202!      invalid opcode: 0000 [#1] PREEMPT SMP      CPU: 1 PID: 810 Comm: mount Not tainted 6.1.0-rc1-next-g9631525255e3 #352      RIP: 0010:__es_tree_search.isra.0+0xb8/0xe0      RSP: 0018:ffffc90001227900 EFLAGS: 00010202      RAX: 0000000000000000 RBX: 0000000077512a0f RCX: 0000000000000000      RDX: 0000000000000002 RSI: 0000000000002a10 RDI: ffff8881004cd0c8      RBP: ffff888177512ac8 R08: 47ffffffffffffff R09: 0000000000000001      R10: 0000000000000001 R11: 00000000000679af R12: 0000000000002a10      R13: ffff888177512d88 R14: 0000000077512a10 R15: 0000000000000000      FS: 00007f4bd76dbc40(0000)GS:ffff88842fd00000(0000)knlGS:0000000000000000      CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033      CR2: 00005653bf993cf8 CR3: 000000017bfdf000 CR4: 00000000000006e0      DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000      DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400      Call Trace:
      <TASK>       ext4_es_cache_extent+0xe2/0x210       ext4_cache_extents+0xd2/0x110       ext4_find_extent+0x5d5/0x8c0       ext4_ext_map_blocks+0x9c/0x1d30       ext4_map_blocks+0x431/0xa50       ext4_getblk+0x82/0x340       ext4_bread+0x14/0x110       ext4_quota_read+0xf0/0x180       v2_read_header+0x24/0x90       v2_check_quota_file+0x2f/0xa0       dquot_load_quota_sb+0x26c/0x760       dquot_load_quota_inode+0xa5/0x190       ext4_enable_quotas+0x14c/0x300
      __ext4_fill_super+0x31cc/0x32c0       ext4_fill_super+0x115/0x2d0       get_tree_bdev+0x1d2/0x360       ext4_get_tree+0x19/0x30       vfs_get_tree+0x26/0xe0       path_mount+0x81d/0xfc0       do_mount+0x8d/0xc0
      __x64_sys_mount+0xc0/0x160       do_syscall_64+0x35/0x80       entry_SYSCALL_64_after_hwframe+0x63/0xcd       </TASK>     ==================================================================

    Above issue may happen as follows:
    -------------------------------------     ext4_fill_super      ext4_orphan_cleanup       ext4_enable_quotas        ext4_quota_enable         ext4_iget --> get error inode <5>          ext4_ext_check_inode --> Wrong imode makes it escape inspection          make_bad_inode(inode) --> EXT4_BOOT_LOADER_INO set imode         dquot_load_quota_inode          vfs_setup_quota_inode --> check pass          dquot_load_quota_sb           v2_check_quota_file            v2_read_header             ext4_quota_read              ext4_bread               ext4_getblk                ext4_map_blocks                 ext4_ext_map_blocks                  ext4_find_extent                   ext4_cache_extents                    ext4_es_cache_extent
                    __es_tree_search.isra.0                      ext4_es_end --> Wrong extents trigger BUG_ON

    In the above issue, s_usr_quota_inum is set to 5, but inode<5> contains     incorrect imode and disordered extents. Because 5 is EXT4_BOOT_LOADER_INO,     the ext4_ext_check_inode check in the ext4_iget function can be bypassed,     finally, the extents that are not checked trigger the BUG_ON in the
    __es_tree_search function. To solve this issue, check whether the inode is     bad_inode in vfs_setup_quota_inode().

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-2026-011069 advisory.

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

    ext4: fix bug_on in __es_tree_search caused by bad quota inode

    We got a issue as fllows:
    ==================================================================      kernel BUG at fs/ext4/extents_status.c:202!      invalid opcode: 0000 [#1] PREEMPT SMP      CPU: 1 PID: 810 Comm: mount Not tainted 6.1.0-rc1-next-g9631525255e3 #352      RIP: 0010:__es_tree_search.isra.0+0xb8/0xe0      RSP: 0018:ffffc90001227900 EFLAGS: 00010202      RAX: 0000000000000000 RBX: 0000000077512a0f RCX: 0000000000000000      RDX: 0000000000000002 RSI: 0000000000002a10 RDI: ffff8881004cd0c8      RBP: ffff888177512ac8 R08: 47ffffffffffffff R09: 0000000000000001      R10: 0000000000000001 R11: 00000000000679af R12: 0000000000002a10      R13: ffff888177512d88 R14: 0000000077512a10 R15: 0000000000000000      FS: 00007f4bd76dbc40(0000)GS:ffff88842fd00000(0000)knlGS:0000000000000000      CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033      CR2: 00005653bf993cf8 CR3: 000000017bfdf000 CR4: 00000000000006e0      DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000      DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400      Call Trace:
      <TASK>       ext4_es_cache_extent+0xe2/0x210       ext4_cache_extents+0xd2/0x110       ext4_find_extent+0x5d5/0x8c0       ext4_ext_map_blocks+0x9c/0x1d30       ext4_map_blocks+0x431/0xa50       ext4_getblk+0x82/0x340       ext4_bread+0x14/0x110       ext4_quota_read+0xf0/0x180       v2_read_header+0x24/0x90       v2_check_quota_file+0x2f/0xa0       dquot_load_quota_sb+0x26c/0x760       dquot_load_quota_inode+0xa5/0x190       ext4_enable_quotas+0x14c/0x300
      __ext4_fill_super+0x31cc/0x32c0       ext4_fill_super+0x115/0x2d0       get_tree_bdev+0x1d2/0x360       ext4_get_tree+0x19/0x30       vfs_get_tree+0x26/0xe0       path_mount+0x81d/0xfc0       do_mount+0x8d/0xc0
      __x64_sys_mount+0xc0/0x160       do_syscall_64+0x35/0x80       entry_SYSCALL_64_after_hwframe+0x63/0xcd       </TASK>     ==================================================================

    Above issue may happen as follows:
    -------------------------------------     ext4_fill_super      ext4_orphan_cleanup       ext4_enable_quotas        ext4_quota_enable         ext4_iget --> get error inode <5>          ext4_ext_check_inode --> Wrong imode makes it escape inspection          make_bad_inode(inode) --> EXT4_BOOT_LOADER_INO set imode         dquot_load_quota_inode          vfs_setup_quota_inode --> check pass          dquot_load_quota_sb           v2_check_quota_file            v2_read_header             ext4_quota_read              ext4_bread               ext4_getblk                ext4_map_blocks                 ext4_ext_map_blocks                  ext4_find_extent                   ext4_cache_extents                    ext4_es_cache_extent
                    __es_tree_search.isra.0                      ext4_es_end --> Wrong extents trigger BUG_ON

    In the above issue, s_usr_quota_inum is set to 5, but inode<5> contains     incorrect imode and disordered extents. Because 5 is EXT4_BOOT_LOADER_INO,     the ext4_ext_check_inode check in the ext4_iget function can be bypassed,     finally, the extents that are not checked trigger the BUG_ON in the
    __es_tree_search function. To solve this issue, check whether the inode is     bad_inode in vfs_setup_quota_inode().

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-2026-007561 advisory.

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

    ext4: fix bug_on in __es_tree_search caused by bad quota inode

    We got a issue as fllows:
    ==================================================================      kernel BUG at fs/ext4/extents_status.c:202!      invalid opcode: 0000 [#1] PREEMPT SMP      CPU: 1 PID: 810 Comm: mount Not tainted 6.1.0-rc1-next-g9631525255e3 #352      RIP: 0010:__es_tree_search.isra.0+0xb8/0xe0      RSP: 0018:ffffc90001227900 EFLAGS: 00010202      RAX: 0000000000000000 RBX: 0000000077512a0f RCX: 0000000000000000      RDX: 0000000000000002 RSI: 0000000000002a10 RDI: ffff8881004cd0c8      RBP: ffff888177512ac8 R08: 47ffffffffffffff R09: 0000000000000001      R10: 0000000000000001 R11: 00000000000679af R12: 0000000000002a10      R13: ffff888177512d88 R14: 0000000077512a10 R15: 0000000000000000      FS: 00007f4bd76dbc40(0000)GS:ffff88842fd00000(0000)knlGS:0000000000000000      CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033      CR2: 00005653bf993cf8 CR3: 000000017bfdf000 CR4: 00000000000006e0      DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000      DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400      Call Trace:
      <TASK>       ext4_es_cache_extent+0xe2/0x210       ext4_cache_extents+0xd2/0x110       ext4_find_extent+0x5d5/0x8c0       ext4_ext_map_blocks+0x9c/0x1d30       ext4_map_blocks+0x431/0xa50       ext4_getblk+0x82/0x340       ext4_bread+0x14/0x110       ext4_quota_read+0xf0/0x180       v2_read_header+0x24/0x90       v2_check_quota_file+0x2f/0xa0       dquot_load_quota_sb+0x26c/0x760       dquot_load_quota_inode+0xa5/0x190       ext4_enable_quotas+0x14c/0x300
      __ext4_fill_super+0x31cc/0x32c0       ext4_fill_super+0x115/0x2d0       get_tree_bdev+0x1d2/0x360       ext4_get_tree+0x19/0x30       vfs_get_tree+0x26/0xe0       path_mount+0x81d/0xfc0       do_mount+0x8d/0xc0
      __x64_sys_mount+0xc0/0x160       do_syscall_64+0x35/0x80       entry_SYSCALL_64_after_hwframe+0x63/0xcd       </TASK>     ==================================================================

    Above issue may happen as follows:
    -------------------------------------     ext4_fill_super      ext4_orphan_cleanup       ext4_enable_quotas        ext4_quota_enable         ext4_iget --> get error inode <5>          ext4_ext_check_inode --> Wrong imode makes it escape inspection          make_bad_inode(inode) --> EXT4_BOOT_LOADER_INO set imode         dquot_load_quota_inode          vfs_setup_quota_inode --> check pass          dquot_load_quota_sb           v2_check_quota_file            v2_read_header             ext4_quota_read              ext4_bread               ext4_getblk                ext4_map_blocks                 ext4_ext_map_blocks                  ext4_find_extent                   ext4_cache_extents                    ext4_es_cache_extent
                    __es_tree_search.isra.0                      ext4_es_end --> Wrong extents trigger BUG_ON

    In the above issue, s_usr_quota_inum is set to 5, but inode<5> contains     incorrect imode and disordered extents. Because 5 is EXT4_BOOT_LOADER_INO,     the ext4_ext_check_inode check in the ext4_iget function can be bypassed,     finally, the extents that are not checked trigger the BUG_ON in the
    __es_tree_search function. To solve this issue, check whether the inode is     bad_inode in vfs_setup_quota_inode().

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 remote SUSE Linux SLES15 / SLES_SAP15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2026:0617-1 advisory.

    The SUSE Linux Enterprise 15 SP4 kernel was updated to fix various security issues

    The following security issues were fixed:

    - CVE-2022-50630: mm: hugetlb: fix UAF in hugetlb_handle_userfault (bsc#1254785).
    - CVE-2022-50697: mrp: introduce active flags to prevent UAF when applicant uninit (bsc#1255594).
    - CVE-2022-50700: wifi: ath10k: Delay the unmapping of the buffer (bsc#1255576).
    - CVE-2023-53215: sched/fair: Don't balance task to its current running CPU (bsc#1250397).
    - CVE-2023-53254: cacheinfo: Fix shared_cpu_map to handle shared caches at different levels (bsc#1249871).
    - CVE-2023-53781: smc: Fix use-after-free in tcp_write_timer_handler() (bsc#1254751).
    - CVE-2023-54142: gtp: Fix use-after-free in __gtp_encap_destroy() (bsc#1256095).
    - CVE-2023-54243: netfilter: ebtables: fix table blob use-after-free (bsc#1255908).
    - CVE-2024-28956: x86/its: Enumerate Indirect Target Selection (ITS) bug (bsc#1242006).
    - CVE-2024-36348: x86/bugs: Add a Transient Scheduler Attacks mitigation (bsc#1238896).
    - CVE-2024-36349: x86/bugs: Add a Transient Scheduler Attacks mitigation (bsc#1238896).
    - CVE-2024-36350: x86/bugs: Add a Transient Scheduler Attacks mitigation (bsc#1238896).
    - CVE-2024-36357: x86/bugs: Add a Transient Scheduler Attacks mitigation (bsc#1238896).
    - CVE-2024-44987: ipv6: prevent UAF in ip6_send_skb() (bsc#1230185).
    - CVE-2024-46854: net: dpaa: Pad packets to ETH_ZLEN (bsc#1231084).
    - CVE-2025-21738: ata: libata-sff: Ensure that we cannot write outside the allocated buffer (bsc#1238917).
    - CVE-2025-38068: crypto: lzo - Fix compression buffer overrun (bsc#1245210).
    - CVE-2025-38129: page_pool: fix inconsistency for page_pool_ring_lock() (bsc#1245723).
    - CVE-2025-38159: wifi: rtw88: fix the 'para' buffer size to avoid reading out of bounds (bsc#1245751).
    - CVE-2025-38375: virtio-net: ensure the received length does not exceed allocated size (bsc#1247177).
    - CVE-2025-39977: futex: Prevent use-after-free during requeue-PI (bsc#1252046).
    - CVE-2025-40019: crypto: essiv - Check ssize for decryption and in-place encryption (bsc#1252678).
    - CVE-2025-40139: net: ipv4: Consolidate ipv4_mtu and ip_dst_mtu_maybe_forward (bsc#1253409).
    - CVE-2025-40215: kABI: xfrm: delete x->tunnel as we delete x (bsc#1254959).
    - CVE-2025-40220: fuse: fix livelock in synchronous file put from fuseblk workers (bsc#1254520).
    - CVE-2025-40233: ocfs2: clear extent cache after moving/defragmenting extents (bsc#1254813).
    - CVE-2025-40257: mptcp: fix a race in mptcp_pm_del_add_timer() (bsc#1254842).
    - CVE-2025-40258: mptcp: fix race condition in mptcp_schedule_work() (bsc#1254843).
    - CVE-2025-40277: drm/vmwgfx: Validate command header size against (bsc#1254894).
    - CVE-2025-40280: tipc: Fix use-after-free in tipc_mon_reinit_self() (bsc#1254847).
    - CVE-2025-40300: Documentation/hw-vuln: Add VMSCAPE documentation (bsc#1247483).
    - CVE-2025-40331: sctp: Prevent TOCTOU out-of-bounds write (bsc#1254615).
    - CVE-2025-68183: ima: don't clear IMA_DIGSIG flag when setting or removing non-IMA xattr (bsc#1255251).
    - CVE-2025-68284: libceph: prevent potential out-of-bounds writes in handle_auth_session_key()     (bsc#1255377).
    - CVE-2025-68285: libceph: fix potential use-after-free in have_mon_and_osd_map() (bsc#1255401).
    - CVE-2025-68312: usbnet: Prevents free active kevent (bsc#1255171).
    - CVE-2025-68732: gpu: host1x: Fix race in syncpt alloc/free (bsc#1255688).
    - CVE-2025-68813: ipvs: fix ipv4 null-ptr-deref in route error path (bsc#1256641).
    - CVE-2025-71085: ipv6: BUG() in pskb_expand_head() as part of calipso_skbuff_setattr() (bsc#1256623).
    - CVE-2025-71089: iommu: disable SVA when CONFIG_X86 is set (bsc#1256612).
    - CVE-2025-71112: net: hns3: add VLAN id validation before using (bsc#1256726).
    - CVE-2025-71116: libceph: make decode_pool() more resilient against corrupted osdmaps (bsc#1256744).
    - CVE-2025-71120: SUNRPC: svcauth_gss: avoid NULL deref on zero length gss_token in gss_read_proxy_verf     (bsc#1256779).
    - CVE-2026-22999: net/sched: sch_qfq: do not free existing class in qfq_change_class() (bsc#1257236).
    - CVE-2026-23001: macvlan: fix possible UAF in macvlan_forward_source() (bsc#1257232).
    - CVE-2026-23074: net/sched: Enforce that teql can only be used as root qdisc (bsc#1257749).
    - CVE-2026-23089: ALSA: usb-audio: Fix use-after-free in snd_usb_mixer_free() (bsc#1257790).

    The following non security issues were fixed:

    - net: hv_netvsc: reject RSS hash key programming without RX indirection table (bsc#1257473).
    - net: tcp: allow zero-window ACK update the window (bsc#1254767).
    - net: tcp: send zero-window ACK when no memory (bsc#1254767).
    - scsi: storvsc: Process unsupported MODE_SENSE_10 (bsc#1257296).
    - tcp: correct handling of extreme memory squeeze (bsc#1254767).
    - x86/CPU/AMD: Add ZenX generations flags (bsc#1238896).
    - x86/its: Fix crash during dynamic its initialization (bsc#1257771).
    - x86/modules: Set VM_FLUSH_RESET_PERMS in module_alloc() (bsc#1257771).
    - x86: make page fault handling disable interrupts properly (git-fixes).

Tenable has extracted the preceding description block directly from the SUSE 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 SUSE Linux SLES12 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2026:0473-1 advisory.

    The SUSE Linux Enterprise 12 SP5 kernel was updated to fix various security issues

    The following security issues were fixed:

    - CVE-2022-50347: mmc: rtsx_usb_sdmmc: fix return value check of mmc_add_host() (bsc#1249928).
    - CVE-2022-50580: blk-throttle: prevent overflow while calculating wait time (bsc#1252542).
    - CVE-2022-50676: net: rds: don't hold sock lock when cancelling work from rds_tcp_reset_callbacks()     (bsc#1254689).
    - CVE-2022-50697: mrp: introduce active flags to prevent UAF when applicant uninit (bsc#1255594).
    - CVE-2022-50709: wifi: ath9k: avoid uninit memory read in ath9k_htc_rx_msg() (bsc#1255565).
    - CVE-2022-50716: wifi: ar5523: Fix use-after-free on ar5523_cmd() timed out (bsc#1255839).
    - CVE-2022-50717: nvmet-tcp: add bounds check on Transfer Tag (bsc#1255844).
    - CVE-2022-50719: ALSA: line6: fix stack overflow in line6_midi_transmit (bsc#1255939).
    - CVE-2022-50740: wifi: ath9k: hif_usb: fix memory leak of urbs in ath9k_hif_usb_dealloc_tx_urbs()     (bsc#1256155).
    - CVE-2022-50744: scsi: lpfc: Fix hard lockup when reading the rx_monitor from debugfs (bsc#1256165).
    - CVE-2022-50749: acct: fix potential integer overflow in encode_comp_t() (bsc#1256191).
    - CVE-2022-50751: configfs: fix possible memory leak in configfs_create_dir() (bsc#1256184).
    - CVE-2022-50760: drm/amdgpu: Fix PCI device refcount leak in amdgpu_atrm_get_bios() (bsc#1255983).
    - CVE-2022-50770: ocfs2: fix memory leak in ocfs2_mount_volume() (bsc#1256221).
    - CVE-2022-50777: net: phy: xgmiitorgmii: Fix refcount leak in xgmiitorgmii_probe (bsc#1256320).
    - CVE-2022-50780: net: fix UAF issue in nfqnl_nf_hook_drop() when ops_init() failed (bsc#1256305).
    - CVE-2022-50782: ext4: fix bug_on in __es_tree_search caused by bad quota inode (bsc#1256282).
    - CVE-2022-50786: media: s5p-mfc: Clear workbit to handle error condition (bsc#1256258).
    - CVE-2022-50816: ipv6: ensure sane device mtu in tunnels (bsc#1256038).
    - CVE-2022-50834: nfc: Fix potential resource leaks (bsc#1256219).
    - CVE-2022-50865: tcp: fix a signed-integer-overflow bug in tcp_add_backlog() (bsc#1256168).
    - CVE-2022-50868: hwrng: amd - Fix PCI device refcount leak (bsc#1256386).
    - CVE-2022-50880: wifi: ath10k: add peer map clean up for peer delete in ath10k_sta_state() (bsc#1256132).
    - CVE-2022-50881: ath9k: Fix typo in function name (bsc#1256130).
    - CVE-2022-50884: drm: Prevent drm_copy_field() to attempt copying a NULL pointer (bsc#1256127).
    - CVE-2022-50885: RDMA/rxe: Fix NULL-ptr-deref in rxe_qp_do_cleanup() when socket create failed     (bsc#1256122).
    - CVE-2022-50887: regulator: core: fix unbalanced of node refcount in regulator_dev_lookup()     (bsc#1256125).
    - CVE-2023-50756: nvme-pci: fix mempool alloc size (bsc#1256216).
    - CVE-2023-53685: tun: Fix memory leak for detached NAPI queue (bsc#1251770).
    - CVE-2023-53747: vc_screen: reload load of struct vc_data pointer in vcs_write() to avoid UAF     (bsc#1254572).
    - CVE-2023-53751: cifs: fix potential use-after-free bugs in TCP_Server_Info::hostname (bsc#1254986).
    - CVE-2023-53825: kcm: Fix error handling for SOCK_DGRAM in kcm_sendmsg() (bsc#1254707).
    - CVE-2023-53853: netlink: annotate accesses to nlk->cb_running (bsc#1254673).
    - CVE-2023-53863: netlink: do not hard code device address lenth in fdb dumps (bsc#1254657).
    - CVE-2023-53992: wifi: cfg80211: ocb: don't leave if not joined (bsc#1256058).
    - CVE-2023-54012: net: fix stack overflow when LRO is disabled for virtual interfaces (bsc#1255571).
    - CVE-2023-54047: drm/rockchip: dw_hdmi: cleanup drm encoder during unbind (bsc#1256398).
    - CVE-2023-54048: RDMA/bnxt_re: Prevent handling any completions after qp destroy (bsc#1256395).
    - CVE-2023-54067: btrfs: fix race when deleting free space root from the dirty cow roots list     (bsc#1256369).
    - CVE-2023-54111: pinctrl: rockchip: Fix refcount leak in rockchip_pinctrl_parse_groups (bsc#1256149).
    - CVE-2023-54112: kcm: Fix memory leak in error path of kcm_sendmsg() (bsc#1256354).
    - CVE-2023-54118: serial: sc16is7xx: setup GPIO controller later in probe (bsc#1256131).
    - CVE-2023-54121: btrfs: fix incorrect splitting in btrfs_drop_extent_map_range (bsc#1256267).
    - CVE-2023-54134: autofs: fix memory leak of waitqueues in autofs_catatonic_mode (bsc#1256106).
    - CVE-2023-54198: tty: fix out-of-bounds access in tty_driver_lookup_tty() (bsc#1255970).
    - CVE-2023-54202: drm/i915: fix race condition UAF in i915_perf_add_config_ioctl (bsc#1255880).
    - CVE-2023-54207: HID: uclogic: Correct devm device reference for hidinput input_dev name (bsc#1255961).
    - CVE-2023-54218: sock: Make sock->sk_stamp thread-safe (bsc#1256229).
    - CVE-2023-54230: amba: bus: fix refcount leak (bsc#1255925).
    - CVE-2023-54243: netfilter: ebtables: fix table blob use-after-free (bsc#1255908).
    - CVE-2023-54265: ipv6: Fix an uninit variable access bug in __ip6_make_skb() (bsc#1255874).
    - CVE-2023-54274: RDMA/srpt: Add a check for valid 'mad_agent' pointer (bsc#1255905).
    - CVE-2023-54282: media: tuners: qt1010: replace BUG_ON with a regular error (bsc#1255810).
    - CVE-2023-54287: tty: serial: imx: disable Ageing Timer interrupt request irq (bsc#1255804).
    - CVE-2023-54311: ext4: fix deadlock when converting an inline directory in nojournal mode (bsc#1255773).
    - CVE-2023-54321: driver core: fix potential null-ptr-deref in device_add() (bsc#1255762).
    - CVE-2024-41007: tcp: use signed arithmetic in tcp_rtx_probe0_timed_out() (bsc#1227863).
    - CVE-2025-40115: scsi: mpt3sas: Fix crash in transport port remove by using ioc_info() (bsc#1253318).
    - CVE-2025-40259: scsi: sg: Do not sleep in atomic context (bsc#1254845).
    - CVE-2025-40261: nvme: nvme-fc: Ensure ->ioerr_work is cancelled in nvme_fc_delete_ctrl() (bsc#1254839).
    - CVE-2025-40264: be2net: pass wrb_params in case of OS2BMC (bsc#1254835).
    - CVE-2025-40271: fs/proc: fix uaf in proc_readdir_de() (bsc#1255297).
    - CVE-2025-40323: fbcon: Set fb_display[i]->mode to NULL when the mode is released (bsc#1255094).
    - CVE-2025-40339: drm/amdgpu: fix nullptr err of vm_handle_moved (bsc#1255428).
    - CVE-2025-40345: usb: storage: sddr55: Reject out-of-bound new_pba (bsc#1255279).
    - CVE-2025-40363: net: ipv6: fix field-spanning memcpy warning in AH output (bsc#1255102).
    - CVE-2025-68188: tcp: use dst_dev_rcu() in tcp_fastopen_active_disable_ofo_check() (bsc#1255269).
    - CVE-2025-68190: drm/amdgpu/atom: Check kcalloc() for WS buffer in amdgpu_atom_execute_table_locked()     (bsc#1255131).
    - CVE-2025-68192: net: usb: qmi_wwan: initialize MAC header offset in qmimux_rx_fixup (bsc#1255246).
    - CVE-2025-68241: ipv4: route: Prevent rt_bind_exception() from rebinding stale fnhe (bsc#1255157).
    - CVE-2025-68245: net: netpoll: fix incorrect refcount handling causing incorrect cleanup (bsc#1255268).
    - CVE-2025-68261: ext4: add i_data_sem protection in ext4_destroy_inline_data_nolock() (bsc#1255164).
    - CVE-2025-68264: ext4: refresh inline data size before write operations (bsc#1255380).
    - CVE-2025-68286: drm/amd/display: Check NULL before accessing (bsc#1255351).
    - CVE-2025-68296: drm, fbcon, vga_switcheroo: Avoid race condition in fbcon setup (bsc#1255128).
    - CVE-2025-68303: platform/x86: intel: punit_ipc: fix memory corruption (bsc#1255122).
    - CVE-2025-68305: Bluetooth: hci_sock: Prevent race in socket write iter and sock bind (bsc#1255169).
    - CVE-2025-68312: usbnet: Prevents free active kevent (bsc#1255171).
    - CVE-2025-68337: jbd2: avoid bug_on in jbd2_journal_get_create_access() when file system corrupted     (bsc#1255482).
    - CVE-2025-68349: NFSv4/pNFS: Clear NFS_INO_LAYOUTCOMMIT in pnfs_mark_layout_stateid_invalid     (bsc#1255544).
    - CVE-2025-68354: regulator: core: Protect regulator_supply_alias_list with regulator_list_mutex     (bsc#1255553).
    - CVE-2025-68362: wifi: rtl818x: rtl8187: Fix potential buffer underflow in rtl8187_rx_cb() (bsc#1255611).
    - CVE-2025-68366: nbd: defer config unlock in nbd_genl_connect (bsc#1255622).
    - CVE-2025-68367: macintosh/mac_hid: fix race condition in mac_hid_toggle_emumouse (bsc#1255547).
    - CVE-2025-68372: nbd: defer config put in recv_work (bsc#1255537).
    - CVE-2025-68379: RDMA/rxe: Fix null deref on srq->rq.queue after resize failure (bsc#1255695).
    - CVE-2025-68740: ima: Handle error code returned by ima_filter_rule_match() (bsc#1255812).
    - CVE-2025-68757: drm/vgem-fence: Fix potential deadlock on release (bsc#1255943).
    - CVE-2025-68767: hfsplus: Verify inode mode when loading from disk (bsc#1256580).
    - CVE-2025-68771: ocfs2: fix kernel BUG in ocfs2_find_victim_chain (bsc#1256582).
    - CVE-2025-68774: hfsplus: fix missing hfs_bnode_get() in __hfs_bnode_create (bsc#1256585).
    - CVE-2025-68783: ALSA: usb-mixer: us16x08: validate meter packet indices (bsc#1256650).
    - CVE-2025-68788: fsnotify: do not generate ACCESS/MODIFY events on child for special files (bsc#1256638).
    - CVE-2025-68795: ethtool: Avoid overflowing userspace buffer on stats query (bsc#1256688).
    - CVE-2025-68797: char: applicom: fix NULL pointer dereference in ac_ioctl (bsc#1256660).
    - CVE-2025-68813: ipvs: fix ipv4 null-ptr-deref in route error path (bsc#1256641).
    - CVE-2025-68816: net/mlx5: fw_tracer, Validate format string parameters (bsc#1256674).
    - CVE-2025-71064: net: hns3: using the num_tqps in the vf driver to apply for resources (bsc#1256654).
    - CVE-2025-71082: Bluetooth: btusb: revert use of devm_kzalloc in btusb (bsc#1256611).
    - CVE-2025-71085: ipv6: BUG() in pskb_expand_head() as part of calipso_skbuff_setattr() (bsc#1256623).
    - CVE-2025-71087: iavf: fix off-by-one issues in iavf_config_rss_reg() (bsc#1256628).
    - CVE-2025-71091: team: fix check for port enabled in team_queue_override_port_prio_changed()     (bsc#1256773).
    - CVE-2025-71093: e1000: fix OOB in e1000_tbi_should_accept() (bsc#1256777).
    - CVE-2025-71096: RDMA/core: Check for the presence of LS_NLA_TYPE_DGID correctly (bsc#1256606).
    - CVE-2025-71098: ip6_gre: make ip6gre_header() robust (bsc#1256591).
    - CVE-2025-71108: usb: typec: ucsi: Handle incorrect num_connectors capability (bsc#1256774).
    - CVE-2025-71112: net: hns3: add VLAN id validation before using (bsc#1256726).
    - CVE-2025-71119: powerpc/kexec: Enable SMT before waking offline CPUs (bsc#1205462).
    - CVE-2025-71120: SUNRPC: svcauth_gss: avoid NULL deref on zero length gss_token in gss_read_proxy_verf     (bsc#1256779).
    - CVE-2026-22976: net_sched: qfq: Fix double list add in class with netem as child qdisc (bsc#1257035).
    - CVE-2026-22978: wifi: avoid kernel-infoleak from struct iw_point (bsc#1257227).
    - CVE-2026-22999: net/sched: sch_qfq: do not free existing class in qfq_change_class() (bsc#1257236).
    - CVE-2026-23001: macvlan: Use 'hash' iterators to simplify code (bsc#1257232).
    - CVE-2026-23011: ipv4: ip_gre: make ipgre_header() robust (bsc#1257207).

    The following non security issues were fixed:

    - RDMA/rxe: Fix the error caused by qp->sk (bsc#1256122).
    - RDMA/srpt: Fix disabling device management (bsc#1255905).
    - RDMA/srpt: Fix handling of SR-IOV and iWARP ports (bsc#1255905).
    - configfs: factor dirent removal into helpers (bsc#1256184).
    - drm/amdgpu: Remove explicit wait after VM validate (bsc#1255428).
    - drm/amdgpu: update mappings not managed by KFD (bsc#1255428).
    - hwrng: amd - Convert PCIBIOS_* return codes to errnos (bsc#1256386).
    - nvmet-tcp: Fix NULL dereference when a connect data comes in h2cdata pdu (bsc#1255844).

Tenable has extracted the preceding description block directly from the SUSE 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 SUSE Linux SLES15 / SLES_SAP15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2026:0317-1 advisory.

    The SUSE Linux Enterprise 15 SP5 kernel was updated to fix various security issues

    The following security issues were fixed:

    - CVE-2022-50630: mm: hugetlb: fix UAF in hugetlb_handle_userfault (bsc#1254785).
    - CVE-2022-50700: wifi: ath10k: Delay the unmapping of the buffer (bsc#1255576).
    - CVE-2023-53254: cacheinfo: Fix shared_cpu_map to handle shared caches at different levels (bsc#1249871).
    - CVE-2023-53781: smc: Fix use-after-free in tcp_write_timer_handler() (bsc#1254751).
    - CVE-2024-56590: Bluetooth: hci_core: Fix not checking skb length on hci_acldata_packet (bsc#1235038).
    - CVE-2025-39977: futex: Prevent use-after-free during requeue-PI (bsc#1252046).
    - CVE-2025-40019: crypto: essiv - Check ssize for decryption and in-place encryption (bsc#1252678).
    - CVE-2025-40139: smc: Use __sk_dst_get() and dst_dev_rcu() in in smc_clc_prfx_set() (bsc#1253409).
    - CVE-2025-40215: kABI: xfrm: delete x->tunnel as we delete x (bsc#1254959).
    - CVE-2025-40220: fuse: fix livelock in synchronous file put from fuseblk workers (bsc#1254520).
    - CVE-2025-40233: ocfs2: clear extent cache after moving/defragmenting extents (bsc#1254813).
    - CVE-2025-40258: mptcp: fix race condition in mptcp_schedule_work() (bsc#1254843).
    - CVE-2025-40277: drm/vmwgfx: Validate command header size against (bsc#1254894).
    - CVE-2025-40280: tipc: Fix use-after-free in tipc_mon_reinit_self() (bsc#1254847).
    - CVE-2025-40331: sctp: Prevent TOCTOU out-of-bounds write (bsc#1254615).
    - CVE-2025-68732: gpu: host1x: Fix race in syncpt alloc/free (bsc#1255688).

    The following non security issues were fixed:

    - ACPI/IORT: Fix memory leak in iort_rmr_alloc_sids() (git-fixes).
    - ACPI: PRM: Remove unnecessary strict handler address checks (git-fixes).
    - ACPI: property: Do not pass NULL handles to acpi_attach_data() (git-fixes).
    - ACPI: property: Fix buffer properties extraction for subnodes (git-fixes).
    - KVM: SVM: Fix TSC_AUX virtualization setup (git-fixes).
    - RDMA/cm: Rate limit destroy CM ID timeout error message (git-fixes).
    - RDMA/counter: Check CAP_NET_RAW check in user namespace for RDMA counters (git-fixes).
    - RDMA/hns: Fix the modification of max_send_sge (git-fixes).
    - RDMA/mlx5: Check CAP_NET_RAW in user namespace for anchor create (git-fixes).
    - RDMA/mlx5: Check CAP_NET_RAW in user namespace for devx create (git-fixes).
    - RDMA/mlx5: Check CAP_NET_RAW in user namespace for flow create (git-fixes).
    - RDMA/mlx5: Fix compilation warning when USER_ACCESS isn't set (git-fixes).
    - RDMA/nldev: Check CAP_NET_RAW in user namespace for QP modify (git-fixes).
    - RDMA/uverbs: Add empty rdma_uattrs_has_raw_cap() declaration (git-fixes).
    - RDMA/uverbs: Check CAP_NET_RAW in user namespace for QP create (git-fixes).
    - RDMA/uverbs: Check CAP_NET_RAW in user namespace for RAW QP create (git-fixes).
    - RDMA/uverbs: Check CAP_NET_RAW in user namespace for flow create (git-fixes).
    - arch/idle: Change arch_cpu_idle() behavior: always exit with IRQs disabled (git-fixes).
    - cpuidle/poll: Ensure IRQs stay disabled after cpuidle_state::enter() calls (git-fixes).
    - cpuidle: Move IRQ state validation (git-fixes).
    - cpuidle: haltpoll: Do not enable interrupts when entering idle (git-fixes).
    - dm: free table mempools if not used in __bind (git-fixes).
    - padata: Honor the caller's alignment in case of chunk_size 0 (bsc#1237563).
    - platform/x86/intel-uncore-freq: Fail module load when plat_info is NULL (git-fixes).
    - x86/bugs: Fix RSB clearing in indirect_branch_prediction_barrier() (git-fixes).
    - x86/bugs: Use SBPB in write_ibpb() if applicable (git-fixes).
    - x86/paravirt: Move halt paravirt calls under CONFIG_PARAVIRT (git-fixes).
    - x86/tdx: Drop flags from __tdx_hypercall() (git-fixes).
    - x86/tdx: Dynamically disable SEPT violations from causing #VEs (git-fixes).
    - x86/tdx: Emit warning if IRQs are enabled during HLT #VE handling (git-fixes).
    - x86/tdx: Extend TDX_MODULE_CALL to support more TDCALL/SEAMCALL leafs (git-fixes).
    - x86/tdx: Fix __noreturn build warning around __tdx_hypercall_failed() (git-fixes).
    - x86/tdx: Fix arch_safe_halt() execution for TDX VMs (git-fixes).
    - x86/tdx: Introduce wrappers to read and write TD metadata (git-fixes).
    - x86/tdx: Make TDX_HYPERCALL asm similar to TDX_MODULE_CALL (git-fixes).
    - x86/tdx: Make macros of TDCALLs consistent with the spec (git-fixes).
    - x86/tdx: Pass TDCALL/SEAMCALL input/output registers via a structure (git-fixes).
    - x86/tdx: Reimplement __tdx_hypercall() using TDX_MODULE_CALL asm (git-fixes).
    - x86/tdx: Remove 'struct tdx_hypercall_args' (git-fixes).
    - x86/tdx: Remove TDX_HCALL_ISSUE_STI (git-fixes).
    - x86/tdx: Rename __tdx_module_call() to __tdcall() (git-fixes).
    - x86/tdx: Rename tdx_parse_tdinfo() to tdx_setup() (git-fixes).
    - x86/tdx: Retry partially-completed page conversion hypercalls (git-fixes).
    - x86/tdx: Skip saving output regs when SEAMCALL fails with VMFailInvalid (git-fixes).
    - x86/tdx: Zero out the missing RSI in TDX_HYPERCALL macro (git-fixes).
    - x86/virt/tdx: Make TDX_MODULE_CALL handle SEAMCALL #UD and #GP (git-fixes).
    - x86/virt/tdx: Wire up basic SEAMCALL functions (git-fixes).
    - xfs: fix sparse inode limits on runt AG (bsc#1254392).

Tenable has extracted the preceding description block directly from the SUSE 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.

  - ext4: fix bug_on in __es_tree_search caused by bad quota inode We got a issue as fllows:
    ================================================================== kernel BUG at     fs/ext4/extents_status.c:202! invalid opcode: 0000 [#1] PREEMPT SMP CPU: 1 PID: 810 Comm: mount Not     tainted 6.1.0-rc1-next-g9631525255e3 #352 RIP: 0010:__es_tree_search.isra.0+0xb8/0xe0 RSP:
    0018:ffffc90001227900 EFLAGS: 00010202 RAX: 0000000000000000 RBX: 0000000077512a0f RCX: 0000000000000000     RDX: 0000000000000002 RSI: 0000000000002a10 RDI: ffff8881004cd0c8 RBP: ffff888177512ac8 R08:
    47ffffffffffffff R09: 0000000000000001 R10: 0000000000000001 R11: 00000000000679af R12: 0000000000002a10     R13: ffff888177512d88 R14: 0000000077512a10 R15: 0000000000000000 FS:
    00007f4bd76dbc40(0000)GS:ffff88842fd00000(0000)knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0:
    0000000080050033 CR2: 00005653bf993cf8 CR3: 000000017bfdf000 CR4: 00000000000006e0 DR0: 0000000000000000     DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7:
    0000000000000400 Call Trace: <TASK> ext4_es_cache_extent+0xe2/0x210 ext4_cache_extents+0xd2/0x110     ext4_find_extent+0x5d5/0x8c0 ext4_ext_map_blocks+0x9c/0x1d30 ext4_map_blocks+0x431/0xa50     ext4_getblk+0x82/0x340 ext4_bread+0x14/0x110 ext4_quota_read+0xf0/0x180 v2_read_header+0x24/0x90     v2_check_quota_file+0x2f/0xa0 dquot_load_quota_sb+0x26c/0x760 dquot_load_quota_inode+0xa5/0x190     ext4_enable_quotas+0x14c/0x300 __ext4_fill_super+0x31cc/0x32c0 ext4_fill_super+0x115/0x2d0     get_tree_bdev+0x1d2/0x360 ext4_get_tree+0x19/0x30 vfs_get_tree+0x26/0xe0 path_mount+0x81d/0xfc0     do_mount+0x8d/0xc0 __x64_sys_mount+0xc0/0x160 do_syscall_64+0x35/0x80     entry_SYSCALL_64_after_hwframe+0x63/0xcd </TASK>     ================================================================== Above issue may happen as follows:
    ------------------------------------- ext4_fill_super ext4_orphan_cleanup ext4_enable_quotas     ext4_quota_enable ext4_iget --> get error inode <5> ext4_ext_check_inode --> Wrong imode makes it escape     inspection make_bad_inode(inode) --> EXT4_BOOT_LOADER_INO set imode dquot_load_quota_inode     vfs_setup_quota_inode --> check pass dquot_load_quota_sb v2_check_quota_file v2_read_header     ext4_quota_read ext4_bread ext4_getblk ext4_map_blocks ext4_ext_map_blocks ext4_find_extent     ext4_cache_extents ext4_es_cache_extent __es_tree_search.isra.0 ext4_es_end --> Wrong extents trigger     BUG_ON In the above issue, s_usr_quota_inum is set to 5, but inode<5> contains incorrect imode and     disordered extents. Because 5 is EXT4_BOOT_LOADER_INO, the ext4_ext_check_inode check in the ext4_iget     function can be bypassed, finally, the extents that are not checked trigger the BUG_ON in the
    __es_tree_search function. To solve this issue, check whether the inode is bad_inode in     vfs_setup_quota_inode(). (CVE-2022-50782)

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.90-54.138. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2KERNEL-5.15-2023-013 advisory.

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

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

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

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

    efi: fix NULL-deref in init error path (CVE-2022-48879)

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

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

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

    fs/ntfs3: Validate BOOT record_size (CVE-2022-50262)

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

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

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

    ext4: fix delayed allocation bug in ext4_clu_mapped for bigalloc + inline (CVE-2022-50286)

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

    btrfs: fix extent map use-after-free when handling missing device in read_one_chunk (CVE-2022-50300)

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

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

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

    block, bfq: fix uaf for bfqq in bfq_exit_icq_bfqq (CVE-2022-50329)

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

    fs/ntfs3: Add null pointer check to attr_load_runs_vcn (CVE-2022-50336)

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

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

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

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

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

    md: fix a crash in mempool_free (CVE-2022-50381)

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

    nvme: fix multipath crash caused by flush request when blktrace is enabled (CVE-2022-50388)

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

    tpm: tpm_crb: Add the missed acpi_put_table() to fix memory leak (CVE-2022-50389)

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

    net: sched: fix memory leak in tcindex_set_parms (CVE-2022-50396)

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

    ext4: fix off-by-one errors in fast-commit block filling (CVE-2022-50428)

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

    ext4: don't set up encryption key during jbd2 transaction (CVE-2022-50436)

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

    fs/ntfs3: Validate buffer length while parsing index (CVE-2022-50442)

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

    fs/ntfs3: Fix memory leak on ntfs_fill_super() error path (CVE-2022-50451)

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

    btrfs: fix resolving backrefs for inline extent followed by prealloc (CVE-2022-50456)

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

    ext4: fix leaking uninitialized memory in fast-commit journal (CVE-2022-50465)

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

    cpufreq: Init completion before kobject_init_and_add() (CVE-2022-50473)

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

    ext4: add EXT4_IGET_BAD flag to prevent unexpected bad inode (CVE-2022-50485)

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

    dm cache: Fix UAF in destroy() (CVE-2022-50496)

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

    fs/ntfs3: Validate data run offset (CVE-2022-50507)

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

    dm thin: Use last transaction's pmd->root when commit failed (CVE-2022-50534)

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

    ext4: fix uninititialized value in 'ext4_evict_inode' (CVE-2022-50546)

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

    dm thin: Fix ABBA deadlock between shrink_slab and dm_pool_abort_metadata (CVE-2022-50549)

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

    tpm: acpi: Call acpi_put_table() to fix memory leak (CVE-2022-50562)

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

    dm thin: Fix UAF in run_timer_softirq() (CVE-2022-50563)

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

    PCI: Fix pci_device_is_present() for VFs by checking PF (CVE-2022-50636)

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

    ext4: fix bug_on in __es_tree_search caused by bad boot loader inode (CVE-2022-50638)

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

    ext4: fix deadlock due to mbcache entry corruption (CVE-2022-50668)

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

    ext4: fix use-after-free in ext4_orphan_cleanup (CVE-2022-50673)

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

    io_uring/rw: defer fsnotify calls to task context (CVE-2022-50705)

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

    ext4: silence the warning when evicting inode with dioread_nolock (CVE-2022-50730)

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

    fs/ntfs3: Validate index root when initialize NTFS security (CVE-2022-50737)

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

    fs/ntfs3: Add null pointer check for inode operations (CVE-2022-50739)

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

    nvme-pci: fix mempool alloc size (CVE-2022-50756)

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

    ext4: fix bug_on in __es_tree_search caused by bad quota inode (CVE-2022-50782)

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

    mptcp: use proper req destructor for IPv6 (CVE-2022-50783)

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

    SUNRPC: Don't leak netobj memory when gss_read_proxy_verf() fails (CVE-2022-50821)

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

    tpm: tpm_tis: Add the missed acpi_put_table() to fix memory leak (CVE-2022-50824)

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

    fs/ntfs3: Add overflow check for attribute size (CVE-2022-50841)

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

    ext4: fix inode leak in ext4_xattr_inode_create() on an error path (CVE-2022-50845)

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

    fs/ntfs3: Fix slab-out-of-bounds in r_page (CVE-2022-50869)

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

    objtool: Fix SEGFAULT (CVE-2022-50879)

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

    dm integrity: Fix UAF in dm_integrity_dtr() (CVE-2022-50889)

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

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

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

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

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

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

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

    The setsockopt TCP_ULP operation does not require any privilege.

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

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

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

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

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

    btrfs: fix race between quota rescan and disable leading to NULL pointer deref (CVE-2023-52896)

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

    xhci: Fix null pointer dereference when host dies (CVE-2023-52898)

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

    usb: xhci: Check endpoint is valid before dereferencing it (CVE-2023-52901)

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

    io_uring: lock overflowing for IOPOLL (CVE-2023-52903)

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

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

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

    iommu/iova: Fix alloc iova overflows issue (CVE-2023-52910)

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

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

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

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

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

    fs/ntfs3: don't hold ni_lock when calling truncate_setsize() (CVE-2023-53163)

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

    netfilter: ipset: Rework long task execution when adding/deleting entries (CVE-2023-53549)

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

    x86/kexec: Fix double-free of elf header buffer (CVE-2023-54146)

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	Type	Severity
361580	AlmaLinux 9.2 [TuxCare] Security Update: bpftool / kernel / kernel-64k / kernel-64k-core / kernel-64k-debug / etc Multiple Vulnerabilities (ALMALINUX9.2:CLSA-2025:1762171389)	Nessus	Alma Linux Local Security Checks	Local	high
353813	Rocky Linux 8 [CIQ] Security Update: bpftool / bpftool-debuginfo / kernel / kernel-abi-stablelists / etc Multiple Vulnerabilities (crxsa-2024_3138)	Nessus	Rocky Linux Local Security Checks	Local	critical
319448	EulerOS Virtualization 2.13.1 : kernel (EulerOS-SA-2026-2132)	Nessus	Huawei Local Security Checks	Local	high
319325	EulerOS Virtualization 2.13.0 : kernel (EulerOS-SA-2026-2171)	Nessus	Huawei Local Security Checks	Local	high
309309	Unity Linux 20.1060a / 20.1070a Security Update: kernel (UTSA-2026-013629)	Nessus	Unity Linux Local Security Checks	Local	medium
308933	Unity Linux 20.1060e / 20.1070e Security Update: kernel (UTSA-2026-011069)	Nessus	Unity Linux Local Security Checks	Local	medium
307250	Unity Linux 20.1050e / 20.1060e / 20.1070e Security Update: kernel (UTSA-2026-007561)	Nessus	Unity Linux Local Security Checks	Local	medium
301628	EulerOS 2.0 SP13 : kernel (EulerOS-SA-2026-1280)	Nessus	Huawei Local Security Checks	Local	high
301595	EulerOS 2.0 SP13 : kernel (EulerOS-SA-2026-1244)	Nessus	Huawei Local Security Checks	Local	high
300092	SUSE SLES15: cluster-md-kmp-default / dlm-kmp-default / gfs2-kmp-default / etc (SUSE-SU-2026:0617-1)	Nessus	SuSE Local Security Checks	Local	medium
298924	SUSE SLES12: cluster-md-kmp-default / dlm-kmp-default / gfs2-kmp-default / etc (SUSE-SU-2026:0473-1)	Nessus	SuSE Local Security Checks	Local	high
297191	SUSE SLES15 : Security update for the Linux Kernel (SUSE-SU-2026:0317-1)	Nessus	SuSE Local Security Checks	Local	high
279859	Linux Distros Unpatched Vulnerability : CVE-2022-50782	Nessus	Misc.	Local	high
171848	Amazon Linux 2 : kernel, --advisory ALAS2KERNEL-5.4-2023-042 (ALASKERNEL-5.4-2023-042)	Nessus	Amazon Linux Local Security Checks	Local	high
171227	Amazon Linux 2 : kernel, --advisory ALAS2KERNEL-5.15-2023-013 (ALASKERNEL-5.15-2023-013)	Nessus	Amazon Linux Local Security Checks	Local	high
171216	Amazon Linux 2 : kernel, --advisory ALAS2KERNEL-5.10-2023-026 (ALASKERNEL-5.10-2023-026)	Nessus	Amazon Linux Local Security Checks	Local	high
151965	Photon OS 4.0: Linux PHSA-2021-4.0-0065	Nessus	PhotonOS Local Security Checks	Local	high

Detections

Analytics

CVE-2022-50782

medium

Tenable Plugins

high

critical

high

high

medium

medium

medium

high

high

medium

high

high

high

high

high

high

high