The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - jffs2: fix memory leak in jffs2_scan_medium If an error is returned in jffs2_scan_eraseblock() and some     memory has been added to the jffs2_summary *s, we can observe the following kmemleak report:
    -------------------------------------------- unreferenced object 0xffff88812b889c40 (size 64): comm     mount, pid 692, jiffies 4294838325 (age 34.288s) hex dump (first 32 bytes): 40 48 b5 14 81 88 ff ff 01     e0 31 00 00 00 50 00 @H........1...P. 00 00 01 00 00 00 01 00 00 00 02 00 00 00 09 08 ................
    backtrace: [<ffffffffae93a3a3>] __kmalloc+0x613/0x910 [<ffffffffaf423b9c>]     jffs2_sum_add_dirent_mem+0x5c/0xa0 [<ffffffffb0f3afa8>] jffs2_scan_medium.cold+0x36e5/0x4794     [<ffffffffb0f3dbe1>] jffs2_do_mount_fs.cold+0xa7/0x2267 [<ffffffffaf40acf3>]     jffs2_do_fill_super+0x383/0xc30 [<ffffffffaf40c00a>] jffs2_fill_super+0x2ea/0x4c0 [<ffffffffb0315d64>]     mtd_get_sb+0x254/0x400 [<ffffffffb0315f5f>] mtd_get_sb_by_nr+0x4f/0xd0 [<ffffffffb0316478>]     get_tree_mtd+0x498/0x840 [<ffffffffaf40bd15>] jffs2_get_tree+0x25/0x30 [<ffffffffae9f358d>]     vfs_get_tree+0x8d/0x2e0 [<ffffffffaea7a98f>] path_mount+0x50f/0x1e50 [<ffffffffaea7c3d7>]     do_mount+0x107/0x130 [<ffffffffaea7c5c5>] __se_sys_mount+0x1c5/0x2f0 [<ffffffffaea7c917>]
    __x64_sys_mount+0xc7/0x160 [<ffffffffb10142f5>] do_syscall_64+0x45/0x70 unreferenced object     0xffff888114b54840 (size 32): comm mount, pid 692, jiffies 4294838325 (age 34.288s) hex dump (first 32     bytes): c0 75 b5 14 81 88 ff ff 02 e0 02 00 00 00 02 00 .u.............. 00 00 84 00 00 00 44 00 00 00 6b     6b 6b 6b 6b a5 ......D...kkkkk. backtrace: [<ffffffffae93be24>] kmem_cache_alloc_trace+0x584/0x880     [<ffffffffaf423b04>] jffs2_sum_add_inode_mem+0x54/0x90 [<ffffffffb0f3bd44>]     jffs2_scan_medium.cold+0x4481/0x4794 [...] unreferenced object 0xffff888114b57280 (size 32): comm mount,     pid 692, jiffies 4294838393 (age 34.357s) hex dump (first 32 bytes): 10 d5 6c 11 81 88 ff ff 08 e0 05 00     00 00 01 00 ..l............. 00 00 38 02 00 00 28 00 00 00 6b 6b 6b 6b 6b a5 ..8...(...kkkkk. backtrace:
    [<ffffffffae93be24>] kmem_cache_alloc_trace+0x584/0x880 [<ffffffffaf423c34>]     jffs2_sum_add_xattr_mem+0x54/0x90 [<ffffffffb0f3a24f>] jffs2_scan_medium.cold+0x298c/0x4794 [...]     unreferenced object 0xffff8881116cd510 (size 16): comm mount, pid 692, jiffies 4294838395 (age 34.355s)     hex dump (first 16 bytes): 00 00 00 00 00 00 00 00 09 e0 60 02 00 00 6b a5 ..........`...k. backtrace:
    [<ffffffffae93be24>] kmem_cache_alloc_trace+0x584/0x880 [<ffffffffaf423cc4>]     jffs2_sum_add_xref_mem+0x54/0x90 [<ffffffffb0f3b2e3>] jffs2_scan_medium.cold+0x3a20/0x4794 [...]
    -------------------------------------------- Therefore, we should call jffs2_sum_reset_collected(s) on     exit to release the memory added in s. In addition, a new tag out_buf is added to prevent the NULL     pointer reference caused by s being NULL. (thanks to Zhang Yi for this analysis) (CVE-2022-49276)

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-2025-987523 advisory.

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

    jffs2: fix memory leak in jffs2_scan_medium

    If an error is returned in jffs2_scan_eraseblock() and some memory     has been added to the jffs2_summary *s, we can observe the following     kmemleak report:

    --------------------------------------------     unreferenced object 0xffff88812b889c40 (size 64):
      comm mount, pid 692, jiffies 4294838325 (age 34.288s)       hex dump (first 32 bytes):
        40 48 b5 14 81 88 ff ff 01 e0 31 00 00 00 50 00  @H........1...P.
        00 00 01 00 00 00 01 00 00 00 02 00 00 00 09 08  ................
      backtrace:
        [<ffffffffae93a3a3>] __kmalloc+0x613/0x910         [<ffffffffaf423b9c>] jffs2_sum_add_dirent_mem+0x5c/0xa0         [<ffffffffb0f3afa8>] jffs2_scan_medium.cold+0x36e5/0x4794         [<ffffffffb0f3dbe1>] jffs2_do_mount_fs.cold+0xa7/0x2267         [<ffffffffaf40acf3>] jffs2_do_fill_super+0x383/0xc30         [<ffffffffaf40c00a>] jffs2_fill_super+0x2ea/0x4c0         [<ffffffffb0315d64>] mtd_get_sb+0x254/0x400         [<ffffffffb0315f5f>] mtd_get_sb_by_nr+0x4f/0xd0         [<ffffffffb0316478>] get_tree_mtd+0x498/0x840         [<ffffffffaf40bd15>] jffs2_get_tree+0x25/0x30         [<ffffffffae9f358d>] vfs_get_tree+0x8d/0x2e0         [<ffffffffaea7a98f>] path_mount+0x50f/0x1e50         [<ffffffffaea7c3d7>] do_mount+0x107/0x130         [<ffffffffaea7c5c5>] __se_sys_mount+0x1c5/0x2f0         [<ffffffffaea7c917>] __x64_sys_mount+0xc7/0x160         [<ffffffffb10142f5>] do_syscall_64+0x45/0x70     unreferenced object 0xffff888114b54840 (size 32):
      comm mount, pid 692, jiffies 4294838325 (age 34.288s)       hex dump (first 32 bytes):
        c0 75 b5 14 81 88 ff ff 02 e0 02 00 00 00 02 00  .u..............
        00 00 84 00 00 00 44 00 00 00 6b 6b 6b 6b 6b a5  ......D...kkkkk.
      backtrace:
        [<ffffffffae93be24>] kmem_cache_alloc_trace+0x584/0x880         [<ffffffffaf423b04>] jffs2_sum_add_inode_mem+0x54/0x90         [<ffffffffb0f3bd44>] jffs2_scan_medium.cold+0x4481/0x4794         [...]     unreferenced object 0xffff888114b57280 (size 32):
      comm mount, pid 692, jiffies 4294838393 (age 34.357s)       hex dump (first 32 bytes):
        10 d5 6c 11 81 88 ff ff 08 e0 05 00 00 00 01 00  ..l.............
        00 00 38 02 00 00 28 00 00 00 6b 6b 6b 6b 6b a5  ..8...(...kkkkk.
      backtrace:
        [<ffffffffae93be24>] kmem_cache_alloc_trace+0x584/0x880         [<ffffffffaf423c34>] jffs2_sum_add_xattr_mem+0x54/0x90         [<ffffffffb0f3a24f>] jffs2_scan_medium.cold+0x298c/0x4794         [...]     unreferenced object 0xffff8881116cd510 (size 16):
      comm mount, pid 692, jiffies 4294838395 (age 34.355s)       hex dump (first 16 bytes):
        00 00 00 00 00 00 00 00 09 e0 60 02 00 00 6b a5  ..........`...k.
      backtrace:
        [<ffffffffae93be24>] kmem_cache_alloc_trace+0x584/0x880         [<ffffffffaf423cc4>] jffs2_sum_add_xref_mem+0x54/0x90         [<ffffffffb0f3b2e3>] jffs2_scan_medium.cold+0x3a20/0x4794         [...]
    --------------------------------------------

    Therefore, we should call jffs2_sum_reset_collected(s) on exit to     release the memory added in s. In addition, a new tag out_buf is     added to prevent the NULL pointer reference caused by s being NULL.
    (thanks to Zhang Yi for this analysis)

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

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

    jffs2: fix memory leak in jffs2_scan_medium

    If an error is returned in jffs2_scan_eraseblock() and some memory     has been added to the jffs2_summary *s, we can observe the following     kmemleak report:

    --------------------------------------------     unreferenced object 0xffff88812b889c40 (size 64):
      comm mount, pid 692, jiffies 4294838325 (age 34.288s)       hex dump (first 32 bytes):
        40 48 b5 14 81 88 ff ff 01 e0 31 00 00 00 50 00  @H........1...P.
        00 00 01 00 00 00 01 00 00 00 02 00 00 00 09 08  ................
      backtrace:
        [<ffffffffae93a3a3>] __kmalloc+0x613/0x910         [<ffffffffaf423b9c>] jffs2_sum_add_dirent_mem+0x5c/0xa0         [<ffffffffb0f3afa8>] jffs2_scan_medium.cold+0x36e5/0x4794         [<ffffffffb0f3dbe1>] jffs2_do_mount_fs.cold+0xa7/0x2267         [<ffffffffaf40acf3>] jffs2_do_fill_super+0x383/0xc30         [<ffffffffaf40c00a>] jffs2_fill_super+0x2ea/0x4c0         [<ffffffffb0315d64>] mtd_get_sb+0x254/0x400         [<ffffffffb0315f5f>] mtd_get_sb_by_nr+0x4f/0xd0         [<ffffffffb0316478>] get_tree_mtd+0x498/0x840         [<ffffffffaf40bd15>] jffs2_get_tree+0x25/0x30         [<ffffffffae9f358d>] vfs_get_tree+0x8d/0x2e0         [<ffffffffaea7a98f>] path_mount+0x50f/0x1e50         [<ffffffffaea7c3d7>] do_mount+0x107/0x130         [<ffffffffaea7c5c5>] __se_sys_mount+0x1c5/0x2f0         [<ffffffffaea7c917>] __x64_sys_mount+0xc7/0x160         [<ffffffffb10142f5>] do_syscall_64+0x45/0x70     unreferenced object 0xffff888114b54840 (size 32):
      comm mount, pid 692, jiffies 4294838325 (age 34.288s)       hex dump (first 32 bytes):
        c0 75 b5 14 81 88 ff ff 02 e0 02 00 00 00 02 00  .u..............
        00 00 84 00 00 00 44 00 00 00 6b 6b 6b 6b 6b a5  ......D...kkkkk.
      backtrace:
        [<ffffffffae93be24>] kmem_cache_alloc_trace+0x584/0x880         [<ffffffffaf423b04>] jffs2_sum_add_inode_mem+0x54/0x90         [<ffffffffb0f3bd44>] jffs2_scan_medium.cold+0x4481/0x4794         [...]     unreferenced object 0xffff888114b57280 (size 32):
      comm mount, pid 692, jiffies 4294838393 (age 34.357s)       hex dump (first 32 bytes):
        10 d5 6c 11 81 88 ff ff 08 e0 05 00 00 00 01 00  ..l.............
        00 00 38 02 00 00 28 00 00 00 6b 6b 6b 6b 6b a5  ..8...(...kkkkk.
      backtrace:
        [<ffffffffae93be24>] kmem_cache_alloc_trace+0x584/0x880         [<ffffffffaf423c34>] jffs2_sum_add_xattr_mem+0x54/0x90         [<ffffffffb0f3a24f>] jffs2_scan_medium.cold+0x298c/0x4794         [...]     unreferenced object 0xffff8881116cd510 (size 16):
      comm mount, pid 692, jiffies 4294838395 (age 34.355s)       hex dump (first 16 bytes):
        00 00 00 00 00 00 00 00 09 e0 60 02 00 00 6b a5  ..........`...k.
      backtrace:
        [<ffffffffae93be24>] kmem_cache_alloc_trace+0x584/0x880         [<ffffffffaf423cc4>] jffs2_sum_add_xref_mem+0x54/0x90         [<ffffffffb0f3b2e3>] jffs2_scan_medium.cold+0x3a20/0x4794         [...]
    --------------------------------------------

    Therefore, we should call jffs2_sum_reset_collected(s) on exit to     release the memory added in s. In addition, a new tag out_buf is     added to prevent the NULL pointer reference caused by s being NULL.
    (thanks to Zhang Yi for this analysis)

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

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


    The following security bugs were fixed:

    - CVE-2024-2201: Fixed information leak in x86/BHI (bsc#1217339).
    - CVE-2024-41092: drm/i915/gt: Fix potential UAF by revoke of fence registers (bsc#1228483).
    - CVE-2024-42098: crypto: ecdh - explicitly zeroize private_key (bsc#1228779).
    - CVE-2024-42229: crypto: aead,cipher - zeroize key buffer after use (bsc#1228708).
    - CVE-2024-57996: net_sched: sch_sfq: do not allow 1 packet limit (bsc#1239076).
    - CVE-2024-58014: wifi: brcmsmac: add gain range check to wlc_phy_iqcal_gainparams_nphy() (bsc#1239109).
    - CVE-2025-21718: net: rose: fix timer races against user threads (bsc#1239073).
    - 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.

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

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

    jffs2: fix memory leak in jffs2_scan_medium

    If an error is returned in jffs2_scan_eraseblock() and some memory     has been added to the jffs2_summary *s, we can observe the following     kmemleak report:

    --------------------------------------------     unreferenced object 0xffff88812b889c40 (size 64):
      comm mount, pid 692, jiffies 4294838325 (age 34.288s)       hex dump (first 32 bytes):
        40 48 b5 14 81 88 ff ff 01 e0 31 00 00 00 50 00  @H........1...P.
        00 00 01 00 00 00 01 00 00 00 02 00 00 00 09 08  ................
      backtrace:
        [<ffffffffae93a3a3>] __kmalloc+0x613/0x910         [<ffffffffaf423b9c>] jffs2_sum_add_dirent_mem+0x5c/0xa0         [<ffffffffb0f3afa8>] jffs2_scan_medium.cold+0x36e5/0x4794         [<ffffffffb0f3dbe1>] jffs2_do_mount_fs.cold+0xa7/0x2267         [<ffffffffaf40acf3>] jffs2_do_fill_super+0x383/0xc30         [<ffffffffaf40c00a>] jffs2_fill_super+0x2ea/0x4c0         [<ffffffffb0315d64>] mtd_get_sb+0x254/0x400         [<ffffffffb0315f5f>] mtd_get_sb_by_nr+0x4f/0xd0         [<ffffffffb0316478>] get_tree_mtd+0x498/0x840         [<ffffffffaf40bd15>] jffs2_get_tree+0x25/0x30         [<ffffffffae9f358d>] vfs_get_tree+0x8d/0x2e0         [<ffffffffaea7a98f>] path_mount+0x50f/0x1e50         [<ffffffffaea7c3d7>] do_mount+0x107/0x130         [<ffffffffaea7c5c5>] __se_sys_mount+0x1c5/0x2f0         [<ffffffffaea7c917>] __x64_sys_mount+0xc7/0x160         [<ffffffffb10142f5>] do_syscall_64+0x45/0x70     unreferenced object 0xffff888114b54840 (size 32):
      comm mount, pid 692, jiffies 4294838325 (age 34.288s)       hex dump (first 32 bytes):
        c0 75 b5 14 81 88 ff ff 02 e0 02 00 00 00 02 00  .u..............
        00 00 84 00 00 00 44 00 00 00 6b 6b 6b 6b 6b a5  ......D...kkkkk.
      backtrace:
        [<ffffffffae93be24>] kmem_cache_alloc_trace+0x584/0x880         [<ffffffffaf423b04>] jffs2_sum_add_inode_mem+0x54/0x90         [<ffffffffb0f3bd44>] jffs2_scan_medium.cold+0x4481/0x4794         [...]     unreferenced object 0xffff888114b57280 (size 32):
      comm mount, pid 692, jiffies 4294838393 (age 34.357s)       hex dump (first 32 bytes):
        10 d5 6c 11 81 88 ff ff 08 e0 05 00 00 00 01 00  ..l.............
        00 00 38 02 00 00 28 00 00 00 6b 6b 6b 6b 6b a5  ..8...(...kkkkk.
      backtrace:
        [<ffffffffae93be24>] kmem_cache_alloc_trace+0x584/0x880         [<ffffffffaf423c34>] jffs2_sum_add_xattr_mem+0x54/0x90         [<ffffffffb0f3a24f>] jffs2_scan_medium.cold+0x298c/0x4794         [...]     unreferenced object 0xffff8881116cd510 (size 16):
      comm mount, pid 692, jiffies 4294838395 (age 34.355s)       hex dump (first 16 bytes):
        00 00 00 00 00 00 00 00 09 e0 60 02 00 00 6b a5  ..........`...k.
      backtrace:
        [<ffffffffae93be24>] kmem_cache_alloc_trace+0x584/0x880         [<ffffffffaf423cc4>] jffs2_sum_add_xref_mem+0x54/0x90         [<ffffffffb0f3b2e3>] jffs2_scan_medium.cold+0x3a20/0x4794         [...]
    --------------------------------------------

    Therefore, we should call jffs2_sum_reset_collected(s) on exit to     release the memory added in s. In addition, a new tag out_buf is     added to prevent the NULL pointer reference caused by s being NULL.
    (thanks to Zhang Yi for this analysis)

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

ID	Name	Product	Family	Published	Updated	Severity
225333	Linux Distros Unpatched Vulnerability : CVE-2022-49276	Nessus	Misc.	3/5/2025	1/15/2026	medium
270899	Unity Linux 20.1070e Security Update: kernel (UTSA-2025-987523)	Nessus	Unity Linux Local Security Checks	10/21/2025	10/21/2025	medium
274301	Unity Linux 20.1070a Security Update: kernel (UTSA-2025-990527)	Nessus	Unity Linux Local Security Checks	11/6/2025	11/6/2025	medium
233410	SUSE SLES15 Security Update : kernel (SUSE-SU-2025:1027-1)	Nessus	SuSE Local Security Checks	3/27/2025	12/30/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
274046	Unity Linux 20.1070a Security Update: kernel (UTSA-2025-989233)	Nessus	Unity Linux Local Security Checks	11/5/2025	11/5/2025	medium
234407	SUSE SLES15 Security Update : kernel (SUSE-SU-2025:1241-1)	Nessus	SuSE Local Security Checks	4/15/2025	12/30/2025	high

Detections

Analytics

Plugins Search

medium

medium

medium

high

high

medium

high