In the Linux kernel, the following vulnerability has been resolved: net: hns: fix possible memory leak in hnae_ae_register() Inject fault while probing module, if device_register() fails, but the refcount of kobject is not decreased to 0, the name allocated in dev_set_name() is leaked. Fix this by calling put_device(), so that name can be freed in callback function kobject_cleanup(). unreferenced object 0xffff00c01aba2100 (size 128): comm "systemd-udevd", pid 1259, jiffies 4294903284 (age 294.152s) hex dump (first 32 bytes): 68 6e 61 65 30 00 00 00 18 21 ba 1a c0 00 ff ff hnae0....!...... 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace: [<0000000034783f26>] slab_post_alloc_hook+0xa0/0x3e0 [<00000000748188f2>] __kmem_cache_alloc_node+0x164/0x2b0 [<00000000ab0743e8>] __kmalloc_node_track_caller+0x6c/0x390 [<000000006c0ffb13>] kvasprintf+0x8c/0x118 [<00000000fa27bfe1>] kvasprintf_const+0x60/0xc8 [<0000000083e10ed7>] kobject_set_name_vargs+0x3c/0xc0 [<000000000b87affc>] dev_set_name+0x7c/0xa0 [<000000003fd8fe26>] hnae_ae_register+0xcc/0x190 [hnae] [<00000000fe97edc9>] hns_dsaf_ae_init+0x9c/0x108 [hns_dsaf] [<00000000c36ff1eb>] hns_dsaf_probe+0x548/0x748 [hns_dsaf]

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

  - In the Linux kernel, the following vulnerability has been resolved: hwmon: (w83792d) Fix NULL pointer     dereference by removing unnecessary structure field If driver read val value sufficient for (val & 0x08)     && (!(val & 0x80)) && ((val & 0x7) == ((val >> 4) & 0x7)) from device then Null pointer dereference     occurs. (It is possible if tmp = 0b0xyz1xyz, where same literals mean same numbers) Also lm75[] does not     serve a purpose anymore after switching to devm_i2c_new_dummy_device() in w83791d_detect_subclients(). The     patch fixes possible NULL pointer dereference by removing lm75[]. Found by Linux Driver Verification     project (linuxtesting.org). [groeck: Dropped unnecessary continuation lines, fixed multipline alignment]     (CVE-2021-47385)

  - In the Linux kernel, the following vulnerability has been resolved: hwmon: (w83791d) Fix NULL pointer     dereference by removing unnecessary structure field If driver read val value sufficient for (val & 0x08)     && (!(val & 0x80)) && ((val & 0x7) == ((val >> 4) & 0x7)) from device then Null pointer dereference     occurs. (It is possible if tmp = 0b0xyz1xyz, where same literals mean same numbers) Also lm75[] does not     serve a purpose anymore after switching to devm_i2c_new_dummy_device() in w83791d_detect_subclients(). The     patch fixes possible NULL pointer dereference by removing lm75[]. Found by Linux Driver Verification     project (linuxtesting.org). [groeck: Dropped unnecessary continuation lines, fixed multi-line alignment]     (CVE-2021-47386)

  - In the Linux kernel, the following vulnerability has been resolved: mm/uffd: fix pte marker when fork()     without fork event Patch series mm: Fixes on pte markers. Patch 1 resolves the syzkiller report from     Pengfei. Patch 2 further harden pte markers when used with the recent swapin error markers. The major case     is we should persist a swapin error marker after fork(), so child shouldn't read a corrupted page. This     patch (of 2): When fork(), dst_vma is not guaranteed to have VM_UFFD_WP even if src may have it and has     pte marker installed. The warning is improper along with the comment. The right thing is to inherit the     pte marker when needed, or keep the dst pte empty. A vague guess is this happened by an accident when     there's the prior patch to introduce src/dst vma into this helper during the uffd-wp feature got developed     and I probably messed up in the rebase, since if we replace dst_vma with src_vma the warning & comment it     all makes sense too. Hugetlb did exactly the right here (copy_hugetlb_page_range()). Fix the general path.
    Reproducer: https://github.com/xupengfe/syzkaller_logs/blob/main/221208_115556_copy_page_range/repro.c     Bugzilla report: https://bugzilla.kernel.org/show_bug.cgi?id=216808 (CVE-2022-49744)

  - In the Linux kernel, the following vulnerability has been resolved: drm/vkms: Fix memory leak in     vkms_init() A memory leak was reported after the vkms module install failed. unreferenced object     0xffff88810bc28520 (size 16): comm modprobe, pid 9662, jiffies 4298009455 (age 42.590s) hex dump (first     16 bytes): 01 01 00 64 81 88 ff ff 00 00 dc 0a 81 88 ff ff ...d............ backtrace:
    [<00000000e7561ff8>] kmalloc_trace+0x27/0x60 [<000000000b1954a0>] 0xffffffffc45200a9 [<00000000abbf1da0>]     do_one_initcall+0xd0/0x4f0 [<000000001505ee87>] do_init_module+0x1a4/0x680 [<00000000958079ad>]     load_module+0x6249/0x7110 [<00000000117e4696>] __do_sys_finit_module+0x140/0x200 [<00000000f74b12d2>]     do_syscall_64+0x35/0x80 [<000000008fc6fcde>] entry_SYSCALL_64_after_hwframe+0x46/0xb0 The reason is that     the vkms_init() returns without checking the return value of vkms_create(), and if the vkms_create()     failed, the config allocated at the beginning of vkms_init() is leaked. vkms_init() config = kmalloc(...)     # config allocated ... return vkms_create() # vkms_create failed and config is leaked Fix this problem by     checking return value of vkms_create() and free the config if error happened. (CVE-2022-50269)

  - In the Linux kernel, the following vulnerability has been resolved: net: hns: fix possible memory leak in     hnae_ae_register() Inject fault while probing module, if device_register() fails, but the refcount of     kobject is not decreased to 0, the name allocated in dev_set_name() is leaked. Fix this by calling     put_device(), so that name can be freed in callback function kobject_cleanup(). unreferenced object     0xffff00c01aba2100 (size 128): comm systemd-udevd, pid 1259, jiffies 4294903284 (age 294.152s) hex dump     (first 32 bytes): 68 6e 61 65 30 00 00 00 18 21 ba 1a c0 00 ff ff hnae0....!...... 00 00 00 00 00 00 00 00     00 00 00 00 00 00 00 00 ................ backtrace: [<0000000034783f26>] slab_post_alloc_hook+0xa0/0x3e0     [<00000000748188f2>] __kmem_cache_alloc_node+0x164/0x2b0 [<00000000ab0743e8>]
    __kmalloc_node_track_caller+0x6c/0x390 [<000000006c0ffb13>] kvasprintf+0x8c/0x118 [<00000000fa27bfe1>]     kvasprintf_const+0x60/0xc8 [<0000000083e10ed7>] kobject_set_name_vargs+0x3c/0xc0 [<000000000b87affc>]     dev_set_name+0x7c/0xa0 [<000000003fd8fe26>] hnae_ae_register+0xcc/0x190 [hnae] [<00000000fe97edc9>]     hns_dsaf_ae_init+0x9c/0x108 [hns_dsaf] [<00000000c36ff1eb>] hns_dsaf_probe+0x548/0x748 [hns_dsaf]     (CVE-2022-50352)

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 9.6 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare ALMALINUX9.6:CLSA-2026:1779434490 advisory.

  - In the Linux kernel, the following vulnerability has been resolved: configfs: fix a race in     configfs_{,un}register_subsystem() When configfs_register_subsystem() or configfs_unregister_subsystem()     is executing link_group() or unlink_group(), it is possible that two processes add or delete list     concurrently. Some unfortunate interleavings of them can cause kernel panic. One of cases is: A --> B -->     C --> D A <-- B <-- C <-- D delete list_head *B | delete list_head *C
    --------------------------------|----------------------------------- configfs_unregister_subsystem |     configfs_unregister_subsystem unlink_group | unlink_group unlink_obj | unlink_obj list_del_init |     list_del_init __list_del_entry | __list_del_entry __list_del | __list_del // next == C | next->prev = prev     | | next->prev = prev prev->next = next | | // prev == B | prev->next = next Fix this by adding mutex when     calling link_group() or unlink_group(), but parent configfs_subsystem is NULL when config_item is root. So     I create a mutex configfs_subsystem_mutex. (CVE-2022-48931)

  - In the Linux kernel, the following vulnerability has been resolved: list: fix a data-race around     ep->rdllist ep_poll() first calls ep_events_available() with no lock held and checks if ep->rdllist is     empty by list_empty_careful(), which reads rdllist->prev. Thus all accesses to it need some protection to     avoid store/load-tearing. Note INIT_LIST_HEAD_RCU() already has the annotation for both prev and next.
    Commit bf3b9f6372c4 (epoll: Add busy poll support to epoll with socket fds.) added the first lockless     ep_events_available(), and commit c5a282e9635e (fs/epoll: reduce the scope of wq lock in epoll_wait())     made some ep_events_available() calls lockless and added single call under a lock, finally commit     e59d3c64cba6 (epoll: eliminate unnecessary lock for zero timeout) made the last ep_events_available()     lockless. BUG: KCSAN: data-race in do_epoll_wait / do_epoll_wait write to 0xffff88810480c7d8 of 8 bytes by     task 1802 on cpu 0: INIT_LIST_HEAD include/linux/list.h:38 [inline] list_splice_init     include/linux/list.h:492 [inline] ep_start_scan fs/eventpoll.c:622 [inline] ep_send_events     fs/eventpoll.c:1656 [inline] ep_poll fs/eventpoll.c:1806 [inline] do_epoll_wait+0x4eb/0xf40     fs/eventpoll.c:2234 do_epoll_pwait fs/eventpoll.c:2268 [inline] __do_sys_epoll_pwait fs/eventpoll.c:2281     [inline] __se_sys_epoll_pwait+0x12b/0x240 fs/eventpoll.c:2275 __x64_sys_epoll_pwait+0x74/0x80     fs/eventpoll.c:2275 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x44/0xd0     arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x44/0xae read to 0xffff88810480c7d8 of 8 bytes     by task 1799 on cpu 1: list_empty_careful include/linux/list.h:329 [inline] ep_events_available     fs/eventpoll.c:381 [inline] ep_poll fs/eventpoll.c:1797 [inline] do_epoll_wait+0x279/0xf40     fs/eventpoll.c:2234 do_epoll_pwait fs/eventpoll.c:2268 [inline] __do_sys_epoll_pwait fs/eventpoll.c:2281     [inline] __se_sys_epoll_pwait+0x12b/0x240 fs/eventpoll.c:2275 __x64_sys_epoll_pwait+0x74/0x80     fs/eventpoll.c:2275 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x44/0xd0     arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x44/0xae value changed: 0xffff88810480c7d0 ->     0xffff888103c15098 Reported by Kernel Concurrency Sanitizer on: CPU: 1 PID: 1799 Comm: syz-fuzzer Tainted:
    G W 5.17.0-rc7-syzkaller-dirty #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS     Google 01/01/2011 (CVE-2022-49443)

  - In the Linux kernel, the following vulnerability has been resolved: ima: Fix potential memory leak in     ima_init_crypto() On failure to allocate the SHA1 tfm, IMA fails to initialize and exits without freeing     the ima_algo_array. Add the missing kfree() for ima_algo_array to avoid the potential memory leak.
    (CVE-2022-49627)

  - In the Linux kernel, the following vulnerability has been resolved: tracing/histograms: Fix memory leak     problem This reverts commit 46bbe5c671e06f070428b9be142cc4ee5cedebac. As commit 46bbe5c671e0 (tracing:
    fix double free) said, the double free problem reported by clang static analyzer is: > In     parse_var_defs() if there is a problem allocating > var_defs.expr, the earlier var_defs.name is freed. >     This free is duplicated by free_var_defs() which frees > the rest of the list. However, if there is a     problem allocating N-th var_defs.expr: + in parse_var_defs(), the freed 'earlier var_defs.name' is     actually the N-th var_defs.name; + then in free_var_defs(), the names from 0th to (N-1)-th are freed; IF     ALLOCATING PROBLEM HAPPENED HERE!!! -+ \ | 0th 1th (N-1)-th N-th V     +-------------+-------------+-----+-------------+----------- var_defs: | name | expr | name | expr | ... |     name | expr | name | /// +-------------+-------------+-----+-------------+----------- These two frees     don't act on same name, so there was no double free problem before. Conversely, after that commit, we     get a memory leak problem because the above N-th var_defs.name is not freed. If enable     CONFIG_DEBUG_KMEMLEAK and inject a fault at where the N-th var_defs.expr allocated, then execute on shell     like: $ echo 'hist:key=call_site:val=$v1,$v2:v1=bytes_req,v2=bytes_alloc' > \     /sys/kernel/debug/tracing/events/kmem/kmalloc/trigger Then kmemleak reports: unreferenced object     0xffff8fb100ef3518 (size 8): comm bash, pid 196, jiffies 4295681690 (age 28.538s) hex dump (first 8     bytes): 76 31 00 00 b1 8f ff ff v1...... backtrace: [<0000000038fe4895>] kstrdup+0x2d/0x60     [<00000000c99c049a>] event_hist_trigger_parse+0x206f/0x20e0 [<00000000ae70d2cc>]     trigger_process_regex+0xc0/0x110 [<0000000066737a4c>] event_trigger_write+0x75/0xd0 [<000000007341e40c>]     vfs_write+0xbb/0x2a0 [<0000000087fde4c2>] ksys_write+0x59/0xd0 [<00000000581e9cdf>]     do_syscall_64+0x3a/0x80 [<00000000cf3b065c>] entry_SYSCALL_64_after_hwframe+0x46/0xb0 (CVE-2022-49648)

  - In the Linux kernel, the following vulnerability has been resolved: linux/dim: Fix divide by 0 in RDMA DIM     Fix a divide 0 error in rdma_dim_stats_compare() when prev->cpe_ratio == 0. CallTrace: Hardware name: H3C     R4900 G3/RS33M2C9S, BIOS 2.00.37P21 03/12/2020 task: ffff880194b78000 task.stack: ffffc90006714000 RIP:
    0010:backport_rdma_dim+0x10e/0x240 [mlx_compat] RSP: 0018:ffff880c10e83ec0 EFLAGS: 00010202 RAX:
    0000000000002710 RBX: ffff88096cd7f780 RCX: 0000000000000064 RDX: 0000000000000000 RSI: 0000000000000002     RDI: 0000000000000001 RBP: 0000000000000001 R08: 0000000000000000 R09: 0000000000000000 R10:
    0000000000000000 R11: 0000000000000000 R12: 000000001d7c6c09 R13: ffff88096cd7f780 R14: ffff880b174fe800     R15: 0000000000000000 FS: 0000000000000000(0000) GS:ffff880c10e80000(0000) knlGS:0000000000000000 CS: 0010     DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00000000a0965b00 CR3: 000000000200a003 CR4: 00000000007606e0     DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6:
    00000000fffe0ff0 DR7: 0000000000000400 PKRU: 55555554 Call Trace: <IRQ> ib_poll_handler+0x43/0x80     [ib_core] irq_poll_softirq+0xae/0x110 __do_softirq+0xd1/0x28c irq_exit+0xde/0xf0 do_IRQ+0x54/0xe0     common_interrupt+0x8f/0x8f </IRQ> ? cpuidle_enter_state+0xd9/0x2a0 ? cpuidle_enter_state+0xc7/0x2a0 ?     do_idle+0x170/0x1d0 ? cpu_startup_entry+0x6f/0x80 ? start_secondary+0x1b9/0x210 ?     secondary_startup_64+0xa5/0xb0 Code: 0f 87 e1 00 00 00 8b 4c 24 14 44 8b 43 14 89 c8 4d 63 c8 44 29 c0 99     31 d0 29 d0 31 d2 48 98 48 8d 04 80 48 8d 04 80 48 c1 e0 02 <49> f7 f1 48 83 f8 0a 0f 86 c1 00 00 00 44 39     c1 7f 10 48 89 df RIP: backport_rdma_dim+0x10e/0x240 [mlx_compat] RSP: ffff880c10e83ec0 (CVE-2022-49670)

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

The AlmaLinux 9.6 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare ALMALINUX9.6:CLSA-2026:1779434490 advisory.

  - In the Linux kernel, the following vulnerability has been resolved: configfs: fix a race in     configfs_{,un}register_subsystem() When configfs_register_subsystem() or configfs_unregister_subsystem()     is executing link_group() or unlink_group(), it is possible that two processes add or delete list     concurrently. Some unfortunate interleavings of them can cause kernel panic. One of cases is: A --> B -->     C --> D A <-- B <-- C <-- D delete list_head *B | delete list_head *C
    --------------------------------|----------------------------------- configfs_unregister_subsystem |     configfs_unregister_subsystem unlink_group | unlink_group unlink_obj | unlink_obj list_del_init |     list_del_init __list_del_entry | __list_del_entry __list_del | __list_del // next == C | next->prev = prev     | | next->prev = prev prev->next = next | | // prev == B | prev->next = next Fix this by adding mutex when     calling link_group() or unlink_group(), but parent configfs_subsystem is NULL when config_item is root. So     I create a mutex configfs_subsystem_mutex. (CVE-2022-48931)

  - In the Linux kernel, the following vulnerability has been resolved: list: fix a data-race around     ep->rdllist ep_poll() first calls ep_events_available() with no lock held and checks if ep->rdllist is     empty by list_empty_careful(), which reads rdllist->prev. Thus all accesses to it need some protection to     avoid store/load-tearing. Note INIT_LIST_HEAD_RCU() already has the annotation for both prev and next.
    Commit bf3b9f6372c4 (epoll: Add busy poll support to epoll with socket fds.) added the first lockless     ep_events_available(), and commit c5a282e9635e (fs/epoll: reduce the scope of wq lock in epoll_wait())     made some ep_events_available() calls lockless and added single call under a lock, finally commit     e59d3c64cba6 (epoll: eliminate unnecessary lock for zero timeout) made the last ep_events_available()     lockless. BUG: KCSAN: data-race in do_epoll_wait / do_epoll_wait write to 0xffff88810480c7d8 of 8 bytes by     task 1802 on cpu 0: INIT_LIST_HEAD include/linux/list.h:38 [inline] list_splice_init     include/linux/list.h:492 [inline] ep_start_scan fs/eventpoll.c:622 [inline] ep_send_events     fs/eventpoll.c:1656 [inline] ep_poll fs/eventpoll.c:1806 [inline] do_epoll_wait+0x4eb/0xf40     fs/eventpoll.c:2234 do_epoll_pwait fs/eventpoll.c:2268 [inline] __do_sys_epoll_pwait fs/eventpoll.c:2281     [inline] __se_sys_epoll_pwait+0x12b/0x240 fs/eventpoll.c:2275 __x64_sys_epoll_pwait+0x74/0x80     fs/eventpoll.c:2275 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x44/0xd0     arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x44/0xae read to 0xffff88810480c7d8 of 8 bytes     by task 1799 on cpu 1: list_empty_careful include/linux/list.h:329 [inline] ep_events_available     fs/eventpoll.c:381 [inline] ep_poll fs/eventpoll.c:1797 [inline] do_epoll_wait+0x279/0xf40     fs/eventpoll.c:2234 do_epoll_pwait fs/eventpoll.c:2268 [inline] __do_sys_epoll_pwait fs/eventpoll.c:2281     [inline] __se_sys_epoll_pwait+0x12b/0x240 fs/eventpoll.c:2275 __x64_sys_epoll_pwait+0x74/0x80     fs/eventpoll.c:2275 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x44/0xd0     arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x44/0xae value changed: 0xffff88810480c7d0 ->     0xffff888103c15098 Reported by Kernel Concurrency Sanitizer on: CPU: 1 PID: 1799 Comm: syz-fuzzer Tainted:
    G W 5.17.0-rc7-syzkaller-dirty #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS     Google 01/01/2011 (CVE-2022-49443)

  - In the Linux kernel, the following vulnerability has been resolved: ima: Fix potential memory leak in     ima_init_crypto() On failure to allocate the SHA1 tfm, IMA fails to initialize and exits without freeing     the ima_algo_array. Add the missing kfree() for ima_algo_array to avoid the potential memory leak.
    (CVE-2022-49627)

  - In the Linux kernel, the following vulnerability has been resolved: tracing/histograms: Fix memory leak     problem This reverts commit 46bbe5c671e06f070428b9be142cc4ee5cedebac. As commit 46bbe5c671e0 (tracing:
    fix double free) said, the double free problem reported by clang static analyzer is: > In     parse_var_defs() if there is a problem allocating > var_defs.expr, the earlier var_defs.name is freed. >     This free is duplicated by free_var_defs() which frees > the rest of the list. However, if there is a     problem allocating N-th var_defs.expr: + in parse_var_defs(), the freed 'earlier var_defs.name' is     actually the N-th var_defs.name; + then in free_var_defs(), the names from 0th to (N-1)-th are freed; IF     ALLOCATING PROBLEM HAPPENED HERE!!! -+ \ | 0th 1th (N-1)-th N-th V     +-------------+-------------+-----+-------------+----------- var_defs: | name | expr | name | expr | ... |     name | expr | name | /// +-------------+-------------+-----+-------------+----------- These two frees     don't act on same name, so there was no double free problem before. Conversely, after that commit, we     get a memory leak problem because the above N-th var_defs.name is not freed. If enable     CONFIG_DEBUG_KMEMLEAK and inject a fault at where the N-th var_defs.expr allocated, then execute on shell     like: $ echo 'hist:key=call_site:val=$v1,$v2:v1=bytes_req,v2=bytes_alloc' > \     /sys/kernel/debug/tracing/events/kmem/kmalloc/trigger Then kmemleak reports: unreferenced object     0xffff8fb100ef3518 (size 8): comm bash, pid 196, jiffies 4295681690 (age 28.538s) hex dump (first 8     bytes): 76 31 00 00 b1 8f ff ff v1...... backtrace: [<0000000038fe4895>] kstrdup+0x2d/0x60     [<00000000c99c049a>] event_hist_trigger_parse+0x206f/0x20e0 [<00000000ae70d2cc>]     trigger_process_regex+0xc0/0x110 [<0000000066737a4c>] event_trigger_write+0x75/0xd0 [<000000007341e40c>]     vfs_write+0xbb/0x2a0 [<0000000087fde4c2>] ksys_write+0x59/0xd0 [<00000000581e9cdf>]     do_syscall_64+0x3a/0x80 [<00000000cf3b065c>] entry_SYSCALL_64_after_hwframe+0x46/0xb0 (CVE-2022-49648)

  - In the Linux kernel, the following vulnerability has been resolved: linux/dim: Fix divide by 0 in RDMA DIM     Fix a divide 0 error in rdma_dim_stats_compare() when prev->cpe_ratio == 0. CallTrace: Hardware name: H3C     R4900 G3/RS33M2C9S, BIOS 2.00.37P21 03/12/2020 task: ffff880194b78000 task.stack: ffffc90006714000 RIP:
    0010:backport_rdma_dim+0x10e/0x240 [mlx_compat] RSP: 0018:ffff880c10e83ec0 EFLAGS: 00010202 RAX:
    0000000000002710 RBX: ffff88096cd7f780 RCX: 0000000000000064 RDX: 0000000000000000 RSI: 0000000000000002     RDI: 0000000000000001 RBP: 0000000000000001 R08: 0000000000000000 R09: 0000000000000000 R10:
    0000000000000000 R11: 0000000000000000 R12: 000000001d7c6c09 R13: ffff88096cd7f780 R14: ffff880b174fe800     R15: 0000000000000000 FS: 0000000000000000(0000) GS:ffff880c10e80000(0000) knlGS:0000000000000000 CS: 0010     DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00000000a0965b00 CR3: 000000000200a003 CR4: 00000000007606e0     DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6:
    00000000fffe0ff0 DR7: 0000000000000400 PKRU: 55555554 Call Trace: <IRQ> ib_poll_handler+0x43/0x80     [ib_core] irq_poll_softirq+0xae/0x110 __do_softirq+0xd1/0x28c irq_exit+0xde/0xf0 do_IRQ+0x54/0xe0     common_interrupt+0x8f/0x8f </IRQ> ? cpuidle_enter_state+0xd9/0x2a0 ? cpuidle_enter_state+0xc7/0x2a0 ?     do_idle+0x170/0x1d0 ? cpu_startup_entry+0x6f/0x80 ? start_secondary+0x1b9/0x210 ?     secondary_startup_64+0xa5/0xb0 Code: 0f 87 e1 00 00 00 8b 4c 24 14 44 8b 43 14 89 c8 4d 63 c8 44 29 c0 99     31 d0 29 d0 31 d2 48 98 48 8d 04 80 48 8d 04 80 48 c1 e0 02 <49> f7 f1 48 83 f8 0a 0f 86 c1 00 00 00 44 39     c1 7f 10 48 89 df RIP: backport_rdma_dim+0x10e/0x240 [mlx_compat] RSP: ffff880c10e83ec0 (CVE-2022-49670)

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

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

    media: v4l2-mem2mem: add lock to protect parameter num_rdy(CVE-2023-53519)

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

    mm/vmscan: don't try to reclaim hwpoison folio(CVE-2025-37834)

    ubi: Fix unreferenced object reported by kmemleak in ubi_resize_volume()(CVE-2023-53271)

    md/raid10: fix wrong setting of max_corr_read_errors(CVE-2023-53313)

    scsi: target: target_core_configfs: Add length check to avoid buffer overflow(CVE-2025-39998)

    loop: Avoid updating block size under exclusive owner(CVE-2025-38709)

    mm/memory-failure: fix VM_BUG_ON_PAGE(PagePoisoned(page)) when unpoison memory(CVE-2025-39883)

    scsi: qla4xxx: Prevent a potential error pointer dereference(CVE-2025-39676)

    NFS: Fix a race when updating an existing write(CVE-2025-39697)

    scsi: ses: Fix possible addl_desc_ptr out-of-bounds accesses(CVE-2023-7324)

    efivarfs: Fix slab-out-of-bounds in efivarfs_d_compare(CVE-2025-39817)

    dm raid: fix address sanitizer warning in raid_resume(CVE-2022-50085)

    usb-storage: alauda: Fix uninit-value in alauda_check_media()(CVE-2023-53847)

    mm/vmscan: fix hwpoisoned large folio handling in shrink_folio_list(CVE-2025-39725)

    md/raid10: fix null-ptr-deref of mreplace in raid10_sync_request(CVE-2023-53380)

    md/raid10: check slab-out-of-bounds in md_bitmap_get_counter(CVE-2023-53357)

    net: sched: cls_u32: Undo tcf_bind_filter if u32_replace_hw_knode(CVE-2023-53733)

    fs: quota: create dedicated workqueue for quota_release_work(CVE-2025-40196)

    partitions: mac: fix handling of bogus partition table(CVE-2025-21772)

    HID: hidraw: fix memory leak in hidraw_release()(CVE-2022-49981)

    pid: Add a judgment for ns null in pid_nr_ns(CVE-2025-40178)

    libceph: fix potential use-after-free in have_mon_and_osd_map()(CVE-2025-68285)

    watchdog: Fix kmemleak in watchdog_cdev_register(CVE-2023-53234)

    drivers/md/md-bitmap: check the return value of md_bitmap_get_counter()(CVE-2022-50402)

    PNP: fix name memory leak in pnp_alloc_dev()(CVE-2022-50278)

    ipvs: Defer ip_vs_ftp unregister during netns cleanup(CVE-2025-40018)

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

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

    ubi: ubi_wl_put_peb: Fix infinite loop when wear-leveling work failed(CVE-2023-53481)

    cacheinfo: Fix shared_cpu_map to handle shared caches at different levels(CVE-2023-53254)

    scsi: mpt3sas: Fix crash in transport port remove by using ioc_info()(CVE-2025-40115)

    scsi: target: iscsi: Fix buffer overflow in lio_target_nacl_info_show()(CVE-2023-53676)

    NFSv4/pNFS: Clear NFS_INO_LAYOUTCOMMIT in pnfs_mark_layout_stateid_invalid(CVE-2025-68349)

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

    md: call __md_stop_writes in md_stop(CVE-2022-49987)

    net/packet: fix a race in packet_set_ring() and packet_notifier()(CVE-2025-38617)

    regulator: of: Fix refcount leak bug in of_get_regulation_constraints()(CVE-2022-50191)

    ubi: Fix use-after-free when volume resizing failed(CVE-2023-53800)

    HID: multitouch: Correct devm device reference for hidinput input_dev name(CVE-2023-53454)

    ipv6: reject malicious packets in ipv6_gso_segment()(CVE-2025-38572)

    md/raid10: fix leak of 'r10bio-remaining' for recovery(CVE-2023-53299)

    scsi: qla2xxx: Wait for io return on terminate rport(CVE-2023-53322)

    udf: Detect system inodes linked into directory hierarchy(CVE-2023-53695)

    igb: Fix igb_down hung on surprise removal(CVE-2023-53148)

    cifs: Fix warning and UAF when destroy the MR list(CVE-2023-53427)

    scsi: ses: Fix slab-out-of-bounds in ses_enclosure_data_process()(CVE-2023-53803)

    ubi: ensure that VID header offset + VID header size = alloc, size(CVE-2023-53265)

    fs/proc: fix uaf in proc_readdir_de()(CVE-2025-40271)

    firmware: arm_scpi: Ensure scpi_info is not assigned if the probe fails(CVE-2022-50087)

    md-raid10: fix KASAN warning(CVE-2022-50211)

    scsi: ses: Fix possible desc_ptr out-of-bounds accesses(CVE-2023-53675)

    mmc: core: Fix kernel panic when remove non-standard SDIO card(CVE-2022-50640)

    nfs: handle failure of nfs_get_lock_context in unlock path(CVE-2025-38023)

    udf: Do not update file length for failed writes to inline files(CVE-2023-53295)

    RDMA/rxe: Fix slab-use-after-free Read in rxe_queue_cleanup bug(CVE-2025-38024)

    sctp: check send stream number after wait_for_sndbuf(CVE-2023-53296)

    net/sched: sch_qfq: Fix race condition on qfq_aggregate(CVE-2025-38477)

    RDMA/rxe: Fix 'kernel NULL pointer dereference' error(CVE-2022-50671)

    i40e: add validation for ring_len param(CVE-2025-39973)

    md/raid1: Fix stack memory use after return in raid1_reshape(CVE-2025-38445)

    Squashfs: check return result of sb_min_blocksize(CVE-2025-38415)

    net/tunnel: wait until all sk_user_data reader finish before releasing the sock(CVE-2022-50405)

    ip6_vti: fix slab-use-after-free in decode_session6(CVE-2023-53821)

    af_unix: Fix data-races around user-unix_inflight.(CVE-2023-53204)

    RDMA/rxe: Fix error unwind in rxe_create_qp()(CVE-2022-50127)

    __legitimize_mnt(): check for MNT_SYNC_UMOUNT should be under mount_lock(CVE-2025-38058)

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

    scsi: hpsa: Fix possible memory leak in hpsa_init_one()(CVE-2022-50646)

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

    vsock: Do not allow binding to VMADDR_PORT_ANY(CVE-2025-38618)

    smb: client: Fix use-after-free in cifs_fill_dirent(CVE-2025-38051)

    scsi: libiscsi: Initialize iscsi_conn-dd_data only if memory is allocated(CVE-2025-38700)

    sctp: fix a potential overflow in sctp_ifwdtsn_skip(CVE-2023-53372)

    pstore/ram: Check start of empty przs during init(CVE-2023-53331)

    clk: samsung: Fix memory leak in _samsung_clk_register_pll()(CVE-2022-50449)

    md/raid10: prevent soft lockup while flush writes(CVE-2023-53151)

    nfsd: call op_release, even when op_func returns an error(CVE-2023-53241)

    cifs: Release folio lock on fscache read hit.(CVE-2023-53593)

    net: bridge: fix soft lockup in br_multicast_query_expired()(CVE-2025-39773)

    cifs: fix small mempool leak in SMB2_negotiate()(CVE-2022-49938)

    dm raid: fix address sanitizer warning in raid_status(CVE-2022-50084)

    nfsd: handle get_client_locked() failure in nfsd4_setclientid_confirm()(CVE-2025-38724)

    scsi: qla2xxx: Check valid rport returned by fc_bsg_to_rport()(CVE-2023-54014)

    block: fix resource leak in blk_register_queue() error path(CVE-2025-37980)

    drm/client: Fix memory leak in drm_client_target_cloned(CVE-2023-54091)

    dm flakey: fix a crash with invalid table line(CVE-2023-53786)

    crypto: lib/mpi - avoid null pointer deref in mpi_cmp_ui()(CVE-2023-53817)

    hwrng: virtio - Fix race on data_avail and actual data(CVE-2023-53998)

    sched/fair: Don't balance task to its current running CPU(CVE-2023-53215)

    ppp: associate skb with a device at tx(CVE-2022-50655)

    fbdev: bitblit: bound-check glyph index in bit_putcs*(CVE-2025-40322)

    acct: fix potential integer overflow in encode_comp_t()(CVE-2022-50749)

    udf: Avoid double brelse() in udf_rename()(CVE-2022-50755)

    tee: add overflow check in register_shm_helper()(CVE-2022-50080)

    drm: Prevent drm_copy_field() to attempt copying a NULL pointer(CVE-2022-50884)

    crypto: api - Use work queue in crypto_destroy_instance(CVE-2023-53799)

    mm/swap: fix swap_info_struct race between swapoff and get_swap_pages()(CVE-2023-53623)

Tenable has extracted the preceding description block directly from the EulerOS Virtualization kernel security advisory.

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

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

    media: v4l2-mem2mem: add lock to protect parameter num_rdy(CVE-2023-53519)

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

    mm/vmscan: don't try to reclaim hwpoison folio(CVE-2025-37834)

    ubi: Fix unreferenced object reported by kmemleak in ubi_resize_volume()(CVE-2023-53271)

    md/raid10: fix wrong setting of max_corr_read_errors(CVE-2023-53313)

    scsi: target: target_core_configfs: Add length check to avoid buffer overflow(CVE-2025-39998)

    loop: Avoid updating block size under exclusive owner(CVE-2025-38709)

    mm/memory-failure: fix VM_BUG_ON_PAGE(PagePoisoned(page)) when unpoison memory(CVE-2025-39883)

    scsi: qla4xxx: Prevent a potential error pointer dereference(CVE-2025-39676)

    NFS: Fix a race when updating an existing write(CVE-2025-39697)

    scsi: ses: Fix possible addl_desc_ptr out-of-bounds accesses(CVE-2023-7324)

    efivarfs: Fix slab-out-of-bounds in efivarfs_d_compare(CVE-2025-39817)

    dm raid: fix address sanitizer warning in raid_resume(CVE-2022-50085)

    usb-storage: alauda: Fix uninit-value in alauda_check_media()(CVE-2023-53847)

    mm/vmscan: fix hwpoisoned large folio handling in shrink_folio_list(CVE-2025-39725)

    md/raid10: fix null-ptr-deref of mreplace in raid10_sync_request(CVE-2023-53380)

    md/raid10: check slab-out-of-bounds in md_bitmap_get_counter(CVE-2023-53357)

    net: sched: cls_u32: Undo tcf_bind_filter if u32_replace_hw_knode(CVE-2023-53733)

    fs: quota: create dedicated workqueue for quota_release_work(CVE-2025-40196)

    partitions: mac: fix handling of bogus partition table(CVE-2025-21772)

    HID: hidraw: fix memory leak in hidraw_release()(CVE-2022-49981)

    pid: Add a judgment for ns null in pid_nr_ns(CVE-2025-40178)

    libceph: fix potential use-after-free in have_mon_and_osd_map()(CVE-2025-68285)

    watchdog: Fix kmemleak in watchdog_cdev_register(CVE-2023-53234)

    drivers/md/md-bitmap: check the return value of md_bitmap_get_counter()(CVE-2022-50402)

    PNP: fix name memory leak in pnp_alloc_dev()(CVE-2022-50278)

    ipvs: Defer ip_vs_ftp unregister during netns cleanup(CVE-2025-40018)

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

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

    ubi: ubi_wl_put_peb: Fix infinite loop when wear-leveling work failed(CVE-2023-53481)

    cacheinfo: Fix shared_cpu_map to handle shared caches at different levels(CVE-2023-53254)

    scsi: mpt3sas: Fix crash in transport port remove by using ioc_info()(CVE-2025-40115)

    scsi: target: iscsi: Fix buffer overflow in lio_target_nacl_info_show()(CVE-2023-53676)

    NFSv4/pNFS: Clear NFS_INO_LAYOUTCOMMIT in pnfs_mark_layout_stateid_invalid(CVE-2025-68349)

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

    md: call __md_stop_writes in md_stop(CVE-2022-49987)

    net/packet: fix a race in packet_set_ring() and packet_notifier()(CVE-2025-38617)

    regulator: of: Fix refcount leak bug in of_get_regulation_constraints()(CVE-2022-50191)

    ubi: Fix use-after-free when volume resizing failed(CVE-2023-53800)

    HID: multitouch: Correct devm device reference for hidinput input_dev name(CVE-2023-53454)

    ipv6: reject malicious packets in ipv6_gso_segment()(CVE-2025-38572)

    md/raid10: fix leak of 'r10bio-remaining' for recovery(CVE-2023-53299)

    scsi: qla2xxx: Wait for io return on terminate rport(CVE-2023-53322)

    udf: Detect system inodes linked into directory hierarchy(CVE-2023-53695)

    igb: Fix igb_down hung on surprise removal(CVE-2023-53148)

    cifs: Fix warning and UAF when destroy the MR list(CVE-2023-53427)

    scsi: ses: Fix slab-out-of-bounds in ses_enclosure_data_process()(CVE-2023-53803)

    ubi: ensure that VID header offset + VID header size = alloc, size(CVE-2023-53265)

    fs/proc: fix uaf in proc_readdir_de()(CVE-2025-40271)

    firmware: arm_scpi: Ensure scpi_info is not assigned if the probe fails(CVE-2022-50087)

    md-raid10: fix KASAN warning(CVE-2022-50211)

    scsi: ses: Fix possible desc_ptr out-of-bounds accesses(CVE-2023-53675)

    mmc: core: Fix kernel panic when remove non-standard SDIO card(CVE-2022-50640)

    nfs: handle failure of nfs_get_lock_context in unlock path(CVE-2025-38023)

    udf: Do not update file length for failed writes to inline files(CVE-2023-53295)

    RDMA/rxe: Fix slab-use-after-free Read in rxe_queue_cleanup bug(CVE-2025-38024)

    sctp: check send stream number after wait_for_sndbuf(CVE-2023-53296)

    net/sched: sch_qfq: Fix race condition on qfq_aggregate(CVE-2025-38477)

    RDMA/rxe: Fix 'kernel NULL pointer dereference' error(CVE-2022-50671)

    i40e: add validation for ring_len param(CVE-2025-39973)

    md/raid1: Fix stack memory use after return in raid1_reshape(CVE-2025-38445)

    Squashfs: check return result of sb_min_blocksize(CVE-2025-38415)

    net/tunnel: wait until all sk_user_data reader finish before releasing the sock(CVE-2022-50405)

    ip6_vti: fix slab-use-after-free in decode_session6(CVE-2023-53821)

    af_unix: Fix data-races around user-unix_inflight.(CVE-2023-53204)

    RDMA/rxe: Fix error unwind in rxe_create_qp()(CVE-2022-50127)

    __legitimize_mnt(): check for MNT_SYNC_UMOUNT should be under mount_lock(CVE-2025-38058)

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

    scsi: hpsa: Fix possible memory leak in hpsa_init_one()(CVE-2022-50646)

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

    vsock: Do not allow binding to VMADDR_PORT_ANY(CVE-2025-38618)

    smb: client: Fix use-after-free in cifs_fill_dirent(CVE-2025-38051)

    scsi: libiscsi: Initialize iscsi_conn-dd_data only if memory is allocated(CVE-2025-38700)

    sctp: fix a potential overflow in sctp_ifwdtsn_skip(CVE-2023-53372)

    pstore/ram: Check start of empty przs during init(CVE-2023-53331)

    clk: samsung: Fix memory leak in _samsung_clk_register_pll()(CVE-2022-50449)

    md/raid10: prevent soft lockup while flush writes(CVE-2023-53151)

    nfsd: call op_release, even when op_func returns an error(CVE-2023-53241)

    cifs: Release folio lock on fscache read hit.(CVE-2023-53593)

    net: bridge: fix soft lockup in br_multicast_query_expired()(CVE-2025-39773)

    cifs: fix small mempool leak in SMB2_negotiate()(CVE-2022-49938)

    dm raid: fix address sanitizer warning in raid_status(CVE-2022-50084)

    nfsd: handle get_client_locked() failure in nfsd4_setclientid_confirm()(CVE-2025-38724)

    scsi: qla2xxx: Check valid rport returned by fc_bsg_to_rport()(CVE-2023-54014)

    block: fix resource leak in blk_register_queue() error path(CVE-2025-37980)

    drm/client: Fix memory leak in drm_client_target_cloned(CVE-2023-54091)

    dm flakey: fix a crash with invalid table line(CVE-2023-53786)

    crypto: lib/mpi - avoid null pointer deref in mpi_cmp_ui()(CVE-2023-53817)

    hwrng: virtio - Fix race on data_avail and actual data(CVE-2023-53998)

    sched/fair: Don't balance task to its current running CPU(CVE-2023-53215)

    ppp: associate skb with a device at tx(CVE-2022-50655)

    fbdev: bitblit: bound-check glyph index in bit_putcs*(CVE-2025-40322)

    acct: fix potential integer overflow in encode_comp_t()(CVE-2022-50749)

    udf: Avoid double brelse() in udf_rename()(CVE-2022-50755)

    tee: add overflow check in register_shm_helper()(CVE-2022-50080)

    drm: Prevent drm_copy_field() to attempt copying a NULL pointer(CVE-2022-50884)

    crypto: api - Use work queue in crypto_destroy_instance(CVE-2023-53799)

    mm/swap: fix swap_info_struct race between swapoff and get_swap_pages()(CVE-2023-53623)

Tenable has extracted the preceding description block directly from the EulerOS kernel security advisory.

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

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

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

    net: hns: fix possible memory leak in hnae_ae_register()

    Inject fault while probing module, if device_register() fails,     but the refcount of kobject is not decreased to 0, the name     allocated in dev_set_name() is leaked. Fix this by calling     put_device(), so that name can be freed in callback function     kobject_cleanup().

    unreferenced object 0xffff00c01aba2100 (size 128):
      comm systemd-udevd, pid 1259, jiffies 4294903284 (age 294.152s)       hex dump (first 32 bytes):
        68 6e 61 65 30 00 00 00 18 21 ba 1a c0 00 ff ff  hnae0....!......
        00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
      backtrace:
        [<0000000034783f26>] slab_post_alloc_hook+0xa0/0x3e0         [<00000000748188f2>] __kmem_cache_alloc_node+0x164/0x2b0         [<00000000ab0743e8>] __kmalloc_node_track_caller+0x6c/0x390         [<000000006c0ffb13>] kvasprintf+0x8c/0x118         [<00000000fa27bfe1>] kvasprintf_const+0x60/0xc8         [<0000000083e10ed7>] kobject_set_name_vargs+0x3c/0xc0         [<000000000b87affc>] dev_set_name+0x7c/0xa0         [<000000003fd8fe26>] hnae_ae_register+0xcc/0x190 [hnae]         [<00000000fe97edc9>] hns_dsaf_ae_init+0x9c/0x108 [hns_dsaf]         [<00000000c36ff1eb>] hns_dsaf_probe+0x548/0x748 [hns_dsaf]

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

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

    net: hns: fix possible memory leak in hnae_ae_register()

    Inject fault while probing module, if device_register() fails,     but the refcount of kobject is not decreased to 0, the name     allocated in dev_set_name() is leaked. Fix this by calling     put_device(), so that name can be freed in callback function     kobject_cleanup().

    unreferenced object 0xffff00c01aba2100 (size 128):
      comm systemd-udevd, pid 1259, jiffies 4294903284 (age 294.152s)       hex dump (first 32 bytes):
        68 6e 61 65 30 00 00 00 18 21 ba 1a c0 00 ff ff  hnae0....!......
        00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
      backtrace:
        [<0000000034783f26>] slab_post_alloc_hook+0xa0/0x3e0         [<00000000748188f2>] __kmem_cache_alloc_node+0x164/0x2b0         [<00000000ab0743e8>] __kmalloc_node_track_caller+0x6c/0x390         [<000000006c0ffb13>] kvasprintf+0x8c/0x118         [<00000000fa27bfe1>] kvasprintf_const+0x60/0xc8         [<0000000083e10ed7>] kobject_set_name_vargs+0x3c/0xc0         [<000000000b87affc>] dev_set_name+0x7c/0xa0         [<000000003fd8fe26>] hnae_ae_register+0xcc/0x190 [hnae]         [<00000000fe97edc9>] hns_dsaf_ae_init+0x9c/0x108 [hns_dsaf]         [<00000000c36ff1eb>] hns_dsaf_probe+0x548/0x748 [hns_dsaf]

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

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

    net: hns: fix possible memory leak in hnae_ae_register()

    Inject fault while probing module, if device_register() fails,     but the refcount of kobject is not decreased to 0, the name     allocated in dev_set_name() is leaked. Fix this by calling     put_device(), so that name can be freed in callback function     kobject_cleanup().

    unreferenced object 0xffff00c01aba2100 (size 128):
      comm systemd-udevd, pid 1259, jiffies 4294903284 (age 294.152s)       hex dump (first 32 bytes):
        68 6e 61 65 30 00 00 00 18 21 ba 1a c0 00 ff ff  hnae0....!......
        00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
      backtrace:
        [<0000000034783f26>] slab_post_alloc_hook+0xa0/0x3e0         [<00000000748188f2>] __kmem_cache_alloc_node+0x164/0x2b0         [<00000000ab0743e8>] __kmalloc_node_track_caller+0x6c/0x390         [<000000006c0ffb13>] kvasprintf+0x8c/0x118         [<00000000fa27bfe1>] kvasprintf_const+0x60/0xc8         [<0000000083e10ed7>] kobject_set_name_vargs+0x3c/0xc0         [<000000000b87affc>] dev_set_name+0x7c/0xa0         [<000000003fd8fe26>] hnae_ae_register+0xcc/0x190 [hnae]         [<00000000fe97edc9>] hns_dsaf_ae_init+0x9c/0x108 [hns_dsaf]         [<00000000c36ff1eb>] hns_dsaf_probe+0x548/0x748 [hns_dsaf]

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 SLES12 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2025:03614-1 advisory.

    The SUSE Linux Enterprise 12 SP5 kernel was updated to receive various security bugfixes.


    The following security bugs were fixed:

    - CVE-2022-50233: Bluetooth: eir: Fix using strlen with hdev->{dev_name,short_name} (bsc#1246968).
    - CVE-2022-50242: drivers: net: qlcnic: Fix potential memory leak in qlcnic_sriov_init() (bsc#1249696).
    - CVE-2022-50244: cxl: fix possible null-ptr-deref in cxl_pci_init_afu|adapter() (bsc#1249647).
    - CVE-2022-50252: igb: Do not free q_vector unless new one was allocated (bsc#1249846).
    - CVE-2022-50258: wifi: brcmfmac: Fix potential stack-out-of-bounds in brcmf_c_preinit_dcmds()     (bsc#1249947).
    - CVE-2022-50265: kcm: annotate data-races around kcm->rx_wait (bsc#1249744).
    - CVE-2022-50278: PNP: fix name memory leak in pnp_alloc_dev() (bsc#1249715).
    - CVE-2022-50285: mm,hugetlb: take hugetlb_lock before decrementing h->resv_huge_pages (bsc#1249803).
    - CVE-2022-50288: qlcnic: prevent ->dcb use-after-free on qlcnic_dcb_enable() failure (bsc#1249802).
    - CVE-2022-50291: kcm: annotate data-races around kcm->rx_psock (bsc#1249798).
    - CVE-2022-50294: wifi: libertas: fix memory leak in lbs_init_adapter() (bsc#1249799).
    - CVE-2022-50297: wifi: ath9k: verify the expected usb_endpoints are present (bsc#1250250).
    - CVE-2022-50304: mm: export bdi_unregister (bsc#1249725).
    - CVE-2022-50311: cxl: Fix refcount leak in cxl_calc_capp_routing (bsc#1249720).
    - CVE-2022-50312: drivers: serial: jsm: fix some leaks in probe (bsc#1249716).
    - CVE-2022-50321: wifi: brcmfmac: fix potential memory leak in brcmf_netdev_start_xmit() (bsc#1249706).
    - CVE-2022-50330: crypto: cavium - prevent integer overflow loading firmware (bsc#1249700).
    - CVE-2022-50349: misc: tifm: fix possible memory leak in tifm_7xx1_switch_media() (bsc#1249920).
    - CVE-2022-50352: net: hns: fix possible memory leak in hnae_ae_register() (bsc#1249922).
    - CVE-2022-50359: media: cx88: Fix a null-ptr-deref bug in buffer_prepare() (bsc#1250269).
    - CVE-2022-50365: skbuff: Account for tail adjustment during pull operations (bsc#1250084).
    - CVE-2022-50375: tty: serial: fsl_lpuart: disable dma rx/tx use flags in lpuart_dma_shutdown     (bsc#1250132).
    - CVE-2022-50386: Bluetooth: L2CAP: Fix user-after-free (bsc#1250301).
    - CVE-2022-50396: net: sched: fix memory leak in tcindex_set_parms (bsc#1250104).
    - CVE-2022-50402: drivers/md/md-bitmap: check the return value of md_bitmap_get_counter() (bsc#1250363).
    - CVE-2022-50405: net/tunnel: wait until all sk_user_data reader finish before releasing the sock     (bsc#1250155).
    - CVE-2022-50406: iomap: iomap: fix memory corruption when recording errors during writeback     (bsc#1250165).
    - CVE-2022-50408: wifi: brcmfmac: fix use-after-free bug in brcmf_netdev_start_xmit() (bsc#1250391).
    - CVE-2022-50409: net: If sock is dead do not access sock's sk_wq in sk_stream_wait_memory (bsc#1250392).
    - CVE-2022-50419: Bluetooth: hci_sysfs: Fix attempting to call device_add multiple times (bsc#1250394).
    - CVE-2023-53148: igb: Do not bring the device up after non-fatal error (bsc#1249842).
    - CVE-2023-53153: wifi: cfg80211: Partial revert 'wifi: cfg80211: Fix use after free for wext'     (bsc#1249877).
    - CVE-2023-53176: serial: 8250: Fix oops for port->pm on uart_change_pm() (bsc#1249991).
    - CVE-2023-53178: mm: zswap: fix missing folio cleanup in writeback race path (bsc#1249827 git-fix).
    - CVE-2023-53199: wifi: ath9k: hif_usb: clean up skbs if ath9k_hif_usb_rx_stream() fails (bsc#1249683).
    - CVE-2023-53201: RDMA/bnxt_re: wraparound mbox producer index (bsc#1249687).
    - CVE-2023-53226: wifi: mwifiex: Fix oob check condition in mwifiex_process_rx_packet (bsc#1249658).
    - CVE-2023-53248: drm/amdgpu: install stub fence into potential unused fence pointers (bsc#1249779).
    - CVE-2023-53254: drivers: base: cacheinfo: Fix shared_cpu_map changes in event of CPU hotplug     (bsc#1249871).
    - CVE-2023-53272: net: ena: fix shift-out-of-bounds in exponential backoff (bsc#1249917).
    - CVE-2023-53277: wifi: iwl3945: Add missing check for create_singlethread_workqueue (bsc#1249936).
    - CVE-2023-53288: drm/client: Fix memory leak in drm_client_modeset_probe (bsc#1250058).
    - CVE-2023-53298: nfc: fix memory leak of se_io context in nfc_genl_se_io (bsc#1249944).
    - CVE-2023-53302: wifi: iwl4965: Add missing check for create_singlethread_workqueue() (bsc#1249958).
    - CVE-2023-53305: Bluetooth: L2CAP: Fix use-after-free (bsc#1250049).
    - CVE-2023-53309: drm/radeon: Fix integer overflow in radeon_cs_parser_init (bsc#1250055).
    - CVE-2023-53317: ext4: fix WARNING in mb_find_extent (bsc#1250081).
    - CVE-2023-53321: wifi: mac80211_hwsim: drop short frames (bsc#1250313).
    - CVE-2023-53335: RDMA/cxgb4: Fix potential null-ptr-deref in pass_establish() (bsc#1250072).
    - CVE-2023-53344: can: bcm: bcm_tx_setup(): fix KMSAN uninit-value in vfs_write (bsc#1250023).
    - CVE-2023-53348: btrfs: fix deadlock when aborting transaction during relocation with scrub     (bsc#1250018).
    - CVE-2023-53365: ip6mr: Fix skb_under_panic in ip6mr_cache_report() (bsc#1249988).
    - CVE-2023-53384: wifi: mwifiex: avoid possible NULL skb pointer dereference (bsc#1250127).
    - CVE-2023-53393: RDMA/mlx5: Fix mlx5_ib_get_hw_stats when used for device (bsc#1250114).
    - CVE-2023-53395: ACPICA: Add AML_NO_OPERAND_RESOLVE flag to Timer (bsc#1250358).
    - CVE-2023-53397: modpost: fix off by one in is_executable_section() (bsc#1250125).
    - CVE-2023-53400: ALSA: hda: Fix Oops by 9.1 surround channel names (bsc#1250328).
    - CVE-2023-53438: x86/MCE: Always save CS register on AMD Zen IF Poison errors (bsc#1250180).
    - CVE-2023-53441: bpf: cpumap: Fix memory leak in cpu_map_update_elem (bsc#1250150).
    - CVE-2024-53194: PCI: Fix use-after-free of slot->bus on hot remove (bsc#1235459).
    - CVE-2024-58240: tls: separate no-async decryption request handling from async (bsc#1248847).
    - CVE-2025-38488: smb: client: fix use-after-free in crypt_message when using async crypto (bsc#1247239).
    - CVE-2025-38527: smb: client: fix use-after-free in cifs_oplock_break (bsc#1248199).
    - CVE-2025-38553: net/sched: Restrict conditions for adding duplicating netems to qdisc tree     (bsc#1248255).
    - CVE-2025-38572: ipv6: reject malicious packets in ipv6_gso_segment() (bsc#1248399).
    - CVE-2025-38574: pptp: ensure minimal skb length in pptp_xmit() (bsc#1248365).
    - CVE-2025-38602: wifi: iwlwifi: Fix error code in iwl_op_mode_dvm_start() (bsc#1248341).
    - CVE-2025-38604: wifi: rtl818x: Kill URBs before clearing tx status queue (bsc#1248333).
    - CVE-2025-38623: PCI: pnv_php: Fix surprise plug detection and recovery (bsc#1248610).
    - CVE-2025-38624: PCI: pnv_php: Clean up allocated IRQs on unplug (bsc#1248617).
    - CVE-2025-38632: pinmux: fix race causing mux_owner NULL with active mux_usecount (bsc#1248669).
    - CVE-2025-38639: netfilter: xt_nfacct: do not assume acct name is null-terminated (bsc#1248674).
    - CVE-2025-38665: can: netlink: can_changelink(): fix NULL pointer deref of struct can_priv::do_set_mode     (bsc#1248648).
    - CVE-2025-38685: fbdev: Fix vmalloc out-of-bounds write in fast_imageblit (bsc#1249220).
    - CVE-2025-38701: ext4: do not BUG when INLINE_DATA_FL lacks system.data xattr (bsc#1249258).
    - CVE-2025-38702: fbdev: fix potential buffer overflow in do_register_framebuffer() (bsc#1249254).
    - CVE-2025-38705: drm/amd/pm: fix null pointer access (bsc#1249334).
    - CVE-2025-38712: hfsplus: do not use BUG_ON() in hfsplus_create_attributes_file() (bsc#1249194).
    - CVE-2025-38713: hfsplus: fix slab-out-of-bounds read in hfsplus_uni2asc() (bsc#1249200).
    - CVE-2025-38729: ALSA: usb-audio: Validate UAC3 power domain descriptors, too (bsc#1249164).
    - CVE-2025-38735: gve: prevent ethtool ops after shutdown (bsc#1249288).
    - CVE-2025-39677: net/sched: Fix backlog accounting in qdisc_dequeue_internal (bsc#1249300).
    - CVE-2025-39691: fs/buffer: fix use-after-free when call bh_read() helper (bsc#1249374).
    - CVE-2025-39705: drm/amd/display: fix a Null pointer dereference vulnerability (bsc#1249295).
    - CVE-2025-39706: drm/amdkfd: Destroy KFD debugfs after destroy KFD wq (bsc#1249413).
    - CVE-2025-39726: s390/ism: fix concurrency management in ism_cmd() (bsc#1249266).
    - CVE-2025-39751: ALSA: hda/ca0132: Fix buffer overflow in add_tuning_control (bsc#1249538).
    - CVE-2025-39754: mm/smaps: fix race between smaps_hugetlb_range and migration (bsc#1249524).
    - CVE-2025-39757: ALSA: usb-audio: Fix size validation in convert_chmap_v3() (bsc#1249515).
    - CVE-2025-39760: usb: core: config: Prevent OOB read in SS endpoint companion parsing (bsc#1249598).
    - CVE-2025-39763: ACPICA: Fix error code path in acpi_ds_call_control_method() (bsc#1249615).
    - CVE-2025-39764: netfilter: ctnetlink: remove refcounting in expectation dumpers (bsc#1249513).
    - CVE-2025-39773: net: bridge: fix soft lockup in br_multicast_query_expired() (bsc#1249504).
    - CVE-2025-39782: jbd2: prevent softlockup in jbd2_log_do_checkpoint() (bsc#1249526).
    - CVE-2025-39787: soc: qcom: mdt_loader: Deal with zero e_shentsize (bsc#1249545).
    - CVE-2025-39800: btrfs: abort transaction on unexpected eb generation at btrfs_copy_root() (bsc#1250177).
    - CVE-2025-39808: HID: hid-ntrig: fix unable to handle page fault in ntrig_report_version() (bsc#1250088).
    - CVE-2025-39824: HID: asus: fix UAF via HID_CLAIMED_INPUT validation (bsc#1250007).
    - CVE-2025-39833: mISDN: hfcpci: Fix warning when deleting uninitialized timer (bsc#1250028).
    - CVE-2025-39838: cifs: prevent NULL pointer dereference in UTF16 conversion (bsc#1250365).
    - CVE-2025-39847: ppp: fix memory leak in pad_compress_skb (bsc#1250292).
    - CVE-2025-39853: i40e: Fix potential invalid access when MAC list is empty (bsc#1250275).
    - CVE-2025-39860: Bluetooth: Fix use-after-free in l2cap_sock_cleanup_listen() (bsc#1250247).
    - CVE-2025-39863: wifi: brcmfmac: fix use-after-free when rescheduling brcmf_btcoex_info work     (bsc#1250281).
    - CVE-2025-39865: tee: fix NULL pointer dereference in tee_shm_put (bsc#1250294).
    - CVE-2025-39869: dmaengine: ti: edma: Fix memory allocation size for queue_priority_map (bsc#1250406).
    - CVE-2025-39885: ocfs2: fix recursive semaphore deadlock in fiemap call (bsc#1250407).
    - CVE-2025-40300: x86/vmscape: Warn when STIBP is disabled with SMT (bsc#1247483).


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.

  - net: hns: fix possible memory leak in hnae_ae_register() Inject fault while probing module, if     device_register() fails, but the refcount of kobject is not decreased to 0, the name allocated in     dev_set_name() is leaked. Fix this by calling put_device(), so that name can be freed in callback function     kobject_cleanup(). unreferenced object 0xffff00c01aba2100 (size 128): comm systemd-udevd, pid 1259,     jiffies 4294903284 (age 294.152s) hex dump (first 32 bytes): 68 6e 61 65 30 00 00 00 18 21 ba 1a c0 00 ff     ff hnae0....!...... 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace:
    [<0000000034783f26>] slab_post_alloc_hook+0xa0/0x3e0 [<00000000748188f2>]
    __kmem_cache_alloc_node+0x164/0x2b0 [<00000000ab0743e8>] __kmalloc_node_track_caller+0x6c/0x390     [<000000006c0ffb13>] kvasprintf+0x8c/0x118 [<00000000fa27bfe1>] kvasprintf_const+0x60/0xc8     [<0000000083e10ed7>] kobject_set_name_vargs+0x3c/0xc0 [<000000000b87affc>] dev_set_name+0x7c/0xa0     [<000000003fd8fe26>] hnae_ae_register+0xcc/0x190 [hnae] [<00000000fe97edc9>] hns_dsaf_ae_init+0x9c/0x108     [hns_dsaf] [<00000000c36ff1eb>] hns_dsaf_probe+0x548/0x748 [hns_dsaf] (CVE-2022-50352)

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.224-128.414. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2KERNEL-5.4-2022-039 advisory.

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

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

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

    A use-after-free flaw was found in the Linux kernel's Unix socket Garbage Collection and io_uring. This     flaw allows a local user to crash or potentially escalate their privileges on the system. (CVE-2022-2602)

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

    A vulnerability classified as problematic was found in Linux Kernel. Affected by this vulnerability is the     function mvpp2_dbgfs_port_init of the file drivers/net/ethernet/marvell/mvpp2/mvpp2_debugfs.c of the     component mvpp2. The manipulation leads to memory leak. It is recommended to apply a patch to fix this     issue. The identifier VDB-211033 was assigned to this vulnerability. (CVE-2022-3535)

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

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

    A vulnerability, which was classified as critical, has been found in Linux Kernel. Affected by this issue     is the function del_timer of the file drivers/isdn/mISDN/l1oip_core.c of the component Bluetooth. The     manipulation leads to use after free. It is recommended to apply a patch to fix this issue. The identifier     of this vulnerability is VDB-211088. (CVE-2022-3565)

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

    A vulnerability was found in Linux Kernel. It has been classified as problematic. Affected is the function     nilfs_new_inode of the file fs/nilfs2/inode.c of the component BPF. The manipulation leads to use after     free. It is possible to launch the attack remotely. It is recommended to apply a patch to fix this issue.
    The identifier of this vulnerability is VDB-211992. (CVE-2022-3649)

    drivers/video/fbdev/smscufx.c in the Linux kernel through 5.19.12 has a race condition and resultant use-     after-free if a physically proximate attacker removes a USB device while calling open(), aka a race     condition between ufx_ops_open and ufx_usb_disconnect. (CVE-2022-41849)

    roccat_report_event in drivers/hid/hid-roccat.c in the Linux kernel through 5.19.12 has a race condition     and resultant use-after-free in certain situations where a report is received while copying a     report->value is in progress. (CVE-2022-41850)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

    ALSA: ac97: fix possible memory leak in snd_ac97_dev_register() (CVE-2022-50427)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

    mmc: core: Fix kernel panic when remove non-standard SDIO card (CVE-2022-50640)

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

    RDMA/rxe: Fix kernel NULL pointer dereference error (CVE-2022-50671)

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

    net: rds: don't hold sock lock when cancelling work from rds_tcp_reset_callbacks() (CVE-2022-50676)

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

    net/ieee802154: don't warn zero-sized raw_sendmsg() (CVE-2022-50706)

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

    net/mlx5: Fix possible use-after-free in async command interface (CVE-2022-50726)

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

    crypto: akcipher - default implementation for setting a private key (CVE-2022-50731)

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

    usb: idmouse: fix an uninit-value in idmouse_open (CVE-2022-50733)

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

    net: fix UAF issue in nfqnl_nf_hook_drop() when ops_init() failed (CVE-2022-50780)

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

    cifs: Fix the error length of VALIDATE_NEGOTIATE_INFO message (CVE-2022-50859)

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

    drm: Prevent drm_copy_field() to attempt copying a NULL pointer (CVE-2022-50884)

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

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

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

Tenable has extracted the preceding description block directly from the tested product security advisory.

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

The version of kernel installed on the remote host is prior to 5.10.155-138.670. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2KERNEL-5.10-2022-023 advisory.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

    ext4: fix potential memory leak in ext4_fc_record_modified_inode() (CVE-2022-50622)

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

    mm: hugetlb: fix UAF in hugetlb_handle_userfault (CVE-2022-50630)

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

    mmc: core: Fix kernel panic when remove non-standard SDIO card (CVE-2022-50640)

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

    cifs: Fix xid leak in cifs_copy_file_range() (CVE-2022-50643)

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

    RDMA/rxe: Fix kernel NULL pointer dereference error (CVE-2022-50671)

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

    net: rds: don't hold sock lock when cancelling work from rds_tcp_reset_callbacks() (CVE-2022-50676)

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

    i40e: Fix DMA mappings leak (CVE-2022-50679)

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

    selinux: enable use of both GFP_KERNEL and GFP_ATOMIC in convert_context() (CVE-2022-50699)

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

    net/ieee802154: don't warn zero-sized raw_sendmsg() (CVE-2022-50706)

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

    net/mlx5: Fix possible use-after-free in async command interface (CVE-2022-50726)

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

    crypto: akcipher - default implementation for setting a private key (CVE-2022-50731)

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

    usb: idmouse: fix an uninit-value in idmouse_open (CVE-2022-50733)

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

    net: fix UAF issue in nfqnl_nf_hook_drop() when ops_init() failed (CVE-2022-50780)

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

    ipv6: ensure sane device mtu in tunnels (CVE-2022-50816)

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

    net: hsr: avoid possible NULL deref in skb_clone() (CVE-2022-50817)

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

    jbd2: add miss release buffer head in fc_do_one_pass() (CVE-2022-50835)

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

    jbd2: fix potential buffer head reference count leak (CVE-2022-50839)

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

    drm/virtio: Check whether transferred 2D BO is shmem (CVE-2022-50842)

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

    cifs: Fix xid leak in cifs_ses_add_channel() (CVE-2022-50856)

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

    cifs: Fix the error length of VALIDATE_NEGOTIATE_INFO message (CVE-2022-50859)

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

    tcp: fix a signed-integer-overflow bug in tcp_add_backlog() (CVE-2022-50865)

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

    drm: Prevent drm_copy_field() to attempt copying a NULL pointer (CVE-2022-50884)

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

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

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

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

Tenable has extracted the preceding description block directly from the tested product security advisory.

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

The version of kernel installed on the remote host is prior to 4.14.299-223.520. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2-2022-1888 advisory.

    In v4l2_m2m_querybuf of v4l2-mem2mem.c, there is a possible out of bounds write due to improper input     validation. This could lead to local escalation of privilege with System execution privileges needed. User     interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID:
    A-223375145References: Upstream kernel (CVE-2022-20369)

    In pppol2tp_create of l2tp_ppp.c, there is a possible use after free due to a race condition. This could     lead to local escalation of privilege with System execution privileges needed. User interaction is not     needed for exploitation. (CVE-2022-20567)

    Non-transparent sharing of return predictor targets between contexts in some Intel(R) Processors may allow     an authorized user to potentially enable information disclosure via local access. (CVE-2022-26373)

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

    There is an infoleak vulnerability in the Linux kernel's net/bluetooth/l2cap_core.c's l2cap_parse_conf_req     function which can be used to leak kernel pointers remotely. We recommend upgrading past commit     https://github.com/torvalds/linux/commit/b1a2cd50c0357f243b7435a732b4e62ba3157a2e     https://www.google.com/url (CVE-2022-42895)

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

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

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

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

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

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

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

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

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

    Bluetooth: L2CAP: fix use-after-free in l2cap_conn_del() (CVE-2022-49909)

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

    Bluetooth: L2CAP: Fix use-after-free caused by l2cap_reassemble_sdu (CVE-2022-49910)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

    ALSA: ac97: fix possible memory leak in snd_ac97_dev_register() (CVE-2022-50427)

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

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

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

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

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

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

    A use-after-free flaw was found in io_uring/poll.c in io_poll_check_events in the io_uring subcomponent in     the Linux Kernel due to a race condition of poll_refs. This flaw may cause a NULL pointer dereference.
    (CVE-2023-0468)

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
361044	AlmaLinux 9.2 [TuxCare] Security Update: bpftool / kernel / kernel-abi-stablelists / kernel-core / etc Multiple Vulnerabilities (ALMALINUX9.2:CLSA-2026:1783355084)	Nessus	Alma Linux Local Security Checks	Local	medium
360889	Rocky Linux 9.6 [TuxCare] Security Update: kernel / kernel-abi-stablelists / kernel-core / etc Multiple Vulnerabilities (ALMALINUX9.6:CLSA-2026:1779434490)	Nessus	Rocky Linux Local Security Checks	Local	high
360724	AlmaLinux 9.6 [TuxCare] Security Update: kernel / kernel-abi-stablelists / kernel-core / etc Multiple Vulnerabilities (ALMALINUX9.6:CLSA-2026:1779434490)	Nessus	Alma Linux Local Security Checks	Local	high
302981	EulerOS Virtualization 2.13.1 : kernel (EulerOS-SA-2026-1637)	Nessus	Huawei Local Security Checks	Local	high
302971	EulerOS Virtualization 2.13.0 : kernel (EulerOS-SA-2026-1629)	Nessus	Huawei Local Security Checks	Local	high
302607	EulerOS Virtualization 2.10.1 : kernel (EulerOS-SA-2026-1537)	Nessus	Huawei Local Security Checks	Local	high
302380	EulerOS 2.0 SP10 : kernel (EulerOS-SA-2026-1339)	Nessus	Huawei Local Security Checks	Local	high
297598	EulerOS 2.0 SP13 : kernel (EulerOS-SA-2026-1212)	Nessus	Huawei Local Security Checks	Local	high
297592	EulerOS 2.0 SP13 : kernel (EulerOS-SA-2026-1224)	Nessus	Huawei Local Security Checks	Local	high
296325	Unity Linux 20.1050e Security Update: kernel (UTSA-2026-004837)	Nessus	Unity Linux Local Security Checks	Local	medium
280984	Unity Linux 20.1060a / 20.1070a Security Update: kernel (UTSA-2025-993003)	Nessus	Unity Linux Local Security Checks	Local	medium
280529	Unity Linux 20.1060e / 20.1070e Security Update: kernel (UTSA-2025-992245)	Nessus	Unity Linux Local Security Checks	Local	medium
270831	SUSE SLES12 Security Update : kernel (SUSE-SU-2025:03614-1)	Nessus	SuSE Local Security Checks	Local	high
265285	Linux Distros Unpatched Vulnerability : CVE-2022-50352	Nessus	Misc.	Local	medium
168727	Amazon Linux 2 : kernel, --advisory ALAS2KERNEL-5.4-2022-039 (ALASKERNEL-5.4-2022-039)	Nessus	Amazon Linux Local Security Checks	Local	high
168520	Amazon Linux 2 : kernel, --advisory ALAS2KERNEL-5.10-2022-023 (ALASKERNEL-5.10-2022-023)	Nessus	Amazon Linux Local Security Checks	Local	high
168430	Amazon Linux 2 : kernel, --advisory ALAS2-2022-1888 (ALAS-2022-1888)	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-50352

medium

Tenable Plugins

medium

high

high

high

high

high

high

high

high

medium

medium

medium

high

medium

high

high

high

high