In the Linux kernel, the following vulnerability has been resolved: serial: imx: Add missing .thaw_noirq hook The following warning is seen with non-console UART instance when system hibernates. [ 37.371969] ------------[ cut here ]------------ [ 37.376599] uart3_root_clk already disabled [ 37.380810] WARNING: CPU: 0 PID: 296 at drivers/clk/clk.c:952 clk_core_disable+0xa4/0xb0 ... [ 37.506986] Call trace: [ 37.509432] clk_core_disable+0xa4/0xb0 [ 37.513270] clk_disable+0x34/0x50 [ 37.516672] imx_uart_thaw+0x38/0x5c [ 37.520250] platform_pm_thaw+0x30/0x6c [ 37.524089] dpm_run_callback.constprop.0+0x3c/0xd4 [ 37.528972] device_resume+0x7c/0x160 [ 37.532633] dpm_resume+0xe8/0x230 [ 37.536036] hibernation_snapshot+0x288/0x430 [ 37.540397] hibernate+0x10c/0x2e0 [ 37.543798] state_store+0xc4/0xd0 [ 37.547203] kobj_attr_store+0x1c/0x30 [ 37.550953] sysfs_kf_write+0x48/0x60 [ 37.554619] kernfs_fop_write_iter+0x118/0x1ac [ 37.559063] new_sync_write+0xe8/0x184 [ 37.562812] vfs_write+0x230/0x290 [ 37.566214] ksys_write+0x68/0xf4 [ 37.569529] __arm64_sys_write+0x20/0x2c [ 37.573452] invoke_syscall.constprop.0+0x50/0xf0 [ 37.578156] do_el0_svc+0x11c/0x150 [ 37.581648] el0_svc+0x30/0x140 [ 37.584792] el0t_64_sync_handler+0xe8/0xf0 [ 37.588976] el0t_64_sync+0x1a0/0x1a4 [ 37.592639] ---[ end trace 56e22eec54676d75 ]--- On hibernating, pm core calls into related hooks in sequence like: .freeze .freeze_noirq .thaw_noirq .thaw With .thaw_noirq hook being absent, the clock will be disabled in a unbalanced call which results the warning above. imx_uart_freeze() clk_prepare_enable() imx_uart_suspend_noirq() clk_disable() imx_uart_thaw clk_disable_unprepare() Adding the missing .thaw_noirq hook as imx_uart_resume_noirq() will have the call sequence corrected as below and thus fix the warning. imx_uart_freeze() clk_prepare_enable() imx_uart_suspend_noirq() clk_disable() imx_uart_resume_noirq() clk_enable() imx_uart_thaw clk_disable_unprepare()

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

  - In the Linux kernel, the following vulnerability has been resolved: xprtrdma: treat all calls not a bcall     when bc_serv is NULL When a rdma server returns a fault format reply, nfs v3 client may treats it as a     bcall when bc service is not exist. The debug message at rpcrdma_bc_receive_call are, [56579.837169] RPC:
    rpcrdma_bc_receive_call: callback XID 00000001, length=20 [56579.837174] RPC: rpcrdma_bc_receive_call: 00     00 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 04 After that, rpcrdma_bc_receive_call will meets     NULL pointer as, [ 226.057890] BUG: unable to handle kernel NULL pointer dereference at 00000000000000c8     ... [ 226.058704] RIP: 0010:_raw_spin_lock+0xc/0x20 ... [ 226.059732] Call Trace: [ 226.059878]     rpcrdma_bc_receive_call+0x138/0x327 [rpcrdma] [ 226.060011] __ib_process_cq+0x89/0x170 [ib_core] [     226.060092] ib_cq_poll_work+0x26/0x80 [ib_core] [ 226.060257] process_one_work+0x1a7/0x360 [ 226.060367] ?     create_worker+0x1a0/0x1a0 [ 226.060440] worker_thread+0x30/0x390 [ 226.060500] ? create_worker+0x1a0/0x1a0     [ 226.060574] kthread+0x116/0x130 [ 226.060661] ? kthread_flush_work_fn+0x10/0x10 [ 226.060724]     ret_from_fork+0x35/0x40 ... (CVE-2022-49321)

  - In the Linux kernel, the following vulnerability has been resolved: af_unix: Fix a data-race in     unix_dgram_peer_wake_me(). unix_dgram_poll() calls unix_dgram_peer_wake_me() without `other`'s lock held     and check if its receive queue is full. Here we need to use unix_recvq_full_lockless() instead of     unix_recvq_full(), otherwise KCSAN will report a data-race. (CVE-2022-49344)

  - In the Linux kernel, the following vulnerability has been resolved: x86/MCE/AMD: Fix memory leak when     threshold_create_bank() fails In mce_threshold_create_device(), if threshold_create_bank() fails, the     previously allocated threshold banks array @bp will be leaked because the call to     mce_threshold_remove_device() will not free it. This happens because mce_threshold_remove_device() fetches     the pointer through the threshold_banks per-CPU variable but bp is written there only after the bank     creation is successful, and not before, when threshold_create_bank() fails. Add a helper which unwinds all     the bank creation work previously done and pass into it the previously allocated threshold banks array for     freeing. [ bp: Massage. ] (CVE-2022-49549)

  - In the Linux kernel, the following vulnerability has been resolved: mm/mempolicy: fix uninit-value in     mpol_rebind_policy() mpol_set_nodemask()(mm/mempolicy.c) does not set up nodemask when pol->mode is     MPOL_LOCAL. Check pol->mode before access pol->w.cpuset_mems_allowed in     mpol_rebind_policy()(mm/mempolicy.c). BUG: KMSAN: uninit-value in mpol_rebind_policy mm/mempolicy.c:352     [inline] BUG: KMSAN: uninit-value in mpol_rebind_task+0x2ac/0x2c0 mm/mempolicy.c:368 mpol_rebind_policy     mm/mempolicy.c:352 [inline] mpol_rebind_task+0x2ac/0x2c0 mm/mempolicy.c:368 cpuset_change_task_nodemask     kernel/cgroup/cpuset.c:1711 [inline] cpuset_attach+0x787/0x15e0 kernel/cgroup/cpuset.c:2278     cgroup_migrate_execute+0x1023/0x1d20 kernel/cgroup/cgroup.c:2515 cgroup_migrate     kernel/cgroup/cgroup.c:2771 [inline] cgroup_attach_task+0x540/0x8b0 kernel/cgroup/cgroup.c:2804
    __cgroup1_procs_write+0x5cc/0x7a0 kernel/cgroup/cgroup-v1.c:520 cgroup1_tasks_write+0x94/0xb0     kernel/cgroup/cgroup-v1.c:539 cgroup_file_write+0x4c2/0x9e0 kernel/cgroup/cgroup.c:3852     kernfs_fop_write_iter+0x66a/0x9f0 fs/kernfs/file.c:296 call_write_iter include/linux/fs.h:2162 [inline]     new_sync_write fs/read_write.c:503 [inline] vfs_write+0x1318/0x2030 fs/read_write.c:590     ksys_write+0x28b/0x510 fs/read_write.c:643 __do_sys_write fs/read_write.c:655 [inline] __se_sys_write     fs/read_write.c:652 [inline] __x64_sys_write+0xdb/0x120 fs/read_write.c:652 do_syscall_x64     arch/x86/entry/common.c:51 [inline] do_syscall_64+0x54/0xd0 arch/x86/entry/common.c:82     entry_SYSCALL_64_after_hwframe+0x44/0xae Uninit was created at: slab_post_alloc_hook mm/slab.h:524     [inline] slab_alloc_node mm/slub.c:3251 [inline] slab_alloc mm/slub.c:3259 [inline]     kmem_cache_alloc+0x902/0x11c0 mm/slub.c:3264 mpol_new mm/mempolicy.c:293 [inline]     do_set_mempolicy+0x421/0xb70 mm/mempolicy.c:853 kernel_set_mempolicy mm/mempolicy.c:1504 [inline]
    __do_sys_set_mempolicy mm/mempolicy.c:1510 [inline] __se_sys_set_mempolicy+0x44c/0xb60 mm/mempolicy.c:1507
    __x64_sys_set_mempolicy+0xd8/0x110 mm/mempolicy.c:1507 do_syscall_x64 arch/x86/entry/common.c:51 [inline]     do_syscall_64+0x54/0xd0 arch/x86/entry/common.c:82 entry_SYSCALL_64_after_hwframe+0x44/0xae KMSAN: uninit-     value in mpol_rebind_task (2)     https://syzkaller.appspot.com/bug?id=d6eb90f952c2a5de9ea718a1b873c55cb13b59dc This patch seems to fix     below bug too. KMSAN: uninit-value in mpol_rebind_mm (2)     https://syzkaller.appspot.com/bug?id=f2fecd0d7013f54ec4162f60743a2b28df40926b The uninit-value is     pol->w.cpuset_mems_allowed in mpol_rebind_policy(). When syzkaller reproducer runs to the beginning of     mpol_new(), mpol_new() mm/mempolicy.c do_mbind() mm/mempolicy.c kernel_mbind() mm/mempolicy.c `mode` is     1(MPOL_PREFERRED), nodes_empty(*nodes) is `true` and `flags` is 0. Then mode = MPOL_LOCAL; ...
    policy->mode = mode; policy->flags = flags; will be executed. So in mpol_set_nodemask(),     mpol_set_nodemask() mm/mempolicy.c do_mbind() kernel_mbind() pol->mode is 4 (MPOL_LOCAL), that `nodemask`     in `pol` is not initialized, which will be accessed in mpol_rebind_policy(). (CVE-2022-49567)

  - In the Linux kernel, the following vulnerability has been resolved: i2c: piix4: Fix a memory leak in the     EFCH MMIO support The recently added support for EFCH MMIO regions introduced a memory leak in that code     path. The leak is caused by the fact that release_resource() merely removes the resource from the tree but     does not free its memory. We need to call release_mem_region() instead, which does free the memory. As a     nice side effect, this brings back some symmetry between the legacy and MMIO paths. (CVE-2022-49653)

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

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

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

    serial: imx: Add missing .thaw_noirq hook

    The following warning is seen with non-console UART instance when     system hibernates.

    [   37.371969] ------------[ cut here ]------------     [   37.376599] uart3_root_clk already disabled     [   37.380810] WARNING: CPU: 0 PID: 296 at drivers/clk/clk.c:952 clk_core_disable+0xa4/0xb0     ...
    [   37.506986] Call trace:
    [   37.509432]  clk_core_disable+0xa4/0xb0     [   37.513270]  clk_disable+0x34/0x50     [   37.516672]  imx_uart_thaw+0x38/0x5c     [   37.520250]  platform_pm_thaw+0x30/0x6c     [   37.524089]  dpm_run_callback.constprop.0+0x3c/0xd4     [   37.528972]  device_resume+0x7c/0x160     [   37.532633]  dpm_resume+0xe8/0x230     [   37.536036]  hibernation_snapshot+0x288/0x430     [   37.540397]  hibernate+0x10c/0x2e0     [   37.543798]  state_store+0xc4/0xd0     [   37.547203]  kobj_attr_store+0x1c/0x30     [   37.550953]  sysfs_kf_write+0x48/0x60     [   37.554619]  kernfs_fop_write_iter+0x118/0x1ac     [   37.559063]  new_sync_write+0xe8/0x184     [   37.562812]  vfs_write+0x230/0x290     [   37.566214]  ksys_write+0x68/0xf4     [   37.569529]  __arm64_sys_write+0x20/0x2c     [   37.573452]  invoke_syscall.constprop.0+0x50/0xf0     [   37.578156]  do_el0_svc+0x11c/0x150     [   37.581648]  el0_svc+0x30/0x140     [   37.584792]  el0t_64_sync_handler+0xe8/0xf0     [   37.588976]  el0t_64_sync+0x1a0/0x1a4     [   37.592639] ---[ end trace 56e22eec54676d75 ]---

    On hibernating, pm core calls into related hooks in sequence like:

        .freeze         .freeze_noirq         .thaw_noirq         .thaw

    With .thaw_noirq hook being absent, the clock will be disabled in a     unbalanced call which results the warning above.

        imx_uart_freeze()             clk_prepare_enable()         imx_uart_suspend_noirq()             clk_disable()         imx_uart_thaw             clk_disable_unprepare()

    Adding the missing .thaw_noirq hook as imx_uart_resume_noirq() will have     the call sequence corrected as below and thus fix the warning.

        imx_uart_freeze()             clk_prepare_enable()         imx_uart_suspend_noirq()             clk_disable()         imx_uart_resume_noirq()             clk_enable()         imx_uart_thaw             clk_disable_unprepare()

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

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

    serial: imx: Add missing .thaw_noirq hook

    The following warning is seen with non-console UART instance when     system hibernates.

    [   37.371969] ------------[ cut here ]------------     [   37.376599] uart3_root_clk already disabled     [   37.380810] WARNING: CPU: 0 PID: 296 at drivers/clk/clk.c:952 clk_core_disable+0xa4/0xb0     ...
    [   37.506986] Call trace:
    [   37.509432]  clk_core_disable+0xa4/0xb0     [   37.513270]  clk_disable+0x34/0x50     [   37.516672]  imx_uart_thaw+0x38/0x5c     [   37.520250]  platform_pm_thaw+0x30/0x6c     [   37.524089]  dpm_run_callback.constprop.0+0x3c/0xd4     [   37.528972]  device_resume+0x7c/0x160     [   37.532633]  dpm_resume+0xe8/0x230     [   37.536036]  hibernation_snapshot+0x288/0x430     [   37.540397]  hibernate+0x10c/0x2e0     [   37.543798]  state_store+0xc4/0xd0     [   37.547203]  kobj_attr_store+0x1c/0x30     [   37.550953]  sysfs_kf_write+0x48/0x60     [   37.554619]  kernfs_fop_write_iter+0x118/0x1ac     [   37.559063]  new_sync_write+0xe8/0x184     [   37.562812]  vfs_write+0x230/0x290     [   37.566214]  ksys_write+0x68/0xf4     [   37.569529]  __arm64_sys_write+0x20/0x2c     [   37.573452]  invoke_syscall.constprop.0+0x50/0xf0     [   37.578156]  do_el0_svc+0x11c/0x150     [   37.581648]  el0_svc+0x30/0x140     [   37.584792]  el0t_64_sync_handler+0xe8/0xf0     [   37.588976]  el0t_64_sync+0x1a0/0x1a4     [   37.592639] ---[ end trace 56e22eec54676d75 ]---

    On hibernating, pm core calls into related hooks in sequence like:

        .freeze         .freeze_noirq         .thaw_noirq         .thaw

    With .thaw_noirq hook being absent, the clock will be disabled in a     unbalanced call which results the warning above.

        imx_uart_freeze()             clk_prepare_enable()         imx_uart_suspend_noirq()             clk_disable()         imx_uart_thaw             clk_disable_unprepare()

    Adding the missing .thaw_noirq hook as imx_uart_resume_noirq() will have     the call sequence corrected as below and thus fix the warning.

        imx_uart_freeze()             clk_prepare_enable()         imx_uart_suspend_noirq()             clk_disable()         imx_uart_resume_noirq()             clk_enable()         imx_uart_thaw             clk_disable_unprepare()

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

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

    serial: imx: Add missing .thaw_noirq hook

    The following warning is seen with non-console UART instance when     system hibernates.

    [   37.371969] ------------[ cut here ]------------     [   37.376599] uart3_root_clk already disabled     [   37.380810] WARNING: CPU: 0 PID: 296 at drivers/clk/clk.c:952 clk_core_disable+0xa4/0xb0     ...
    [   37.506986] Call trace:
    [   37.509432]  clk_core_disable+0xa4/0xb0     [   37.513270]  clk_disable+0x34/0x50     [   37.516672]  imx_uart_thaw+0x38/0x5c     [   37.520250]  platform_pm_thaw+0x30/0x6c     [   37.524089]  dpm_run_callback.constprop.0+0x3c/0xd4     [   37.528972]  device_resume+0x7c/0x160     [   37.532633]  dpm_resume+0xe8/0x230     [   37.536036]  hibernation_snapshot+0x288/0x430     [   37.540397]  hibernate+0x10c/0x2e0     [   37.543798]  state_store+0xc4/0xd0     [   37.547203]  kobj_attr_store+0x1c/0x30     [   37.550953]  sysfs_kf_write+0x48/0x60     [   37.554619]  kernfs_fop_write_iter+0x118/0x1ac     [   37.559063]  new_sync_write+0xe8/0x184     [   37.562812]  vfs_write+0x230/0x290     [   37.566214]  ksys_write+0x68/0xf4     [   37.569529]  __arm64_sys_write+0x20/0x2c     [   37.573452]  invoke_syscall.constprop.0+0x50/0xf0     [   37.578156]  do_el0_svc+0x11c/0x150     [   37.581648]  el0_svc+0x30/0x140     [   37.584792]  el0t_64_sync_handler+0xe8/0xf0     [   37.588976]  el0t_64_sync+0x1a0/0x1a4     [   37.592639] ---[ end trace 56e22eec54676d75 ]---

    On hibernating, pm core calls into related hooks in sequence like:

        .freeze         .freeze_noirq         .thaw_noirq         .thaw

    With .thaw_noirq hook being absent, the clock will be disabled in a     unbalanced call which results the warning above.

        imx_uart_freeze()             clk_prepare_enable()         imx_uart_suspend_noirq()             clk_disable()         imx_uart_thaw             clk_disable_unprepare()

    Adding the missing .thaw_noirq hook as imx_uart_resume_noirq() will have     the call sequence corrected as below and thus fix the warning.

        imx_uart_freeze()             clk_prepare_enable()         imx_uart_suspend_noirq()             clk_disable()         imx_uart_resume_noirq()             clk_enable()         imx_uart_thaw             clk_disable_unprepare()

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

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

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

  - In the Linux kernel, the following vulnerability has been resolved: serial: imx: Add missing .thaw_noirq     hook The following warning is seen with non-console UART instance when system hibernates. [ 37.371969]
    ------------[ cut here ]------------ [ 37.376599] uart3_root_clk already disabled [ 37.380810] WARNING:
    CPU: 0 PID: 296 at drivers/clk/clk.c:952 clk_core_disable+0xa4/0xb0 ... [ 37.506986] Call trace: [     37.509432] clk_core_disable+0xa4/0xb0 [ 37.513270] clk_disable+0x34/0x50 [ 37.516672]     imx_uart_thaw+0x38/0x5c [ 37.520250] platform_pm_thaw+0x30/0x6c [ 37.524089]     dpm_run_callback.constprop.0+0x3c/0xd4 [ 37.528972] device_resume+0x7c/0x160 [ 37.532633]     dpm_resume+0xe8/0x230 [ 37.536036] hibernation_snapshot+0x288/0x430 [ 37.540397] hibernate+0x10c/0x2e0 [     37.543798] state_store+0xc4/0xd0 [ 37.547203] kobj_attr_store+0x1c/0x30 [ 37.550953]     sysfs_kf_write+0x48/0x60 [ 37.554619] kernfs_fop_write_iter+0x118/0x1ac [ 37.559063]     new_sync_write+0xe8/0x184 [ 37.562812] vfs_write+0x230/0x290 [ 37.566214] ksys_write+0x68/0xf4 [     37.569529] __arm64_sys_write+0x20/0x2c [ 37.573452] invoke_syscall.constprop.0+0x50/0xf0 [ 37.578156]     do_el0_svc+0x11c/0x150 [ 37.581648] el0_svc+0x30/0x140 [ 37.584792] el0t_64_sync_handler+0xe8/0xf0 [     37.588976] el0t_64_sync+0x1a0/0x1a4 [ 37.592639] ---[ end trace 56e22eec54676d75 ]--- On hibernating, pm     core calls into related hooks in sequence like: .freeze .freeze_noirq .thaw_noirq .thaw With .thaw_noirq     hook being absent, the clock will be disabled in a unbalanced call which results the warning above.
    imx_uart_freeze() clk_prepare_enable() imx_uart_suspend_noirq() clk_disable() imx_uart_thaw     clk_disable_unprepare() Adding the missing .thaw_noirq hook as imx_uart_resume_noirq() will have the call     sequence corrected as below and thus fix the warning. imx_uart_freeze() clk_prepare_enable()     imx_uart_suspend_noirq() clk_disable() imx_uart_resume_noirq() clk_enable() imx_uart_thaw     clk_disable_unprepare() (CVE-2022-49841)

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

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

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

    The following security bugs were fixed:

    - CVE-2022-49110: netfilter: conntrack: revisit gc autotuning (bsc#1237981).
    - CVE-2022-49139: Bluetooth: fix null ptr deref on hci_sync_conn_complete_evt (bsc#1238032).
    - CVE-2022-49767: 9p/trans_fd: always use O_NONBLOCK read/write (bsc#1242493).
    - CVE-2022-49775: tcp: cdg: allow tcp_cdg_release() to be called multiple times (bsc#1242245).
    - CVE-2022-49858: octeontx2-pf: Fix SQE threshold checking (bsc#1242589).
    - CVE-2023-53058: net/mlx5: E-Switch, Fix an Oops in error handling code (bsc#1242237).
    - CVE-2023-53060: igb: revert rtnl_lock() that causes deadlock (bsc#1242241).
    - CVE-2023-53064: iavf: Fix hang on reboot with ice (bsc#1242222).
    - CVE-2023-53066: qed/qed_sriov: guard against NULL derefs from qed_iov_get_vf_info (bsc#1242227).
    - CVE-2023-53079: net/mlx5: Fix steering rules cleanup (bsc#1242765).
    - CVE-2023-53114: i40e: Fix kernel crash during reboot when adapter is in recovery mode (bsc#1242398).
    - CVE-2023-53134: bnxt_en: Avoid order-5 memory allocation for TPA data (bsc#1242380)
    - CVE-2024-53168: net: make sock_inuse_add() available (bsc#1234887).
    - CVE-2024-56558: nfsd: make sure exp active before svc_export_show (bsc#1235100).
    - CVE-2025-21888: RDMA/mlx5: Fix a WARN during dereg_mr for DM type (bsc#1240177).
    - CVE-2025-21999: proc: fix UAF in proc_get_inode() (bsc#1240802).
    - CVE-2025-22056: netfilter: nft_tunnel: fix geneve_opt type confusion addition (bsc#1241525).
    - CVE-2025-22060: net: mvpp2: Prevent parser TCAM memory corruption (bsc#1241526).
    - CVE-2025-23138: watch_queue: fix pipe accounting mismatch (bsc#1241648).
    - CVE-2025-23145: mptcp: fix NULL pointer in can_accept_new_subflow (bsc#1242596).
    - CVE-2025-37785: ext4: fix OOB read when checking dotdot dir (bsc#1241640).
    - CVE-2025-37789: net: openvswitch: fix nested key length validation in the set() action (bsc#1242762).


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

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


    The following security bugs were fixed:

    - CVE-2022-49775: tcp: cdg: allow tcp_cdg_release() to be called multiple times (bsc#1242245).
    - CVE-2024-53168: net: make sock_inuse_add() available (bsc#1234887).
    - CVE-2024-56558: nfsd: make sure exp active before svc_export_show (bsc#1235100).
    - CVE-2025-21999: proc: fix UAF in proc_get_inode() (bsc#1240802).
    - CVE-2025-22056: netfilter: nft_tunnel: fix geneve_opt type confusion addition (bsc#1241525).
    - CVE-2025-23145: mptcp: fix NULL pointer in can_accept_new_subflow (bsc#1242596).
    - CVE-2025-37789: net: openvswitch: fix nested key length validation in the set() action (bsc#1242762).
    - CVE-2024-28956: x86/its: Add support for ITS-safe indirect thunk (bsc#1242006).
    - CVE-2025-37785: ext4: fix OOB read when checking dotdot dir (bsc#1241640).


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

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


    The following security bugs were fixed:

    - CVE-2021-32399: Fixed a race condition when removing the HCI controller (bsc#1184611).
    - CVE-2022-49110: netfilter: conntrack: revisit gc autotuning (bsc#1237981).
    - CVE-2022-49139: Bluetooth: fix null ptr deref on hci_sync_conn_complete_evt (bsc#1238032).
    - CVE-2022-49320: dmaengine: zynqmp_dma: In struct zynqmp_dma_chan fix desc_size data type (bsc#1238394).
    - CVE-2022-49767: 9p/trans_fd: always use O_NONBLOCK read/write (bsc#1242493).
    - CVE-2022-49769: gfs2: Check sb_bsize_shift after reading superblock (bsc#1242440).
    - CVE-2022-49770: ceph: avoid putting the realm twice when decoding snaps fails (bsc#1242597).
    - CVE-2022-49775: tcp: cdg: allow tcp_cdg_release() to be called multiple times (bsc#1242245).
    - CVE-2022-49789: scsi: zfcp: Fix double free of FSF request when qdio send fails (bsc#1242366).
    - CVE-2023-53039: HID: intel-ish-hid: ipc: Fix potential use-after-free in work function (bsc#1242745).
    - CVE-2024-53168: net: make sock_inuse_add() available (bsc#1234887).
    - CVE-2024-56558: nfsd: make sure exp active before svc_export_show (bsc#1235100).
    - CVE-2024-56705: media: atomisp: add check for rgby_data memory allocation failure (bsc#1235568).
    - CVE-2025-21812: ax25: rcu protect dev->ax25_ptr (bsc#1238471).
    - CVE-2025-21999: proc: fix UAF in proc_get_inode() (bsc#1240802).
    - CVE-2025-22028: media: vimc: skip .s_stream() for stopped entities (bsc#1241362).
    - CVE-2025-22121: ext4: fix out-of-bound read in ext4_xattr_inode_dec_ref_all() (bsc#1241593).
    - CVE-2025-37789: net: openvswitch: fix nested key length validation in the set() action (bsc#1242762).
    - CVE-2025-37846: arm64: mops: Do not dereference src reg for a set operation (bsc#1242963).
    - CVE-2025-40364: io_uring: fix io_req_prep_async with provided buffers (bsc#1241637).


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.

An update of the linux package has been released.

ID	Name	Product	Family	Type	Severity
362341	AlmaLinux 9.2 [TuxCare] Security Update: bpftool / kernel / kernel-abi-stablelists / kernel-core / etc Multiple Vulnerabilities (ALMALINUX9.2:CLSA-2026:1778769697)	Nessus	Alma Linux Local Security Checks	Local	high
296330	Unity Linux 20.1050e Security Update: kernel (UTSA-2026-004878)	Nessus	Unity Linux Local Security Checks	Local	medium
281453	Unity Linux 20.1060a / 20.1070a Security Update: kernel (UTSA-2025-993231)	Nessus	Unity Linux Local Security Checks	Local	medium
275047	Unity Linux 20.1060e / 20.1070e Security Update: kernel (UTSA-2025-990765)	Nessus	Unity Linux Local Security Checks	Local	medium
248803	Linux Distros Unpatched Vulnerability : CVE-2022-49841	Nessus	Misc.	Local	medium
241966	SUSE SLES15: cluster-md-kmp-default / dlm-kmp-default / gfs2-kmp-default / etc (SUSE-SU-2025:02262-1)	Nessus	SuSE Local Security Checks	Local	high
241036	SUSE SLES15 : Security update for the Linux Kernel (SUSE-SU-2025:02173-1)	Nessus	SuSE Local Security Checks	Local	medium
240812	SUSE SLES15 Security Update : kernel (SUSE-SU-2025:01982-1)	Nessus	SuSE Local Security Checks	Local	high
151965	Photon OS 4.0: Linux PHSA-2021-4.0-0065	Nessus	PhotonOS Local Security Checks	Local	high

Detections

Analytics

CVE-2022-49841

medium

Tenable Plugins

high

medium

medium

medium

medium

high

medium

high

high