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

ID	Name	Product	Family	Severity
296330	Unity Linux 20.1050e Security Update: kernel (UTSA-2026-004878)	Nessus	Unity Linux Local Security Checks	medium
281453	Unity Linux 20.1060a / 20.1070a Security Update: kernel (UTSA-2025-993231)	Nessus	Unity Linux Local Security Checks	medium
275047	Unity Linux 20.1070e Security Update: kernel (UTSA-2025-990765)	Nessus	Unity Linux Local Security Checks	medium
248803	Linux Distros Unpatched Vulnerability : CVE-2022-49841	Nessus	Misc.	medium
241966	SUSE SLES15 : Recommended update for initial livepatch (SUSE-SU-2025:02262-1)	Nessus	SuSE Local Security Checks	high
241036	SUSE SLES15 Security Update : kernel (SUSE-SU-2025:02173-1)	Nessus	SuSE Local Security Checks	medium
240812	SUSE SLES15 Security Update : kernel (SUSE-SU-2025:01982-1)	Nessus	SuSE Local Security Checks	high

Detections

Analytics

CVE-2022-49841

medium

Tenable Plugins

medium

medium

medium

medium

high

medium

high