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

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


    The following security bugs were fixed:

    - CVE-2022-48933: netfilter: nf_tables: fix memory leak during stateful obj update (bsc#1229621).
    - 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-2024-46763: fou: Fix null-ptr-deref in GRO (bsc#1230764).
    - CVE-2024-50038: netfilter: xtables: avoid NFPROTO_UNSPEC where needed (bsc#1231910).
    - CVE-2025-21726: padata: avoid UAF for reorder_work (bsc#1238865).
    - CVE-2025-21785: arm64: cacheinfo: Avoid out-of-bounds write to cacheinfo array (bsc#1238747).
    - CVE-2025-21791: vrf: use RCU protection in l3mdev_l3_out() (bsc#1238512).
    - CVE-2025-21812: ax25: rcu protect dev->ax25_ptr (bsc#1238471).
    - CVE-2025-21839: KVM: x86: Load DR6 with guest value only before entering .vcpu_run() loop (bsc#1239061).
    - CVE-2025-22004: net: atm: fix use after free in lec_send() (bsc#1240835).
    - CVE-2025-22020: memstick: rtsx_usb_ms: Fix slab-use-after-free in rtsx_usb_ms_drv_remove (bsc#1241280).
    - CVE-2025-22045: x86/mm: Fix flush_tlb_range() when used for zapping normal PMDs (bsc#1241433).
    - CVE-2025-22055: net: fix geneve_opt length integer overflow (bsc#1241371).
    - CVE-2025-22097: drm/vkms: Fix use after free and double free on init error (bsc#1241541).
    - CVE-2025-2312: CIFS: New mount option for cifs.upcall namespace resolution (bsc#1239684).
    - CVE-2025-23138: watch_queue: fix pipe accounting mismatch (bsc#1241648).
    - CVE-2025-39735: jfs: fix slab-out-of-bounds read in ea_get() (bsc#1241625).


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 Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - 9p/trans_fd: always use O_NONBLOCK read/write syzbot is reporting hung task at p9_fd_close() [1], for     p9_mux_poll_stop() from p9_conn_destroy() from p9_fd_close() is failing to interrupt already started     kernel_read() from p9_fd_read() from p9_read_work() and/or kernel_write() from p9_fd_write() from     p9_write_work() requests. Since p9_socket_open() sets O_NONBLOCK flag, p9_mux_poll_stop() does not need to     interrupt kernel_read()/kernel_write(). However, since p9_fd_open() does not set O_NONBLOCK flag, but pipe     blocks unless signal is pending, p9_mux_poll_stop() needs to interrupt kernel_read()/kernel_write() when     the file descriptor refers to a pipe. In other words, pipe file descriptor needs to be handled as if     socket file descriptor. We somehow need to interrupt kernel_read()/kernel_write() on pipes. A minimal     change, which this patch is doing, is to set O_NONBLOCK flag from p9_fd_open(), for O_NONBLOCK flag does     not affect reading/writing of regular files. But this approach changes O_NONBLOCK flag on userspace-     supplied file descriptors (which might break userspace programs), and O_NONBLOCK flag could be changed by     userspace. It would be possible to set O_NONBLOCK flag every time p9_fd_read()/p9_fd_write() is invoked,     but still remains small race window for clearing O_NONBLOCK flag. If we don't want to manipulate     O_NONBLOCK flag, we might be able to surround kernel_read()/kernel_write() with     set_thread_flag(TIF_SIGPENDING) and recalc_sigpending(). Since p9_read_work()/p9_write_work() works are     processed by kernel threads which process global system_wq workqueue, signals could not be delivered from     remote threads when p9_mux_poll_stop() from p9_conn_destroy() from p9_fd_close() is called. Therefore,     calling set_thread_flag(TIF_SIGPENDING)/recalc_sigpending() every time would be needed if we count on     signals for making kernel_read()/kernel_write() non-blocking. [Dominique: add comment at Christian's     suggestion] (CVE-2022-49767)

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

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

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

    9p/trans_fd: always use O_NONBLOCK read/write

    syzbot is reporting hung task at p9_fd_close() [1], for p9_mux_poll_stop()      from p9_conn_destroy() from p9_fd_close() is failing to interrupt already     started kernel_read() from p9_fd_read() from p9_read_work() and/or     kernel_write() from p9_fd_write() from p9_write_work() requests.

    Since p9_socket_open() sets O_NONBLOCK flag, p9_mux_poll_stop() does not     need to interrupt kernel_read()/kernel_write(). However, since p9_fd_open()     does not set O_NONBLOCK flag, but pipe blocks unless signal is pending,     p9_mux_poll_stop() needs to interrupt kernel_read()/kernel_write() when     the file descriptor refers to a pipe. In other words, pipe file descriptor     needs to be handled as if socket file descriptor.

    We somehow need to interrupt kernel_read()/kernel_write() on pipes.

    A minimal change, which this patch is doing, is to set O_NONBLOCK flag      from p9_fd_open(), for O_NONBLOCK flag does not affect reading/writing     of regular files. But this approach changes O_NONBLOCK flag on userspace-     supplied file descriptors (which might break userspace programs), and     O_NONBLOCK flag could be changed by userspace. It would be possible to set     O_NONBLOCK flag every time p9_fd_read()/p9_fd_write() is invoked, but still     remains small race window for clearing O_NONBLOCK flag.

    If we don't want to manipulate O_NONBLOCK flag, we might be able to     surround kernel_read()/kernel_write() with set_thread_flag(TIF_SIGPENDING)     and recalc_sigpending(). Since p9_read_work()/p9_write_work() works are     processed by kernel threads which process global system_wq workqueue,     signals could not be delivered from remote threads when p9_mux_poll_stop()      from p9_conn_destroy() from p9_fd_close() is called. Therefore, calling     set_thread_flag(TIF_SIGPENDING)/recalc_sigpending() every time would be     needed if we count on signals for making kernel_read()/kernel_write()     non-blocking.

    [Dominique: add comment at Christian's suggestion]

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: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 Unity Linux 20 host has a package installed that is affected by a vulnerability as referenced in the UTSA-2025-991140 advisory.

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

    9p/trans_fd: always use O_NONBLOCK read/write

    syzbot is reporting hung task at p9_fd_close() [1], for p9_mux_poll_stop()      from p9_conn_destroy() from p9_fd_close() is failing to interrupt already     started kernel_read() from p9_fd_read() from p9_read_work() and/or     kernel_write() from p9_fd_write() from p9_write_work() requests.

    Since p9_socket_open() sets O_NONBLOCK flag, p9_mux_poll_stop() does not     need to interrupt kernel_read()/kernel_write(). However, since p9_fd_open()     does not set O_NONBLOCK flag, but pipe blocks unless signal is pending,     p9_mux_poll_stop() needs to interrupt kernel_read()/kernel_write() when     the file descriptor refers to a pipe. In other words, pipe file descriptor     needs to be handled as if socket file descriptor.

    We somehow need to interrupt kernel_read()/kernel_write() on pipes.

    A minimal change, which this patch is doing, is to set O_NONBLOCK flag      from p9_fd_open(), for O_NONBLOCK flag does not affect reading/writing     of regular files. But this approach changes O_NONBLOCK flag on userspace-     supplied file descriptors (which might break userspace programs), and     O_NONBLOCK flag could be changed by userspace. It would be possible to set     O_NONBLOCK flag every time p9_fd_read()/p9_fd_write() is invoked, but still     remains small race window for clearing O_NONBLOCK flag.

    If we don't want to manipulate O_NONBLOCK flag, we might be able to     surround kernel_read()/kernel_write() with set_thread_flag(TIF_SIGPENDING)     and recalc_sigpending(). Since p9_read_work()/p9_write_work() works are     processed by kernel threads which process global system_wq workqueue,     signals could not be delivered from remote threads when p9_mux_poll_stop()      from p9_conn_destroy() from p9_fd_close() is called. Therefore, calling     set_thread_flag(TIF_SIGPENDING)/recalc_sigpending() every time would be     needed if we count on signals for making kernel_read()/kernel_write()     non-blocking.

    [Dominique: add comment at Christian's suggestion]

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

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

    9p/trans_fd: always use O_NONBLOCK read/write

    syzbot is reporting hung task at p9_fd_close() [1], for p9_mux_poll_stop()      from p9_conn_destroy() from p9_fd_close() is failing to interrupt already     started kernel_read() from p9_fd_read() from p9_read_work() and/or     kernel_write() from p9_fd_write() from p9_write_work() requests.

    Since p9_socket_open() sets O_NONBLOCK flag, p9_mux_poll_stop() does not     need to interrupt kernel_read()/kernel_write(). However, since p9_fd_open()     does not set O_NONBLOCK flag, but pipe blocks unless signal is pending,     p9_mux_poll_stop() needs to interrupt kernel_read()/kernel_write() when     the file descriptor refers to a pipe. In other words, pipe file descriptor     needs to be handled as if socket file descriptor.

    We somehow need to interrupt kernel_read()/kernel_write() on pipes.

    A minimal change, which this patch is doing, is to set O_NONBLOCK flag      from p9_fd_open(), for O_NONBLOCK flag does not affect reading/writing     of regular files. But this approach changes O_NONBLOCK flag on userspace-     supplied file descriptors (which might break userspace programs), and     O_NONBLOCK flag could be changed by userspace. It would be possible to set     O_NONBLOCK flag every time p9_fd_read()/p9_fd_write() is invoked, but still     remains small race window for clearing O_NONBLOCK flag.

    If we don't want to manipulate O_NONBLOCK flag, we might be able to     surround kernel_read()/kernel_write() with set_thread_flag(TIF_SIGPENDING)     and recalc_sigpending(). Since p9_read_work()/p9_write_work() works are     processed by kernel threads which process global system_wq workqueue,     signals could not be delivered from remote threads when p9_mux_poll_stop()      from p9_conn_destroy() from p9_fd_close() is called. Therefore, calling     set_thread_flag(TIF_SIGPENDING)/recalc_sigpending() every time would be     needed if we count on signals for making kernel_read()/kernel_write()     non-blocking.

    [Dominique: add comment at Christian's suggestion]

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
237098	SUSE SLES15 Security Update : kernel (SUSE-SU-2025:01620-1)	Nessus	SuSE Local Security Checks	5/22/2025	9/24/2025	high
246821	Linux Distros Unpatched Vulnerability : CVE-2022-49767	Nessus	Misc.	8/9/2025	1/15/2026	medium
240812	SUSE SLES15 Security Update : kernel (SUSE-SU-2025:01982-1)	Nessus	SuSE Local Security Checks	6/27/2025	6/27/2025	high
151965	Photon OS 4.0: Linux PHSA-2021-4.0-0065	Nessus	PhotonOS Local Security Checks	7/22/2021	3/23/2026	high
275129	Unity Linux 20.1070e Security Update: kernel (UTSA-2025-990737)	Nessus	Unity Linux Local Security Checks	11/12/2025	11/12/2025	medium
241966	SUSE SLES15 : Recommended update for initial livepatch (SUSE-SU-2025:02262-1)	Nessus	SuSE Local Security Checks	7/11/2025	12/9/2025	high
278225	Unity Linux 20.1050e Security Update: kernel (UTSA-2025-991140)	Nessus	Unity Linux Local Security Checks	12/11/2025	12/11/2025	medium
281275	Unity Linux 20.1060a / 20.1070a Security Update: kernel (UTSA-2025-993166)	Nessus	Unity Linux Local Security Checks	12/31/2025	12/31/2025	medium

Detections

Analytics

Plugins Search

high

medium

high

high

medium

high

medium

medium