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: tracing/osnoise: Do not unregister     events twice Nicolas reported that using: # trace-cmd record -e all -M 10 -p osnoise --poll Resulted in     the following kernel warning: ------------[ cut here ]------------ WARNING: CPU: 0 PID: 1217 at     kernel/tracepoint.c:404 tracepoint_probe_unregister+0x280/0x370 [...] CPU: 0 PID: 1217 Comm: trace-cmd Not     tainted 5.17.0-rc6-next-20220307-nico+ #19 RIP: 0010:tracepoint_probe_unregister+0x280/0x370 [...] CR2:
    00007ff919b29497 CR3: 0000000109da4005 CR4: 0000000000170ef0 Call Trace: <TASK>     osnoise_workload_stop+0x36/0x90 tracing_set_tracer+0x108/0x260 tracing_set_trace_write+0x94/0xd0 ?
    __check_object_size.part.0+0x10a/0x150 ? selinux_file_permission+0x104/0x150 vfs_write+0xb5/0x290     ksys_write+0x5f/0xe0 do_syscall_64+0x3b/0x90 entry_SYSCALL_64_after_hwframe+0x44/0xae RIP:
    0033:0x7ff919a18127 [...] ---[ end trace 0000000000000000 ]--- The warning complains about an attempt to     unregister an unregistered tracepoint. This happens on trace-cmd because it first stops tracing, and then     switches the tracer to nop. Which is equivalent to: # cd /sys/kernel/tracing/ # echo osnoise >     current_tracer # echo 0 > tracing_on # echo nop > current_tracer The osnoise tracer stops the workload     when no trace instance is actually collecting data. This can be caused both by disabling tracing or     disabling the tracer itself. To avoid unregistering events twice, use the existing     trace_osnoise_callback_enabled variable to check if the events (and the workload) are actually active     before trying to deactivate them. (CVE-2022-48848)

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

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

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

    tracing/osnoise: Do not unregister events twice

    Nicolas reported that using:

     # trace-cmd record -e all -M 10 -p osnoise --poll

    Resulted in the following kernel warning:

     ------------[ cut here ]------------      WARNING: CPU: 0 PID: 1217 at kernel/tracepoint.c:404 tracepoint_probe_unregister+0x280/0x370      [...]      CPU: 0 PID: 1217 Comm: trace-cmd Not tainted 5.17.0-rc6-next-20220307-nico+ #19      RIP: 0010:tracepoint_probe_unregister+0x280/0x370      [...]      CR2: 00007ff919b29497 CR3: 0000000109da4005 CR4: 0000000000170ef0      Call Trace:
      <TASK>       osnoise_workload_stop+0x36/0x90       tracing_set_tracer+0x108/0x260       tracing_set_trace_write+0x94/0xd0       ? __check_object_size.part.0+0x10a/0x150       ? selinux_file_permission+0x104/0x150       vfs_write+0xb5/0x290       ksys_write+0x5f/0xe0       do_syscall_64+0x3b/0x90       entry_SYSCALL_64_after_hwframe+0x44/0xae      RIP: 0033:0x7ff919a18127      [...]
     ---[ end trace 0000000000000000 ]---

    The warning complains about an attempt to unregister an     unregistered tracepoint.

    This happens on trace-cmd because it first stops tracing, and     then switches the tracer to nop. Which is equivalent to:

      # cd /sys/kernel/tracing/       # echo osnoise > current_tracer       # echo 0 > tracing_on       # echo nop > current_tracer

    The osnoise tracer stops the workload when no trace instance     is actually collecting data. This can be caused both by     disabling tracing or disabling the tracer itself.

    To avoid unregistering events twice, use the existing     trace_osnoise_callback_enabled variable to check if the events     (and the workload) are actually active before trying to     deactivate them.

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-2026-013779 advisory.

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

    tracing/osnoise: Do not unregister events twice

    Nicolas reported that using:

     # trace-cmd record -e all -M 10 -p osnoise --poll

    Resulted in the following kernel warning:

     ------------[ cut here ]------------      WARNING: CPU: 0 PID: 1217 at kernel/tracepoint.c:404 tracepoint_probe_unregister+0x280/0x370      [...]      CPU: 0 PID: 1217 Comm: trace-cmd Not tainted 5.17.0-rc6-next-20220307-nico+ #19      RIP: 0010:tracepoint_probe_unregister+0x280/0x370      [...]      CR2: 00007ff919b29497 CR3: 0000000109da4005 CR4: 0000000000170ef0      Call Trace:
      <TASK>       osnoise_workload_stop+0x36/0x90       tracing_set_tracer+0x108/0x260       tracing_set_trace_write+0x94/0xd0       ? __check_object_size.part.0+0x10a/0x150       ? selinux_file_permission+0x104/0x150       vfs_write+0xb5/0x290       ksys_write+0x5f/0xe0       do_syscall_64+0x3b/0x90       entry_SYSCALL_64_after_hwframe+0x44/0xae      RIP: 0033:0x7ff919a18127      [...]
     ---[ end trace 0000000000000000 ]---

    The warning complains about an attempt to unregister an     unregistered tracepoint.

    This happens on trace-cmd because it first stops tracing, and     then switches the tracer to nop. Which is equivalent to:

      # cd /sys/kernel/tracing/       # echo osnoise > current_tracer       # echo 0 > tracing_on       # echo nop > current_tracer

    The osnoise tracer stops the workload when no trace instance     is actually collecting data. This can be caused both by     disabling tracing or disabling the tracer itself.

    To avoid unregistering events twice, use the existing     trace_osnoise_callback_enabled variable to check if the events     (and the workload) are actually active before trying to     deactivate them.

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.

ID	Name	Product	Family	Published	Updated	Severity
208330	EulerOS 2.0 SP12 : kernel (EulerOS-SA-2024-2544)	Nessus	Huawei Local Security Checks	10/9/2024	1/6/2026	high
208351	EulerOS 2.0 SP12 : kernel (EulerOS-SA-2024-2519)	Nessus	Huawei Local Security Checks	10/9/2024	1/6/2026	high
209777	EulerOS Virtualization 2.12.1 : kernel (EulerOS-SA-2024-2763)	Nessus	Huawei Local Security Checks	10/27/2024	1/6/2026	high
225224	Linux Distros Unpatched Vulnerability : CVE-2022-48848	Nessus	Misc.	3/5/2025	9/14/2025	high
308540	Unity Linux 20.1050e / 20.1060e / 20.1070e Security Update: kernel (UTSA-2026-010698)	Nessus	Unity Linux Local Security Checks	4/21/2026	4/22/2026	high
309555	Unity Linux 20.1070a Security Update: kernel (UTSA-2026-013779)	Nessus	Unity Linux Local Security Checks	4/22/2026	4/22/2026	high
209785	EulerOS Virtualization 2.12.0 : kernel (EulerOS-SA-2024-2781)	Nessus	Huawei Local Security Checks	10/27/2024	1/6/2026	high

Detections

Analytics

Plugins Search

high

high

high

high

high

high

high