In the Linux kernel, the following vulnerability has been resolved: can: j1939: fix errant WARN_ON_ONCE in j1939_session_deactivate The conclusion "j1939_session_deactivate() should be called with a session ref-count of at least 2" is incorrect. In some concurrent scenarios, j1939_session_deactivate can be called with the session ref-count less than 2. But there is not any problem because it will check the session active state before session putting in j1939_session_deactivate_locked(). Here is the concurrent scenario of the problem reported by syzbot and my reproduction log. cpu0 cpu1 j1939_xtp_rx_eoma j1939_xtp_rx_abort_one j1939_session_get_by_addr [kref == 2] j1939_session_get_by_addr [kref == 3] j1939_session_deactivate [kref == 2] j1939_session_put [kref == 1] j1939_session_completed j1939_session_deactivate WARN_ON_ONCE(kref < 2) ===================================================== WARNING: CPU: 1 PID: 21 at net/can/j1939/transport.c:1088 j1939_session_deactivate+0x5f/0x70 CPU: 1 PID: 21 Comm: ksoftirqd/1 Not tainted 5.14.0-rc7+ #32 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1 04/01/2014 RIP: 0010:j1939_session_deactivate+0x5f/0x70 Call Trace: j1939_session_deactivate_activate_next+0x11/0x28 j1939_xtp_rx_eoma+0x12a/0x180 j1939_tp_recv+0x4a2/0x510 j1939_can_recv+0x226/0x380 can_rcv_filter+0xf8/0x220 can_receive+0x102/0x220 ? process_backlog+0xf0/0x2c0 can_rcv+0x53/0xf0 __netif_receive_skb_one_core+0x67/0x90 ? process_backlog+0x97/0x2c0 __netif_receive_skb+0x22/0x80

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

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

    can: j1939: fix errant WARN_ON_ONCE in j1939_session_deactivate

    The conclusion j1939_session_deactivate() should be called with a     session ref-count of at least 2 is incorrect. In some concurrent     scenarios, j1939_session_deactivate can be called with the session     ref-count less than 2. But there is not any problem because it     will check the session active state before session putting in     j1939_session_deactivate_locked().

    Here is the concurrent scenario of the problem reported by syzbot     and my reproduction log.

            cpu0                            cpu1                                     j1939_xtp_rx_eoma     j1939_xtp_rx_abort_one                                     j1939_session_get_by_addr [kref == 2]     j1939_session_get_by_addr [kref == 3]     j1939_session_deactivate [kref == 2]     j1939_session_put [kref == 1]                                     j1939_session_completed                                     j1939_session_deactivate                                     WARN_ON_ONCE(kref < 2)

    =====================================================     WARNING: CPU: 1 PID: 21 at net/can/j1939/transport.c:1088 j1939_session_deactivate+0x5f/0x70     CPU: 1 PID: 21 Comm: ksoftirqd/1 Not tainted 5.14.0-rc7+ #32     Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1 04/01/2014     RIP: 0010:j1939_session_deactivate+0x5f/0x70     Call Trace:
     j1939_session_deactivate_activate_next+0x11/0x28      j1939_xtp_rx_eoma+0x12a/0x180      j1939_tp_recv+0x4a2/0x510      j1939_can_recv+0x226/0x380      can_rcv_filter+0xf8/0x220      can_receive+0x102/0x220      ? process_backlog+0xf0/0x2c0      can_rcv+0x53/0xf0
     __netif_receive_skb_one_core+0x67/0x90      ? process_backlog+0x97/0x2c0
     __netif_receive_skb+0x22/0x80

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

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

    can: j1939: fix errant WARN_ON_ONCE in j1939_session_deactivate

    The conclusion j1939_session_deactivate() should be called with a     session ref-count of at least 2 is incorrect. In some concurrent     scenarios, j1939_session_deactivate can be called with the session     ref-count less than 2. But there is not any problem because it     will check the session active state before session putting in     j1939_session_deactivate_locked().

    Here is the concurrent scenario of the problem reported by syzbot     and my reproduction log.

            cpu0                            cpu1                                     j1939_xtp_rx_eoma     j1939_xtp_rx_abort_one                                     j1939_session_get_by_addr [kref == 2]     j1939_session_get_by_addr [kref == 3]     j1939_session_deactivate [kref == 2]     j1939_session_put [kref == 1]                                     j1939_session_completed                                     j1939_session_deactivate                                     WARN_ON_ONCE(kref < 2)

    =====================================================     WARNING: CPU: 1 PID: 21 at net/can/j1939/transport.c:1088 j1939_session_deactivate+0x5f/0x70     CPU: 1 PID: 21 Comm: ksoftirqd/1 Not tainted 5.14.0-rc7+ #32     Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1 04/01/2014     RIP: 0010:j1939_session_deactivate+0x5f/0x70     Call Trace:
     j1939_session_deactivate_activate_next+0x11/0x28      j1939_xtp_rx_eoma+0x12a/0x180      j1939_tp_recv+0x4a2/0x510      j1939_can_recv+0x226/0x380      can_rcv_filter+0xf8/0x220      can_receive+0x102/0x220      ? process_backlog+0xf0/0x2c0      can_rcv+0x53/0xf0
     __netif_receive_skb_one_core+0x67/0x90      ? process_backlog+0x97/0x2c0
     __netif_receive_skb+0x22/0x80

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: can: j1939: fix errant WARN_ON_ONCE in     j1939_session_deactivate The conclusion j1939_session_deactivate() should be called with a session ref-     count of at least 2 is incorrect. In some concurrent scenarios, j1939_session_deactivate can be called     with the session ref-count less than 2. But there is not any problem because it will check the session     active state before session putting in j1939_session_deactivate_locked(). Here is the concurrent scenario     of the problem reported by syzbot and my reproduction log. cpu0 cpu1 j1939_xtp_rx_eoma     j1939_xtp_rx_abort_one j1939_session_get_by_addr [kref == 2] j1939_session_get_by_addr [kref == 3]     j1939_session_deactivate [kref == 2] j1939_session_put [kref == 1] j1939_session_completed     j1939_session_deactivate WARN_ON_ONCE(kref < 2) =====================================================     WARNING: CPU: 1 PID: 21 at net/can/j1939/transport.c:1088 j1939_session_deactivate+0x5f/0x70 CPU: 1 PID:
    21 Comm: ksoftirqd/1 Not tainted 5.14.0-rc7+ #32 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996),     BIOS 1.13.0-1ubuntu1 04/01/2014 RIP: 0010:j1939_session_deactivate+0x5f/0x70 Call Trace:
    j1939_session_deactivate_activate_next+0x11/0x28 j1939_xtp_rx_eoma+0x12a/0x180 j1939_tp_recv+0x4a2/0x510     j1939_can_recv+0x226/0x380 can_rcv_filter+0xf8/0x220 can_receive+0x102/0x220 ? process_backlog+0xf0/0x2c0     can_rcv+0x53/0xf0 __netif_receive_skb_one_core+0x67/0x90 ? process_backlog+0x97/0x2c0
    __netif_receive_skb+0x22/0x80 (CVE-2021-4454)

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

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

    The following security bugs were fixed:

    - CVE-2022-49053: scsi: target: tcmu: Fix possible page UAF (bsc#1237918).
    - CVE-2022-49465: blk-throttle: Set BIO_THROTTLED when bio has been throttled (bsc#1238919).
    - CVE-2022-49739: gfs2: Always check inode size of inline inodes (bsc#1240207).
    - CVE-2023-52935: mm/khugepaged: fix ->anon_vma race (bsc#1240276).
    - CVE-2024-53124: net: fix data-races around sk->sk_forward_alloc (bsc#1234074).
    - CVE-2024-53176: smb: During unmount, ensure all cached dir instances drop their dentry (bsc#1234894).
    - CVE-2024-53178: smb: Do not leak cfid when reconnect races with open_cached_dir (bsc#1234895).
    - CVE-2024-56651: can: hi311x: hi3110_can_ist(): fix potential use-after-free (bsc#1235528).
    - CVE-2024-57996: net_sched: sch_sfq: do not allow 1 packet limit (bsc#1239076).
    - CVE-2024-58013: Bluetooth: MGMT: Fix slab-use-after-free Read in mgmt_remove_adv_monitor_sync     (bsc#1239095).
    - CVE-2024-58014: wifi: brcmsmac: add gain range check to wlc_phy_iqcal_gainparams_nphy() (bsc#1239109).
    - CVE-2025-21693: mm: zswap: properly synchronize freeing resources during CPU hotunplug (bsc#1237029).
    - CVE-2025-21718: net: rose: fix timer races against user threads (bsc#1239073).
    - CVE-2025-21772: partitions: mac: fix handling of bogus partition table (bsc#1238911).
    - CVE-2025-21780: drm/amdgpu: avoid buffer overflow attach in smu_sys_set_pp_table() (bsc#1239115).


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

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

    The following security bugs were fixed:

    - CVE-2022-49053: scsi: target: tcmu: Fix possible page UAF (bsc#1237918).
    - CVE-2022-49465: blk-throttle: Set BIO_THROTTLED when bio has been throttled (bsc#1238919).
    - CVE-2022-49739: gfs2: Always check inode size of inline inodes (bsc#1240207).
    - CVE-2023-52935: mm/khugepaged: fix ->anon_vma race (bsc#1240276).
    - CVE-2024-53064: idpf: fix idpf_vc_core_init error path (bsc#1233558 bsc#1234464).
    - CVE-2024-56651: can: hi311x: hi3110_can_ist(): fix potential use-after-free (bsc#1235528).
    - CVE-2024-58083: KVM: Explicitly verify target vCPU is online in kvm_get_vcpu() (bsc#1239036).
    - CVE-2025-21693: mm: zswap: properly synchronize freeing resources during CPU hotunplug (bsc#1237029).
    - CVE-2025-21714: RDMA/mlx5: Fix implicit ODP use after free (bsc#1237890).
    - CVE-2025-21732: RDMA/mlx5: Fix a race for an ODP MR which leads to CQE with error (bsc#1237877).
    - CVE-2025-21753: btrfs: fix use-after-free when attempting to join an aborted transaction (bsc#1237875).
    - CVE-2025-21772: partitions: mac: fix handling of bogus partition table (bsc#1238911).


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
273930	Unity Linux 20.1070e Security Update: kernel (UTSA-2025-989711)	Nessus	Unity Linux Local Security Checks	medium
273628	Unity Linux 20.1070a Security Update: kernel (UTSA-2025-989362)	Nessus	Unity Linux Local Security Checks	medium
247475	Linux Distros Unpatched Vulnerability : CVE-2021-4454	Nessus	Misc.	medium
234407	SUSE SLES15 Security Update : kernel (SUSE-SU-2025:1241-1)	Nessus	SuSE Local Security Checks	high
234182	SUSE SLES15 Security Update : kernel (SUSE-SU-2025:1195-1)	Nessus	SuSE Local Security Checks	high

Detections

Analytics

CVE-2021-4454

medium

Tenable Plugins

medium

medium

medium

high

high