In the Linux kernel, the following vulnerability has been resolved: firmware: xilinx: don't make a sleepable memory allocation from an atomic context The following issue was discovered using lockdep: [ 6.691371] BUG: sleeping function called from invalid context at include/linux/sched/mm.h:209 [ 6.694602] in_atomic(): 1, irqs_disabled(): 128, non_block: 0, pid: 1, name: swapper/0 [ 6.702431] 2 locks held by swapper/0/1: [ 6.706300] #0: ffffff8800f6f188 (&dev->mutex){....}-{3:3}, at: __device_driver_lock+0x4c/0x90 [ 6.714900] #1: ffffffc009a2abb8 (enable_lock){....}-{2:2}, at: clk_enable_lock+0x4c/0x140 [ 6.723156] irq event stamp: 304030 [ 6.726596] hardirqs last enabled at (304029): [<ffffffc008d17ee0>] _raw_spin_unlock_irqrestore+0xc0/0xd0 [ 6.736142] hardirqs last disabled at (304030): [<ffffffc00876bc5c>] clk_enable_lock+0xfc/0x140 [ 6.744742] softirqs last enabled at (303958): [<ffffffc0080904f0>] _stext+0x4f0/0x894 [ 6.752655] softirqs last disabled at (303951): [<ffffffc0080e53b8>] irq_exit+0x238/0x280 [ 6.760744] CPU: 1 PID: 1 Comm: swapper/0 Tainted: G U 5.15.36 #2 [ 6.768048] Hardware name: xlnx,zynqmp (DT) [ 6.772179] Call trace: [ 6.774584] dump_backtrace+0x0/0x300 [ 6.778197] show_stack+0x18/0x30 [ 6.781465] dump_stack_lvl+0xb8/0xec [ 6.785077] dump_stack+0x1c/0x38 [ 6.788345] ___might_sleep+0x1a8/0x2a0 [ 6.792129] __might_sleep+0x6c/0xd0 [ 6.795655] kmem_cache_alloc_trace+0x270/0x3d0 [ 6.800127] do_feature_check_call+0x100/0x220 [ 6.804513] zynqmp_pm_invoke_fn+0x8c/0xb0 [ 6.808555] zynqmp_pm_clock_getstate+0x90/0xe0 [ 6.813027] zynqmp_pll_is_enabled+0x8c/0x120 [ 6.817327] zynqmp_pll_enable+0x38/0xc0 [ 6.821197] clk_core_enable+0x144/0x400 [ 6.825067] clk_core_enable+0xd4/0x400 [ 6.828851] clk_core_enable+0xd4/0x400 [ 6.832635] clk_core_enable+0xd4/0x400 [ 6.836419] clk_core_enable+0xd4/0x400 [ 6.840203] clk_core_enable+0xd4/0x400 [ 6.843987] clk_core_enable+0xd4/0x400 [ 6.847771] clk_core_enable+0xd4/0x400 [ 6.851555] clk_core_enable_lock+0x24/0x50 [ 6.855683] clk_enable+0x24/0x40 [ 6.858952] fclk_probe+0x84/0xf0 [ 6.862220] platform_probe+0x8c/0x110 [ 6.865918] really_probe+0x110/0x5f0 [ 6.869530] __driver_probe_device+0xcc/0x210 [ 6.873830] driver_probe_device+0x64/0x140 [ 6.877958] __driver_attach+0x114/0x1f0 [ 6.881828] bus_for_each_dev+0xe8/0x160 [ 6.885698] driver_attach+0x34/0x50 [ 6.889224] bus_add_driver+0x228/0x300 [ 6.893008] driver_register+0xc0/0x1e0 [ 6.896792] __platform_driver_register+0x44/0x60 [ 6.901436] fclk_driver_init+0x1c/0x28 [ 6.905220] do_one_initcall+0x104/0x590 [ 6.909091] kernel_init_freeable+0x254/0x2bc [ 6.913390] kernel_init+0x24/0x130 [ 6.916831] ret_from_fork+0x10/0x20 Fix it by passing the GFP_ATOMIC gfp flag for the corresponding memory allocation.

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

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

    firmware: xilinx: don't make a sleepable memory allocation from an atomic context

    The following issue was discovered using lockdep:
    [    6.691371] BUG: sleeping function called from invalid context at include/linux/sched/mm.h:209     [    6.694602] in_atomic(): 1, irqs_disabled(): 128, non_block: 0, pid: 1, name: swapper/0     [    6.702431] 2 locks held by swapper/0/1:
    [    6.706300]  #0: ffffff8800f6f188 (&dev->mutex){....}-{3:3}, at: __device_driver_lock+0x4c/0x90     [    6.714900]  #1: ffffffc009a2abb8 (enable_lock){....}-{2:2}, at: clk_enable_lock+0x4c/0x140     [    6.723156] irq event stamp: 304030     [    6.726596] hardirqs last  enabled at (304029): [<ffffffc008d17ee0>]
    _raw_spin_unlock_irqrestore+0xc0/0xd0     [    6.736142] hardirqs last disabled at (304030): [<ffffffc00876bc5c>] clk_enable_lock+0xfc/0x140     [    6.744742] softirqs last  enabled at (303958): [<ffffffc0080904f0>] _stext+0x4f0/0x894     [    6.752655] softirqs last disabled at (303951): [<ffffffc0080e53b8>] irq_exit+0x238/0x280     [    6.760744] CPU: 1 PID: 1 Comm: swapper/0 Tainted: G     U            5.15.36 #2     [    6.768048] Hardware name: xlnx,zynqmp (DT)     [    6.772179] Call trace:
    [    6.774584]  dump_backtrace+0x0/0x300     [    6.778197]  show_stack+0x18/0x30     [    6.781465]  dump_stack_lvl+0xb8/0xec     [    6.785077]  dump_stack+0x1c/0x38     [    6.788345]  ___might_sleep+0x1a8/0x2a0     [    6.792129]  __might_sleep+0x6c/0xd0     [    6.795655]  kmem_cache_alloc_trace+0x270/0x3d0     [    6.800127]  do_feature_check_call+0x100/0x220     [    6.804513]  zynqmp_pm_invoke_fn+0x8c/0xb0     [    6.808555]  zynqmp_pm_clock_getstate+0x90/0xe0     [    6.813027]  zynqmp_pll_is_enabled+0x8c/0x120     [    6.817327]  zynqmp_pll_enable+0x38/0xc0     [    6.821197]  clk_core_enable+0x144/0x400     [    6.825067]  clk_core_enable+0xd4/0x400     [    6.828851]  clk_core_enable+0xd4/0x400     [    6.832635]  clk_core_enable+0xd4/0x400     [    6.836419]  clk_core_enable+0xd4/0x400     [    6.840203]  clk_core_enable+0xd4/0x400     [    6.843987]  clk_core_enable+0xd4/0x400     [    6.847771]  clk_core_enable+0xd4/0x400     [    6.851555]  clk_core_enable_lock+0x24/0x50     [    6.855683]  clk_enable+0x24/0x40     [    6.858952]  fclk_probe+0x84/0xf0     [    6.862220]  platform_probe+0x8c/0x110     [    6.865918]  really_probe+0x110/0x5f0     [    6.869530]  __driver_probe_device+0xcc/0x210     [    6.873830]  driver_probe_device+0x64/0x140     [    6.877958]  __driver_attach+0x114/0x1f0     [    6.881828]  bus_for_each_dev+0xe8/0x160     [    6.885698]  driver_attach+0x34/0x50     [    6.889224]  bus_add_driver+0x228/0x300     [    6.893008]  driver_register+0xc0/0x1e0     [    6.896792]  __platform_driver_register+0x44/0x60     [    6.901436]  fclk_driver_init+0x1c/0x28     [    6.905220]  do_one_initcall+0x104/0x590     [    6.909091]  kernel_init_freeable+0x254/0x2bc     [    6.913390]  kernel_init+0x24/0x130     [    6.916831]  ret_from_fork+0x10/0x20

    Fix it by passing the GFP_ATOMIC gfp flag for the corresponding     memory allocation.

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

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

    firmware: xilinx: don't make a sleepable memory allocation from an atomic context

    The following issue was discovered using lockdep:
    [    6.691371] BUG: sleeping function called from invalid context at include/linux/sched/mm.h:209     [    6.694602] in_atomic(): 1, irqs_disabled(): 128, non_block: 0, pid: 1, name: swapper/0     [    6.702431] 2 locks held by swapper/0/1:
    [    6.706300]  #0: ffffff8800f6f188 (&dev->mutex){....}-{3:3}, at: __device_driver_lock+0x4c/0x90     [    6.714900]  #1: ffffffc009a2abb8 (enable_lock){....}-{2:2}, at: clk_enable_lock+0x4c/0x140     [    6.723156] irq event stamp: 304030     [    6.726596] hardirqs last  enabled at (304029): [<ffffffc008d17ee0>]
    _raw_spin_unlock_irqrestore+0xc0/0xd0     [    6.736142] hardirqs last disabled at (304030): [<ffffffc00876bc5c>] clk_enable_lock+0xfc/0x140     [    6.744742] softirqs last  enabled at (303958): [<ffffffc0080904f0>] _stext+0x4f0/0x894     [    6.752655] softirqs last disabled at (303951): [<ffffffc0080e53b8>] irq_exit+0x238/0x280     [    6.760744] CPU: 1 PID: 1 Comm: swapper/0 Tainted: G     U            5.15.36 #2     [    6.768048] Hardware name: xlnx,zynqmp (DT)     [    6.772179] Call trace:
    [    6.774584]  dump_backtrace+0x0/0x300     [    6.778197]  show_stack+0x18/0x30     [    6.781465]  dump_stack_lvl+0xb8/0xec     [    6.785077]  dump_stack+0x1c/0x38     [    6.788345]  ___might_sleep+0x1a8/0x2a0     [    6.792129]  __might_sleep+0x6c/0xd0     [    6.795655]  kmem_cache_alloc_trace+0x270/0x3d0     [    6.800127]  do_feature_check_call+0x100/0x220     [    6.804513]  zynqmp_pm_invoke_fn+0x8c/0xb0     [    6.808555]  zynqmp_pm_clock_getstate+0x90/0xe0     [    6.813027]  zynqmp_pll_is_enabled+0x8c/0x120     [    6.817327]  zynqmp_pll_enable+0x38/0xc0     [    6.821197]  clk_core_enable+0x144/0x400     [    6.825067]  clk_core_enable+0xd4/0x400     [    6.828851]  clk_core_enable+0xd4/0x400     [    6.832635]  clk_core_enable+0xd4/0x400     [    6.836419]  clk_core_enable+0xd4/0x400     [    6.840203]  clk_core_enable+0xd4/0x400     [    6.843987]  clk_core_enable+0xd4/0x400     [    6.847771]  clk_core_enable+0xd4/0x400     [    6.851555]  clk_core_enable_lock+0x24/0x50     [    6.855683]  clk_enable+0x24/0x40     [    6.858952]  fclk_probe+0x84/0xf0     [    6.862220]  platform_probe+0x8c/0x110     [    6.865918]  really_probe+0x110/0x5f0     [    6.869530]  __driver_probe_device+0xcc/0x210     [    6.873830]  driver_probe_device+0x64/0x140     [    6.877958]  __driver_attach+0x114/0x1f0     [    6.881828]  bus_for_each_dev+0xe8/0x160     [    6.885698]  driver_attach+0x34/0x50     [    6.889224]  bus_add_driver+0x228/0x300     [    6.893008]  driver_register+0xc0/0x1e0     [    6.896792]  __platform_driver_register+0x44/0x60     [    6.901436]  fclk_driver_init+0x1c/0x28     [    6.905220]  do_one_initcall+0x104/0x590     [    6.909091]  kernel_init_freeable+0x254/0x2bc     [    6.913390]  kernel_init+0x24/0x130     [    6.916831]  ret_from_fork+0x10/0x20

    Fix it by passing the GFP_ATOMIC gfp flag for the corresponding     memory allocation.

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: firmware: xilinx: don't make a     sleepable memory allocation from an atomic context The following issue was discovered using lockdep: [     6.691371] BUG: sleeping function called from invalid context at include/linux/sched/mm.h:209 [ 6.694602]     in_atomic(): 1, irqs_disabled(): 128, non_block: 0, pid: 1, name: swapper/0 [ 6.702431] 2 locks held by     swapper/0/1: [ 6.706300] #0: ffffff8800f6f188 (&dev->mutex){....}-{3:3}, at:
    __device_driver_lock+0x4c/0x90 [ 6.714900] #1: ffffffc009a2abb8 (enable_lock){....}-{2:2}, at:
    clk_enable_lock+0x4c/0x140 [ 6.723156] irq event stamp: 304030 [ 6.726596] hardirqs last enabled at     (304029): [<ffffffc008d17ee0>] _raw_spin_unlock_irqrestore+0xc0/0xd0 [ 6.736142] hardirqs last disabled at     (304030): [<ffffffc00876bc5c>] clk_enable_lock+0xfc/0x140 [ 6.744742] softirqs last enabled at (303958):
    [<ffffffc0080904f0>] _stext+0x4f0/0x894 [ 6.752655] softirqs last disabled at (303951):
    [<ffffffc0080e53b8>] irq_exit+0x238/0x280 [ 6.760744] CPU: 1 PID: 1 Comm: swapper/0 Tainted: G U 5.15.36     #2 [ 6.768048] Hardware name: xlnx,zynqmp (DT) [ 6.772179] Call trace: [ 6.774584]     dump_backtrace+0x0/0x300 [ 6.778197] show_stack+0x18/0x30 [ 6.781465] dump_stack_lvl+0xb8/0xec [ 6.785077]     dump_stack+0x1c/0x38 [ 6.788345] ___might_sleep+0x1a8/0x2a0 [ 6.792129] __might_sleep+0x6c/0xd0 [     6.795655] kmem_cache_alloc_trace+0x270/0x3d0 [ 6.800127] do_feature_check_call+0x100/0x220 [ 6.804513]     zynqmp_pm_invoke_fn+0x8c/0xb0 [ 6.808555] zynqmp_pm_clock_getstate+0x90/0xe0 [ 6.813027]     zynqmp_pll_is_enabled+0x8c/0x120 [ 6.817327] zynqmp_pll_enable+0x38/0xc0 [ 6.821197]     clk_core_enable+0x144/0x400 [ 6.825067] clk_core_enable+0xd4/0x400 [ 6.828851] clk_core_enable+0xd4/0x400     [ 6.832635] clk_core_enable+0xd4/0x400 [ 6.836419] clk_core_enable+0xd4/0x400 [ 6.840203]     clk_core_enable+0xd4/0x400 [ 6.843987] clk_core_enable+0xd4/0x400 [ 6.847771] clk_core_enable+0xd4/0x400 [     6.851555] clk_core_enable_lock+0x24/0x50 [ 6.855683] clk_enable+0x24/0x40 [ 6.858952] fclk_probe+0x84/0xf0     [ 6.862220] platform_probe+0x8c/0x110 [ 6.865918] really_probe+0x110/0x5f0 [ 6.869530]
    __driver_probe_device+0xcc/0x210 [ 6.873830] driver_probe_device+0x64/0x140 [ 6.877958]
    __driver_attach+0x114/0x1f0 [ 6.881828] bus_for_each_dev+0xe8/0x160 [ 6.885698] driver_attach+0x34/0x50 [     6.889224] bus_add_driver+0x228/0x300 [ 6.893008] driver_register+0xc0/0x1e0 [ 6.896792]
    __platform_driver_register+0x44/0x60 [ 6.901436] fclk_driver_init+0x1c/0x28 [ 6.905220]     do_one_initcall+0x104/0x590 [ 6.909091] kernel_init_freeable+0x254/0x2bc [ 6.913390]     kernel_init+0x24/0x130 [ 6.916831] ret_from_fork+0x10/0x20 Fix it by passing the GFP_ATOMIC gfp flag for     the corresponding memory allocation. (CVE-2023-53099)

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.

ID	Name	Product	Family	Severity
281060	Unity Linux 20.1060a / 20.1070a Security Update: kernel (UTSA-2025-993029)	Nessus	Unity Linux Local Security Checks	medium
275137	Unity Linux 20.1070e Security Update: kernel (UTSA-2025-990784)	Nessus	Unity Linux Local Security Checks	medium
244525	Linux Distros Unpatched Vulnerability : CVE-2023-53099	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

Detections

Analytics

CVE-2023-53099

medium

Tenable Plugins

medium

medium

medium

high

medium