In the Linux kernel, the following vulnerability has been resolved: can: isotp: sanitize CAN ID checks in isotp_bind() Syzbot created an environment that lead to a state machine status that can not be reached with a compliant CAN ID address configuration. The provided address information consisted of CAN ID 0x6000001 and 0xC28001 which both boil down to 11 bit CAN IDs 0x001 in sending and receiving. Sanitize the SFF/EFF CAN ID values before performing the address checks.

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

  - In the Linux kernel, the following vulnerability has been resolved: net: bcmgenet: Use stronger register     read/writes to assure ordering GCC12 appears to be much smarter about its dependency tracking and is aware     that the relaxed variants are just normal loads and stores and this is causing problems like: [     210.074549] ------------[ cut here ]------------ [ 210.079223] NETDEV WATCHDOG: enabcm6e4ei0 (bcmgenet):
    transmit queue 1 timed out [ 210.086717] WARNING: CPU: 1 PID: 0 at net/sched/sch_generic.c:529     dev_watchdog+0x234/0x240 [ 210.095044] Modules linked in: genet(E) nft_fib_inet nft_fib_ipv4 nft_fib_ipv6     nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat] [ 210.146561] ACPI     CPPC: PCC check channel failed for ss: 0. ret=-110 [ 210.146927] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G     E 5.17.0-rc7G12+ #58 [ 210.153226] CPPC Cpufreq:cppc_scale_freq_workfn: failed to read perf counters [     210.161349] Hardware name: Raspberry Pi Foundation Raspberry Pi 4 Model B/Raspberry Pi 4 Model B, BIOS     EDK2-DEV 02/08/2022 [ 210.161353] pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [     210.161358] pc : dev_watchdog+0x234/0x240 [ 210.161364] lr : dev_watchdog+0x234/0x240 [ 210.161368] sp :
    ffff8000080a3a40 [ 210.161370] x29: ffff8000080a3a40 x28: ffffcd425af87000 x27: ffff8000080a3b20 [     210.205150] x26: ffffcd425aa00000 x25: 0000000000000001 x24: ffffcd425af8ec08 [ 210.212321] x23:
    0000000000000100 x22: ffffcd425af87000 x21: ffff55b142688000 [ 210.219491] x20: 0000000000000001 x19:
    ffff55b1426884c8 x18: ffffffffffffffff [ 210.226661] x17: 64656d6974203120 x16: 0000000000000001 x15:
    6d736e617274203a [ 210.233831] x14: 2974656e65676d63 x13: ffffcd4259c300d8 x12: ffffcd425b07d5f0 [     210.241001] x11: 00000000ffffffff x10: ffffcd425b07d5f0 x9 : ffffcd4258bdad9c [ 210.248171] x8 :
    00000000ffffdfff x7 : 000000000000003f x6 : 0000000000000000 [ 210.255341] x5 : 0000000000000000 x4 :
    0000000000000000 x3 : 0000000000001000 [ 210.262511] x2 : 0000000000001000 x1 : 0000000000000005 x0 :
    0000000000000044 [ 210.269682] Call trace: [ 210.272133] dev_watchdog+0x234/0x240 [ 210.275811]     call_timer_fn+0x3c/0x15c [ 210.279489] __run_timers.part.0+0x288/0x310 [ 210.283777]     run_timer_softirq+0x48/0x80 [ 210.287716] __do_softirq+0x128/0x360 [ 210.291392]
    __irq_exit_rcu+0x138/0x140 [ 210.295243] irq_exit_rcu+0x1c/0x30 [ 210.298745] el1_interrupt+0x38/0x54 [     210.302334] el1h_64_irq_handler+0x18/0x24 [ 210.306445] el1h_64_irq+0x7c/0x80 [ 210.309857]     arch_cpu_idle+0x18/0x2c [ 210.313445] default_idle_call+0x4c/0x140 [ 210.317470]     cpuidle_idle_call+0x14c/0x1a0 [ 210.321584] do_idle+0xb0/0x100 [ 210.324737] cpu_startup_entry+0x30/0x8c [     210.328675] secondary_start_kernel+0xe4/0x110 [ 210.333138] __secondary_switched+0x94/0x98 The assumption     when these were relaxed seems to be that device memory would be mapped non reordering, and that other     constructs (spinlocks/etc) would provide the barriers to assure that packet data and in memory     rings/queues were ordered with respect to device register reads/writes. This itself seems a bit sketchy,     but the real problem with GCC12 is that it is moving the actual reads/writes around at will as though they     were independent operations when in truth they are not, but the compiler can't know that. When looking at     the assembly dumps for many of these routines its possible to see very clean, but not strictly in program     order operations occurring as the compiler would be free to do if these weren't actually register     reads/write operations. Its possible to suppress the timeout with a liberal bit of dma_mb()'s sprinkled     around but the device still seems unable to reliably send/receive data. A better plan is to use the safer     readl/writel everywhere. Since this partially reverts an older commit, which notes the use of the relaxed     variants for performance reasons. I would suggest that any performance problems ---truncated---     (CVE-2022-49194)

  - In the Linux kernel, the following vulnerability has been resolved: can: isotp: sanitize CAN ID checks in     isotp_bind() Syzbot created an environment that lead to a state machine status that can not be reached     with a compliant CAN ID address configuration. The provided address information consisted of CAN ID     0x6000001 and 0xC28001 which both boil down to 11 bit CAN IDs 0x001 in sending and receiving. Sanitize the     SFF/EFF CAN ID values before performing the address checks. (CVE-2022-49269)

  - In the Linux kernel, the following vulnerability has been resolved: net/smc: Reset connection when trying     to use SMCRv2 fails. We found a crash when using SMCRv2 with 2 Mellanox ConnectX-4. It can be reproduced     by: - smc_run nginx - smc_run wrk -t 32 -c 500 -d 30 http://<ip>:<port> BUG: kernel NULL pointer     dereference, address: 0000000000000014 #PF: supervisor read access in kernel mode #PF: error_code(0x0000)
    - not-present page PGD 8000000108713067 P4D 8000000108713067 PUD 151127067 PMD 0 Oops: 0000 [#1] PREEMPT     SMP PTI CPU: 4 PID: 2441 Comm: kworker/4:249 Kdump: loaded Tainted: G W E 6.4.0-rc1+ #42 Workqueue:
    smc_hs_wq smc_listen_work [smc] RIP: 0010:smc_clc_send_confirm_accept+0x284/0x580 [smc] RSP:
    0018:ffffb8294b2d7c78 EFLAGS: 00010a06 RAX: ffff8f1873238880 RBX: ffffb8294b2d7dc8 RCX: 0000000000000000     RDX: 00000000000000b4 RSI: 0000000000000001 RDI: 0000000000b40c00 RBP: ffffb8294b2d7db8 R08:
    ffff8f1815c5860c R09: 0000000000000000 R10: 0000000000000400 R11: 0000000000000000 R12: ffff8f1846f56180     R13: ffff8f1815c5860c R14: 0000000000000001 R15: 0000000000000001 FS: 0000000000000000(0000)     GS:ffff8f1aefd00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2:
    0000000000000014 CR3: 00000001027a0001 CR4: 00000000003706e0 DR0: 0000000000000000 DR1: 0000000000000000     DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK>     ? mlx5_ib_map_mr_sg+0xa1/0xd0 [mlx5_ib] ? smcr_buf_map_link+0x24b/0x290 [smc] ?
    __smc_buf_create+0x4ee/0x9b0 [smc] smc_clc_send_accept+0x4c/0xb0 [smc] smc_listen_work+0x346/0x650 [smc] ?
    __schedule+0x279/0x820 process_one_work+0x1e5/0x3f0 worker_thread+0x4d/0x2f0 ?
    __pfx_worker_thread+0x10/0x10 kthread+0xe5/0x120 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x2c/0x50 </TASK>     During the CLC handshake, server sequentially tries available SMCRv2 and SMCRv1 devices in     smc_listen_work(). If an SMCRv2 device is found. SMCv2 based link group and link will be assigned to the     connection. Then assumed that some buffer assignment errors happen later in the CLC handshake, such as RMB     registration failure, server will give up SMCRv2 and try SMCRv1 device instead. But the resources assigned     to the connection won't be reset. When server tries SMCRv1 device, the connection creation process will be     executed again. Since conn->lnk has been assigned when trying SMCRv2, it will not be set to the correct     SMCRv1 link in smcr_lgr_conn_assign_link(). So in such situation, conn->lgr points to correct SMCRv1 link     group but conn->lnk points to the SMCRv2 link mistakenly. Then in smc_clc_send_confirm_accept(),     conn->rmb_desc->mr[link->link_idx] will be accessed. Since the link->link_idx is not correct, the related     MR may not have been initialized, so crash happens. | Try SMCRv2 device first | |-> conn->lgr: assign     existed SMCRv2 link group; | |-> conn->link: assign existed SMCRv2 link (link_idx may be 1 in     SMC_LGR_SYMMETRIC); | |-> sndbuf & RMB creation fails, quit; | | Try SMCRv1 device then | |-> conn->lgr:
    create SMCRv1 link group and assign; | |-> conn->link: keep SMCRv2 link mistakenly; | |-> sndbuf & RMB     creation succeed, only RMB->mr[link_idx = 0] | initialized. | | Then smc_clc_send_confirm_accept()     accesses | conn->rmb_desc->mr[conn->link->link_idx, which is 1], then crash. v This patch tries to fix     this by cleaning conn->lnk before assigning link. In addition, it is better to reset the connection and     clean the resources assigned if trying SMCRv2 failed in buffer creation or registration. (CVE-2023-53382)

  - In the Linux kernel, the following vulnerability has been resolved: RDMA/irdma: Cap MSIX used to online     CPUs + 1 The irdma driver can use a maximum number of msix vectors equal to num_online_cpus() + 1 and the     kernel warning stack below is shown if that number is exceeded. The kernel throws a warning as the driver     tries to update the affinity hint with a CPU mask greater than the max CPU IDs. Fix this by capping the     MSIX vectors to num_online_cpus() + 1. WARNING: CPU: 7 PID: 23655 at include/linux/cpumask.h:106     irdma_cfg_ceq_vector+0x34c/0x3f0 [irdma] RIP: 0010:irdma_cfg_ceq_vector+0x34c/0x3f0 [irdma] Call Trace:
    irdma_rt_init_hw+0xa62/0x1290 [irdma] ? irdma_alloc_local_mac_entry+0x1a0/0x1a0 [irdma] ?
    __is_kernel_percpu_address+0x63/0x310 ? rcu_read_lock_held_common+0xe/0xb0 ?     irdma_lan_unregister_qset+0x280/0x280 [irdma] ? irdma_request_reset+0x80/0x80 [irdma] ?     ice_get_qos_params+0x84/0x390 [ice] irdma_probe+0xa40/0xfc0 [irdma] ? rcu_read_lock_bh_held+0xd0/0xd0 ?     irdma_remove+0x140/0x140 [irdma] ? rcu_read_lock_sched_held+0x62/0xe0 ? down_write+0x187/0x3d0 ?     auxiliary_match_id+0xf0/0x1a0 ? irdma_remove+0x140/0x140 [irdma] auxiliary_bus_probe+0xa6/0x100
    __driver_probe_device+0x4a4/0xd50 ? __device_attach_driver+0x2c0/0x2c0 driver_probe_device+0x4a/0x110
    __driver_attach+0x1aa/0x350 bus_for_each_dev+0x11d/0x1b0 ? subsys_dev_iter_init+0xe0/0xe0     bus_add_driver+0x3b1/0x610 driver_register+0x18e/0x410 ? 0xffffffffc0b88000 irdma_init_module+0x50/0xaa     [irdma] do_one_initcall+0x103/0x5f0 ? perf_trace_initcall_level+0x420/0x420 ? do_init_module+0x4e/0x700 ?
    __kasan_kmalloc+0x7d/0xa0 ? kmem_cache_alloc_trace+0x188/0x2b0 ? kasan_unpoison+0x21/0x50     do_init_module+0x1d1/0x700 load_module+0x3867/0x5260 ? layout_and_allocate+0x3990/0x3990 ?     rcu_read_lock_held_common+0xe/0xb0 ? rcu_read_lock_sched_held+0x62/0xe0 ? rcu_read_lock_bh_held+0xd0/0xd0     ? __vmalloc_node_range+0x46b/0x890 ? lock_release+0x5c8/0xba0 ? alloc_vm_area+0x120/0x120 ?     selinux_kernel_module_from_file+0x2a5/0x300 ? __inode_security_revalidate+0xf0/0xf0 ?
    __do_sys_init_module+0x1db/0x260 __do_sys_init_module+0x1db/0x260 ? load_module+0x5260/0x5260 ?     do_syscall_64+0x22/0x450 do_syscall_64+0xa5/0x450 entry_SYSCALL_64_after_hwframe+0x66/0xdb     (CVE-2023-53811)

  - In the Linux kernel, the following vulnerability has been resolved: i2c: smbus: fix NULL function pointer     dereference Baruch reported an OOPS when using the designware controller as target only. Target-only modes     break the assumption of one transfer function always being available. Fix this by always checking the     pointer in __i2c_transfer. [wsa: dropped the simplification in core-smbus to avoid theoretical     regressions] (CVE-2024-35984)

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

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

  - In the Linux kernel, the following vulnerability has been resolved: net: bcmgenet: Use stronger register     read/writes to assure ordering GCC12 appears to be much smarter about its dependency tracking and is aware     that the relaxed variants are just normal loads and stores and this is causing problems like: [     210.074549] ------------[ cut here ]------------ [ 210.079223] NETDEV WATCHDOG: enabcm6e4ei0 (bcmgenet):
    transmit queue 1 timed out [ 210.086717] WARNING: CPU: 1 PID: 0 at net/sched/sch_generic.c:529     dev_watchdog+0x234/0x240 [ 210.095044] Modules linked in: genet(E) nft_fib_inet nft_fib_ipv4 nft_fib_ipv6     nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat] [ 210.146561] ACPI     CPPC: PCC check channel failed for ss: 0. ret=-110 [ 210.146927] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G     E 5.17.0-rc7G12+ #58 [ 210.153226] CPPC Cpufreq:cppc_scale_freq_workfn: failed to read perf counters [     210.161349] Hardware name: Raspberry Pi Foundation Raspberry Pi 4 Model B/Raspberry Pi 4 Model B, BIOS     EDK2-DEV 02/08/2022 [ 210.161353] pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [     210.161358] pc : dev_watchdog+0x234/0x240 [ 210.161364] lr : dev_watchdog+0x234/0x240 [ 210.161368] sp :
    ffff8000080a3a40 [ 210.161370] x29: ffff8000080a3a40 x28: ffffcd425af87000 x27: ffff8000080a3b20 [     210.205150] x26: ffffcd425aa00000 x25: 0000000000000001 x24: ffffcd425af8ec08 [ 210.212321] x23:
    0000000000000100 x22: ffffcd425af87000 x21: ffff55b142688000 [ 210.219491] x20: 0000000000000001 x19:
    ffff55b1426884c8 x18: ffffffffffffffff [ 210.226661] x17: 64656d6974203120 x16: 0000000000000001 x15:
    6d736e617274203a [ 210.233831] x14: 2974656e65676d63 x13: ffffcd4259c300d8 x12: ffffcd425b07d5f0 [     210.241001] x11: 00000000ffffffff x10: ffffcd425b07d5f0 x9 : ffffcd4258bdad9c [ 210.248171] x8 :
    00000000ffffdfff x7 : 000000000000003f x6 : 0000000000000000 [ 210.255341] x5 : 0000000000000000 x4 :
    0000000000000000 x3 : 0000000000001000 [ 210.262511] x2 : 0000000000001000 x1 : 0000000000000005 x0 :
    0000000000000044 [ 210.269682] Call trace: [ 210.272133] dev_watchdog+0x234/0x240 [ 210.275811]     call_timer_fn+0x3c/0x15c [ 210.279489] __run_timers.part.0+0x288/0x310 [ 210.283777]     run_timer_softirq+0x48/0x80 [ 210.287716] __do_softirq+0x128/0x360 [ 210.291392]
    __irq_exit_rcu+0x138/0x140 [ 210.295243] irq_exit_rcu+0x1c/0x30 [ 210.298745] el1_interrupt+0x38/0x54 [     210.302334] el1h_64_irq_handler+0x18/0x24 [ 210.306445] el1h_64_irq+0x7c/0x80 [ 210.309857]     arch_cpu_idle+0x18/0x2c [ 210.313445] default_idle_call+0x4c/0x140 [ 210.317470]     cpuidle_idle_call+0x14c/0x1a0 [ 210.321584] do_idle+0xb0/0x100 [ 210.324737] cpu_startup_entry+0x30/0x8c [     210.328675] secondary_start_kernel+0xe4/0x110 [ 210.333138] __secondary_switched+0x94/0x98 The assumption     when these were relaxed seems to be that device memory would be mapped non reordering, and that other     constructs (spinlocks/etc) would provide the barriers to assure that packet data and in memory     rings/queues were ordered with respect to device register reads/writes. This itself seems a bit sketchy,     but the real problem with GCC12 is that it is moving the actual reads/writes around at will as though they     were independent operations when in truth they are not, but the compiler can't know that. When looking at     the assembly dumps for many of these routines its possible to see very clean, but not strictly in program     order operations occurring as the compiler would be free to do if these weren't actually register     reads/write operations. Its possible to suppress the timeout with a liberal bit of dma_mb()'s sprinkled     around but the device still seems unable to reliably send/receive data. A better plan is to use the safer     readl/writel everywhere. Since this partially reverts an older commit, which notes the use of the relaxed     variants for performance reasons. I would suggest that any performance problems ---truncated---     (CVE-2022-49194)

  - In the Linux kernel, the following vulnerability has been resolved: can: isotp: sanitize CAN ID checks in     isotp_bind() Syzbot created an environment that lead to a state machine status that can not be reached     with a compliant CAN ID address configuration. The provided address information consisted of CAN ID     0x6000001 and 0xC28001 which both boil down to 11 bit CAN IDs 0x001 in sending and receiving. Sanitize the     SFF/EFF CAN ID values before performing the address checks. (CVE-2022-49269)

  - In the Linux kernel, the following vulnerability has been resolved: net/smc: Reset connection when trying     to use SMCRv2 fails. We found a crash when using SMCRv2 with 2 Mellanox ConnectX-4. It can be reproduced     by: - smc_run nginx - smc_run wrk -t 32 -c 500 -d 30 http://<ip>:<port> BUG: kernel NULL pointer     dereference, address: 0000000000000014 #PF: supervisor read access in kernel mode #PF: error_code(0x0000)
    - not-present page PGD 8000000108713067 P4D 8000000108713067 PUD 151127067 PMD 0 Oops: 0000 [#1] PREEMPT     SMP PTI CPU: 4 PID: 2441 Comm: kworker/4:249 Kdump: loaded Tainted: G W E 6.4.0-rc1+ #42 Workqueue:
    smc_hs_wq smc_listen_work [smc] RIP: 0010:smc_clc_send_confirm_accept+0x284/0x580 [smc] RSP:
    0018:ffffb8294b2d7c78 EFLAGS: 00010a06 RAX: ffff8f1873238880 RBX: ffffb8294b2d7dc8 RCX: 0000000000000000     RDX: 00000000000000b4 RSI: 0000000000000001 RDI: 0000000000b40c00 RBP: ffffb8294b2d7db8 R08:
    ffff8f1815c5860c R09: 0000000000000000 R10: 0000000000000400 R11: 0000000000000000 R12: ffff8f1846f56180     R13: ffff8f1815c5860c R14: 0000000000000001 R15: 0000000000000001 FS: 0000000000000000(0000)     GS:ffff8f1aefd00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2:
    0000000000000014 CR3: 00000001027a0001 CR4: 00000000003706e0 DR0: 0000000000000000 DR1: 0000000000000000     DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK>     ? mlx5_ib_map_mr_sg+0xa1/0xd0 [mlx5_ib] ? smcr_buf_map_link+0x24b/0x290 [smc] ?
    __smc_buf_create+0x4ee/0x9b0 [smc] smc_clc_send_accept+0x4c/0xb0 [smc] smc_listen_work+0x346/0x650 [smc] ?
    __schedule+0x279/0x820 process_one_work+0x1e5/0x3f0 worker_thread+0x4d/0x2f0 ?
    __pfx_worker_thread+0x10/0x10 kthread+0xe5/0x120 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x2c/0x50 </TASK>     During the CLC handshake, server sequentially tries available SMCRv2 and SMCRv1 devices in     smc_listen_work(). If an SMCRv2 device is found. SMCv2 based link group and link will be assigned to the     connection. Then assumed that some buffer assignment errors happen later in the CLC handshake, such as RMB     registration failure, server will give up SMCRv2 and try SMCRv1 device instead. But the resources assigned     to the connection won't be reset. When server tries SMCRv1 device, the connection creation process will be     executed again. Since conn->lnk has been assigned when trying SMCRv2, it will not be set to the correct     SMCRv1 link in smcr_lgr_conn_assign_link(). So in such situation, conn->lgr points to correct SMCRv1 link     group but conn->lnk points to the SMCRv2 link mistakenly. Then in smc_clc_send_confirm_accept(),     conn->rmb_desc->mr[link->link_idx] will be accessed. Since the link->link_idx is not correct, the related     MR may not have been initialized, so crash happens. | Try SMCRv2 device first | |-> conn->lgr: assign     existed SMCRv2 link group; | |-> conn->link: assign existed SMCRv2 link (link_idx may be 1 in     SMC_LGR_SYMMETRIC); | |-> sndbuf & RMB creation fails, quit; | | Try SMCRv1 device then | |-> conn->lgr:
    create SMCRv1 link group and assign; | |-> conn->link: keep SMCRv2 link mistakenly; | |-> sndbuf & RMB     creation succeed, only RMB->mr[link_idx = 0] | initialized. | | Then smc_clc_send_confirm_accept()     accesses | conn->rmb_desc->mr[conn->link->link_idx, which is 1], then crash. v This patch tries to fix     this by cleaning conn->lnk before assigning link. In addition, it is better to reset the connection and     clean the resources assigned if trying SMCRv2 failed in buffer creation or registration. (CVE-2023-53382)

  - In the Linux kernel, the following vulnerability has been resolved: RDMA/irdma: Cap MSIX used to online     CPUs + 1 The irdma driver can use a maximum number of msix vectors equal to num_online_cpus() + 1 and the     kernel warning stack below is shown if that number is exceeded. The kernel throws a warning as the driver     tries to update the affinity hint with a CPU mask greater than the max CPU IDs. Fix this by capping the     MSIX vectors to num_online_cpus() + 1. WARNING: CPU: 7 PID: 23655 at include/linux/cpumask.h:106     irdma_cfg_ceq_vector+0x34c/0x3f0 [irdma] RIP: 0010:irdma_cfg_ceq_vector+0x34c/0x3f0 [irdma] Call Trace:
    irdma_rt_init_hw+0xa62/0x1290 [irdma] ? irdma_alloc_local_mac_entry+0x1a0/0x1a0 [irdma] ?
    __is_kernel_percpu_address+0x63/0x310 ? rcu_read_lock_held_common+0xe/0xb0 ?     irdma_lan_unregister_qset+0x280/0x280 [irdma] ? irdma_request_reset+0x80/0x80 [irdma] ?     ice_get_qos_params+0x84/0x390 [ice] irdma_probe+0xa40/0xfc0 [irdma] ? rcu_read_lock_bh_held+0xd0/0xd0 ?     irdma_remove+0x140/0x140 [irdma] ? rcu_read_lock_sched_held+0x62/0xe0 ? down_write+0x187/0x3d0 ?     auxiliary_match_id+0xf0/0x1a0 ? irdma_remove+0x140/0x140 [irdma] auxiliary_bus_probe+0xa6/0x100
    __driver_probe_device+0x4a4/0xd50 ? __device_attach_driver+0x2c0/0x2c0 driver_probe_device+0x4a/0x110
    __driver_attach+0x1aa/0x350 bus_for_each_dev+0x11d/0x1b0 ? subsys_dev_iter_init+0xe0/0xe0     bus_add_driver+0x3b1/0x610 driver_register+0x18e/0x410 ? 0xffffffffc0b88000 irdma_init_module+0x50/0xaa     [irdma] do_one_initcall+0x103/0x5f0 ? perf_trace_initcall_level+0x420/0x420 ? do_init_module+0x4e/0x700 ?
    __kasan_kmalloc+0x7d/0xa0 ? kmem_cache_alloc_trace+0x188/0x2b0 ? kasan_unpoison+0x21/0x50     do_init_module+0x1d1/0x700 load_module+0x3867/0x5260 ? layout_and_allocate+0x3990/0x3990 ?     rcu_read_lock_held_common+0xe/0xb0 ? rcu_read_lock_sched_held+0x62/0xe0 ? rcu_read_lock_bh_held+0xd0/0xd0     ? __vmalloc_node_range+0x46b/0x890 ? lock_release+0x5c8/0xba0 ? alloc_vm_area+0x120/0x120 ?     selinux_kernel_module_from_file+0x2a5/0x300 ? __inode_security_revalidate+0xf0/0xf0 ?
    __do_sys_init_module+0x1db/0x260 __do_sys_init_module+0x1db/0x260 ? load_module+0x5260/0x5260 ?     do_syscall_64+0x22/0x450 do_syscall_64+0xa5/0x450 entry_SYSCALL_64_after_hwframe+0x66/0xdb     (CVE-2023-53811)

  - In the Linux kernel, the following vulnerability has been resolved: i2c: smbus: fix NULL function pointer     dereference Baruch reported an OOPS when using the designware controller as target only. Target-only modes     break the assumption of one transfer function always being available. Fix this by always checking the     pointer in __i2c_transfer. [wsa: dropped the simplification in core-smbus to avoid theoretical     regressions] (CVE-2024-35984)

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

The Rocky Linux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the CIQ crlsa-2025_20518 advisory.

    * kernel: can: isotp: fix potential CAN frame reception race in isotp_rcv() (CVE-2022-48830)

    * kernel: soc: qcom: cmd-db: Map shared memory as WC, not WB (CVE-2024-46689)

    * kernel: Squashfs: sanity check symbolic link size (CVE-2024-46744)

    * kernel: vfs: fix race between evice_inodes() and find_inode()&iput() (CVE-2024-47679)

    * kernel: x86/tdx: Fix in-kernel MMIO check (CVE-2024-47727)

    * kernel: rxrpc: Fix a race between socket set up and I/O thread creation (CVE-2024-49864)

    * kernel: io_uring: check if we need to reschedule during overflow flush (CVE-2024-50060)

    * kernel: can: m_can: pci: add missing m_can_class_free_dev() in probe/remove methods (CVE-2022-49024)

    * kernel: posix-clock: Fix missing timespec64 check in pc_clock_settime() (CVE-2024-50195)

    * kernel: rxrpc: Fix missing locking causing hanging calls (CVE-2024-50294)

    * kernel: io_uring/rw: fix missing NOWAIT check for O_DIRECT start write (CVE-2024-53052)

    * kernel: afs: Fix lock recursion (CVE-2024-53090)

    * kernel: virtio/vsock: Fix accept_queue memory leak (CVE-2024-53119)

    * kernel: KVM: VMX: Bury Intel PT virtualization (guest/host mode) behind CONFIG_BROKEN (CVE-2024-53135)

    * kernel: xen: Xen hypercall page unsafe against speculative attacks (Xen Security Advisory 466)     (CVE-2024-53241)

    * kernel: RDMA/rxe: Fix the qp flush warnings in req (CVE-2024-53229)

    * kernel: block: fix uaf for flush rq while iterating tags (CVE-2024-53170)

    * kernel: nfsd: release svc_expkey/svc_export with rcu_work (CVE-2024-53216)

    * kernel: net: af_can: do not leave a dangling sk pointer in can_create() (CVE-2024-56603)

    * kernel: blk-cgroup: Fix UAF in blkcg_unpin_online() (CVE-2024-56672)

    * kernel: acpi: nfit: vmalloc-out-of-bounds Read in acpi_nfit_ctl (CVE-2024-56662)

    * kernel: bpf: Fix UAF via mismatching bpf_prog/attachment RCU flavors (CVE-2024-56675)

    * kernel: can: j1939: j1939_session_new(): fix skb reference counting (CVE-2024-56645)

    * kernel: crypto: pcrypt - Call crypto layer directly when padata_do_parallel() return -EBUSY     (CVE-2024-56690)

    * kernel: io_uring: check if iowq is killed before queuing (CVE-2024-56709)

    * kernel: rtc: check if __rtc_read_time was successful in rtc_timer_do_work() (CVE-2024-56739)

    * kernel: bpf: put bpf_link's program when link is safe to be deallocated (CVE-2024-56786)

    * kernel: igb: Fix potential invalid memory access in igb_init_module() (CVE-2024-52332)

    * kernel: ipvs: fix UB due to uninitialized stack access in ip_vs_protocol_init() (CVE-2024-53680)

    * kernel: netfilter: conntrack: clamp maximum hashtable size to INT_MAX (CVE-2025-21648)

    * kernel: sched: sch_cake: add bounds checks to host bulk flow fairness counts (CVE-2025-21647)

    * kernel: block, bfq: fix waker_bfqq UAF after bfq_split_bfqq() (CVE-2025-21631)

    * kernel: zram: fix potential UAF of zram table (CVE-2025-21671)

    * kernel: afs: Fix merge preference rule failure condition (CVE-2025-21672)

    * kernel: mm: zswap: properly synchronize freeing resources during CPU hotunplug (CVE-2025-21693)

    * kernel: cachestat: fix page cache statistics permission checking (CVE-2025-21691)

    * kernel: mm: clear uffd-wp PTE/PMD state on mremap() (CVE-2025-21696)

    * kernel: pfifo_tail_enqueue: Drop new packet when sch->limit == 0 (CVE-2025-21702)

    * kernel: usbnet: fix memory leak in error case (CVE-2022-49657)

    * kernel: powerpc/xics: fix refcount leak in icp_opal_init() (CVE-2022-49432)

    * kernel: net: tun: unlink NAPI from device on destruction (CVE-2022-49672)

    * kernel: powerpc/papr_scm: don't requests stats with '0' sized stats buffer (CVE-2022-49353)

    * kernel: powerpc/xive: Fix refcount leak in xive_spapr_init (CVE-2022-49437)

    * kernel: ima: Fix potential memory leak in ima_init_crypto() (CVE-2022-49627)

    * kernel: linux/dim: Fix divide by 0 in RDMA DIM (CVE-2022-49670)

    * kernel: can: isotp: sanitize CAN ID checks in isotp_bind() (CVE-2022-49269)

    * kernel: ima: Fix a potential integer overflow in ima_appraise_measurement (CVE-2022-49643)

    * kernel: powerpc/xive/spapr: correct bitmap allocation size (CVE-2022-49623)

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

    * kernel: list: fix a data-race around ep->rdllist (CVE-2022-49443)

    * kernel: tracing/histograms: Fix memory leak problem (CVE-2022-49648)

    * kernel: Input: synaptics - fix crash when enabling pass-through port (CVE-2025-21746)

    * kernel: NFSD: fix hang in nfsd4_shutdown_callback (CVE-2025-21795)

    * kernel: bpf: Send signals asynchronously if !preemptible (CVE-2025-21728)

    * kernel: NFS: Fix potential buffer overflowin nfs_sysfs_link_rpc_client() (CVE-2024-54456)

    * kernel: Bluetooth: btrtl: check for NULL in btrtl_setup_realtek() (CVE-2024-57987)

    * kernel: wifi: brcmsmac: add gain range check to wlc_phy_iqcal_gainparams_nphy() (CVE-2024-58014)

    * kernel: Bluetooth: btbcm: Fix NULL deref in btbcm_get_board_name() (CVE-2024-57988)

    * kernel: RDMA/mlx5: Fix implicit ODP use after free (CVE-2025-21714)

    * kernel: drm/xe/tracing: Fix a potential TP_printk UAF (CVE-2024-49570)

    * kernel: HID: hid-thrustmaster: Fix warning in thrustmaster_probe by adding endpoint check     (CVE-2024-57993)

    * kernel: wifi: rtw89: fix race between cancel_hw_scan and hw_scan completion (CVE-2025-21729)

    * kernel: wifi: mt76: mt7925: fix NULL deref check in mt7925_change_vif_links (CVE-2024-57989)

    * kernel: wifi: ath12k: Fix for out-of bound access error (CVE-2024-58015)

    * kernel: OPP: add index check to assert to avoid buffer overflow in _read_freq() (CVE-2024-57998)

    * kernel: wifi: ath12k: fix read pointer after free in ath12k_mac_assign_vif_to_vdev() (CVE-2024-57995)

    * kernel: nfsd: clear acl_access/acl_default after releasing them (CVE-2025-21796)

    * kernel: scsi: ufs: core: Fix use-after free in init error and remove paths (CVE-2025-21739)

    * kernel: workqueue: Put the pwq after detaching the rescuer from the pool (CVE-2025-21786)

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

    * kernel: HID: core: Fix assumption that Resolution Multipliers must be in Logical Collections     (CVE-2024-57986)

    * kernel: padata: avoid UAF for reorder_work (CVE-2025-21726)

    * kernel: vrf: use RCU protection in l3mdev_l3_out() (CVE-2025-21791)

    * kernel: team: better TEAM_OPTION_TYPE_STRING validation (CVE-2025-21787)

    * kernel: usb: xhci: Fix NULL pointer dereference on certain command aborts (CVE-2024-57981)

    * kernel: vxlan: check vxlan_vnigroup_init() return value (CVE-2025-21790)

    * kernel: wifi: mt76: mt7925: fix off by one in mt7925_load_clc() (CVE-2024-57990)

    * kernel: ipv6: use RCU protection in ip6_default_advmss() (CVE-2025-21765)

    * kernel: ASoC: SOF: Intel: hda-dai: Ensure DAI widget is valid during params (CVE-2024-58012)

    * kernel: blk-cgroup: Fix class @block_class's subsystem refcount leakage (CVE-2025-21745)

    * kernel: net: let net.core.dev_weight always be non-zero (CVE-2025-21806)

    * kernel: wifi: rtlwifi: remove unused check_buddy_priv (CVE-2024-58072)

    * kernel: OPP: fix dev_pm_opp_find_bw_*() when bandwidth table not initialized (CVE-2024-58068)

    * kernel: wifi: iwlwifi: mvm: avoid NULL pointer dereference (CVE-2024-58062)

    * kernel: idpf: convert workqueues to unbound (CVE-2024-58057)

    * kernel: wifi: mac80211: don't flush non-uploaded STAs (CVE-2025-21828)

    * kernel: KVM: Explicitly verify target vCPU is online in kvm_get_vcpu() (CVE-2024-58083)

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

    * kernel: ASoC: soc-pcm: don't use soc_pcm_ret() on .prepare callback (CVE-2024-58077)

    * kernel: crypto: tegra - do not transfer req when tegra init fails (CVE-2024-58075)

    * kernel: RDMA/rxe: Fix the warning __rxe_cleanup+0x12c/0x170 [rdma_rxe] (CVE-2025-21829)

    * kernel: KVM: x86: Load DR6 with guest value only before entering .vcpu_run() loop (CVE-2025-21839)

    * kernel: io_uring/uring_cmd: unconditionally copy SQEs at prep time (CVE-2025-21837)

    * kernel: information leak via transient execution vulnerability in some AMD processors (CVE-2024-36350)

    * kernel: transient execution vulnerability in some AMD processors (CVE-2024-36357)

    * kernel: bpf: Fix softlockup in arena_map_free on 64k page kernel (CVE-2025-21851)

    * kernel: ibmvnic: Don't reference skb after sending to VIOS (CVE-2025-21855)

    * kernel: smb: client: Add check for next_buffer in receive_encrypted_standard() (CVE-2025-21844)

    * kernel: bpf: avoid holding freeze_mutex during mmap operation (CVE-2025-21853)

    * kernel: ASoC: SOF: stream-ipc: Check for cstream nullity in sof_ipc_msg_data() (CVE-2025-21847)

    * kernel: tcp: drop secpath at the same time as we currently drop dst (CVE-2025-21864)

    * kernel: bpf: Fix deadlock when freeing cgroup storage (CVE-2024-58088)

    * kernel: acct: perform last write from workqueue (CVE-2025-21846)

    * kernel: mm/migrate_device: don't add folio to be freed to LRU in migrate_device_finalize()     (CVE-2025-21861)

    * kernel: io_uring: prevent opcode speculation (CVE-2025-21863)

    * kernel: nfp: bpf: Add check for nfp_app_ctrl_msg_alloc() (CVE-2025-21848)

    * kernel: netfilter: nft_tunnel: fix geneve_opt type confusion addition (CVE-2025-22056)

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

    * kernel: usb: typec: ucsi: displayport: Fix NULL pointer access (CVE-2025-37994)

    * kernel: wifi: ath12k: fix uaf in ath12k_core_init() (CVE-2025-38116)

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

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

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

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

  - In the Linux kernel, the following vulnerability has been resolved: phy: mdio: fix memory leak Syzbot     reported memory leak in MDIO bus interface, the problem was in wrong state logic. MDIOBUS_ALLOCATED     indicates 2 states: 1. Bus is only allocated 2. Bus allocated and __mdiobus_register() fails, but     device_register() was called In case of device_register() has been called we should call put_device() to     correctly free the memory allocated for this device, but mdiobus_free() calls just kfree(dev) in case of     MDIOBUS_ALLOCATED state To avoid this behaviour we need to set bus->state to MDIOBUS_UNREGISTERED _before_     calling device_register(), because put_device() should be called even in case of device_register()     failure. (CVE-2021-47416)

  - An out-of-bounds read flaw was found in the Linux kernel's TeleTYpe subsystem. The issue occurs in how a     user triggers a race condition using ioctls TIOCSPTLCK and TIOCGPTPEER and TIOCSTI and TCXONC with leakage     of memory in the flush_to_ldisc function. This flaw allows a local user to crash the system or read     unauthorized random data from memory. (CVE-2022-1462)

  - In the Linux kernel, the following vulnerability has been resolved: can: isotp: sanitize CAN ID checks in     isotp_bind() Syzbot created an environment that lead to a state machine status that can not be reached     with a compliant CAN ID address configuration. The provided address information consisted of CAN ID     0x6000001 and 0xC28001 which both boil down to 11 bit CAN IDs 0x001 in sending and receiving. Sanitize the     SFF/EFF CAN ID values before performing the address checks. (CVE-2022-49269)

  - In the Linux kernel, the following vulnerability has been resolved: tty: fix deadlock caused by calling     printk() under tty_port->lock pty_write() invokes kmalloc() which may invoke a normal printk() to print     failure message. This can cause a deadlock in the scenario reported by syz-bot below: CPU0 CPU1 CPU2 ----
    ---- ---- lock(console_owner); lock(&port_lock_key); lock(&port->lock); lock(&port_lock_key);
    lock(&port->lock); lock(console_owner); As commit dbdda842fe96 (printk: Add console owner and waiter     logic to load balance console writes) said, such deadlock can be prevented by using printk_deferred() in     kmalloc() (which is invoked in the section guarded by the port->lock). But there are too many printk() on     the kmalloc() path, and kmalloc() can be called from anywhere, so changing printk() to printk_deferred()     is too complicated and inelegant. Therefore, this patch chooses to specify __GFP_NOWARN to kmalloc(), so     that printk() will not be called, and this deadlock problem can be avoided. Syzbot reported the following     lockdep error: ====================================================== WARNING: possible circular locking     dependency detected 5.4.143-00237-g08ccc19a-dirty #10 Not tainted
    ------------------------------------------------------ syz-executor.4/29420 is trying to acquire lock:
    ffffffff8aedb2a0 (console_owner){....}-{0:0}, at: console_trylock_spinning kernel/printk/printk.c:1752     [inline] ffffffff8aedb2a0 (console_owner){....}-{0:0}, at: vprintk_emit+0x2ca/0x470     kernel/printk/printk.c:2023 but task is already holding lock: ffff8880119c9158 (&port->lock){-.-.}-{2:2},     at: pty_write+0xf4/0x1f0 drivers/tty/pty.c:120 which lock already depends on the new lock. the existing     dependency chain (in reverse order) is: -> #2 (&port->lock){-.-.}-{2:2}: __raw_spin_lock_irqsave     include/linux/spinlock_api_smp.h:110 [inline] _raw_spin_lock_irqsave+0x35/0x50     kernel/locking/spinlock.c:159 tty_port_tty_get drivers/tty/tty_port.c:288 [inline] <-- lock(&port->lock);
    tty_port_default_wakeup+0x1d/0xb0 drivers/tty/tty_port.c:47 serial8250_tx_chars+0x530/0xa80     drivers/tty/serial/8250/8250_port.c:1767 serial8250_handle_irq.part.0+0x31f/0x3d0     drivers/tty/serial/8250/8250_port.c:1854 serial8250_handle_irq drivers/tty/serial/8250/8250_port.c:1827     [inline] <-- lock(&port_lock_key); serial8250_default_handle_irq+0xb2/0x220     drivers/tty/serial/8250/8250_port.c:1870 serial8250_interrupt+0xfd/0x200     drivers/tty/serial/8250/8250_core.c:126 __handle_irq_event_percpu+0x109/0xa50 kernel/irq/handle.c:156     [...] -> #1 (&port_lock_key){-.-.}-{2:2}: __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110     [inline] _raw_spin_lock_irqsave+0x35/0x50 kernel/locking/spinlock.c:159     serial8250_console_write+0x184/0xa40 drivers/tty/serial/8250/8250_port.c:3198 <-- lock(&port_lock_key);
    call_console_drivers kernel/printk/printk.c:1819 [inline] console_unlock+0x8cb/0xd00     kernel/printk/printk.c:2504 vprintk_emit+0x1b5/0x470 kernel/printk/printk.c:2024 <-- lock(console_owner);
    vprintk_func+0x8d/0x250 kernel/printk/printk_safe.c:394 printk+0xba/0xed kernel/printk/printk.c:2084     register_console+0x8b3/0xc10 kernel/printk/printk.c:2829 univ8250_console_init+0x3a/0x46     drivers/tty/serial/8250/8250_core.c:681 console_init+0x49d/0x6d3 kernel/printk/printk.c:2915     start_kernel+0x5e9/0x879 init/main.c:713 secondary_startup_64+0xa4/0xb0 arch/x86/kernel/head_64.S:241 ->     #0 (console_owner){....}-{0:0}: [...] lock_acquire+0x127/0x340 kernel/locking/lockdep.c:4734     console_trylock_spinning kernel/printk/printk.c:1773 ---truncated--- (CVE-2022-49441)

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

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

The remote MiracleLinux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the AXSA:2025-11493:94 advisory.

    * kernel: can: isotp: fix potential CAN frame reception race in isotp_rcv() (CVE-2022-48830)
      * kernel: soc: qcom: cmd-db: Map shared memory as WC, not WB (CVE-2024-46689)
      * kernel: Squashfs: sanity check symbolic link size (CVE-2024-46744)
      * kernel: vfs: fix race between evice_inodes() and find_inode()&iput() (CVE-2024-47679)
      * kernel: x86/tdx: Fix in-kernel MMIO check (CVE-2024-47727)
      * kernel: rxrpc: Fix a race between socket set up and I/O thread creation (CVE-2024-49864)
      * kernel: io_uring: check if we need to reschedule during overflow flush (CVE-2024-50060)
      * kernel: can: m_can: pci: add missing m_can_class_free_dev() in probe/remove methods (CVE-2022-49024)
      * kernel: posix-clock: Fix missing timespec64 check in pc_clock_settime() (CVE-2024-50195)
      * kernel: rxrpc: Fix missing locking causing hanging calls (CVE-2024-50294)
      * kernel: io_uring/rw: fix missing NOWAIT check for O_DIRECT start write (CVE-2024-53052)
      * kernel: afs: Fix lock recursion (CVE-2024-53090)
      * kernel: virtio/vsock: Fix accept_queue memory leak (CVE-2024-53119)
      * kernel: KVM: VMX: Bury Intel PT virtualization (guest/host mode) behind CONFIG_BROKEN (CVE-2024-53135)
      * kernel: xen: Xen hypercall page unsafe against speculative attacks (Xen Security Advisory 466)     (CVE-2024-53241)
      * kernel: RDMA/rxe: Fix the qp flush warnings in req (CVE-2024-53229)
      * kernel: block: fix uaf for flush rq while iterating tags (CVE-2024-53170)
      * kernel: nfsd: release svc_expkey/svc_export with rcu_work (CVE-2024-53216)
      * kernel: net: af_can: do not leave a dangling sk pointer in can_create() (CVE-2024-56603)
      * kernel: blk-cgroup: Fix UAF in blkcg_unpin_online() (CVE-2024-56672)
      * kernel: acpi: nfit: vmalloc-out-of-bounds Read in acpi_nfit_ctl (CVE-2024-56662)
      * kernel: bpf: Fix UAF via mismatching bpf_prog/attachment RCU flavors (CVE-2024-56675)
      * kernel: can: j1939: j1939_session_new(): fix skb reference counting (CVE-2024-56645)
      * kernel: crypto: pcrypt - Call crypto layer directly when padata_do_parallel() return -EBUSY     (CVE-2024-56690)
      * kernel: io_uring: check if iowq is killed before queuing (CVE-2024-56709)
      * kernel: rtc: check if __rtc_read_time was successful in rtc_timer_do_work() (CVE-2024-56739)
      * kernel: bpf: put bpf_link's program when link is safe to be deallocated (CVE-2024-56786)
      * kernel: igb: Fix potential invalid memory access in igb_init_module() (CVE-2024-52332)
      * kernel: ipvs: fix UB due to uninitialized stack access in ip_vs_protocol_init() (CVE-2024-53680)
      * kernel: netfilter: conntrack: clamp maximum hashtable size to INT_MAX (CVE-2025-21648)
      * kernel: sched: sch_cake: add bounds checks to host bulk flow fairness counts (CVE-2025-21647)
      * kernel: block, bfq: fix waker_bfqq UAF after bfq_split_bfqq() (CVE-2025-21631)
      * kernel: zram: fix potential UAF of zram table (CVE-2025-21671)
      * kernel: afs: Fix merge preference rule failure condition (CVE-2025-21672)
      * kernel: mm: zswap: properly synchronize freeing resources during CPU hotunplug (CVE-2025-21693)
      * kernel: cachestat: fix page cache statistics permission checking (CVE-2025-21691)
      * kernel: mm: clear uffd-wp PTE/PMD state on mremap() (CVE-2025-21696)
      * kernel: pfifo_tail_enqueue: Drop new packet when sch->limit == 0 (CVE-2025-21702)
      * kernel: usbnet: fix memory leak in error case (CVE-2022-49657)
      * kernel: powerpc/xics: fix refcount leak in icp_opal_init() (CVE-2022-49432)
      * kernel: net: tun: unlink NAPI from device on destruction (CVE-2022-49672)
      * kernel: powerpc/papr_scm: don't requests stats with '0' sized stats buffer (CVE-2022-49353)
      * kernel: powerpc/xive: Fix refcount leak in xive_spapr_init (CVE-2022-49437)
      * kernel: ima: Fix potential memory leak in ima_init_crypto() (CVE-2022-49627)
      * kernel: linux/dim: Fix divide by 0 in RDMA DIM (CVE-2022-49670)
      * kernel: can: isotp: sanitize CAN ID checks in isotp_bind() (CVE-2022-49269)
      * kernel: ima: Fix a potential integer overflow in ima_appraise_measurement (CVE-2022-49643)
      * kernel: powerpc/xive/spapr: correct bitmap allocation size (CVE-2022-49623)
      * kernel: efi: Do not import certificates from UEFI Secure Boot for T2 Macs (CVE-2022-49357)
      * kernel: list: fix a data-race around ep->rdllist (CVE-2022-49443)
      * kernel: tracing/histograms: Fix memory leak problem (CVE-2022-49648)
      * kernel: Input: synaptics - fix crash when enabling pass-through port (CVE-2025-21746)
      * kernel: NFSD: fix hang in nfsd4_shutdown_callback (CVE-2025-21795)
      * kernel: bpf: Send signals asynchronously if !preemptible (CVE-2025-21728)
      * kernel: NFS: Fix potential buffer overflowin nfs_sysfs_link_rpc_client() (CVE-2024-54456)
      * kernel: Bluetooth: btrtl: check for NULL in btrtl_setup_realtek() (CVE-2024-57987)
      * kernel: wifi: brcmsmac: add gain range check to wlc_phy_iqcal_gainparams_nphy() (CVE-2024-58014)
      * kernel: Bluetooth: btbcm: Fix NULL deref in btbcm_get_board_name() (CVE-2024-57988)
      * kernel: RDMA/mlx5: Fix implicit ODP use after free (CVE-2025-21714)
      * kernel: drm/xe/tracing: Fix a potential TP_printk UAF (CVE-2024-49570)
      * kernel: HID: hid-thrustmaster: Fix warning in thrustmaster_probe by adding endpoint check     (CVE-2024-57993)
      * kernel: wifi: rtw89: fix race between cancel_hw_scan and hw_scan completion (CVE-2025-21729)
      * kernel: wifi: mt76: mt7925: fix NULL deref check in mt7925_change_vif_links (CVE-2024-57989)
      * kernel: wifi: ath12k: Fix for out-of bound access error (CVE-2024-58015)
      * kernel: OPP: add index check to assert to avoid buffer overflow in _read_freq() (CVE-2024-57998)
      * kernel: wifi: ath12k: fix read pointer after free in ath12k_mac_assign_vif_to_vdev() (CVE-2024-57995)
      * kernel: nfsd: clear acl_access/acl_default after releasing them (CVE-2025-21796)
      * kernel: scsi: ufs: core: Fix use-after free in init error and remove paths (CVE-2025-21739)
      * kernel: workqueue: Put the pwq after detaching the rescuer from the pool (CVE-2025-21786)
      * kernel: ata: libata-sff: Ensure that we cannot write outside the allocated buffer (CVE-2025-21738)
      * kernel: HID: core: Fix assumption that Resolution Multipliers must be in Logical Collections     (CVE-2024-57986)
      * kernel: padata: avoid UAF for reorder_work (CVE-2025-21726)
      * kernel: vrf: use RCU protection in l3mdev_l3_out() (CVE-2025-21791)
      * kernel: team: better TEAM_OPTION_TYPE_STRING validation (CVE-2025-21787)
      * kernel: usb: xhci: Fix NULL pointer dereference on certain command aborts (CVE-2024-57981)
      * kernel: vxlan: check vxlan_vnigroup_init() return value (CVE-2025-21790)
      * kernel: wifi: mt76: mt7925: fix off by one in mt7925_load_clc() (CVE-2024-57990)
      * kernel: ipv6: use RCU protection in ip6_default_advmss() (CVE-2025-21765)
      * kernel: ASoC: SOF: Intel: hda-dai: Ensure DAI widget is valid during params (CVE-2024-58012)
      * kernel: blk-cgroup: Fix class @block_class's subsystem refcount leakage (CVE-2025-21745)
      * kernel: net: let net.core.dev_weight always be non-zero (CVE-2025-21806)
      * kernel: wifi: rtlwifi: remove unused check_buddy_priv (CVE-2024-58072)
      * kernel: OPP: fix dev_pm_opp_find_bw_*() when bandwidth table not initialized (CVE-2024-58068)
      * kernel: wifi: iwlwifi: mvm: avoid NULL pointer dereference (CVE-2024-58062)
      * kernel: idpf: convert workqueues to unbound (CVE-2024-58057)
      * kernel: wifi: mac80211: don't flush non-uploaded STAs (CVE-2025-21828)
      * kernel: KVM: Explicitly verify target vCPU is online in kvm_get_vcpu() (CVE-2024-58083)
      * kernel: netfilter: nf_tables: reject mismatching sum of field_len with set key length (CVE-2025-21826)
      * kernel: ASoC: soc-pcm: don't use soc_pcm_ret() on .prepare callback (CVE-2024-58077)
      * kernel: crypto: tegra - do not transfer req when tegra init fails (CVE-2024-58075)
      * kernel: RDMA/rxe: Fix the warning __rxe_cleanup+0x12c/0x170 [rdma_rxe] (CVE-2025-21829)
      * kernel: KVM: x86: Load DR6 with guest value only before entering .vcpu_run() loop (CVE-2025-21839)
      * kernel: io_uring/uring_cmd: unconditionally copy SQEs at prep time (CVE-2025-21837)
      * kernel: information leak via transient execution vulnerability in some AMD processors (CVE-2024-36350)
      * kernel: transient execution vulnerability in some AMD processors (CVE-2024-36357)
      * kernel: bpf: Fix softlockup in arena_map_free on 64k page kernel (CVE-2025-21851)
      * kernel: ibmvnic: Don't reference skb after sending to VIOS (CVE-2025-21855)
      * kernel: smb: client: Add check for next_buffer in receive_encrypted_standard() (CVE-2025-21844)
      * kernel: bpf: avoid holding freeze_mutex during mmap operation (CVE-2025-21853)
      * kernel: ASoC: SOF: stream-ipc: Check for cstream nullity in sof_ipc_msg_data() (CVE-2025-21847)
      * kernel: tcp: drop secpath at the same time as we currently drop dst (CVE-2025-21864)
      * kernel: bpf: Fix deadlock when freeing cgroup storage (CVE-2024-58088)
      * kernel: acct: perform last write from workqueue (CVE-2025-21846)
      * kernel: mm/migrate_device: don't add folio to be freed to LRU in migrate_device_finalize()     (CVE-2025-21861)
      * kernel: io_uring: prevent opcode speculation (CVE-2025-21863)
      * kernel: nfp: bpf: Add check for nfp_app_ctrl_msg_alloc() (CVE-2025-21848)
      * kernel: netfilter: nft_tunnel: fix geneve_opt type confusion addition (CVE-2025-22056)
      * kernel: can: j1939: j1939_send_one(): fix missing CAN header initialization (CVE-2022-49845)
      * kernel: usb: typec: ucsi: displayport: Fix NULL pointer access (CVE-2025-37994)
      * kernel: wifi: ath12k: fix uaf in ath12k_core_init() (CVE-2025-38116)
      * kernel: fs: export anon_inode_make_secure_inode() and fix secretmem LSM bypass (CVE-2025-38396)

Tenable has extracted the preceding description block directly from the MiracleLinux 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 RockyLinux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the RLSA-2025:20518 advisory.

    * kernel: can: isotp: fix potential CAN frame reception race in isotp_rcv() (CVE-2022-48830)

    * kernel: soc: qcom: cmd-db: Map shared memory as WC, not WB (CVE-2024-46689)

    * kernel: Squashfs: sanity check symbolic link size (CVE-2024-46744)

    * kernel: vfs: fix race between evice_inodes() and find_inode()&iput() (CVE-2024-47679)

    * kernel: x86/tdx: Fix in-kernel MMIO check (CVE-2024-47727)

    * kernel: rxrpc: Fix a race between socket set up and I/O thread creation (CVE-2024-49864)

    * kernel: io_uring: check if we need to reschedule during overflow flush (CVE-2024-50060)

    * kernel: can: m_can: pci: add missing m_can_class_free_dev() in probe/remove methods (CVE-2022-49024)

    * kernel: posix-clock: Fix missing timespec64 check in pc_clock_settime() (CVE-2024-50195)

    * kernel: rxrpc: Fix missing locking causing hanging calls (CVE-2024-50294)

    * kernel: io_uring/rw: fix missing NOWAIT check for O_DIRECT start write (CVE-2024-53052)

    * kernel: afs: Fix lock recursion (CVE-2024-53090)

    * kernel: virtio/vsock: Fix accept_queue memory leak (CVE-2024-53119)

    * kernel: KVM: VMX: Bury Intel PT virtualization (guest/host mode) behind CONFIG_BROKEN (CVE-2024-53135)

    * kernel: xen: Xen hypercall page unsafe against speculative attacks (Xen Security Advisory 466)     (CVE-2024-53241)

    * kernel: RDMA/rxe: Fix the qp flush warnings in req (CVE-2024-53229)

    * kernel: block: fix uaf for flush rq while iterating tags (CVE-2024-53170)

    * kernel: nfsd: release svc_expkey/svc_export with rcu_work (CVE-2024-53216)

    * kernel: net: af_can: do not leave a dangling sk pointer in can_create() (CVE-2024-56603)

    * kernel: blk-cgroup: Fix UAF in blkcg_unpin_online() (CVE-2024-56672)

    * kernel: acpi: nfit: vmalloc-out-of-bounds Read in acpi_nfit_ctl (CVE-2024-56662)

    * kernel: bpf: Fix UAF via mismatching bpf_prog/attachment RCU flavors (CVE-2024-56675)

    * kernel: can: j1939: j1939_session_new(): fix skb reference counting (CVE-2024-56645)

    * kernel: crypto: pcrypt - Call crypto layer directly when padata_do_parallel() return -EBUSY     (CVE-2024-56690)

    * kernel: io_uring: check if iowq is killed before queuing (CVE-2024-56709)

    * kernel: rtc: check if __rtc_read_time was successful in rtc_timer_do_work() (CVE-2024-56739)

    * kernel: bpf: put bpf_link's program when link is safe to be deallocated (CVE-2024-56786)

    * kernel: igb: Fix potential invalid memory access in igb_init_module() (CVE-2024-52332)

    * kernel: ipvs: fix UB due to uninitialized stack access in ip_vs_protocol_init() (CVE-2024-53680)

    * kernel: netfilter: conntrack: clamp maximum hashtable size to INT_MAX (CVE-2025-21648)

    * kernel: sched: sch_cake: add bounds checks to host bulk flow fairness counts (CVE-2025-21647)

    * kernel: block, bfq: fix waker_bfqq UAF after bfq_split_bfqq() (CVE-2025-21631)

    * kernel: zram: fix potential UAF of zram table (CVE-2025-21671)

    * kernel: afs: Fix merge preference rule failure condition (CVE-2025-21672)

    * kernel: mm: zswap: properly synchronize freeing resources during CPU hotunplug (CVE-2025-21693)

    * kernel: cachestat: fix page cache statistics permission checking (CVE-2025-21691)

    * kernel: mm: clear uffd-wp PTE/PMD state on mremap() (CVE-2025-21696)

    * kernel: pfifo_tail_enqueue: Drop new packet when sch->limit == 0 (CVE-2025-21702)

    * kernel: usbnet: fix memory leak in error case (CVE-2022-49657)

    * kernel: powerpc/xics: fix refcount leak in icp_opal_init() (CVE-2022-49432)

    * kernel: net: tun: unlink NAPI from device on destruction (CVE-2022-49672)

    * kernel: powerpc/papr_scm: don't requests stats with '0' sized stats buffer (CVE-2022-49353)

    * kernel: powerpc/xive: Fix refcount leak in xive_spapr_init (CVE-2022-49437)

    * kernel: ima: Fix potential memory leak in ima_init_crypto() (CVE-2022-49627)

    * kernel: linux/dim: Fix divide by 0 in RDMA DIM (CVE-2022-49670)

    * kernel: can: isotp: sanitize CAN ID checks in isotp_bind() (CVE-2022-49269)

    * kernel: ima: Fix a potential integer overflow in ima_appraise_measurement (CVE-2022-49643)

    * kernel: powerpc/xive/spapr: correct bitmap allocation size (CVE-2022-49623)

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

    * kernel: list: fix a data-race around ep->rdllist (CVE-2022-49443)

    * kernel: tracing/histograms: Fix memory leak problem (CVE-2022-49648)

    * kernel: Input: synaptics - fix crash when enabling pass-through port (CVE-2025-21746)

    * kernel: NFSD: fix hang in nfsd4_shutdown_callback (CVE-2025-21795)

    * kernel: bpf: Send signals asynchronously if !preemptible (CVE-2025-21728)

    * kernel: NFS: Fix potential buffer overflowin nfs_sysfs_link_rpc_client() (CVE-2024-54456)

    * kernel: Bluetooth: btrtl: check for NULL in btrtl_setup_realtek() (CVE-2024-57987)

    * kernel: wifi: brcmsmac: add gain range check to wlc_phy_iqcal_gainparams_nphy() (CVE-2024-58014)

    * kernel: Bluetooth: btbcm: Fix NULL deref in btbcm_get_board_name() (CVE-2024-57988)

    * kernel: RDMA/mlx5: Fix implicit ODP use after free (CVE-2025-21714)

    * kernel: drm/xe/tracing: Fix a potential TP_printk UAF (CVE-2024-49570)

    * kernel: HID: hid-thrustmaster: Fix warning in thrustmaster_probe by adding endpoint check     (CVE-2024-57993)

    * kernel: wifi: rtw89: fix race between cancel_hw_scan and hw_scan completion (CVE-2025-21729)

    * kernel: wifi: mt76: mt7925: fix NULL deref check in mt7925_change_vif_links (CVE-2024-57989)

    * kernel: wifi: ath12k: Fix for out-of bound access error (CVE-2024-58015)

    * kernel: OPP: add index check to assert to avoid buffer overflow in _read_freq() (CVE-2024-57998)

    * kernel: wifi: ath12k: fix read pointer after free in ath12k_mac_assign_vif_to_vdev() (CVE-2024-57995)

    * kernel: nfsd: clear acl_access/acl_default after releasing them (CVE-2025-21796)

    * kernel: scsi: ufs: core: Fix use-after free in init error and remove paths (CVE-2025-21739)

    * kernel: workqueue: Put the pwq after detaching the rescuer from the pool (CVE-2025-21786)

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

    * kernel: HID: core: Fix assumption that Resolution Multipliers must be in Logical Collections     (CVE-2024-57986)

    * kernel: padata: avoid UAF for reorder_work (CVE-2025-21726)

    * kernel: vrf: use RCU protection in l3mdev_l3_out() (CVE-2025-21791)

    * kernel: team: better TEAM_OPTION_TYPE_STRING validation (CVE-2025-21787)

    * kernel: usb: xhci: Fix NULL pointer dereference on certain command aborts (CVE-2024-57981)

    * kernel: vxlan: check vxlan_vnigroup_init() return value (CVE-2025-21790)

    * kernel: wifi: mt76: mt7925: fix off by one in mt7925_load_clc() (CVE-2024-57990)

    * kernel: ipv6: use RCU protection in ip6_default_advmss() (CVE-2025-21765)

    * kernel: ASoC: SOF: Intel: hda-dai: Ensure DAI widget is valid during params (CVE-2024-58012)

    * kernel: blk-cgroup: Fix class @block_class's subsystem refcount leakage (CVE-2025-21745)

    * kernel: net: let net.core.dev_weight always be non-zero (CVE-2025-21806)

    * kernel: wifi: rtlwifi: remove unused check_buddy_priv (CVE-2024-58072)

    * kernel: OPP: fix dev_pm_opp_find_bw_*() when bandwidth table not initialized (CVE-2024-58068)

    * kernel: wifi: iwlwifi: mvm: avoid NULL pointer dereference (CVE-2024-58062)

    * kernel: idpf: convert workqueues to unbound (CVE-2024-58057)

    * kernel: wifi: mac80211: don't flush non-uploaded STAs (CVE-2025-21828)

    * kernel: KVM: Explicitly verify target vCPU is online in kvm_get_vcpu() (CVE-2024-58083)

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

    * kernel: ASoC: soc-pcm: don't use soc_pcm_ret() on .prepare callback (CVE-2024-58077)

    * kernel: crypto: tegra - do not transfer req when tegra init fails (CVE-2024-58075)

    * kernel: RDMA/rxe: Fix the warning __rxe_cleanup+0x12c/0x170 [rdma_rxe] (CVE-2025-21829)

    * kernel: KVM: x86: Load DR6 with guest value only before entering .vcpu_run() loop (CVE-2025-21839)

    * kernel: io_uring/uring_cmd: unconditionally copy SQEs at prep time (CVE-2025-21837)

    * kernel: information leak via transient execution vulnerability in some AMD processors (CVE-2024-36350)

    * kernel: transient execution vulnerability in some AMD processors (CVE-2024-36357)

    * kernel: bpf: Fix softlockup in arena_map_free on 64k page kernel (CVE-2025-21851)

    * kernel: ibmvnic: Don't reference skb after sending to VIOS (CVE-2025-21855)

    * kernel: smb: client: Add check for next_buffer in receive_encrypted_standard() (CVE-2025-21844)

    * kernel: bpf: avoid holding freeze_mutex during mmap operation (CVE-2025-21853)

    * kernel: ASoC: SOF: stream-ipc: Check for cstream nullity in sof_ipc_msg_data() (CVE-2025-21847)

    * kernel: tcp: drop secpath at the same time as we currently drop dst (CVE-2025-21864)

    * kernel: bpf: Fix deadlock when freeing cgroup storage (CVE-2024-58088)

    * kernel: acct: perform last write from workqueue (CVE-2025-21846)

    * kernel: mm/migrate_device: don't add folio to be freed to LRU in migrate_device_finalize()     (CVE-2025-21861)

    * kernel: io_uring: prevent opcode speculation (CVE-2025-21863)

    * kernel: nfp: bpf: Add check for nfp_app_ctrl_msg_alloc() (CVE-2025-21848)

    * kernel: netfilter: nft_tunnel: fix geneve_opt type confusion addition (CVE-2025-22056)

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

    * kernel: usb: typec: ucsi: displayport: Fix NULL pointer access (CVE-2025-37994)

    * kernel: wifi: ath12k: fix uaf in ath12k_core_init() (CVE-2025-38116)

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

Tenable has extracted the preceding description block directly from the RockyLinux 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 Oracle Linux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the ELSA-2025-205180 advisory.

    - io_uring/futex: ensure io_futex_wait() cleans up properly on failure (CKI Backport Bot) [RHEL-114336]     {CVE-2025-39698}
    - NFS: Fix filehandle bounds checking in nfs_fh_to_dentry() (CKI Backport Bot) [RHEL-113611]     {CVE-2025-39730}
    - eventpoll: Fix semi-unbounded recursion (CKI Backport Bot) [RHEL-111050] {CVE-2025-38614}
    - ALSA: hda/ca0132: Fix buffer overflow in add_tuning_control (CKI Backport Bot) [RHEL-114850]     {CVE-2025-39751}
    - wifi: ath12k: Decrement TID on RX peer frag setup error handling (CKI Backport Bot) [RHEL-114708]     {CVE-2025-39761}
    - ALSA: usb-audio: Validate UAC3 power domain descriptors, too (Jaroslav Kysela) [RHEL-114691]     {CVE-2025-38729}
    - ALSA: usb-audio: Validate UAC3 cluster segment descriptors (CKI Backport Bot) [RHEL-114691]     {CVE-2025-39757}
    - selftests: tls: add tests for zero-length records (Sabrina Dubroca) [RHEL-114324] {CVE-2025-39682}
    - tls: fix handling of zero-length records on the rx_list (Sabrina Dubroca) [RHEL-114324] {CVE-2025-39682}

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

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

The remote AlmaLinux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the ALSA-2025:20518 advisory.

    * kernel: can: isotp: fix potential CAN frame reception race in isotp_rcv() (CVE-2022-48830)
      * kernel: soc: qcom: cmd-db: Map shared memory as WC, not WB (CVE-2024-46689)
      * kernel: Squashfs: sanity check symbolic link size (CVE-2024-46744)
      * kernel: vfs: fix race between evice_inodes() and find_inode()&iput() (CVE-2024-47679)
      * kernel: x86/tdx: Fix in-kernel MMIO check (CVE-2024-47727)
      * kernel: rxrpc: Fix a race between socket set up and I/O thread creation (CVE-2024-49864)
      * kernel: io_uring: check if we need to reschedule during overflow flush (CVE-2024-50060)
      * kernel: can: m_can: pci: add missing m_can_class_free_dev() in probe/remove methods (CVE-2022-49024)
      * kernel: posix-clock: Fix missing timespec64 check in pc_clock_settime() (CVE-2024-50195)
      * kernel: rxrpc: Fix missing locking causing hanging calls (CVE-2024-50294)
      * kernel: io_uring/rw: fix missing NOWAIT check for O_DIRECT start write (CVE-2024-53052)
      * kernel: afs: Fix lock recursion (CVE-2024-53090)
      * kernel: virtio/vsock: Fix accept_queue memory leak (CVE-2024-53119)
      * kernel: KVM: VMX: Bury Intel PT virtualization (guest/host mode) behind CONFIG_BROKEN (CVE-2024-53135)
      * kernel: xen: Xen hypercall page unsafe against speculative attacks (Xen Security Advisory 466)     (CVE-2024-53241)
      * kernel: RDMA/rxe: Fix the qp flush warnings in req (CVE-2024-53229)
      * kernel: block: fix uaf for flush rq while iterating tags (CVE-2024-53170)
      * kernel: nfsd: release svc_expkey/svc_export with rcu_work (CVE-2024-53216)
      * kernel: net: af_can: do not leave a dangling sk pointer in can_create() (CVE-2024-56603)
      * kernel: blk-cgroup: Fix UAF in blkcg_unpin_online() (CVE-2024-56672)
      * kernel: acpi: nfit: vmalloc-out-of-bounds Read in acpi_nfit_ctl (CVE-2024-56662)
      * kernel: bpf: Fix UAF via mismatching bpf_prog/attachment RCU flavors (CVE-2024-56675)
      * kernel: can: j1939: j1939_session_new(): fix skb reference counting (CVE-2024-56645)
      * kernel: crypto: pcrypt - Call crypto layer directly when padata_do_parallel() return -EBUSY     (CVE-2024-56690)
      * kernel: io_uring: check if iowq is killed before queuing (CVE-2024-56709)
      * kernel: rtc: check if __rtc_read_time was successful in rtc_timer_do_work() (CVE-2024-56739)
      * kernel: bpf: put bpf_link's program when link is safe to be deallocated (CVE-2024-56786)
      * kernel: igb: Fix potential invalid memory access in igb_init_module() (CVE-2024-52332)
      * kernel: ipvs: fix UB due to uninitialized stack access in ip_vs_protocol_init() (CVE-2024-53680)
      * kernel: netfilter: conntrack: clamp maximum hashtable size to INT_MAX (CVE-2025-21648)
      * kernel: sched: sch_cake: add bounds checks to host bulk flow fairness counts (CVE-2025-21647)
      * kernel: block, bfq: fix waker_bfqq UAF after bfq_split_bfqq() (CVE-2025-21631)
      * kernel: zram: fix potential UAF of zram table (CVE-2025-21671)
      * kernel: afs: Fix merge preference rule failure condition (CVE-2025-21672)
      * kernel: mm: zswap: properly synchronize freeing resources during CPU hotunplug (CVE-2025-21693)
      * kernel: cachestat: fix page cache statistics permission checking (CVE-2025-21691)
      * kernel: mm: clear uffd-wp PTE/PMD state on mremap() (CVE-2025-21696)
      * kernel: pfifo_tail_enqueue: Drop new packet when sch->limit == 0 (CVE-2025-21702)
      * kernel: usbnet: fix memory leak in error case (CVE-2022-49657)
      * kernel: powerpc/xics: fix refcount leak in icp_opal_init() (CVE-2022-49432)
      * kernel: net: tun: unlink NAPI from device on destruction (CVE-2022-49672)
      * kernel: powerpc/papr_scm: don't requests stats with '0' sized stats buffer (CVE-2022-49353)
      * kernel: powerpc/xive: Fix refcount leak in xive_spapr_init (CVE-2022-49437)
      * kernel: ima: Fix potential memory leak in ima_init_crypto() (CVE-2022-49627)
      * kernel: linux/dim: Fix divide by 0 in RDMA DIM (CVE-2022-49670)
      * kernel: can: isotp: sanitize CAN ID checks in isotp_bind() (CVE-2022-49269)
      * kernel: ima: Fix a potential integer overflow in ima_appraise_measurement (CVE-2022-49643)
      * kernel: powerpc/xive/spapr: correct bitmap allocation size (CVE-2022-49623)
      * kernel: efi: Do not import certificates from UEFI Secure Boot for T2 Macs (CVE-2022-49357)
      * kernel: list: fix a data-race around ep->rdllist (CVE-2022-49443)
      * kernel: tracing/histograms: Fix memory leak problem (CVE-2022-49648)
      * kernel: Input: synaptics - fix crash when enabling pass-through port (CVE-2025-21746)
      * kernel: NFSD: fix hang in nfsd4_shutdown_callback (CVE-2025-21795)
      * kernel: bpf: Send signals asynchronously if !preemptible (CVE-2025-21728)
      * kernel: NFS: Fix potential buffer overflowin nfs_sysfs_link_rpc_client() (CVE-2024-54456)
      * kernel: Bluetooth: btrtl: check for NULL in btrtl_setup_realtek() (CVE-2024-57987)
      * kernel: wifi: brcmsmac: add gain range check to wlc_phy_iqcal_gainparams_nphy() (CVE-2024-58014)
      * kernel: Bluetooth: btbcm: Fix NULL deref in btbcm_get_board_name() (CVE-2024-57988)
      * kernel: RDMA/mlx5: Fix implicit ODP use after free (CVE-2025-21714)
      * kernel: drm/xe/tracing: Fix a potential TP_printk UAF (CVE-2024-49570)
      * kernel: HID: hid-thrustmaster: Fix warning in thrustmaster_probe by adding endpoint check     (CVE-2024-57993)
      * kernel: wifi: rtw89: fix race between cancel_hw_scan and hw_scan completion (CVE-2025-21729)
      * kernel: wifi: mt76: mt7925: fix NULL deref check in mt7925_change_vif_links (CVE-2024-57989)
      * kernel: wifi: ath12k: Fix for out-of bound access error (CVE-2024-58015)
      * kernel: OPP: add index check to assert to avoid buffer overflow in _read_freq() (CVE-2024-57998)
      * kernel: wifi: ath12k: fix read pointer after free in ath12k_mac_assign_vif_to_vdev() (CVE-2024-57995)
      * kernel: nfsd: clear acl_access/acl_default after releasing them (CVE-2025-21796)
      * kernel: scsi: ufs: core: Fix use-after free in init error and remove paths (CVE-2025-21739)
      * kernel: workqueue: Put the pwq after detaching the rescuer from the pool (CVE-2025-21786)
      * kernel: ata: libata-sff: Ensure that we cannot write outside the allocated buffer (CVE-2025-21738)
      * kernel: HID: core: Fix assumption that Resolution Multipliers must be in Logical Collections     (CVE-2024-57986)
      * kernel: padata: avoid UAF for reorder_work (CVE-2025-21726)
      * kernel: vrf: use RCU protection in l3mdev_l3_out() (CVE-2025-21791)
      * kernel: team: better TEAM_OPTION_TYPE_STRING validation (CVE-2025-21787)
      * kernel: usb: xhci: Fix NULL pointer dereference on certain command aborts (CVE-2024-57981)
      * kernel: vxlan: check vxlan_vnigroup_init() return value (CVE-2025-21790)
      * kernel: wifi: mt76: mt7925: fix off by one in mt7925_load_clc() (CVE-2024-57990)
      * kernel: ipv6: use RCU protection in ip6_default_advmss() (CVE-2025-21765)
      * kernel: ASoC: SOF: Intel: hda-dai: Ensure DAI widget is valid during params (CVE-2024-58012)
      * kernel: blk-cgroup: Fix class @block_class's subsystem refcount leakage (CVE-2025-21745)
      * kernel: net: let net.core.dev_weight always be non-zero (CVE-2025-21806)
      * kernel: wifi: rtlwifi: remove unused check_buddy_priv (CVE-2024-58072)
      * kernel: OPP: fix dev_pm_opp_find_bw_*() when bandwidth table not initialized (CVE-2024-58068)
      * kernel: wifi: iwlwifi: mvm: avoid NULL pointer dereference (CVE-2024-58062)
      * kernel: idpf: convert workqueues to unbound (CVE-2024-58057)
      * kernel: wifi: mac80211: don't flush non-uploaded STAs (CVE-2025-21828)
      * kernel: KVM: Explicitly verify target vCPU is online in kvm_get_vcpu() (CVE-2024-58083)
      * kernel: netfilter: nf_tables: reject mismatching sum of field_len with set key length (CVE-2025-21826)
      * kernel: ASoC: soc-pcm: don't use soc_pcm_ret() on .prepare callback (CVE-2024-58077)
      * kernel: crypto: tegra - do not transfer req when tegra init fails (CVE-2024-58075)
      * kernel: RDMA/rxe: Fix the warning __rxe_cleanup+0x12c/0x170 [rdma_rxe] (CVE-2025-21829)
      * kernel: KVM: x86: Load DR6 with guest value only before entering .vcpu_run() loop (CVE-2025-21839)
      * kernel: io_uring/uring_cmd: unconditionally copy SQEs at prep time (CVE-2025-21837)
      * kernel: information leak via transient execution vulnerability in some AMD processors (CVE-2024-36350)
      * kernel: transient execution vulnerability in some AMD processors (CVE-2024-36357)
      * kernel: bpf: Fix softlockup in arena_map_free on 64k page kernel (CVE-2025-21851)
      * kernel: ibmvnic: Don't reference skb after sending to VIOS (CVE-2025-21855)
      * kernel: smb: client: Add check for next_buffer in receive_encrypted_standard() (CVE-2025-21844)
      * kernel: bpf: avoid holding freeze_mutex during mmap operation (CVE-2025-21853)
      * kernel: ASoC: SOF: stream-ipc: Check for cstream nullity in sof_ipc_msg_data() (CVE-2025-21847)
      * kernel: tcp: drop secpath at the same time as we currently drop dst (CVE-2025-21864)
      * kernel: bpf: Fix deadlock when freeing cgroup storage (CVE-2024-58088)
      * kernel: acct: perform last write from workqueue (CVE-2025-21846)
      * kernel: mm/migrate_device: don't add folio to be freed to LRU in migrate_device_finalize()     (CVE-2025-21861)
      * kernel: io_uring: prevent opcode speculation (CVE-2025-21863)
      * kernel: nfp: bpf: Add check for nfp_app_ctrl_msg_alloc() (CVE-2025-21848)
      * kernel: netfilter: nft_tunnel: fix geneve_opt type confusion addition (CVE-2025-22056)
      * kernel: can: j1939: j1939_send_one(): fix missing CAN header initialization (CVE-2022-49845)
      * kernel: usb: typec: ucsi: displayport: Fix NULL pointer access (CVE-2025-37994)
      * kernel: wifi: ath12k: fix uaf in ath12k_core_init() (CVE-2025-38116)
      * kernel: fs: export anon_inode_make_secure_inode() and fix secretmem LSM bypass (CVE-2025-38396)

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

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

The remote Redhat Enterprise Linux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2025:20518 advisory.

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

    Security Fix(es):

    * kernel: can: isotp: fix potential CAN frame reception race in isotp_rcv() (CVE-2022-48830)

    * kernel: soc: qcom: cmd-db: Map shared memory as WC, not WB (CVE-2024-46689)

    * kernel: Squashfs: sanity check symbolic link size (CVE-2024-46744)

    * kernel: vfs: fix race between evice_inodes() and find_inode()&iput() (CVE-2024-47679)

    * kernel: x86/tdx: Fix in-kernel MMIO check (CVE-2024-47727)

    * kernel: rxrpc: Fix a race between socket set up and I/O thread creation (CVE-2024-49864)

    * kernel: io_uring: check if we need to reschedule during overflow flush (CVE-2024-50060)

    * kernel: can: m_can: pci: add missing m_can_class_free_dev() in probe/remove methods (CVE-2022-49024)

    * kernel: posix-clock: Fix missing timespec64 check in pc_clock_settime() (CVE-2024-50195)

    * kernel: rxrpc: Fix missing locking causing hanging calls (CVE-2024-50294)

    * kernel: io_uring/rw: fix missing NOWAIT check for O_DIRECT start write (CVE-2024-53052)

    * kernel: afs: Fix lock recursion (CVE-2024-53090)

    * kernel: virtio/vsock: Fix accept_queue memory leak (CVE-2024-53119)

    * kernel: KVM: VMX: Bury Intel PT virtualization (guest/host mode) behind CONFIG_BROKEN (CVE-2024-53135)

    * kernel: xen: Xen hypercall page unsafe against speculative attacks (Xen Security Advisory 466)     (CVE-2024-53241)

    * kernel: RDMA/rxe: Fix the qp flush warnings in req (CVE-2024-53229)

    * kernel: block: fix uaf for flush rq while iterating tags (CVE-2024-53170)

    * kernel: nfsd: release svc_expkey/svc_export with rcu_work (CVE-2024-53216)

    * kernel: net: af_can: do not leave a dangling sk pointer in can_create() (CVE-2024-56603)

    * kernel: blk-cgroup: Fix UAF in blkcg_unpin_online() (CVE-2024-56672)

    * kernel: acpi: nfit: vmalloc-out-of-bounds Read in acpi_nfit_ctl (CVE-2024-56662)

    * kernel: bpf: Fix UAF via mismatching bpf_prog/attachment RCU flavors (CVE-2024-56675)

    * kernel: can: j1939: j1939_session_new(): fix skb reference counting (CVE-2024-56645)

    * kernel: crypto: pcrypt - Call crypto layer directly when padata_do_parallel() return -EBUSY     (CVE-2024-56690)

    * kernel: io_uring: check if iowq is killed before queuing (CVE-2024-56709)

    * kernel: rtc: check if __rtc_read_time was successful in rtc_timer_do_work() (CVE-2024-56739)

    * kernel: bpf: put bpf_link's program when link is safe to be deallocated (CVE-2024-56786)

    * kernel: igb: Fix potential invalid memory access in igb_init_module() (CVE-2024-52332)

    * kernel: ipvs: fix UB due to uninitialized stack access in ip_vs_protocol_init() (CVE-2024-53680)

    * kernel: netfilter: conntrack: clamp maximum hashtable size to INT_MAX (CVE-2025-21648)

    * kernel: sched: sch_cake: add bounds checks to host bulk flow fairness counts (CVE-2025-21647)

    * kernel: block, bfq: fix waker_bfqq UAF after bfq_split_bfqq() (CVE-2025-21631)

    * kernel: zram: fix potential UAF of zram table (CVE-2025-21671)

    * kernel: afs: Fix merge preference rule failure condition (CVE-2025-21672)

    * kernel: mm: zswap: properly synchronize freeing resources during CPU hotunplug (CVE-2025-21693)

    * kernel: cachestat: fix page cache statistics permission checking (CVE-2025-21691)

    * kernel: mm: clear uffd-wp PTE/PMD state on mremap() (CVE-2025-21696)

    * kernel: pfifo_tail_enqueue: Drop new packet when sch->limit == 0 (CVE-2025-21702)

    * kernel: usbnet: fix memory leak in error case (CVE-2022-49657)

    * kernel: powerpc/xics: fix refcount leak in icp_opal_init() (CVE-2022-49432)

    * kernel: net: tun: unlink NAPI from device on destruction (CVE-2022-49672)

    * kernel: powerpc/papr_scm: don't requests stats with '0' sized stats buffer (CVE-2022-49353)

    * kernel: powerpc/xive: Fix refcount leak in xive_spapr_init (CVE-2022-49437)

    * kernel: ima: Fix potential memory leak in ima_init_crypto() (CVE-2022-49627)

    * kernel: linux/dim: Fix divide by 0 in RDMA DIM (CVE-2022-49670)

    * kernel: can: isotp: sanitize CAN ID checks in isotp_bind() (CVE-2022-49269)

    * kernel: ima: Fix a potential integer overflow in ima_appraise_measurement (CVE-2022-49643)

    * kernel: powerpc/xive/spapr: correct bitmap allocation size (CVE-2022-49623)

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

    * kernel: list: fix a data-race around ep->rdllist (CVE-2022-49443)

    * kernel: tracing/histograms: Fix memory leak problem (CVE-2022-49648)

    * kernel: Input: synaptics - fix crash when enabling pass-through port (CVE-2025-21746)

    * kernel: NFSD: fix hang in nfsd4_shutdown_callback (CVE-2025-21795)

    * kernel: bpf: Send signals asynchronously if !preemptible (CVE-2025-21728)

    * kernel: NFS: Fix potential buffer overflowin nfs_sysfs_link_rpc_client() (CVE-2024-54456)

    * kernel: Bluetooth: btrtl: check for NULL in btrtl_setup_realtek() (CVE-2024-57987)

    * kernel: wifi: brcmsmac: add gain range check to wlc_phy_iqcal_gainparams_nphy() (CVE-2024-58014)

    * kernel: Bluetooth: btbcm: Fix NULL deref in btbcm_get_board_name() (CVE-2024-57988)

    * kernel: RDMA/mlx5: Fix implicit ODP use after free (CVE-2025-21714)

    * kernel: drm/xe/tracing: Fix a potential TP_printk UAF (CVE-2024-49570)

    * kernel: HID: hid-thrustmaster: Fix warning in thrustmaster_probe by adding endpoint check     (CVE-2024-57993)

    * kernel: wifi: rtw89: fix race between cancel_hw_scan and hw_scan completion (CVE-2025-21729)

    * kernel: wifi: mt76: mt7925: fix NULL deref check in mt7925_change_vif_links (CVE-2024-57989)

    * kernel: wifi: ath12k: Fix for out-of bound access error (CVE-2024-58015)

    * kernel: OPP: add index check to assert to avoid buffer overflow in _read_freq() (CVE-2024-57998)

    * kernel: wifi: ath12k: fix read pointer after free in ath12k_mac_assign_vif_to_vdev() (CVE-2024-57995)

    * kernel: nfsd: clear acl_access/acl_default after releasing them (CVE-2025-21796)

    * kernel: scsi: ufs: core: Fix use-after free in init error and remove paths (CVE-2025-21739)

    * kernel: workqueue: Put the pwq after detaching the rescuer from the pool (CVE-2025-21786)

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

    * kernel: HID: core: Fix assumption that Resolution Multipliers must be in Logical Collections     (CVE-2024-57986)

    * kernel: padata: avoid UAF for reorder_work (CVE-2025-21726)

    * kernel: vrf: use RCU protection in l3mdev_l3_out() (CVE-2025-21791)

    * kernel: team: better TEAM_OPTION_TYPE_STRING validation (CVE-2025-21787)

    * kernel: usb: xhci: Fix NULL pointer dereference on certain command aborts (CVE-2024-57981)

    * kernel: vxlan: check vxlan_vnigroup_init() return value (CVE-2025-21790)

    * kernel: wifi: mt76: mt7925: fix off by one in mt7925_load_clc() (CVE-2024-57990)

    * kernel: ipv6: use RCU protection in ip6_default_advmss() (CVE-2025-21765)

    * kernel: ASoC: SOF: Intel: hda-dai: Ensure DAI widget is valid during params (CVE-2024-58012)

    * kernel: blk-cgroup: Fix class @block_class's subsystem refcount leakage (CVE-2025-21745)

    * kernel: net: let net.core.dev_weight always be non-zero (CVE-2025-21806)

    * kernel: wifi: rtlwifi: remove unused check_buddy_priv (CVE-2024-58072)

    * kernel: OPP: fix dev_pm_opp_find_bw_*() when bandwidth table not initialized (CVE-2024-58068)

    * kernel: wifi: iwlwifi: mvm: avoid NULL pointer dereference (CVE-2024-58062)

    * kernel: idpf: convert workqueues to unbound (CVE-2024-58057)

    * kernel: wifi: mac80211: don't flush non-uploaded STAs (CVE-2025-21828)

    * kernel: KVM: Explicitly verify target vCPU is online in kvm_get_vcpu() (CVE-2024-58083)

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

    * kernel: ASoC: soc-pcm: don't use soc_pcm_ret() on .prepare callback (CVE-2024-58077)

    * kernel: crypto: tegra - do not transfer req when tegra init fails (CVE-2024-58075)

    * kernel: RDMA/rxe: Fix the warning __rxe_cleanup+0x12c/0x170 [rdma_rxe] (CVE-2025-21829)

    * kernel: KVM: x86: Load DR6 with guest value only before entering .vcpu_run() loop (CVE-2025-21839)

    * kernel: io_uring/uring_cmd: unconditionally copy SQEs at prep time (CVE-2025-21837)

    * kernel: information leak via transient execution vulnerability in some AMD processors (CVE-2024-36350)

    * kernel: transient execution vulnerability in some AMD processors (CVE-2024-36357)

    * kernel: bpf: Fix softlockup in arena_map_free on 64k page kernel (CVE-2025-21851)

    * kernel: ibmvnic: Don't reference skb after sending to VIOS (CVE-2025-21855)

    * kernel: smb: client: Add check for next_buffer in receive_encrypted_standard() (CVE-2025-21844)

    * kernel: bpf: avoid holding freeze_mutex during mmap operation (CVE-2025-21853)

    * kernel: ASoC: SOF: stream-ipc: Check for cstream nullity in sof_ipc_msg_data() (CVE-2025-21847)

    * kernel: tcp: drop secpath at the same time as we currently drop dst (CVE-2025-21864)

    * kernel: bpf: Fix deadlock when freeing cgroup storage (CVE-2024-58088)

    * kernel: acct: perform last write from workqueue (CVE-2025-21846)

    * kernel: mm/migrate_device: don't add folio to be freed to LRU in migrate_device_finalize()     (CVE-2025-21861)

    * kernel: io_uring: prevent opcode speculation (CVE-2025-21863)

    * kernel: nfp: bpf: Add check for nfp_app_ctrl_msg_alloc() (CVE-2025-21848)

    * kernel: netfilter: nft_tunnel: fix geneve_opt type confusion addition (CVE-2025-22056)

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

    * kernel: usb: typec: ucsi: displayport: Fix NULL pointer access (CVE-2025-37994)

    * kernel: wifi: ath12k: fix uaf in ath12k_core_init() (CVE-2025-38116)

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

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

    Additional Changes:

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

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux security advisory.

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

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

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

    can: isotp: sanitize CAN ID checks in isotp_bind()

    Syzbot created an environment that lead to a state machine status that     can not be reached with a compliant CAN ID address configuration.
    The provided address information consisted of CAN ID 0x6000001 and 0xC28001     which both boil down to 11 bit CAN IDs 0x001 in sending and receiving.

    Sanitize the SFF/EFF CAN ID values before performing the address checks.

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

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

    can: isotp: sanitize CAN ID checks in isotp_bind()

    Syzbot created an environment that lead to a state machine status that     can not be reached with a compliant CAN ID address configuration.
    The provided address information consisted of CAN ID 0x6000001 and 0xC28001     which both boil down to 11 bit CAN IDs 0x001 in sending and receiving.

    Sanitize the SFF/EFF CAN ID values before performing the address checks.

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

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

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

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

    The following security bugs were fixed:

    - CVE-2022-49053: scsi: target: tcmu: Fix possible page UAF (bsc#1237918).
    - CVE-2022-49465: blk-throttle: Set BIO_THROTTLED when bio has been throttled (bsc#1238919).
    - CVE-2022-49739: gfs2: Always check inode size of inline inodes (bsc#1240207).
    - CVE-2023-52935: mm/khugepaged: fix ->anon_vma race (bsc#1240276).
    - CVE-2024-53124: net: fix data-races around sk->sk_forward_alloc (bsc#1234074).
    - CVE-2024-53176: smb: During unmount, ensure all cached dir instances drop their dentry (bsc#1234894).
    - CVE-2024-53178: smb: Do not leak cfid when reconnect races with open_cached_dir (bsc#1234895).
    - CVE-2024-56651: can: hi311x: hi3110_can_ist(): fix potential use-after-free (bsc#1235528).
    - CVE-2024-57996: net_sched: sch_sfq: do not allow 1 packet limit (bsc#1239076).
    - CVE-2024-58013: Bluetooth: MGMT: Fix slab-use-after-free Read in mgmt_remove_adv_monitor_sync     (bsc#1239095).
    - CVE-2024-58014: wifi: brcmsmac: add gain range check to wlc_phy_iqcal_gainparams_nphy() (bsc#1239109).
    - CVE-2025-21693: mm: zswap: properly synchronize freeing resources during CPU hotunplug (bsc#1237029).
    - CVE-2025-21718: net: rose: fix timer races against user threads (bsc#1239073).
    - CVE-2025-21772: partitions: mac: fix handling of bogus partition table (bsc#1238911).
    - CVE-2025-21780: drm/amdgpu: avoid buffer overflow attach in smu_sys_set_pp_table() (bsc#1239115).


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:1027-1 advisory.

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


    The following security bugs were fixed:

    - CVE-2024-2201: Fixed information leak in x86/BHI (bsc#1217339).
    - CVE-2024-41092: drm/i915/gt: Fix potential UAF by revoke of fence registers (bsc#1228483).
    - CVE-2024-42098: crypto: ecdh - explicitly zeroize private_key (bsc#1228779).
    - CVE-2024-42229: crypto: aead,cipher - zeroize key buffer after use (bsc#1228708).
    - CVE-2024-57996: net_sched: sch_sfq: do not allow 1 packet limit (bsc#1239076).
    - CVE-2024-58014: wifi: brcmsmac: add gain range check to wlc_phy_iqcal_gainparams_nphy() (bsc#1239109).
    - CVE-2025-21718: net: rose: fix timer races against user threads (bsc#1239073).
    - CVE-2025-21780: drm/amdgpu: avoid buffer overflow attach in smu_sys_set_pp_table() (bsc#1239115).


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 CentOS Linux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the kernel-5.14.0-573.el9 build changelog.

  - In the Linux kernel, the following vulnerability has been resolved: scsi: sg: Fix slab-use-after-free read     in sg_release() Fix a use-after-free bug in sg_release(), detected by syzbot with KASAN: BUG: KASAN: slab-     use-after-free in lock_release+0x151/0xa30 kernel/locking/lockdep.c:5838
    __mutex_unlock_slowpath+0xe2/0x750 kernel/locking/mutex.c:912 sg_release+0x1f4/0x2e0 drivers/scsi/sg.c:407     In sg_release(), the function kref_put(&sfp->f_ref, sg_remove_sfp) is called before releasing the     open_rel_lock mutex. The kref_put() call may decrement the reference count of sfp to zero, triggering its     cleanup through sg_remove_sfp(). This cleanup includes scheduling deferred work via     sg_remove_sfp_usercontext(), which ultimately frees sfp. After kref_put(), sg_release() continues to     unlock open_rel_lock and may reference sfp or sdp. If sfp has already been freed, this results in a slab-     use-after-free error. Move the kref_put(&sfp->f_ref, sg_remove_sfp) call after unlocking the open_rel_lock     mutex. This ensures: - No references to sfp or sdp occur after the reference count is decremented. -     Cleanup functions such as sg_remove_sfp() and sg_remove_sfp_usercontext() can safely execute without     impacting the mutex handling in sg_release(). The fix has been tested and validated by syzbot. This patch     closes the bug reported at the following syzkaller link and ensures proper sequencing of resource cleanup     and mutex operations, eliminating the risk of use-after-free errors in sg_release(). (CVE-2024-56631)

  - In the Linux kernel, the following vulnerability has been resolved: can: isotp: sanitize CAN ID checks in     isotp_bind() Syzbot created an environment that lead to a state machine status that can not be reached     with a compliant CAN ID address configuration. The provided address information consisted of CAN ID     0x6000001 and 0xC28001 which both boil down to 11 bit CAN IDs 0x001 in sending and receiving. Sanitize the     SFF/EFF CAN ID values before performing the address checks. (CVE-2022-49269)

  - In the Linux kernel, the following vulnerability has been resolved: can: bcm: Fix UAF in bcm_proc_show()     BUG: KASAN: slab-use-after-free in bcm_proc_show+0x969/0xa80 Read of size 8 at addr ffff888155846230 by     task cat/7862 CPU: 1 PID: 7862 Comm: cat Not tainted 6.5.0-rc1-00153-gc8746099c197 #230 Hardware name:
    QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014 Call Trace: <TASK>     dump_stack_lvl+0xd5/0x150 print_report+0xc1/0x5e0 kasan_report+0xba/0xf0 bcm_proc_show+0x969/0xa80     seq_read_iter+0x4f6/0x1260 seq_read+0x165/0x210 proc_reg_read+0x227/0x300 vfs_read+0x1d5/0x8d0     ksys_read+0x11e/0x240 do_syscall_64+0x35/0xb0 entry_SYSCALL_64_after_hwframe+0x63/0xcd Allocated by task     7846: kasan_save_stack+0x1e/0x40 kasan_set_track+0x21/0x30 __kasan_kmalloc+0x9e/0xa0     bcm_sendmsg+0x264b/0x44e0 sock_sendmsg+0xda/0x180 ____sys_sendmsg+0x735/0x920 ___sys_sendmsg+0x11d/0x1b0
    __sys_sendmsg+0xfa/0x1d0 do_syscall_64+0x35/0xb0 entry_SYSCALL_64_after_hwframe+0x63/0xcd Freed by task     7846: kasan_save_stack+0x1e/0x40 kasan_set_track+0x21/0x30 kasan_save_free_info+0x27/0x40
    ____kasan_slab_free+0x161/0x1c0 slab_free_freelist_hook+0x119/0x220 __kmem_cache_free+0xb4/0x2e0     rcu_core+0x809/0x1bd0 bcm_op is freed before procfs entry be removed in bcm_release(), this lead to     bcm_proc_show() may read the freed bcm_op. (CVE-2023-52922)

  - In the Linux kernel, the following vulnerability has been resolved: x86/xen: don't do PV iret hypercall     through hypercall page Instead of jumping to the Xen hypercall page for doing the iret hypercall, directly     code the required sequence in xen-asm.S. This is done in preparation of no longer using hypercall page at     all, as it has shown to cause problems with speculation mitigations. This is part of XSA-466 /     CVE-2024-53241. (CVE-2024-53241)

  - In the Linux kernel, the following vulnerability has been resolved: scsi: megaraid_sas: Fix for a     potential deadlock This fixes a 'possible circular locking dependency detected' warning CPU0 CPU1 ----
    ---- lock(&instance->reset_mutex); lock(&shost->scan_mutex); lock(&instance->reset_mutex);
    lock(&shost->scan_mutex); Fix this by temporarily releasing the reset_mutex. (CVE-2024-57807)

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: can: isotp: sanitize CAN ID checks in     isotp_bind() Syzbot created an environment that lead to a state machine status that can not be reached     with a compliant CAN ID address configuration. The provided address information consisted of CAN ID     0x6000001 and 0xC28001 which both boil down to 11 bit CAN IDs 0x001 in sending and receiving. Sanitize the     SFF/EFF CAN ID values before performing the address checks. (CVE-2022-49269)

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

An update of the linux package has been released.

ID	Name	Product	Family	Type	Severity
360243	AlmaLinux 9.6 [TuxCare] Security Update: kernel / kernel-abi-stablelists / kernel-core / etc Multiple Vulnerabilities (ALMALINUX9.6:CLSA-2026:1783091784)	Nessus	Alma Linux Local Security Checks	Local	medium
360066	Rocky Linux 9.6 [TuxCare] Security Update: kernel / kernel-abi-stablelists / kernel-core / etc Multiple Vulnerabilities (ALMALINUX9.6:CLSA-2026:1783091784)	Nessus	Rocky Linux Local Security Checks	Local	medium
357988	Rocky Linux 9 [CIQ] Security Update: kernel / kernel-64k / kernel-64k-core / kernel-64k-debug / etc Multiple Vulnerabilities (crlsa-2025_20518)	Nessus	Rocky Linux Local Security Checks	Local	high
352871	AlmaLinux 9.2 [TuxCare] Security Update: bpftool / kernel / kernel-abi-stablelists / kernel-core / etc Multiple Vulnerabilities (ALMALINUX9.2:CLSA-2026:1783791447)	Nessus	Alma Linux Local Security Checks	Local	medium
282807	MiracleLinux 9 : kernel-5.14.0-611.5.1.el9_7 (AXSA:2025-11493:94)	Nessus	Miracle Linux Local Security Checks	Local	high
277164	RockyLinux 9 : kernel (RLSA-2025:20518)	Nessus	Rocky Linux Local Security Checks	Local	high
276689	Oracle Linux 9 : ELSA-2025-20518-0: / kernel (ELSA-2025-205180)	Nessus	Oracle Linux Local Security Checks	Local	high
275824	AlmaLinux 9 : kernel (ALSA-2025:20518)	Nessus	Alma Linux Local Security Checks	Local	high
274839	RHEL 9 : kernel (RHSA-2025:20518)	Nessus	Red Hat Local Security Checks	Local	high
273855	Unity Linux 20.1070a Security Update: kernel (UTSA-2025-988989)	Nessus	Unity Linux Local Security Checks	Local	medium
273711	Unity Linux 20.1070e Security Update: kernel (UTSA-2025-989451)	Nessus	Unity Linux Local Security Checks	Local	medium
234407	SUSE SLES15 : Security update for the Linux Kernel (SUSE-SU-2025:1241-1)	Nessus	SuSE Local Security Checks	Local	high
233410	SUSE SLES15: cluster-md-kmp-default / dlm-kmp-default / gfs2-kmp-default / etc (SUSE-SU-2025:1027-1)	Nessus	SuSE Local Security Checks	Local	high
233298	CentOS 9 : kernel-5.14.0-573.el9	Nessus	CentOS Local Security Checks	Local	high
225403	Linux Distros Unpatched Vulnerability : CVE-2022-49269	Nessus	Misc.	Local	medium
151965	Photon OS 4.0: Linux PHSA-2021-4.0-0065	Nessus	PhotonOS Local Security Checks	Local	high

Detections

Analytics

CVE-2022-49269

medium

Tenable Plugins

medium

medium

high

medium

high

high

high

high

high

medium

medium

high

high

high

medium

high