In the Linux kernel, the following vulnerability has been resolved: crypto: arm64/poly1305 - fix a read out-of-bound A kasan error was reported during fuzzing: BUG: KASAN: slab-out-of-bounds in neon_poly1305_blocks.constprop.0+0x1b4/0x250 [poly1305_neon] Read of size 4 at addr ffff0010e293f010 by task syz-executor.5/1646715 CPU: 4 PID: 1646715 Comm: syz-executor.5 Kdump: loaded Not tainted 5.10.0.aarch64 #1 Hardware name: Huawei TaiShan 2280 /BC11SPCD, BIOS 1.59 01/31/2019 Call trace: dump_backtrace+0x0/0x394 show_stack+0x34/0x4c arch/arm64/kernel/stacktrace.c:196 __dump_stack lib/dump_stack.c:77 [inline] dump_stack+0x158/0x1e4 lib/dump_stack.c:118 print_address_description.constprop.0+0x68/0x204 mm/kasan/report.c:387 __kasan_report+0xe0/0x140 mm/kasan/report.c:547 kasan_report+0x44/0xe0 mm/kasan/report.c:564 check_memory_region_inline mm/kasan/generic.c:187 [inline] __asan_load4+0x94/0xd0 mm/kasan/generic.c:252 neon_poly1305_blocks.constprop.0+0x1b4/0x250 [poly1305_neon] neon_poly1305_do_update+0x6c/0x15c [poly1305_neon] neon_poly1305_update+0x9c/0x1c4 [poly1305_neon] crypto_shash_update crypto/shash.c:131 [inline] shash_finup_unaligned+0x84/0x15c crypto/shash.c:179 crypto_shash_finup+0x8c/0x140 crypto/shash.c:193 shash_digest_unaligned+0xb8/0xe4 crypto/shash.c:201 crypto_shash_digest+0xa4/0xfc crypto/shash.c:217 crypto_shash_tfm_digest+0xb4/0x150 crypto/shash.c:229 essiv_skcipher_setkey+0x164/0x200 [essiv] crypto_skcipher_setkey+0xb0/0x160 crypto/skcipher.c:612 skcipher_setkey+0x3c/0x50 crypto/algif_skcipher.c:305 alg_setkey+0x114/0x2a0 crypto/af_alg.c:220 alg_setsockopt+0x19c/0x210 crypto/af_alg.c:253 __sys_setsockopt+0x190/0x2e0 net/socket.c:2123 __do_sys_setsockopt net/socket.c:2134 [inline] __se_sys_setsockopt net/socket.c:2131 [inline] __arm64_sys_setsockopt+0x78/0x94 net/socket.c:2131 __invoke_syscall arch/arm64/kernel/syscall.c:36 [inline] invoke_syscall+0x64/0x100 arch/arm64/kernel/syscall.c:48 el0_svc_common.constprop.0+0x220/0x230 arch/arm64/kernel/syscall.c:155 do_el0_svc+0xb4/0xd4 arch/arm64/kernel/syscall.c:217 el0_svc+0x24/0x3c arch/arm64/kernel/entry-common.c:353 el0_sync_handler+0x160/0x164 arch/arm64/kernel/entry-common.c:369 el0_sync+0x160/0x180 arch/arm64/kernel/entry.S:683 This error can be reproduced by the following code compiled as ko on a system with kasan enabled: #include <linux/module.h> #include <linux/crypto.h> #include <crypto/hash.h> #include <crypto/poly1305.h> char test_data[] = "\x00\x01\x02\x03\x04\x05\x06\x07" "\x08\x09\x0a\x0b\x0c\x0d\x0e\x0f" "\x10\x11\x12\x13\x14\x15\x16\x17" "\x18\x19\x1a\x1b\x1c\x1d\x1e"; int init(void) { struct crypto_shash *tfm = NULL; char *data = NULL, *out = NULL; tfm = crypto_alloc_shash("poly1305", 0, 0); data = kmalloc(POLY1305_KEY_SIZE - 1, GFP_KERNEL); out = kmalloc(POLY1305_DIGEST_SIZE, GFP_KERNEL); memcpy(data, test_data, POLY1305_KEY_SIZE - 1); crypto_shash_tfm_digest(tfm, data, POLY1305_KEY_SIZE - 1, out); kfree(data); kfree(out); return 0; } void deinit(void) { } module_init(init) module_exit(deinit) MODULE_LICENSE("GPL"); The root cause of the bug sits in neon_poly1305_blocks. The logic neon_poly1305_blocks() performed is that if it was called with both s[] and r[] uninitialized, it will first try to initialize them with the data from the first "block" that it believed to be 32 bytes in length. First 16 bytes are used as the key and the next 16 bytes for s[]. This would lead to the aforementioned read out-of-bound. However, after calling poly1305_init_arch(), only 16 bytes were deducted from the input and s[] is initialized yet again with the following 16 bytes. The second initialization of s[] is certainly redundent which indicates that the first initialization should be for r[] only. This patch fixes the issue by calling poly1305_init_arm64() instead o ---truncated---

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

  - In the Linux kernel, the following vulnerability has been resolved: tracing/histogram: Fix a potential     memory leak for kstrdup() kfree() is missing on an error path to free the memory allocated by kstrdup(): p     = param = kstrdup(data->params[i], GFP_KERNEL); So it is better to free it via kfree(p). (CVE-2022-48768)

  - In the Linux kernel, the following vulnerability has been resolved: can: af_can: fix NULL pointer     dereference in can_rx_register() It causes NULL pointer dereference when testing as following: (a) use     syscall(__NR_socket, 0x10ul, 3ul, 0) to create netlink socket. (b) use syscall(__NR_sendmsg, ...) to     create bond link device and vxcan link device, and bind vxcan device to bond device (can also use     ifenslave command to bind vxcan device to bond device). (c) use syscall(__NR_socket, 0x1dul, 3ul, 1) to     create CAN socket. (d) use syscall(__NR_bind, ...) to bind the bond device to CAN socket. The bond device     invokes the can-raw protocol registration interface to receive CAN packets. However, ml_priv is not     allocated to the dev, dev_rcv_lists is assigned to NULL in can_rx_register(). In this case, it will occur     the NULL pointer dereference issue. The following is the stack information: BUG: kernel NULL pointer     dereference, address: 0000000000000008 PGD 122a4067 P4D 122a4067 PUD 1223c067 PMD 0 Oops: 0000 [#1]     PREEMPT SMP RIP: 0010:can_rx_register+0x12d/0x1e0 Call Trace: <TASK> raw_enable_filters+0x8d/0x120     raw_enable_allfilters+0x3b/0x130 raw_bind+0x118/0x4f0 __sys_bind+0x163/0x1a0 __x64_sys_bind+0x1e/0x30     do_syscall_64+0x35/0x80 entry_SYSCALL_64_after_hwframe+0x63/0xcd </TASK> (CVE-2022-49863)

  - In the Linux kernel, the following vulnerability has been resolved: net/tipc: fix slab-use-after-free Read     in tipc_aead_encrypt_done Syzbot reported a slab-use-after-free with the following call trace:
    ================================================================== BUG: KASAN: slab-use-after-free in     tipc_aead_encrypt_done+0x4bd/0x510 net/tipc/crypto.c:840 Read of size 8 at addr ffff88807a733000 by task     kworker/1:0/25 Call Trace: kasan_report+0xd9/0x110 mm/kasan/report.c:601     tipc_aead_encrypt_done+0x4bd/0x510 net/tipc/crypto.c:840 crypto_request_complete     include/crypto/algapi.h:266 aead_request_complete include/crypto/internal/aead.h:85     cryptd_aead_crypt+0x3b8/0x750 crypto/cryptd.c:772 crypto_request_complete include/crypto/algapi.h:266     cryptd_queue_worker+0x131/0x200 crypto/cryptd.c:181 process_one_work+0x9fb/0x1b60 kernel/workqueue.c:3231     Allocated by task 8355: kzalloc_noprof include/linux/slab.h:778 tipc_crypto_start+0xcc/0x9e0     net/tipc/crypto.c:1466 tipc_init_net+0x2dd/0x430 net/tipc/core.c:72 ops_init+0xb9/0x650     net/core/net_namespace.c:139 setup_net+0x435/0xb40 net/core/net_namespace.c:343 copy_net_ns+0x2f0/0x670     net/core/net_namespace.c:508 create_new_namespaces+0x3ea/0xb10 kernel/nsproxy.c:110     unshare_nsproxy_namespaces+0xc0/0x1f0 kernel/nsproxy.c:228 ksys_unshare+0x419/0x970 kernel/fork.c:3323
    __do_sys_unshare kernel/fork.c:3394 Freed by task 63: kfree+0x12a/0x3b0 mm/slub.c:4557     tipc_crypto_stop+0x23c/0x500 net/tipc/crypto.c:1539 tipc_exit_net+0x8c/0x110 net/tipc/core.c:119     ops_exit_list+0xb0/0x180 net/core/net_namespace.c:173 cleanup_net+0x5b7/0xbf0 net/core/net_namespace.c:640     process_one_work+0x9fb/0x1b60 kernel/workqueue.c:3231 After freed the tipc_crypto tx by delete namespace,     tipc_aead_encrypt_done may still visit it in cryptd_queue_worker workqueue. I reproduce this issue by: ip     netns add ns1 ip link add veth1 type veth peer name veth2 ip link set veth1 netns ns1 ip netns exec ns1     tipc bearer enable media eth dev veth1 ip netns exec ns1 tipc node set key this_is_a_master_key master ip     netns exec ns1 tipc bearer disable media eth dev veth1 ip netns del ns1 The key of reproduction is that,     simd_aead_encrypt is interrupted, leading to crypto_simd_usable() return false. Thus, the     cryptd_queue_worker is triggered, and the tipc_crypto tx will be visited. tipc_disc_timeout     tipc_bearer_xmit_skb tipc_crypto_xmit tipc_aead_encrypt crypto_aead_encrypt // encrypt() simd_aead_encrypt     // crypto_simd_usable() is false child = &ctx->cryptd_tfm->base; simd_aead_encrypt crypto_aead_encrypt //     encrypt() cryptd_aead_encrypt_enqueue cryptd_aead_enqueue cryptd_enqueue_request // trigger     cryptd_queue_worker queue_work_on(smp_processor_id(), cryptd_wq, &cpu_queue->work) Fix this by holding net     reference count before encrypt. (CVE-2025-38052)

  - In the Linux kernel, the following vulnerability has been resolved: Bluetooth: eir: Fix possible crashes     on eir_create_adv_data eir_create_adv_data may attempt to add EIR_FLAGS and EIR_TX_POWER without checking     if that would fit. (CVE-2025-38303)

  - In the Linux kernel, the following vulnerability has been resolved: gve: prevent ethtool ops after     shutdown A crash can occur if an ethtool operation is invoked after shutdown() is called. shutdown() is     invoked during system shutdown to stop DMA operations without performing expensive deallocations. It is     discouraged to unregister the netdev in this path, so the device may still be visible to userspace and     kernel helpers. In gve, shutdown() tears down most internal data structures. If an ethtool operation is     dispatched after shutdown(), it will dereference freed or NULL pointers, leading to a kernel panic. While     graceful shutdown normally quiesces userspace before invoking the reboot syscall, forced shutdowns (as     observed on GCP VMs) can still trigger this path. Fix by calling netif_device_detach() in shutdown(). This     marks the device as detached so the ethtool ioctl handler will skip dispatching operations to the driver.
    (CVE-2025-38735)

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:1788168285 advisory.

  - In the Linux kernel, the following vulnerability has been resolved: tracing/histogram: Fix a potential     memory leak for kstrdup() kfree() is missing on an error path to free the memory allocated by kstrdup(): p     = param = kstrdup(data->params[i], GFP_KERNEL); So it is better to free it via kfree(p). (CVE-2022-48768)

  - In the Linux kernel, the following vulnerability has been resolved: can: af_can: fix NULL pointer     dereference in can_rx_register() It causes NULL pointer dereference when testing as following: (a) use     syscall(__NR_socket, 0x10ul, 3ul, 0) to create netlink socket. (b) use syscall(__NR_sendmsg, ...) to     create bond link device and vxcan link device, and bind vxcan device to bond device (can also use     ifenslave command to bind vxcan device to bond device). (c) use syscall(__NR_socket, 0x1dul, 3ul, 1) to     create CAN socket. (d) use syscall(__NR_bind, ...) to bind the bond device to CAN socket. The bond device     invokes the can-raw protocol registration interface to receive CAN packets. However, ml_priv is not     allocated to the dev, dev_rcv_lists is assigned to NULL in can_rx_register(). In this case, it will occur     the NULL pointer dereference issue. The following is the stack information: BUG: kernel NULL pointer     dereference, address: 0000000000000008 PGD 122a4067 P4D 122a4067 PUD 1223c067 PMD 0 Oops: 0000 [#1]     PREEMPT SMP RIP: 0010:can_rx_register+0x12d/0x1e0 Call Trace: <TASK> raw_enable_filters+0x8d/0x120     raw_enable_allfilters+0x3b/0x130 raw_bind+0x118/0x4f0 __sys_bind+0x163/0x1a0 __x64_sys_bind+0x1e/0x30     do_syscall_64+0x35/0x80 entry_SYSCALL_64_after_hwframe+0x63/0xcd </TASK> (CVE-2022-49863)

  - In the Linux kernel, the following vulnerability has been resolved: net/tipc: fix slab-use-after-free Read     in tipc_aead_encrypt_done Syzbot reported a slab-use-after-free with the following call trace:
    ================================================================== BUG: KASAN: slab-use-after-free in     tipc_aead_encrypt_done+0x4bd/0x510 net/tipc/crypto.c:840 Read of size 8 at addr ffff88807a733000 by task     kworker/1:0/25 Call Trace: kasan_report+0xd9/0x110 mm/kasan/report.c:601     tipc_aead_encrypt_done+0x4bd/0x510 net/tipc/crypto.c:840 crypto_request_complete     include/crypto/algapi.h:266 aead_request_complete include/crypto/internal/aead.h:85     cryptd_aead_crypt+0x3b8/0x750 crypto/cryptd.c:772 crypto_request_complete include/crypto/algapi.h:266     cryptd_queue_worker+0x131/0x200 crypto/cryptd.c:181 process_one_work+0x9fb/0x1b60 kernel/workqueue.c:3231     Allocated by task 8355: kzalloc_noprof include/linux/slab.h:778 tipc_crypto_start+0xcc/0x9e0     net/tipc/crypto.c:1466 tipc_init_net+0x2dd/0x430 net/tipc/core.c:72 ops_init+0xb9/0x650     net/core/net_namespace.c:139 setup_net+0x435/0xb40 net/core/net_namespace.c:343 copy_net_ns+0x2f0/0x670     net/core/net_namespace.c:508 create_new_namespaces+0x3ea/0xb10 kernel/nsproxy.c:110     unshare_nsproxy_namespaces+0xc0/0x1f0 kernel/nsproxy.c:228 ksys_unshare+0x419/0x970 kernel/fork.c:3323
    __do_sys_unshare kernel/fork.c:3394 Freed by task 63: kfree+0x12a/0x3b0 mm/slub.c:4557     tipc_crypto_stop+0x23c/0x500 net/tipc/crypto.c:1539 tipc_exit_net+0x8c/0x110 net/tipc/core.c:119     ops_exit_list+0xb0/0x180 net/core/net_namespace.c:173 cleanup_net+0x5b7/0xbf0 net/core/net_namespace.c:640     process_one_work+0x9fb/0x1b60 kernel/workqueue.c:3231 After freed the tipc_crypto tx by delete namespace,     tipc_aead_encrypt_done may still visit it in cryptd_queue_worker workqueue. I reproduce this issue by: ip     netns add ns1 ip link add veth1 type veth peer name veth2 ip link set veth1 netns ns1 ip netns exec ns1     tipc bearer enable media eth dev veth1 ip netns exec ns1 tipc node set key this_is_a_master_key master ip     netns exec ns1 tipc bearer disable media eth dev veth1 ip netns del ns1 The key of reproduction is that,     simd_aead_encrypt is interrupted, leading to crypto_simd_usable() return false. Thus, the     cryptd_queue_worker is triggered, and the tipc_crypto tx will be visited. tipc_disc_timeout     tipc_bearer_xmit_skb tipc_crypto_xmit tipc_aead_encrypt crypto_aead_encrypt // encrypt() simd_aead_encrypt     // crypto_simd_usable() is false child = &ctx->cryptd_tfm->base; simd_aead_encrypt crypto_aead_encrypt //     encrypt() cryptd_aead_encrypt_enqueue cryptd_aead_enqueue cryptd_enqueue_request // trigger     cryptd_queue_worker queue_work_on(smp_processor_id(), cryptd_wq, &cpu_queue->work) Fix this by holding net     reference count before encrypt. (CVE-2025-38052)

  - In the Linux kernel, the following vulnerability has been resolved: Bluetooth: eir: Fix possible crashes     on eir_create_adv_data eir_create_adv_data may attempt to add EIR_FLAGS and EIR_TX_POWER without checking     if that would fit. (CVE-2025-38303)

  - In the Linux kernel, the following vulnerability has been resolved: gve: prevent ethtool ops after     shutdown A crash can occur if an ethtool operation is invoked after shutdown() is called. shutdown() is     invoked during system shutdown to stop DMA operations without performing expensive deallocations. It is     discouraged to unregister the netdev in this path, so the device may still be visible to userspace and     kernel helpers. In gve, shutdown() tears down most internal data structures. If an ethtool operation is     dispatched after shutdown(), it will dereference freed or NULL pointers, leading to a kernel panic. While     graceful shutdown normally quiesces userspace before invoking the reboot syscall, forced shutdowns (as     observed on GCP VMs) can still trigger this path. Fix by calling netif_device_detach() in shutdown(). This     marks the device as detached so the ethtool ioctl handler will skip dispatching operations to the driver.
    (CVE-2025-38735)

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

  - A flaw was found in the KVM's AMD nested virtualization (SVM). A malicious L1 guest could purposely fail     to intercept the shutdown of a cooperative nested guest (L2), possibly leading to a page fault and kernel     panic in the host (L0). (CVE-2022-3344)

  - In the Linux kernel, the following vulnerability has been resolved: usbnet: Run unregister_netdev() before     unbind() again Commit 2c9d6c2b871d (usbnet: run unbind() before unregister_netdev()) sought to fix a     use-after-free on disconnect of USB Ethernet adapters. It turns out that a different fix is necessary to     address the issue:
    https://lore.kernel.org/netdev/18b3541e5372bc9b9fc733d422f4e698c089077c.1650177997.git.lukas@wunner.de/ So     the commit was not necessary. The commit made binding and unbinding of USB Ethernet asymmetrical: Before,     usbnet_probe() first invoked the ->bind() callback and then register_netdev(). usbnet_disconnect()     mirrored that by first invoking unregister_netdev() and then ->unbind(). Since the commit, the order in     usbnet_disconnect() is reversed and no longer mirrors usbnet_probe(). One consequence is that a PHY     disconnected (and stopped) in ->unbind() is afterwards stopped once more by unregister_netdev() as it     closes the netdev before unregistering. That necessitates a contortion in ->stop() because the PHY may     only be stopped if it hasn't already been disconnected. Reverting the commit allows making the call to     phy_stop() unconditional in ->stop(). (CVE-2022-49501)

  - In the Linux kernel, the following vulnerability has been resolved: crypto: arm64/poly1305 - fix a read     out-of-bound A kasan error was reported during fuzzing: BUG: KASAN: slab-out-of-bounds in     neon_poly1305_blocks.constprop.0+0x1b4/0x250 [poly1305_neon] Read of size 4 at addr ffff0010e293f010 by     task syz-executor.5/1646715 CPU: 4 PID: 1646715 Comm: syz-executor.5 Kdump: loaded Not tainted     5.10.0.aarch64 #1 Hardware name: Huawei TaiShan 2280 /BC11SPCD, BIOS 1.59 01/31/2019 Call trace:
    dump_backtrace+0x0/0x394 show_stack+0x34/0x4c arch/arm64/kernel/stacktrace.c:196 __dump_stack     lib/dump_stack.c:77 [inline] dump_stack+0x158/0x1e4 lib/dump_stack.c:118     print_address_description.constprop.0+0x68/0x204 mm/kasan/report.c:387 __kasan_report+0xe0/0x140     mm/kasan/report.c:547 kasan_report+0x44/0xe0 mm/kasan/report.c:564 check_memory_region_inline     mm/kasan/generic.c:187 [inline] __asan_load4+0x94/0xd0 mm/kasan/generic.c:252     neon_poly1305_blocks.constprop.0+0x1b4/0x250 [poly1305_neon] neon_poly1305_do_update+0x6c/0x15c     [poly1305_neon] neon_poly1305_update+0x9c/0x1c4 [poly1305_neon] crypto_shash_update crypto/shash.c:131     [inline] shash_finup_unaligned+0x84/0x15c crypto/shash.c:179 crypto_shash_finup+0x8c/0x140     crypto/shash.c:193 shash_digest_unaligned+0xb8/0xe4 crypto/shash.c:201 crypto_shash_digest+0xa4/0xfc     crypto/shash.c:217 crypto_shash_tfm_digest+0xb4/0x150 crypto/shash.c:229 essiv_skcipher_setkey+0x164/0x200     [essiv] crypto_skcipher_setkey+0xb0/0x160 crypto/skcipher.c:612 skcipher_setkey+0x3c/0x50     crypto/algif_skcipher.c:305 alg_setkey+0x114/0x2a0 crypto/af_alg.c:220 alg_setsockopt+0x19c/0x210     crypto/af_alg.c:253 __sys_setsockopt+0x190/0x2e0 net/socket.c:2123 __do_sys_setsockopt net/socket.c:2134     [inline] __se_sys_setsockopt net/socket.c:2131 [inline] __arm64_sys_setsockopt+0x78/0x94 net/socket.c:2131
    __invoke_syscall arch/arm64/kernel/syscall.c:36 [inline] invoke_syscall+0x64/0x100     arch/arm64/kernel/syscall.c:48 el0_svc_common.constprop.0+0x220/0x230 arch/arm64/kernel/syscall.c:155     do_el0_svc+0xb4/0xd4 arch/arm64/kernel/syscall.c:217 el0_svc+0x24/0x3c arch/arm64/kernel/entry-     common.c:353 el0_sync_handler+0x160/0x164 arch/arm64/kernel/entry-common.c:369 el0_sync+0x160/0x180     arch/arm64/kernel/entry.S:683 This error can be reproduced by the following code compiled as ko on a     system with kasan enabled: #include <linux/module.h> #include <linux/crypto.h> #include <crypto/hash.h>     #include <crypto/poly1305.h> char test_data[] = \x00\x01\x02\x03\x04\x05\x06\x07     \x08\x09\x0a\x0b\x0c\x0d\x0e\x0f \x10\x11\x12\x13\x14\x15\x16\x17 \x18\x19\x1a\x1b\x1c\x1d\x1e; int     init(void) { struct crypto_shash *tfm = NULL; char *data = NULL, *out = NULL; tfm =     crypto_alloc_shash(poly1305, 0, 0); data = kmalloc(POLY1305_KEY_SIZE - 1, GFP_KERNEL); out =     kmalloc(POLY1305_DIGEST_SIZE, GFP_KERNEL); memcpy(data, test_data, POLY1305_KEY_SIZE - 1);
    crypto_shash_tfm_digest(tfm, data, POLY1305_KEY_SIZE - 1, out); kfree(data); kfree(out); return 0; } void     deinit(void) { } module_init(init) module_exit(deinit) MODULE_LICENSE(GPL); The root cause of the bug     sits in neon_poly1305_blocks. The logic neon_poly1305_blocks() performed is that if it was called with     both s[] and r[] uninitialized, it will first try to initialize them with the data from the first block     that it believed to be 32 bytes in length. First 16 bytes are used as the key and the next 16 bytes for     s[]. This would lead to the aforementioned read out-of-bound. However, after calling poly1305_init_arch(),     only 16 bytes were deducted from the input and s[] is initialized yet again with the following 16 bytes.
    The second initialization of s[] is certainly redundent which indicates that the first initialization     should be for r[] only. This patch fixes the issue by calling poly1305_init_arm64() instead o
    ---truncated--- (CVE-2022-50231)

  - In the Linux kernel, the following vulnerability has been resolved: bpf: Fix reference state management     for synchronous callbacks Currently, verifier verifies callback functions (sync and async) as if they will     be executed once, (i.e. it explores execution state as if the function was being called once). The next     insn to explore is set to start of subprog and the exit from nested frame is handled using curframe > 0     and prepare_func_exit. In case of async callback it uses a customized variant of push_stack simulating a     kind of branch to set up custom state and execution context for the async callback. While this approach is     simple and works when callback really will be executed only once, it is unsafe for all of our current     helpers which are for_each style, i.e. they execute the callback multiple times. A callback releasing     acquired references of the caller may do so multiple times, but currently verifier sees it as one call     inside the frame, which then returns to caller. Hence, it thinks it released some reference that the cb     e.g. got access through callback_ctx (register filled inside cb from spilled typed register on stack).
    Similarly, it may see that an acquire call is unpaired inside the callback, so the caller will copy the     reference state of callback and then will have to release the register with new ref_obj_ids. But again,     the callback may execute multiple times, but the verifier will only account for acquired references for a     single symbolic execution of the callback, which will cause leaks. Note that for async callback case,     things are different. While currently we have bpf_timer_set_callback which only executes it once, even for     multiple executions it would be safe, as reference state is NULL and check_reference_leak would force     program to release state before BPF_EXIT. The state is also unaffected by analysis for the caller frame.
    Hence async callback is safe. Since we want the reference state to be accessible, e.g. for pointers loaded     from stack through callback_ctx's PTR_TO_STACK, we still have to copy caller's reference_state to     callback's bpf_func_state, but we enforce that whatever references it adds to that reference_state has     been released before it hits BPF_EXIT. This requires introducing a new callback_ref member in the     reference state to distinguish between caller vs callee references. Hence, check_reference_leak now errors     out if it sees we are in callback_fn and we have not released callback_ref refs. Since there can be     multiple nested callbacks, like frame 0 -> cb1 -> cb2 etc. we need to also distinguish between whether     this particular ref belongs to this callback frame or parent, and only error for our own, so we store     state->frameno (which is always non-zero for callbacks). In short, callbacks can read parent     reference_state, but cannot mutate it, to be able to use pointers acquired by the caller. They must only     undo their changes (by releasing their own acquired_refs before BPF_EXIT) on top of caller reference_state     before returning (at which point the caller and callback state will match anyway, so no need to copy it     back to caller). (CVE-2022-50650)

  - In the Linux kernel, the following vulnerability has been resolved: net: stmmac: fix possible memory leak     in stmmac_dvr_probe() The bitmap_free() should be called to free priv->af_xdp_zc_qps when     create_singlethread_workqueue() fails, otherwise there will be a memory leak, so we add the err path     error_wq_init to fix it. (CVE-2022-50663)

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-2025-993035 advisory.

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

    crypto: arm64/poly1305 - fix a read out-of-bound

    A kasan error was reported during fuzzing:

    BUG: KASAN: slab-out-of-bounds in neon_poly1305_blocks.constprop.0+0x1b4/0x250 [poly1305_neon]     Read of size 4 at addr ffff0010e293f010 by task syz-executor.5/1646715     CPU: 4 PID: 1646715 Comm: syz-executor.5 Kdump: loaded Not tainted 5.10.0.aarch64 #1     Hardware name: Huawei TaiShan 2280 /BC11SPCD, BIOS 1.59 01/31/2019     Call trace:
     dump_backtrace+0x0/0x394      show_stack+0x34/0x4c arch/arm64/kernel/stacktrace.c:196
     __dump_stack lib/dump_stack.c:77 [inline]      dump_stack+0x158/0x1e4 lib/dump_stack.c:118      print_address_description.constprop.0+0x68/0x204 mm/kasan/report.c:387
     __kasan_report+0xe0/0x140 mm/kasan/report.c:547      kasan_report+0x44/0xe0 mm/kasan/report.c:564      check_memory_region_inline mm/kasan/generic.c:187 [inline]
     __asan_load4+0x94/0xd0 mm/kasan/generic.c:252      neon_poly1305_blocks.constprop.0+0x1b4/0x250 [poly1305_neon]      neon_poly1305_do_update+0x6c/0x15c [poly1305_neon]      neon_poly1305_update+0x9c/0x1c4 [poly1305_neon]      crypto_shash_update crypto/shash.c:131 [inline]      shash_finup_unaligned+0x84/0x15c crypto/shash.c:179      crypto_shash_finup+0x8c/0x140 crypto/shash.c:193      shash_digest_unaligned+0xb8/0xe4 crypto/shash.c:201      crypto_shash_digest+0xa4/0xfc crypto/shash.c:217      crypto_shash_tfm_digest+0xb4/0x150 crypto/shash.c:229      essiv_skcipher_setkey+0x164/0x200 [essiv]      crypto_skcipher_setkey+0xb0/0x160 crypto/skcipher.c:612      skcipher_setkey+0x3c/0x50 crypto/algif_skcipher.c:305      alg_setkey+0x114/0x2a0 crypto/af_alg.c:220      alg_setsockopt+0x19c/0x210 crypto/af_alg.c:253
     __sys_setsockopt+0x190/0x2e0 net/socket.c:2123
     __do_sys_setsockopt net/socket.c:2134 [inline]
     __se_sys_setsockopt net/socket.c:2131 [inline]
     __arm64_sys_setsockopt+0x78/0x94 net/socket.c:2131
     __invoke_syscall arch/arm64/kernel/syscall.c:36 [inline]      invoke_syscall+0x64/0x100 arch/arm64/kernel/syscall.c:48      el0_svc_common.constprop.0+0x220/0x230 arch/arm64/kernel/syscall.c:155      do_el0_svc+0xb4/0xd4 arch/arm64/kernel/syscall.c:217      el0_svc+0x24/0x3c arch/arm64/kernel/entry-common.c:353      el0_sync_handler+0x160/0x164 arch/arm64/kernel/entry-common.c:369      el0_sync+0x160/0x180 arch/arm64/kernel/entry.S:683

    This error can be reproduced by the following code compiled as ko on a     system with kasan enabled:

    #include <linux/module.h>     #include <linux/crypto.h>     #include <crypto/hash.h>     #include <crypto/poly1305.h>

    char test_data[] = \x00\x01\x02\x03\x04\x05\x06\x07                        \x08\x09\x0a\x0b\x0c\x0d\x0e\x0f                        \x10\x11\x12\x13\x14\x15\x16\x17                        \x18\x19\x1a\x1b\x1c\x1d\x1e;

    int init(void)     {             struct crypto_shash *tfm = NULL;
            char *data = NULL, *out = NULL;

            tfm = crypto_alloc_shash(poly1305, 0, 0);
            data = kmalloc(POLY1305_KEY_SIZE - 1, GFP_KERNEL);
            out = kmalloc(POLY1305_DIGEST_SIZE, GFP_KERNEL);
            memcpy(data, test_data, POLY1305_KEY_SIZE - 1);
            crypto_shash_tfm_digest(tfm, data, POLY1305_KEY_SIZE - 1, out);

            kfree(data);
            kfree(out);
            return 0;
    }

    void deinit(void)     {     }

    module_init(init)     module_exit(deinit)     MODULE_LICENSE(GPL);

    The root cause of the bug sits in neon_poly1305_blocks. The logic     neon_poly1305_blocks() performed is that if it was called with both s[]     and r[] uninitialized, it will first try to initialize them with the     data from the first block that it believed to be 32 bytes in length.
    First 16 bytes are used as the key and the next 16 bytes for s[]. This     would lead to the aforementioned read out-of-bound. However, after     calling poly1305_init_arch(), only 16 bytes were deducted from the input     and s[] is initialized yet again with the following 16 bytes. The second     initialization of s[] is certainly redundent which indicates that the     first initialization should be for r[] only.

    This patch fixes the issue by calling poly1305_init_arm64() instead o
    ---truncated---

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

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

    crypto: arm64/poly1305 - fix a read out-of-bound

    A kasan error was reported during fuzzing:

    BUG: KASAN: slab-out-of-bounds in neon_poly1305_blocks.constprop.0+0x1b4/0x250 [poly1305_neon]     Read of size 4 at addr ffff0010e293f010 by task syz-executor.5/1646715     CPU: 4 PID: 1646715 Comm: syz-executor.5 Kdump: loaded Not tainted 5.10.0.aarch64 #1     Hardware name: Huawei TaiShan 2280 /BC11SPCD, BIOS 1.59 01/31/2019     Call trace:
     dump_backtrace+0x0/0x394      show_stack+0x34/0x4c arch/arm64/kernel/stacktrace.c:196
     __dump_stack lib/dump_stack.c:77 [inline]      dump_stack+0x158/0x1e4 lib/dump_stack.c:118      print_address_description.constprop.0+0x68/0x204 mm/kasan/report.c:387
     __kasan_report+0xe0/0x140 mm/kasan/report.c:547      kasan_report+0x44/0xe0 mm/kasan/report.c:564      check_memory_region_inline mm/kasan/generic.c:187 [inline]
     __asan_load4+0x94/0xd0 mm/kasan/generic.c:252      neon_poly1305_blocks.constprop.0+0x1b4/0x250 [poly1305_neon]      neon_poly1305_do_update+0x6c/0x15c [poly1305_neon]      neon_poly1305_update+0x9c/0x1c4 [poly1305_neon]      crypto_shash_update crypto/shash.c:131 [inline]      shash_finup_unaligned+0x84/0x15c crypto/shash.c:179      crypto_shash_finup+0x8c/0x140 crypto/shash.c:193      shash_digest_unaligned+0xb8/0xe4 crypto/shash.c:201      crypto_shash_digest+0xa4/0xfc crypto/shash.c:217      crypto_shash_tfm_digest+0xb4/0x150 crypto/shash.c:229      essiv_skcipher_setkey+0x164/0x200 [essiv]      crypto_skcipher_setkey+0xb0/0x160 crypto/skcipher.c:612      skcipher_setkey+0x3c/0x50 crypto/algif_skcipher.c:305      alg_setkey+0x114/0x2a0 crypto/af_alg.c:220      alg_setsockopt+0x19c/0x210 crypto/af_alg.c:253
     __sys_setsockopt+0x190/0x2e0 net/socket.c:2123
     __do_sys_setsockopt net/socket.c:2134 [inline]
     __se_sys_setsockopt net/socket.c:2131 [inline]
     __arm64_sys_setsockopt+0x78/0x94 net/socket.c:2131
     __invoke_syscall arch/arm64/kernel/syscall.c:36 [inline]      invoke_syscall+0x64/0x100 arch/arm64/kernel/syscall.c:48      el0_svc_common.constprop.0+0x220/0x230 arch/arm64/kernel/syscall.c:155      do_el0_svc+0xb4/0xd4 arch/arm64/kernel/syscall.c:217      el0_svc+0x24/0x3c arch/arm64/kernel/entry-common.c:353      el0_sync_handler+0x160/0x164 arch/arm64/kernel/entry-common.c:369      el0_sync+0x160/0x180 arch/arm64/kernel/entry.S:683

    This error can be reproduced by the following code compiled as ko on a     system with kasan enabled:

    #include <linux/module.h>     #include <linux/crypto.h>     #include <crypto/hash.h>     #include <crypto/poly1305.h>

    char test_data[] = \x00\x01\x02\x03\x04\x05\x06\x07                        \x08\x09\x0a\x0b\x0c\x0d\x0e\x0f                        \x10\x11\x12\x13\x14\x15\x16\x17                        \x18\x19\x1a\x1b\x1c\x1d\x1e;

    int init(void)     {             struct crypto_shash *tfm = NULL;
            char *data = NULL, *out = NULL;

            tfm = crypto_alloc_shash(poly1305, 0, 0);
            data = kmalloc(POLY1305_KEY_SIZE - 1, GFP_KERNEL);
            out = kmalloc(POLY1305_DIGEST_SIZE, GFP_KERNEL);
            memcpy(data, test_data, POLY1305_KEY_SIZE - 1);
            crypto_shash_tfm_digest(tfm, data, POLY1305_KEY_SIZE - 1, out);

            kfree(data);
            kfree(out);
            return 0;
    }

    void deinit(void)     {     }

    module_init(init)     module_exit(deinit)     MODULE_LICENSE(GPL);

    The root cause of the bug sits in neon_poly1305_blocks. The logic     neon_poly1305_blocks() performed is that if it was called with both s[]     and r[] uninitialized, it will first try to initialize them with the     data from the first block that it believed to be 32 bytes in length.
    First 16 bytes are used as the key and the next 16 bytes for s[]. This     would lead to the aforementioned read out-of-bound. However, after     calling poly1305_init_arch(), only 16 bytes were deducted from the input     and s[] is initialized yet again with the following 16 bytes. The second     initialization of s[] is certainly redundent which indicates that the     first initialization should be for r[] only.

    This patch fixes the issue by calling poly1305_init_arm64() instead o
    ---truncated---

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

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

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

    KVM: VMX: Do _all_ initialization before exposing /dev/kvm to userspace(CVE-2022-49932)

    drivers:md:fix a potential use-after-free bug(CVE-2022-50022)

    ceph: don't leak snap_rwsem in handle_cap_grant(CVE-2022-50059)

    posix-cpu-timers: Cleanup CPU timers before freeing them during exec(CVE-2022-50095)

    scsi: qla2xxx: Fix crash due to stale SRB access around I/O timeouts(CVE-2022-50098)

    sched/core: Do not requeue task on CPU excluded from cpus_mask(CVE-2022-50100)

    sched, cpuset: Fix dl_cpu_busy() panic due to empty cs-cpus_allowed(CVE-2022-50103)

    An issue was discovered in drivers/tty/n_gsm.c in the Linux kernel 6.2. There is a sleeping function     called from an invalid context in gsmld_write, which will block the kernel. Note: This has been disputed     by 3rd parties as not a valid vulnerability.(CVE-2023-31082)

    scsi: qla2xxx: Perform lockless command completion in abort path(CVE-2023-53041)

    drm/nouveau: prime: fix ttm_bo_delayed_delete oops(CVE-2025-37765)

    dmaengine: idxd: fix memory leak in error handling path of idxd_alloc(CVE-2025-38015)

    padata: do not leak refcount in reorder_work(CVE-2025-38031)

    nvmet-tcp: don't restore null sk_state_change(CVE-2025-38035)

    rseq: Fix segfault on registration when rseq_cs is non-zero(CVE-2025-38067)

    libnvdimm/labels: Fix divide error in nd_label_data_init()(CVE-2025-38072)

    HID: usbhid: Eliminate recurrent out-of-bounds bug in usbhid_parse()(CVE-2025-38103)

    net: openvswitch: Fix the dead loop of MPLS parse(CVE-2025-38146)

    calipso: Don't call calipso functions for AF_INET sk.(CVE-2025-38147)

    tipc: fix null-ptr-deref when acquiring remote ip of ethernet bearer(CVE-2025-38184)

    net: clear the dst when changing skb protocol(CVE-2025-38192)

    ipc: fix to protect IPCS lookups using RCU(CVE-2025-38212)

    fbdev: Fix do_register_framebuffer to prevent null-ptr-deref in fb_videomode_to_var(CVE-2025-38215)

    sched/rt: Fix race in push_rt_task(CVE-2025-38234)

    nvme-tcp: sanitize request list handling(CVE-2025-38264)

    net: tipc: fix refcount warning in tipc_aead_encrypt(CVE-2025-38273)

    fbdev: core: fbcvt: avoid division by 0 in fb_cvt_hperiod()(CVE-2025-38312)

    arm64/ptrace: Fix stack-out-of-bounds read in regs_get_kernel_stack_nth()(CVE-2025-38320)

    virtio-net: ensure the received length does not exceed allocated size(CVE-2025-38375)

    NFSv4/pNFS: Fix a race to wake on NFS_LAYOUT_DRAIN(CVE-2025-38393)

    perf: Fix sample vs do_exit()(CVE-2025-38424)

    net/sched: Abort __tc_modify_qdisc if parent class does not exist(CVE-2025-38457)

    tipc: Fix use-after-free in tipc_conn_close().(CVE-2025-38464)

    netlink: Fix wraparounds of sk-sk_rmem_alloc.(CVE-2025-38465)

    perf: Revert to requiring CAP_SYS_ADMIN for uprobes(CVE-2025-38466)

    do_change_type(): refuse to operate on unmounted/not ours mounts(CVE-2025-38498)

    tracing: Add down_write(trace_event_sem) when adding trace event(CVE-2025-38539)

    perf/core: Prevent VMA split of buffer mappings(CVE-2025-38563)

    perf/core: Exit early on perf_mmap() fail(CVE-2025-38565)

    pptp: ensure minimal skb length in pptp_xmit()(CVE-2025-38574)

    pinmux: fix race causing mux_owner NULL with active mux_usecount(CVE-2025-38632)

    i2c: qup: jump out of the loop in case of timeout(CVE-2025-38671)

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

    netfilter: conntrack: revisit gc autotuning(CVE-2022-49110)

    bpf, sockmap: Fix memleak in sk_psock_queue_msg(CVE-2022-49207)

    block: fix rq-qos breakage from skipping rq_qos_done_bio()(CVE-2022-49266)

    tcp: add accessors to read/set tp-snd_cwnd(CVE-2022-49325)

    ip_gre: test csum_start instead of transport header(CVE-2022-49340)

    netfilter: nf_tables: double hook unregistration in netns path(CVE-2022-49558)

    tcp: Fix data-races around sysctl_tcp_recovery.(CVE-2022-49574)

    igmp: Fix data-races around sysctl_igmp_llm_reports.(CVE-2022-49590)

    tcp: Fix a data-race around sysctl_tcp_probe_interval.(CVE-2022-49593)

    ALSA: usb-audio: Drop snd_BUG_ON() from snd_usbmidi_output_open()(CVE-2022-49772)

    macvlan: enforce a consistent minimal mtu(CVE-2022-49776)

    x86/sgx: Add overflow check in sgx_validate_offset_length()(CVE-2022-49785)

    mmc: sdhci-pci: Fix possible memory leak caused by missing pci_dev_put()(CVE-2022-49787)

    tracing: Fix memory leak in tracing_read_pipe()(CVE-2022-49801)

    netdevsim: Fix memory leak of nsim_dev-fa_cookie(CVE-2022-49803)

    bridge: switchdev: Fix memory leaks when changing VLAN protocol(CVE-2022-49812)

    net: ena: Fix error handling in ena_init()(CVE-2022-49813)

    sctp: clear out_curr if all frag chunks of current msg are pruned(CVE-2022-49838)

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

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

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

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

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

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

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

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

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

    tty: n_gsm: add sanity check for gsm-receive in gsm_receive_buf()(CVE-2022-49940)

    vt: Clear selection before changing the font(CVE-2022-49948)

    bpf: Do mark_chain_precision for ARG_CONST_ALLOC_SIZE_OR_ZERO(CVE-2022-49961)

    arm64: cacheinfo: Fix incorrect assignment of signed error value to unsigned fw_level(CVE-2022-49964)

    bpf: Fix a data-race around bpf_jit_limit.(CVE-2022-49967)

    ftrace: Fix NULL pointer dereference in is_ftrace_trampoline when ftrace is dead(CVE-2022-49977)

    net: fix refcount bug in sk_psock_get (2)(CVE-2022-49979)

    media: pvrusb2: fix memory leak in pvr_probe(CVE-2022-49982)

    bpf: Don't use tnum_range on array range checking for poke descriptors(CVE-2022-49985)

    ice: xsk: prohibit usage of non-balanced queue id(CVE-2022-50003)

    kprobes: don't call disarm_kprobe() for disabled kprobes(CVE-2022-50008)

    ext4: avoid resizing to a partial cluster size(CVE-2022-50020)

    x86/fpu: KVM: Set the base guest FPU uABI size to sizeof(struct kvm_xsave).(CVE-2022-49557)

    A cross-privilege Spectre v2 vulnerability allows attackers to bypass all deployed mitigations, including     the recent Fine(IBT), and to leak arbitrary Linux kernel memory on Intel systems.(CVE-2024-2201)

    perf/x86/amd/uncore: Fix memory leak for events array(CVE-2022-49784)

    perf/x86/amd: Fix crash due to race between amd_pmu_enable_all, perf NMI and throttling(CVE-2022-49781)

    perf/x86/amd/core: Always clear status for idx(CVE-2023-53073)

    drm/drv: Fix potential memory leak in drm_dev_init().(CVE-2022-49830)

    drm/shmem-helper: Remove another errant put in error path(CVE-2023-53084)

    perf/core: Fix perf_output_begin parameter is incorrectly invoked in perf_event_bpf_output(CVE-2023-53065)

    arm64: bpf: Only mitigate cBPF programs loaded by unprivileged users(CVE-2025-37963)

    arm64: bpf: Add BHB mitigation to the epilogue for cBPF programs(CVE-2025-37948)

    crypto: null - Use spin lock instead of mutex(CVE-2025-37808)

    tracing: Fix oob write in trace_seq_to_buffer().(CVE-2025-37923)

    media: dw2102: Fix null-ptr-deref in dw2102_i2c_transfer().(CVE-2023-53146)

    usb: ucsi: Fix NULL pointer deref in ucsi_connector_change().(CVE-2023-53049)

    iommu/amd: Fix potential buffer overflow in parse_ivrs_acpihid(CVE-2025-37927)

    drm     ouveau: Fix WARN_ON in nouveau_fence_context_kill().(CVE-2025-37930)

    module: ensure that kobject_put() is safe for module type kobjects(CVE-2025-37995)

    bnxt_en: Fix out-of-bound memcpy() during ethtool -w(CVE-2025-37911)

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

    HID: intel-ish-hid: ipc: Fix potential use-after-free in work function(CVE-2023-53039)

    IB/hfi1: Correctly move list in sc_disable().(CVE-2022-49931)

    tpm: do not start chip while suspended(CVE-2025-23149)

    bpf: check changes_pkt_data property for extension programs(CVE-2024-58100)

    ext4: block range must be validated before use in ext4_mb_clear_bb()(CVE-2022-50021)

    iavf: Fix adminq error handling(CVE-2022-50055)

    virtio_net: fix memory leak inside XPD_TX with mergeable(CVE-2022-50065)

    net: atlantic: fix aq_vec index out of range error(CVE-2022-50066)

    BPF: Fix potential bad pointer dereference in bpf_sys_bpf()(CVE-2022-50069)

    net: tap: NULL pointer derefence in dev_parse_header_protocol when skb-dev is null(CVE-2022-50073)

    apparmor: Fix memleak in aa_simple_write_to_buffer()(CVE-2022-50074)

    resolved: apparmor: fix reference count leak in aa_pivotroot() (CVE-2022-50077)

    ext4: fix warning in ext4_iomap_begin as race between bmap and write(CVE-2022-50082)

    Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering     Authority.(CVE-2022-50083)

    block: don't allow the same type rq_qos add more than once(CVE-2022-50086)

    jbd2: fix assertion 'jh-b_frozen_data == NULL' failure when journal aborted(CVE-2022-50126)

    RDMA/srpt: Fix a use-after-free(CVE-2022-50129)

    RDMA/hfi1: fix potential memory leak in setup_base_ctxt()(CVE-2022-50134)

    RDMA/qedr: Fix potential memory leak in __qedr_alloc_mr()(CVE-2022-50138)

    bpf: fix potential 32-bit overflow when accessing ARRAY map element(CVE-2022-50167)

    virtio-gpu: fix a missing check to avoid NULL dereference(CVE-2022-50181)

    selinux: Add boundary check in put_entry()(CVE-2022-50200)

    PM: hibernate: defer device probing when resuming from hibernation(CVE-2022-50202)

    arm64: fix oops in concurrently setting insn_emulation sysctls(CVE-2022-50206)

    netfilter: nf_tables: do not allow SET_ID to refer to another table(CVE-2022-50213)

    scsi: sg: Allow waiting for commands to complete on removed device(CVE-2022-50215)

    bpf: Fix KASAN use-after-free Read in compute_effective_progs(CVE-2022-50219)

    usbnet: Fix linkwatch use-after-free on disconnect(CVE-2022-50220)

    tty: vt: initialize unicode screen buffer(CVE-2022-50222)

    KVM: SVM: Don't BUG if userspace injects an interrupt with GIF=0(CVE-2022-50228)

    arm64: set UXN on swapper page tables(CVE-2022-50230)

    crypto: arm64/poly1305 - fix a read out-of-bound(CVE-2022-50231)

    arm64: set UXN on swapper page tables(CVE-2022-50232)

    netfilter: nf_tables: don't fail inserts if duplicate has expired(CVE-2023-52925)

    netfilter: allow exp not to be removed in nf_ct_find_expectation(CVE-2023-52927)

    dm crypt: add cond_resched() to dmcrypt_write()(CVE-2023-53051)

    erspan: do not use skb_mac_header() in ndo_start_xmit()(CVE-2023-53053)

    net/mlx5: E-Switch, Fix an Oops in error handling code(CVE-2023-53058)

    net: usb: smsc95xx: Limit packet length to skb-len(CVE-2023-53062)

    qed/qed_sriov: guard against NULL derefs from qed_iov_get_vf_info(CVE-2023-53066)

    net: usb: lan78xx: Limit packet length to skb-len(CVE-2023-53068)

    net/mlx5: Fix steering rules cleanup(CVE-2023-53079)

    xsk: Add missing overflow check in xdp_umem_reg(CVE-2023-53080)

    ice: xsk: disable txq irq before flushing hw(CVE-2023-53102)

    bonding: restore bond's IFF_SLAVE flag if a non-eth dev enslave fails(CVE-2023-53103)

    net: tunnels: annotate lockless accesses to dev-needed_headroom(CVE-2023-53109)

    i40e: Fix kernel crash during reboot when adapter is in recovery mode(CVE-2023-53114)

    tcp: tcp_make_synack() can be called from process context(CVE-2023-53121)

    net: usb: smsc75xx: Limit packet length to skb-len(CVE-2023-53125)

    SUNRPC: Fix a server shutdown leak(CVE-2023-53131)

    bpf, sockmap: Fix an infinite loop error when len is 0 in tcp_bpf_recvmsg_parser()(CVE-2023-53133)

    bpf: consider that tail calls invalidate packet pointers(CVE-2024-58237)

    net: avoid race between device unregistration and ethnl ops(CVE-2025-21701)

    ata: libata-sff: Ensure that we cannot write outside the allocated buffer(CVE-2025-21738)

    block: mark GFP_NOIO around sysfs -store()(CVE-2025-21817)

    netfilter: nf_tables: reject mismatching sum of field_len with set key length(CVE-2025-21826)

    netfilter: socket: Lookup orig tuple for IPv6 SNAT(CVE-2025-22021)

    net: fix geneve_opt length integer overflow(CVE-2025-22055)

    net: decrease cached dst counters in dst_release(CVE-2025-22057)

    rtnetlink: Allocate vfinfo size for VF GUIDs when supported(CVE-2025-22075)

    RDMA/mlx5: Fix mlx5_poll_one() cur_qp update flow(CVE-2025-22086)

    net: fix NULL pointer dereference in l3mdev_l3_rcv(CVE-2025-22103)

    sctp: detect and prevent references to a freed transport in sendmsg(CVE-2025-23142)

    net: ppp: Add bound checking for skb data on ppp_sync_txmung Ensure we have enough data in linear buffer     from skb before accessing initial bytes.(CVE-2025-37749)

    net: tls: explicitly disallow disconnect(CVE-2025-37756)

    tipc: fix memory leak in tipc_link_xmit(CVE-2025-37757)

    cxgb4: fix memory leak in cxgb4_init_ethtool_filters() error path(CVE-2025-37788)

    net: openvswitch: fix nested key length validation in the set() action(CVE-2025-37789)

    net_sched: hfsc: Fix a UAF vulnerability in class handling(CVE-2025-37797)

    codel: remove sch-q.qlen check before qdisc_tree_reduce_backlog()(CVE-2025-37798)

    net_sched: hfsc: Fix a potential UAF in hfsc_dequeue() too(CVE-2025-37823)

    tipc: fix NULL pointer dereference in tipc_mon_reinit_self()(CVE-2025-37824)

    page_pool: avoid infinite loop to schedule delayed worker(CVE-2025-37859)

    HID: pidff: Fix null pointer dereference in pidff_find_fields(CVE-2025-37862)

    net_sched: hfsc: Fix a UAF vulnerability in class with netem as child qdisc(CVE-2025-37890)

    net_sched: qfq: Fix double list add in class with netem as child qdisc(CVE-2025-37913)

    net_sched: drr: Fix double list add in class with netem as child qdisc(CVE-2025-37915)

    xsk: Fix race condition in AF_XDP generic RX path(CVE-2025-37920)

    sch_htb: make htb_qlen_notify() idempotent(CVE-2025-37932)

    bpf: Scrub packet on bpf_redirect_peer(CVE-2025-37959)

    ipvs: fix uninit-value for saddr in do_output_route4(CVE-2025-37961)

    net: phy: leds: fix memory leak(CVE-2025-37989)

    net_sched: Flush gso_skb list too during -change()(CVE-2025-37992)

    netfilter: ipset: fix region locking in hash types(CVE-2025-37997)

    openvswitch: Fix unsafe attribute parsing in output_userspace()(CVE-2025-37998)

    sch_hfsc: Fix qlen accounting bug when using peek in hfsc_enqueue()(CVE-2025-38000)

    net_sched: hfsc: Address reentrant enqueue adding class to eltree twice(CVE-2025-38001)

    dmaengine: idxd: Refactor remove call with idxd_cleanup() helper(CVE-2025-38014)

    serial: mctrl_gpio: split disable_ms into sync and no_sync APIs(CVE-2025-38040)

    media: cx231xx: set device_caps for 417(CVE-2025-38044)

    net/tipc: fix slab-use-after-free Read in tipc_aead_encrypt_done(CVE-2025-38052)

    net: pktgen: fix access outside of user given buffer in pktgen_thread_write()(CVE-2025-38061)

    dm: fix unconditional IO throttle caused by REQ_PREFLUSH(CVE-2025-38063)

    dm cache: prevent BUG_ON by blocking retries on failed device resumes(CVE-2025-38066)

    crypto: lzo - Fix compression buffer overrun(CVE-2025-38068)

    vhost-scsi: protect vq-log_used with vq-mutex(CVE-2025-38074)

    scsi: target: iscsi: Fix timeout on deleted connection(CVE-2025-38075)

    net_sched: prio: fix a race in prio_tune()(CVE-2025-38083)

    mm/hugetlb: unshare page tables during VMA split, not before(CVE-2025-38084)

    net: ch9200: fix uninitialised access during mii_nway_restart(CVE-2025-38086)

    x86/iopl: Cure TIF_IO_BITMAP inconsistencies(CVE-2025-38100)

    VMCI: fix race between vmci_host_setup_notify and vmci_ctx_unset_notify(CVE-2025-38102)

    net_sched: red: fix a race in __red_change()(CVE-2025-38108)

    net/mdiobus: Fix potential out-of-bounds read/write access(CVE-2025-38111)

    net: Fix TOCTOU issue in sk_is_readable()(CVE-2025-38112)

    net_sched: sch_sfq: fix a potential crash on gso_skb handling(CVE-2025-38115)

    netfilter: nf_set_pipapo_avx2: fix initial map fill(CVE-2025-38120)

    net: fix udp gso skb_segment after pull from frag_list(CVE-2025-38124)

    ice: fix Tx scheduler error handling in XDP callback(CVE-2025-38127)

    page_pool: Fix use-after-free in page_pool_recycle_in_ring(CVE-2025-38129)

    bpf, sockmap: Avoid using sk_socket after free when sending(CVE-2025-38154)

    netfilter: nft_set_pipapo: prevent overflow in lookup table allocation(CVE-2025-38162)

    bpf, sockmap: Fix panic when calling skb_linearize(CVE-2025-38165)

    bpf: fix ktls panic with sockmap(CVE-2025-38166)

    RDMA/iwcm: Fix use-after-free of work objects after cm_id destruction(CVE-2025-38211)

    fbdev: Fix fb_set_var to prevent null-ptr-deref in fb_videomode_to_var(CVE-2025-38214)

    ext4: inline: fix len overflow in ext4_prepare_inline_data(CVE-2025-38222)

    media: cxusb: no longer judge rbuf when the write fails(CVE-2025-38229)

    bpf: Avoid __bpf_prog_ret0_warn when jit fails(CVE-2025-38280)

    bpf: Fix WARN() in get_bpf_raw_tp_regs(CVE-2025-38285)

    EDAC/skx_common: Fix general protection fault(CVE-2025-38298)

    mpls: Use rcu_dereference_rtnl() in mpls_route_input_rcu().(CVE-2025-38324)

    jbd2: fix data-race and null-ptr-deref in jbd2_journal_dirty_metadata()(CVE-2025-38337)

    ACPICA: fix acpi operand cache leak in dswstate.c(CVE-2025-38345)

    ftrace: Fix UAF when lookup kallsym after ftrace disabled(CVE-2025-38346)

    posix-cpu-timers: fix race between handle_posix_cpu_timers() and posix_cpu_timer_del()(CVE-2025-38352)

    ACPICA: Refuse to evaluate a method if arguments are missing(CVE-2025-38386)

    usb: typec: altmodes/displayport: do not index invalid pin_assignments(CVE-2025-38391)

    fs: export anon_inode_make_secure_inode() and fix secretmem LSM bypass(CVE-2025-38396)

    scsi: target: Fix NULL pointer dereference in core_scsi3_decode_spec_i_port()(CVE-2025-38399)

    drm/gem: Acquire references on GEM handles for framebuffers(CVE-2025-38449)

    HID: core: ensure the allocated report buffer can contain the reserved report ID(CVE-2025-38495)

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 :

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

    netfilter: conntrack: revisit gc autotuning(CVE-2022-49110)

    bpf, sockmap: Fix memleak in sk_psock_queue_msg(CVE-2022-49207)

    block: fix rq-qos breakage from skipping rq_qos_done_bio()(CVE-2022-49266)

    tcp: add accessors to read/set tp-snd_cwnd(CVE-2022-49325)

    ip_gre: test csum_start instead of transport header(CVE-2022-49340)

    netfilter: nf_tables: double hook unregistration in netns path(CVE-2022-49558)

    tcp: Fix data-races around sysctl_tcp_recovery.(CVE-2022-49574)

    igmp: Fix data-races around sysctl_igmp_llm_reports.(CVE-2022-49590)

    tcp: Fix a data-race around sysctl_tcp_probe_interval.(CVE-2022-49593)

    ALSA: usb-audio: Drop snd_BUG_ON() from snd_usbmidi_output_open()(CVE-2022-49772)

    macvlan: enforce a consistent minimal mtu(CVE-2022-49776)

    x86/sgx: Add overflow check in sgx_validate_offset_length()(CVE-2022-49785)

    mmc: sdhci-pci: Fix possible memory leak caused by missing pci_dev_put()(CVE-2022-49787)

    tracing: Fix memory leak in tracing_read_pipe()(CVE-2022-49801)

    netdevsim: Fix memory leak of nsim_dev-fa_cookie(CVE-2022-49803)

    bridge: switchdev: Fix memory leaks when changing VLAN protocol(CVE-2022-49812)

    net: ena: Fix error handling in ena_init()(CVE-2022-49813)

    sctp: clear out_curr if all frag chunks of current msg are pruned(CVE-2022-49838)

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

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

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

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

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

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

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

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

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

    tty: n_gsm: add sanity check for gsm-receive in gsm_receive_buf()(CVE-2022-49940)

    vt: Clear selection before changing the font(CVE-2022-49948)

    bpf: Do mark_chain_precision for ARG_CONST_ALLOC_SIZE_OR_ZERO(CVE-2022-49961)

    arm64: cacheinfo: Fix incorrect assignment of signed error value to unsigned fw_level(CVE-2022-49964)

    bpf: Fix a data-race around bpf_jit_limit.(CVE-2022-49967)

    ftrace: Fix NULL pointer dereference in is_ftrace_trampoline when ftrace is dead(CVE-2022-49977)

    net: fix refcount bug in sk_psock_get (2)(CVE-2022-49979)

    media: pvrusb2: fix memory leak in pvr_probe(CVE-2022-49982)

    bpf: Don't use tnum_range on array range checking for poke descriptors(CVE-2022-49985)

    ice: xsk: prohibit usage of non-balanced queue id(CVE-2022-50003)

    kprobes: don't call disarm_kprobe() for disabled kprobes(CVE-2022-50008)

    ext4: avoid resizing to a partial cluster size(CVE-2022-50020)

    ext4: block range must be validated before use in ext4_mb_clear_bb()(CVE-2022-50021)

    iavf: Fix adminq error handling(CVE-2022-50055)

    virtio_net: fix memory leak inside XPD_TX with mergeable(CVE-2022-50065)

    net: atlantic: fix aq_vec index out of range error(CVE-2022-50066)

    BPF: Fix potential bad pointer dereference in bpf_sys_bpf()(CVE-2022-50069)

    net: tap: NULL pointer derefence in dev_parse_header_protocol when skb-dev is null(CVE-2022-50073)

    apparmor: Fix memleak in aa_simple_write_to_buffer()(CVE-2022-50074)

    resolved: apparmor: fix reference count leak in aa_pivotroot() (CVE-2022-50077)

    ext4: fix warning in ext4_iomap_begin as race between bmap and write(CVE-2022-50082)

    Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering     Authority.(CVE-2022-50083)

    block: don't allow the same type rq_qos add more than once(CVE-2022-50086)

    jbd2: fix assertion 'jh-b_frozen_data == NULL' failure when journal aborted(CVE-2022-50126)

    RDMA/srpt: Fix a use-after-free(CVE-2022-50129)

    RDMA/hfi1: fix potential memory leak in setup_base_ctxt()(CVE-2022-50134)

    RDMA/qedr: Fix potential memory leak in __qedr_alloc_mr()(CVE-2022-50138)

    bpf: fix potential 32-bit overflow when accessing ARRAY map element(CVE-2022-50167)

    virtio-gpu: fix a missing check to avoid NULL dereference(CVE-2022-50181)

    selinux: Add boundary check in put_entry()(CVE-2022-50200)

    PM: hibernate: defer device probing when resuming from hibernation(CVE-2022-50202)

    arm64: fix oops in concurrently setting insn_emulation sysctls(CVE-2022-50206)

    netfilter: nf_tables: do not allow SET_ID to refer to another table(CVE-2022-50213)

    scsi: sg: Allow waiting for commands to complete on removed device(CVE-2022-50215)

    bpf: Fix KASAN use-after-free Read in compute_effective_progs(CVE-2022-50219)

    usbnet: Fix linkwatch use-after-free on disconnect(CVE-2022-50220)

    tty: vt: initialize unicode screen buffer(CVE-2022-50222)

    KVM: SVM: Don't BUG if userspace injects an interrupt with GIF=0(CVE-2022-50228)

    arm64: set UXN on swapper page tables(CVE-2022-50230)

    crypto: arm64/poly1305 - fix a read out-of-bound(CVE-2022-50231)

    arm64: set UXN on swapper page tables(CVE-2022-50232)

    netfilter: nf_tables: don't fail inserts if duplicate has expired(CVE-2023-52925)

    netfilter: allow exp not to be removed in nf_ct_find_expectation(CVE-2023-52927)

    dm crypt: add cond_resched() to dmcrypt_write()(CVE-2023-53051)

    erspan: do not use skb_mac_header() in ndo_start_xmit()(CVE-2023-53053)

    net/mlx5: E-Switch, Fix an Oops in error handling code(CVE-2023-53058)

    net: usb: smsc95xx: Limit packet length to skb-len(CVE-2023-53062)

    qed/qed_sriov: guard against NULL derefs from qed_iov_get_vf_info(CVE-2023-53066)

    net: usb: lan78xx: Limit packet length to skb-len(CVE-2023-53068)

    net/mlx5: Fix steering rules cleanup(CVE-2023-53079)

    xsk: Add missing overflow check in xdp_umem_reg(CVE-2023-53080)

    ice: xsk: disable txq irq before flushing hw(CVE-2023-53102)

    bonding: restore bond's IFF_SLAVE flag if a non-eth dev enslave fails(CVE-2023-53103)

    net: tunnels: annotate lockless accesses to dev-needed_headroom(CVE-2023-53109)

    i40e: Fix kernel crash during reboot when adapter is in recovery mode(CVE-2023-53114)

    tcp: tcp_make_synack() can be called from process context(CVE-2023-53121)

    net: usb: smsc75xx: Limit packet length to skb-len(CVE-2023-53125)

    SUNRPC: Fix a server shutdown leak(CVE-2023-53131)

    bpf, sockmap: Fix an infinite loop error when len is 0 in tcp_bpf_recvmsg_parser()(CVE-2023-53133)

    bpf: consider that tail calls invalidate packet pointers(CVE-2024-58237)

    net: avoid race between device unregistration and ethnl ops(CVE-2025-21701)

    ata: libata-sff: Ensure that we cannot write outside the allocated buffer(CVE-2025-21738)

    block: mark GFP_NOIO around sysfs -store()(CVE-2025-21817)

    netfilter: nf_tables: reject mismatching sum of field_len with set key length(CVE-2025-21826)

    netfilter: socket: Lookup orig tuple for IPv6 SNAT(CVE-2025-22021)

    net: fix geneve_opt length integer overflow(CVE-2025-22055)

    net: decrease cached dst counters in dst_release(CVE-2025-22057)

    rtnetlink: Allocate vfinfo size for VF GUIDs when supported(CVE-2025-22075)

    RDMA/mlx5: Fix mlx5_poll_one() cur_qp update flow(CVE-2025-22086)

    net: fix NULL pointer dereference in l3mdev_l3_rcv(CVE-2025-22103)

    sctp: detect and prevent references to a freed transport in sendmsg(CVE-2025-23142)

    net: ppp: Add bound checking for skb data on ppp_sync_txmung Ensure we have enough data in linear buffer     from skb before accessing initial bytes.(CVE-2025-37749)

    net: tls: explicitly disallow disconnect(CVE-2025-37756)

    tipc: fix memory leak in tipc_link_xmit(CVE-2025-37757)

    cxgb4: fix memory leak in cxgb4_init_ethtool_filters() error path(CVE-2025-37788)

    net: openvswitch: fix nested key length validation in the set() action(CVE-2025-37789)

    net_sched: hfsc: Fix a UAF vulnerability in class handling(CVE-2025-37797)

    codel: remove sch-q.qlen check before qdisc_tree_reduce_backlog()(CVE-2025-37798)

    net_sched: hfsc: Fix a potential UAF in hfsc_dequeue() too(CVE-2025-37823)

    tipc: fix NULL pointer dereference in tipc_mon_reinit_self()(CVE-2025-37824)

    page_pool: avoid infinite loop to schedule delayed worker(CVE-2025-37859)

    HID: pidff: Fix null pointer dereference in pidff_find_fields(CVE-2025-37862)

    net_sched: hfsc: Fix a UAF vulnerability in class with netem as child qdisc(CVE-2025-37890)

    net_sched: qfq: Fix double list add in class with netem as child qdisc(CVE-2025-37913)

    net_sched: drr: Fix double list add in class with netem as child qdisc(CVE-2025-37915)

    xsk: Fix race condition in AF_XDP generic RX path(CVE-2025-37920)

    sch_htb: make htb_qlen_notify() idempotent(CVE-2025-37932)

    bpf: Scrub packet on bpf_redirect_peer(CVE-2025-37959)

    ipvs: fix uninit-value for saddr in do_output_route4(CVE-2025-37961)

    net: phy: leds: fix memory leak(CVE-2025-37989)

    net_sched: Flush gso_skb list too during -change()(CVE-2025-37992)

    netfilter: ipset: fix region locking in hash types(CVE-2025-37997)

    openvswitch: Fix unsafe attribute parsing in output_userspace()(CVE-2025-37998)

    sch_hfsc: Fix qlen accounting bug when using peek in hfsc_enqueue()(CVE-2025-38000)

    net_sched: hfsc: Address reentrant enqueue adding class to eltree twice(CVE-2025-38001)

    dmaengine: idxd: Refactor remove call with idxd_cleanup() helper(CVE-2025-38014)

    serial: mctrl_gpio: split disable_ms into sync and no_sync APIs(CVE-2025-38040)

    media: cx231xx: set device_caps for 417(CVE-2025-38044)

    net/tipc: fix slab-use-after-free Read in tipc_aead_encrypt_done(CVE-2025-38052)

    net: pktgen: fix access outside of user given buffer in pktgen_thread_write()(CVE-2025-38061)

    dm: fix unconditional IO throttle caused by REQ_PREFLUSH(CVE-2025-38063)

    dm cache: prevent BUG_ON by blocking retries on failed device resumes(CVE-2025-38066)

    crypto: lzo - Fix compression buffer overrun(CVE-2025-38068)

    vhost-scsi: protect vq-log_used with vq-mutex(CVE-2025-38074)

    scsi: target: iscsi: Fix timeout on deleted connection(CVE-2025-38075)

    net_sched: prio: fix a race in prio_tune()(CVE-2025-38083)

    mm/hugetlb: unshare page tables during VMA split, not before(CVE-2025-38084)

    net: ch9200: fix uninitialised access during mii_nway_restart(CVE-2025-38086)

    x86/iopl: Cure TIF_IO_BITMAP inconsistencies(CVE-2025-38100)

    VMCI: fix race between vmci_host_setup_notify and vmci_ctx_unset_notify(CVE-2025-38102)

    net_sched: red: fix a race in __red_change()(CVE-2025-38108)

    net/mdiobus: Fix potential out-of-bounds read/write access(CVE-2025-38111)

    net: Fix TOCTOU issue in sk_is_readable()(CVE-2025-38112)

    net_sched: sch_sfq: fix a potential crash on gso_skb handling(CVE-2025-38115)

    netfilter: nf_set_pipapo_avx2: fix initial map fill(CVE-2025-38120)

    net: fix udp gso skb_segment after pull from frag_list(CVE-2025-38124)

    ice: fix Tx scheduler error handling in XDP callback(CVE-2025-38127)

    page_pool: Fix use-after-free in page_pool_recycle_in_ring(CVE-2025-38129)

    bpf, sockmap: Avoid using sk_socket after free when sending(CVE-2025-38154)

    netfilter: nft_set_pipapo: prevent overflow in lookup table allocation(CVE-2025-38162)

    bpf, sockmap: Fix panic when calling skb_linearize(CVE-2025-38165)

    bpf: fix ktls panic with sockmap(CVE-2025-38166)

    RDMA/iwcm: Fix use-after-free of work objects after cm_id destruction(CVE-2025-38211)

    fbdev: Fix fb_set_var to prevent null-ptr-deref in fb_videomode_to_var(CVE-2025-38214)

    ext4: inline: fix len overflow in ext4_prepare_inline_data(CVE-2025-38222)

    media: cxusb: no longer judge rbuf when the write fails(CVE-2025-38229)

    bpf: Avoid __bpf_prog_ret0_warn when jit fails(CVE-2025-38280)

    bpf: Fix WARN() in get_bpf_raw_tp_regs(CVE-2025-38285)

    EDAC/skx_common: Fix general protection fault(CVE-2025-38298)

    mpls: Use rcu_dereference_rtnl() in mpls_route_input_rcu().(CVE-2025-38324)

    jbd2: fix data-race and null-ptr-deref in jbd2_journal_dirty_metadata()(CVE-2025-38337)

    ACPICA: fix acpi operand cache leak in dswstate.c(CVE-2025-38345)

    ftrace: Fix UAF when lookup kallsym after ftrace disabled(CVE-2025-38346)

    posix-cpu-timers: fix race between handle_posix_cpu_timers() and posix_cpu_timer_del()(CVE-2025-38352)

    ACPICA: Refuse to evaluate a method if arguments are missing(CVE-2025-38386)

    usb: typec: altmodes/displayport: do not index invalid pin_assignments(CVE-2025-38391)

    fs: export anon_inode_make_secure_inode() and fix secretmem LSM bypass(CVE-2025-38396)

    scsi: target: Fix NULL pointer dereference in core_scsi3_decode_spec_i_port()(CVE-2025-38399)

    drm/gem: Acquire references on GEM handles for framebuffers(CVE-2025-38449)

    HID: core: ensure the allocated report buffer can contain the reserved report ID(CVE-2025-38495)

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

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

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

  - In the Linux kernel, the following vulnerability has been resolved: crypto: arm64/poly1305 - fix a read     out-of-bound A kasan error was reported during fuzzing: BUG: KASAN: slab-out-of-bounds in     neon_poly1305_blocks.constprop.0+0x1b4/0x250 [poly1305_neon] Read of size 4 at addr ffff0010e293f010 by     task syz-executor.5/1646715 CPU: 4 PID: 1646715 Comm: syz-executor.5 Kdump: loaded Not tainted     5.10.0.aarch64 #1 Hardware name: Huawei TaiShan 2280 /BC11SPCD, BIOS 1.59 01/31/2019 Call trace:
    dump_backtrace+0x0/0x394 show_stack+0x34/0x4c arch/arm64/kernel/stacktrace.c:196 __dump_stack     lib/dump_stack.c:77 [inline] dump_stack+0x158/0x1e4 lib/dump_stack.c:118     print_address_description.constprop.0+0x68/0x204 mm/kasan/report.c:387 __kasan_report+0xe0/0x140     mm/kasan/report.c:547 kasan_report+0x44/0xe0 mm/kasan/report.c:564 check_memory_region_inline     mm/kasan/generic.c:187 [inline] __asan_load4+0x94/0xd0 mm/kasan/generic.c:252     neon_poly1305_blocks.constprop.0+0x1b4/0x250 [poly1305_neon] neon_poly1305_do_update+0x6c/0x15c     [poly1305_neon] neon_poly1305_update+0x9c/0x1c4 [poly1305_neon] crypto_shash_update crypto/shash.c:131     [inline] shash_finup_unaligned+0x84/0x15c crypto/shash.c:179 crypto_shash_finup+0x8c/0x140     crypto/shash.c:193 shash_digest_unaligned+0xb8/0xe4 crypto/shash.c:201 crypto_shash_digest+0xa4/0xfc     crypto/shash.c:217 crypto_shash_tfm_digest+0xb4/0x150 crypto/shash.c:229 essiv_skcipher_setkey+0x164/0x200     [essiv] crypto_skcipher_setkey+0xb0/0x160 crypto/skcipher.c:612 skcipher_setkey+0x3c/0x50     crypto/algif_skcipher.c:305 alg_setkey+0x114/0x2a0 crypto/af_alg.c:220 alg_setsockopt+0x19c/0x210     crypto/af_alg.c:253 __sys_setsockopt+0x190/0x2e0 net/socket.c:2123 __do_sys_setsockopt net/socket.c:2134     [inline] __se_sys_setsockopt net/socket.c:2131 [inline] __arm64_sys_setsockopt+0x78/0x94 net/socket.c:2131
    __invoke_syscall arch/arm64/kernel/syscall.c:36 [inline] invoke_syscall+0x64/0x100     arch/arm64/kernel/syscall.c:48 el0_svc_common.constprop.0+0x220/0x230 arch/arm64/kernel/syscall.c:155     do_el0_svc+0xb4/0xd4 arch/arm64/kernel/syscall.c:217 el0_svc+0x24/0x3c arch/arm64/kernel/entry-     common.c:353 el0_sync_handler+0x160/0x164 arch/arm64/kernel/entry-common.c:369 el0_sync+0x160/0x180     arch/arm64/kernel/entry.S:683 This error can be reproduced by the following code compiled as ko on a     system with kasan enabled: #include <linux/module.h> #include <linux/crypto.h> #include <crypto/hash.h>     #include <crypto/poly1305.h> char test_data[] = \x00\x01\x02\x03\x04\x05\x06\x07     \x08\x09\x0a\x0b\x0c\x0d\x0e\x0f \x10\x11\x12\x13\x14\x15\x16\x17 \x18\x19\x1a\x1b\x1c\x1d\x1e; int     init(void) { struct crypto_shash *tfm = NULL; char *data = NULL, *out = NULL; tfm =     crypto_alloc_shash(poly1305, 0, 0); data = kmalloc(POLY1305_KEY_SIZE - 1, GFP_KERNEL); out =     kmalloc(POLY1305_DIGEST_SIZE, GFP_KERNEL); memcpy(data, test_data, POLY1305_KEY_SIZE - 1);
    crypto_shash_tfm_digest(tfm, data, POLY1305_KEY_SIZE - 1, out); kfree(data); kfree(out); return 0; } void     deinit(void) { } module_init(init) module_exit(deinit) MODULE_LICENSE(GPL); The root cause of the bug     sits in neon_poly1305_blocks. The logic neon_poly1305_blocks() performed is that if it was called with     both s[] and r[] uninitialized, it will first try to initialize them with the data from the first block     that it believed to be 32 bytes in length. First 16 bytes are used as the key and the next 16 bytes for     s[]. This would lead to the aforementioned read out-of-bound. However, after calling poly1305_init_arch(),     only 16 bytes were deducted from the input and s[] is initialized yet again with the following 16 bytes.
    The second initialization of s[] is certainly redundent which indicates that the first initialization     should be for r[] only. This patch fixes the issue by calling poly1305_init_arm64() instead o
    ---truncated--- (CVE-2022-50231)

Note that Nessus relies on the presence of the package as reported by the vendor.

The remote SUSE Linux SLES15 / SLES_SAP15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2025:02537-1 advisory.

    The SUSE Linux Enterprise 15 SP4 kernel was updated to receive various security bugfixes.


    The following security bugs were fixed:

    - CVE-2021-47557: net/sched: sch_ets: do not peek at classes beyond 'nbands' (bsc#1207361 bsc#1225468).
    - CVE-2021-47595: net/sched: sch_ets: do not remove idle classes from the round-robin list (bsc#1207361     bsc#1226552).
    - CVE-2023-52924: netfilter: nf_tables: do not skip expired elements during walk (bsc#1236821).
    - CVE-2023-52925: netfilter: nf_tables: do not fail inserts if duplicate has expired (bsc#1236822).
    - CVE-2024-26808: netfilter: nft_chain_filter: handle NETDEV_UNREGISTER for inet/ingress basechain     (bsc#1222634).
    - CVE-2024-26924: scsi: lpfc: Release hbalock before calling lpfc_worker_wake_up() (bsc#1225820).
    - CVE-2024-27397: kabi: place tstamp needed for nftables set in a hole (bsc#1224095).
    - CVE-2024-36978: net: sched: sch_multiq: fix possible OOB write in multiq_tune() (bsc#1226514).
    - CVE-2024-46800: sch/netem: fix use after free in netem_dequeue (bsc#1230827).
    - CVE-2024-53057: net/sched: stop qdisc_tree_reduce_backlog on TC_H_ROOT (bsc#1233551).
    - CVE-2024-53125: bpf: sync_linked_regs() must preserve subreg_def (bsc#1234156).
    - CVE-2024-53141: netfilter: ipset: add missing range check in bitmap_ip_uadt (bsc#1234381).
    - CVE-2024-56770: sch/netem: fix use after free in netem_dequeue (bsc#1235637).
    - CVE-2024-57947: netfilter: nf_set_pipapo: fix initial map fill (bsc#1236333).
    - CVE-2025-21700: net: sched: Disallow replacing of child qdisc from one parent to another (bsc#1237159).
    - CVE-2025-21702: pfifo_tail_enqueue: Drop new packet when sch->limit == 0 (bsc#1237312).
    - CVE-2025-21703: netem: Update sch->q.qlen before qdisc_tree_reduce_backlog() (bsc#1237313).
    - CVE-2025-21756: vsock: Orphan socket after transport release (bsc#1238876).
    - CVE-2025-23141: KVM: x86: Acquire SRCU in KVM_GET_MP_STATE to protect guest memory accesses     (bsc#1242782).
    - CVE-2025-37752: net_sched: sch_sfq: move the limit validation (bsc#1242504).
    - CVE-2025-37797: net_sched: hfsc: Fix a UAF vulnerability in class handling (bsc#1242417).
    - CVE-2025-37823: net_sched: hfsc: Fix a potential UAF in hfsc_dequeue() too (bsc#1242924).
    - CVE-2025-37890: net_sched: hfsc: Fix a UAF vulnerability in class with netem as child qdisc     (bsc#1243330).
    - CVE-2025-37997: netfilter: ipset: fix region locking in hash types (bsc#1243832).
    - CVE-2025-38000: sch_hfsc: Fix qlen accounting bug when using peek in hfsc_enqueue() (bsc#1244277).
    - CVE-2025-38001: net_sched: hfsc: Address reentrant enqueue adding class to eltree twice (bsc#1244234).
    - CVE-2025-38014: dmaengine: idxd: Refactor remove call with idxd_cleanup() helper (bsc#1244732).
    - CVE-2025-38083: net_sched: prio: fix a race in prio_tune() (bsc#1245183).


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

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

The remote SUSE Linux SLES15 / SLES_SAP15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2025:02308-1 advisory.

    The SUSE Linux Enterprise 15 SP3 kernel was updated to receive various security bugfixes.


    The following security bugs were fixed:

    - CVE-2022-50085: dm raid: fix address sanitizer warning in raid_resume (bsc#1245147).
    - CVE-2022-50087: firmware: arm_scpi: Ensure scpi_info is not assigned if the probe fails (bsc#1245119).
    - CVE-2022-50200: selinux: Add boundary check in put_entry() (bsc#1245149).
    - CVE-2024-26924: scsi: lpfc: Release hbalock before calling lpfc_worker_wake_up() (bsc#1225820).
    - CVE-2024-27397: kabi: place tstamp needed for nftables set in a hole (bsc#1224095).
    - CVE-2024-36978: net: sched: sch_multiq: fix possible OOB write in multiq_tune() (bsc#1226514).
    - CVE-2024-46800: sch/netem: fix use after free in netem_dequeue (bsc#1230827).
    - CVE-2024-53141: netfilter: ipset: add missing range check in bitmap_ip_uadt (bsc#1234381).
    - CVE-2024-56770: sch/netem: fix use after free in netem_dequeue (bsc#1235637).
    - CVE-2025-21700: net: sched: Disallow replacing of child qdisc from one parent to another (bsc#1237159).
    - CVE-2025-21702: pfifo_tail_enqueue: Drop new packet when sch->limit == 0 (bsc#1237312).
    - CVE-2025-21703: netem: Update sch->q.qlen before qdisc_tree_reduce_backlog() (bsc#1237313).
    - CVE-2025-37752: net_sched: sch_sfq: move the limit validation (bsc#1242504).
    - CVE-2025-37823: net_sched: hfsc: Fix a potential UAF in hfsc_dequeue() too (bsc#1242924).
    - CVE-2025-37890: net_sched: hfsc: Fix a UAF vulnerability in class with netem as child qdisc     (bsc#1243330).
    - CVE-2025-37997: netfilter: ipset: fix region locking in hash types (bsc#1243832).
    - CVE-2025-38000: sch_hfsc: Fix qlen accounting bug when using peek in hfsc_enqueue() (bsc#1244277).
    - CVE-2025-38001: net_sched: hfsc: Address reentrant enqueue adding class to eltree twice (bsc#1244234).
    - CVE-2025-38083: net_sched: prio: fix a race in prio_tune() (bsc#1245183).


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

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

The remote SUSE Linux SLES15 / SLES_SAP15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2025:02264-1 advisory.

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


    The following security bugs were fixed:

    - CVE-2021-47557: net/sched: sch_ets: do not peek at classes beyond 'nbands' (bsc#1207361 bsc#1225468).
    - CVE-2021-47595: net/sched: sch_ets: do not remove idle classes from the round-robin list (bsc#1207361     bsc#1226552).
    - CVE-2023-52924: netfilter: nf_tables: do not skip expired elements during walk (bsc#1236821).
    - CVE-2023-52925: netfilter: nf_tables: do not fail inserts if duplicate has expired (bsc#1236822).
    - CVE-2024-26808: netfilter: nft_chain_filter: handle NETDEV_UNREGISTER for inet/ingress basechain     (bsc#1222634).
    - CVE-2024-26924: scsi: lpfc: Release hbalock before calling lpfc_worker_wake_up() (bsc#1225820).
    - CVE-2024-27397: kabi: place tstamp needed for nftables set in a hole (bsc#1224095).
    - CVE-2024-36978: net: sched: sch_multiq: fix possible OOB write in multiq_tune() (bsc#1226514).
    - CVE-2024-46800: sch/netem: fix use after free in netem_dequeue (bsc#1230827).
    - CVE-2024-53125: bpf: sync_linked_regs() must preserve subreg_def (bsc#1234156).
    - CVE-2024-53141: netfilter: ipset: add missing range check in bitmap_ip_uadt (bsc#1234381).
    - CVE-2024-53197: ALSA: usb-audio: Fix potential out-of-bound accesses for Extigy and Mbox devices     (bsc#1235464).
    - CVE-2024-56770: sch/netem: fix use after free in netem_dequeue (bsc#1235637).
    - CVE-2025-21700: net: sched: Disallow replacing of child qdisc from one parent to another (bsc#1237159).
    - CVE-2025-21702: pfifo_tail_enqueue: Drop new packet when sch->limit == 0 (bsc#1237312).
    - CVE-2025-21703: netem: Update sch->q.qlen before qdisc_tree_reduce_backlog() (bsc#1237313).
    - CVE-2025-21756: vsock: Orphan socket after transport release (bsc#1238876).
    - CVE-2025-23141: KVM: x86: Acquire SRCU in KVM_GET_MP_STATE to protect guest memory accesses     (bsc#1242782).
    - CVE-2025-37752: net_sched: sch_sfq: move the limit validation (bsc#1242504).
    - CVE-2025-37823: net_sched: hfsc: Fix a potential UAF in hfsc_dequeue() too (bsc#1242924).
    - CVE-2025-37890: net_sched: hfsc: Fix a UAF vulnerability in class with netem as child qdisc     (bsc#1243330).
    - CVE-2025-37997: netfilter: ipset: fix region locking in hash types (bsc#1243832).
    - CVE-2025-38000: sch_hfsc: Fix qlen accounting bug when using peek in hfsc_enqueue() (bsc#1244277).
    - CVE-2025-38001: net_sched: hfsc: Address reentrant enqueue adding class to eltree twice (bsc#1244234).
    - CVE-2025-38014: dmaengine: idxd: Refactor remove call with idxd_cleanup() helper (bsc#1244732).
    - CVE-2025-38060: bpf: abort verification if env->cur_state->loop_entry != NULL (bsc#1245155).
    - CVE-2025-38083: net_sched: prio: fix a race in prio_tune() (bsc#1245183).


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 version of kernel installed on the remote host is prior to 5.10.144-127.601. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2KERNEL-5.10-2022-020 advisory.

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

    i2c: Fix a potential use after free

    Free the adap structure only after we are done using it.This patch just moves the put_device() down a bit     to avoid theuse after free.

    [wsa: added comment to the code, added Fixes tag] (CVE-2019-25162)

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

    tun: avoid double free in tun_free_netdev (CVE-2021-47082)

    A use-after-free flaw was found in the Linux kernel's Atheros wireless adapter driver in the way a user     forces the ath9k_htc_wait_for_target function to fail with some input messages. This flaw allows a local     user to crash or potentially escalate their privileges on the system. (CVE-2022-1679)

    A flaw was found in the Linux kernel's KVM when attempting to set a SynIC IRQ. This issue makes it     possible for a misbehaving VMM to write to SYNIC/STIMER MSRs, causing a NULL pointer dereference. This     flaw allows an unprivileged local attacker on the host to issue specific ioctl calls, causing a kernel     oops condition that results in a denial of service. (CVE-2022-2153)

    A use-after-free flaw was found in the Linux kernel's POSIX CPU timers functionality in the way a user     creates and then deletes the timer in the non-leader thread of the program. This flaw allows a local user     to crash or potentially escalate their privileges on the system. (CVE-2022-2585)

    It was discovered that a nft object or expression could reference a nft set on a different nft table,     leading to a use-after-free once that table was deleted. (CVE-2022-2586)

    A use-after-free flaw was found in route4_change in the net/sched/cls_route.c filter implementation in the     Linux kernel. This flaw allows a local user to crash the system and possibly lead to a local privilege     escalation problem. (CVE-2022-2588)

    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)

    An issue was found in the Linux kernel in nf_conntrack_irc where the message handling can be confused and     incorrectly matches the message. A firewall may be able to be bypassed when users are using unencrypted     IRC with nf_conntrack_irc configured. (CVE-2022-2663)

    An out-of-bounds memory read flaw was found in the Linux kernel's BPF subsystem in how a user calls the     bpf_tail_call function with a key larger than the max_entries of the map. This flaw allows a local user to     gain unauthorized access to data. (CVE-2022-2905)

    A race condition was found in the Linux kernel's IP framework for transforming packets (XFRM subsystem)     when multiple calls to xfrm_probe_algs occurred simultaneously. This flaw could allow a local attacker to     potentially trigger an out-of-bounds write or leak kernel heap memory by performing an out-of-bounds read     and copying it into a socket. (CVE-2022-3028)

    A use-after-free flaw was found in io_uring in the Linux kernel. This flaw allows a local user to trigger     the issue if a signalfd or binder fd is polled with the io_uring poll due to a lack of io_uring POLLFREE     handling. (CVE-2022-3176)

    A vulnerability was found in Linux Kernel. It has been classified as critical. This affects the function     devlink_param_set/devlink_param_get of the file net/core/devlink.c of the component IPsec. The     manipulation leads to use after free. It is recommended to apply a patch to fix this issue. The identifier     VDB-211929 was assigned to this vulnerability. (CVE-2022-3625)

    An issue was discovered in include/asm-generic/tlb.h in the Linux kernel before 5.19. Because of a race     condition (unmap_mapping_range versus munmap), a device driver can free a page while it still has stale     TLB entries. This only occurs in situations with VM_PFNMAP VMAs. (CVE-2022-39188)

    An issue was discovered in net/netfilter/nf_tables_api.c in the Linux kernel before 5.19.6. A denial of     service can occur upon binding to an already bound chain. (CVE-2022-39190)

    A race condition in the Linux kernel's EFI capsule loader driver was found in the way it handled write and     flush operations on the device node of the EFI capsule. A local user could potentially use this flaw to     crash the system. (CVE-2022-40307)

    mm/mremap.c in the Linux kernel before 5.13.3 has a use-after-free via a stale TLB because an rmap lock is     not held during a PUD move. (CVE-2022-41222)

    A double-free flaw was found in the Linux kernel's TUN/TAP device driver functionality in how a user     registers the device when the register_netdevice function fails (NETDEV_REGISTER notifier). This flaw     allows a local user to crash or potentially escalate their privileges on the system. (CVE-2022-4744)

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

    IB/core: Fix a nested dead lock as part of ODP flow (CVE-2022-48675)

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

    nvme-tcp: fix UAF when detecting digest errors (CVE-2022-48686)

    In the Linux kernel, the following vulnerability has been resolved: ipv6: sr: fix out-of-bounds read when     setting HMAC data. The SRv6 layer allows defining HMAC data that can later be used to sign IPv6 Segment     Routing Headers. This configuration is realised via netlink through four attributes: SEG6_ATTR_HMACKEYID,     SEG6_ATTR_SECRET, SEG6_ATTR_SECRETLEN and SEG6_ATTR_ALGID. (CVE-2022-48687)

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

    i40e: Fix kernel crash during module removal (CVE-2022-48688)

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

    netfilter: nf_tables: clean up hook list when offload flags check fails (CVE-2022-48691)

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

    scsi: mpt3sas: Fix use-after-free warning (CVE-2022-48695)

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

    nvmet: fix a use-after-free (CVE-2022-48697)

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

    drm/radeon: add a force flush to delay work when radeon (CVE-2022-48704)

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

    sched/fair: Fix fault in reweight_entity (CVE-2022-48921)

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

    tcp: Fix data-races around sysctl_tcp_l3mdev_accept. (CVE-2022-49599)

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

    USB: core: Prevent nested device-reset calls (CVE-2022-49936)

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

    vt: Clear selection before changing the font (CVE-2022-49948)

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

    net/sched: fix netdevice reference leaks in attach_default_qdiscs() (CVE-2022-49958)

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

    arm64: cacheinfo: Fix incorrect assignment of signed error value to unsigned fw_level (CVE-2022-49964)

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

    bpf: Don't redirect packets with invalid pkt_len (CVE-2022-49975)

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

    ftrace: Fix NULL pointer dereference in is_ftrace_trampoline when ftrace is dead (CVE-2022-49977)

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

    net: fix refcount bug in sk_psock_get (2) (CVE-2022-49979)

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

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

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

    HID: steam: Prevent NULL pointer dereference in steam_{recv,send}_report (CVE-2022-49984)

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

    bpf: Don't use tnum_range on array range checking for poke descriptors (CVE-2022-49985)

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

    scsi: storvsc: Remove WQ_MEM_RECLAIM from storvsc_error_wq (CVE-2022-49986)

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

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

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

    xen/privcmd: fix error exit of privcmd_ioctl_dm_op() (CVE-2022-49989)

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

    loop: Check for overflow while configuring loop (CVE-2022-49993)

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

    rxrpc: Fix locking in rxrpc's sendmsg (CVE-2022-49998)

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

    xfrm: policy: fix metadata dst->dev xmit null pointer dereference (CVE-2022-50004)

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

    NFSv4.2 fix problems with __nfs42_ssc_open (CVE-2022-50006)

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

    xfrm: fix refcount leak in __xfrm_policy_check() (CVE-2022-50007)

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

    kprobes: don't call disarm_kprobe() for disabled kprobes (CVE-2022-50008)

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

    drivers:md:fix a potential use-after-free bug (CVE-2022-50022)

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

    scsi: lpfc: Prevent buffer overflow crashes in debugfs with malformed user input (CVE-2022-50030)

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

    net: genl: fix error path memory leak in policy dumping (CVE-2022-50042)

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

    iavf: Fix adminq error handling (CVE-2022-50055)

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

    ceph: don't leak snap_rwsem in handle_cap_grant (CVE-2022-50059)

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

    virtio_net: fix memory leak inside XPD_TX with mergeable (CVE-2022-50065)

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

    NFSv4/pnfs: Fix a use-after-free bug in open (CVE-2022-50072)

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

    ext4: fix warning in ext4_iomap_begin as race between bmap and write (CVE-2022-50082)

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

    ext4: add EXT4_INODE_HAS_XATTR_SPACE macro in xattr.h (CVE-2022-50083)

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

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

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

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

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

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

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

    dm thin: fix use-after-free crash in dm_sm_register_threshold_callback (CVE-2022-50092)

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

    iommu/vt-d: avoid invalid memory access via node_online(NUMA_NO_NODE) (CVE-2022-50093)

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

    posix-cpu-timers: Cleanup CPU timers before freeing them during exec (CVE-2022-50095)

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

    video: fbdev: s3fb: Check the size of screen before memset_io() (CVE-2022-50097)

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

    sched, cpuset: Fix dl_cpu_busy() panic due to empty cs->cpus_allowed (CVE-2022-50103)

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

    jbd2: fix assertion 'jh->b_frozen_data == NULL' failure when journal aborted (CVE-2022-50126)

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

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

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

    RDMA/srpt: Fix a use-after-free (CVE-2022-50129)

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

    RDMA/qedr: Fix potential memory leak in __qedr_alloc_mr() (CVE-2022-50138)

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

    driver core: fix potential deadlock in __driver_attach (CVE-2022-50149)

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

    usb: host: Fix refcount leak in ehci_hcd_ppc_of_probe (CVE-2022-50153)

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

    virtio-gpu: fix a missing check to avoid NULL dereference (CVE-2022-50181)

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

    drm/radeon: fix potential buffer overflow in ni_set_mc_special_registers() (CVE-2022-50185)

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

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

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

    selinux: Add boundary check in put_entry() (CVE-2022-50200)

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

    PM: hibernate: defer device probing when resuming from hibernation (CVE-2022-50202)

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

    ext2: Add more validity checks for inode counts (CVE-2022-50205)

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

    arm64: fix oops in concurrently setting insn_emulation sysctls (CVE-2022-50206)

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

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

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

    netfilter: nf_tables: do not allow CHAIN_ID to refer to another table (CVE-2022-50212)

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

    netfilter: nf_tables: do not allow SET_ID to refer to another table (CVE-2022-50213)

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

    scsi: sg: Allow waiting for commands to complete on removed device (CVE-2022-50215)

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

    bpf: Fix KASAN use-after-free Read in compute_effective_progs (CVE-2022-50219)

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

    usbnet: Fix linkwatch use-after-free on disconnect (CVE-2022-50220)

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

    tty: vt: initialize unicode screen buffer (CVE-2022-50222)

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

    KVM: SVM: Don't BUG if userspace injects an interrupt with GIF=0 (CVE-2022-50228)

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

    crypto: arm64/poly1305 - fix a read out-of-bound (CVE-2022-50231)

    In nf_tables_updtable, if nf_tables_table_enable returns an error, nft_trans_destroy is called to free the     transaction object. nft_trans_destroy() calls list_del(), but the transaction was never placed on a list
    -- the list head is all zeroes, this results in a NULL pointer dereference. (CVE-2023-1095)

    The upstream advisory describes this issue as follows:

    This vulnerability allows local attackers to disclose sensitive information on affected installations of     the Linux Kernel. An attacker must first obtain the ability to execute high-privileged code on the target     system in order to exploit this vulnerability.

    The specific flaw exists within the processing of seg6 attributes. The issue results from the lack of     proper validation of user-supplied data, which can result in a read past the end of an allocated buffer.
    An attacker can leverage this in conjunction with other vulnerabilties to escalate privileges and execute     arbitrary code in the context of the kernel. (CVE-2023-2860)

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
360902	Rocky Linux 9.6 [TuxCare] Security Update: kernel / kernel-abi-stablelists / kernel-core / etc Multiple Vulnerabilities (ALMALINUX9.6:CLSA-2026:1788168285)	Nessus	Rocky Linux Local Security Checks	Local	high
360768	AlmaLinux 9.6 [TuxCare] Security Update: kernel / kernel-abi-stablelists / kernel-core / etc Multiple Vulnerabilities (ALMALINUX9.6:CLSA-2026:1788168285)	Nessus	Alma Linux Local Security Checks	Local	high
352031	AlmaLinux 9.2 [TuxCare] Security Update: bpftool / kernel / kernel-64k / kernel-64k-core / kernel-64k-debug / etc Multiple Vulnerabilities (ALMALINUX9.2:CLSA-2026:1786761805)	Nessus	Alma Linux Local Security Checks	Local	critical
281388	Unity Linux 20.1060a / 20.1070a Security Update: kernel (UTSA-2025-993035)	Nessus	Unity Linux Local Security Checks	Local	high
280270	Unity Linux 20.1060e / 20.1070e Security Update: kernel (UTSA-2025-992378)	Nessus	Unity Linux Local Security Checks	Local	high
279319	EulerOS Virtualization 2.13.0 : kernel (EulerOS-SA-2025-2581)	Nessus	Huawei Local Security Checks	Local	high
279287	EulerOS Virtualization 2.13.1 : kernel (EulerOS-SA-2025-2546)	Nessus	Huawei Local Security Checks	Local	high
271309	EulerOS 2.0 SP13 : kernel (EulerOS-SA-2025-2264)	Nessus	Huawei Local Security Checks	Local	high
271298	EulerOS 2.0 SP13 : kernel (EulerOS-SA-2025-2296)	Nessus	Huawei Local Security Checks	Local	high
244276	Linux Distros Unpatched Vulnerability : CVE-2022-50231	Nessus	Misc.	Local	high
242951	SUSE SLES15: cluster-md-kmp-default / dlm-kmp-default / gfs2-kmp-default / etc (SUSE-SU-2025:02537-1)	Nessus	SuSE Local Security Checks	Local	high
242100	SUSE SLES15: cluster-md-kmp-default / dlm-kmp-default / gfs2-kmp-default / etc (SUSE-SU-2025:02308-1)	Nessus	SuSE Local Security Checks	Local	high
241963	SUSE SLES15 : Security update for the Linux Kernel (SUSE-SU-2025:02264-1)	Nessus	SuSE Local Security Checks	Local	high
166124	Amazon Linux 2 : kernel, --advisory ALAS2KERNEL-5.10-2022-020 (ALASKERNEL-5.10-2022-020)	Nessus	Amazon Linux Local Security Checks	Local	high
166118	Amazon Linux 2 : kernel, --advisory ALAS2KERNEL-5.15-2022-008 (ALASKERNEL-5.15-2022-008)	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-50231

high

Tenable Plugins

high

high

critical

high

high

high

high

high

high

high

high

high

high

high

high

high