In the Linux kernel, the following vulnerability has been resolved: jffs2: fix use-after-free in jffs2_clear_xattr_subsystem When we mount a jffs2 image, assume that the first few blocks of the image are normal and contain at least one xattr-related inode, but the next block is abnormal. As a result, an error is returned in jffs2_scan_eraseblock(). jffs2_clear_xattr_subsystem() is then called in jffs2_build_filesystem() and then again in jffs2_do_fill_super(). Finally we can observe the following report: ================================================================== BUG: KASAN: use-after-free in jffs2_clear_xattr_subsystem+0x95/0x6ac Read of size 8 at addr ffff8881243384e0 by task mount/719 Call Trace: dump_stack+0x115/0x16b jffs2_clear_xattr_subsystem+0x95/0x6ac jffs2_do_fill_super+0x84f/0xc30 jffs2_fill_super+0x2ea/0x4c0 mtd_get_sb+0x254/0x400 mtd_get_sb_by_nr+0x4f/0xd0 get_tree_mtd+0x498/0x840 jffs2_get_tree+0x25/0x30 vfs_get_tree+0x8d/0x2e0 path_mount+0x50f/0x1e50 do_mount+0x107/0x130 __se_sys_mount+0x1c5/0x2f0 __x64_sys_mount+0xc7/0x160 do_syscall_64+0x45/0x70 entry_SYSCALL_64_after_hwframe+0x44/0xa9 Allocated by task 719: kasan_save_stack+0x23/0x60 __kasan_kmalloc.constprop.0+0x10b/0x120 kasan_slab_alloc+0x12/0x20 kmem_cache_alloc+0x1c0/0x870 jffs2_alloc_xattr_ref+0x2f/0xa0 jffs2_scan_medium.cold+0x3713/0x4794 jffs2_do_mount_fs.cold+0xa7/0x2253 jffs2_do_fill_super+0x383/0xc30 jffs2_fill_super+0x2ea/0x4c0 [...] Freed by task 719: kmem_cache_free+0xcc/0x7b0 jffs2_free_xattr_ref+0x78/0x98 jffs2_clear_xattr_subsystem+0xa1/0x6ac jffs2_do_mount_fs.cold+0x5e6/0x2253 jffs2_do_fill_super+0x383/0xc30 jffs2_fill_super+0x2ea/0x4c0 [...] The buggy address belongs to the object at ffff8881243384b8 which belongs to the cache jffs2_xattr_ref of size 48 The buggy address is located 40 bytes inside of 48-byte region [ffff8881243384b8, ffff8881243384e8) [...] ================================================================== The triggering of the BUG is shown in the following stack: ----------------------------------------------------------- jffs2_fill_super jffs2_do_fill_super jffs2_do_mount_fs jffs2_build_filesystem jffs2_scan_medium jffs2_scan_eraseblock <--- ERROR jffs2_clear_xattr_subsystem <--- free jffs2_clear_xattr_subsystem <--- free again ----------------------------------------------------------- An error is returned in jffs2_do_mount_fs(). If the error is returned by jffs2_sum_init(), the jffs2_clear_xattr_subsystem() does not need to be executed. If the error is returned by jffs2_build_filesystem(), the jffs2_clear_xattr_subsystem() also does not need to be executed again. So move jffs2_clear_xattr_subsystem() from 'out_inohash' to 'out_root' to fix this UAF problem.

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

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

    jffs2: fix use-after-free in jffs2_clear_xattr_subsystem

    When we mount a jffs2 image, assume that the first few blocks of     the image are normal and contain at least one xattr-related inode,     but the next block is abnormal. As a result, an error is returned     in jffs2_scan_eraseblock(). jffs2_clear_xattr_subsystem() is then     called in jffs2_build_filesystem() and then again in     jffs2_do_fill_super().

    Finally we can observe the following report:
     ==================================================================      BUG: KASAN: use-after-free in jffs2_clear_xattr_subsystem+0x95/0x6ac      Read of size 8 at addr ffff8881243384e0 by task mount/719

     Call Trace:
      dump_stack+0x115/0x16b       jffs2_clear_xattr_subsystem+0x95/0x6ac       jffs2_do_fill_super+0x84f/0xc30       jffs2_fill_super+0x2ea/0x4c0       mtd_get_sb+0x254/0x400       mtd_get_sb_by_nr+0x4f/0xd0       get_tree_mtd+0x498/0x840       jffs2_get_tree+0x25/0x30       vfs_get_tree+0x8d/0x2e0       path_mount+0x50f/0x1e50       do_mount+0x107/0x130
      __se_sys_mount+0x1c5/0x2f0
      __x64_sys_mount+0xc7/0x160       do_syscall_64+0x45/0x70       entry_SYSCALL_64_after_hwframe+0x44/0xa9

     Allocated by task 719:
      kasan_save_stack+0x23/0x60
      __kasan_kmalloc.constprop.0+0x10b/0x120       kasan_slab_alloc+0x12/0x20       kmem_cache_alloc+0x1c0/0x870       jffs2_alloc_xattr_ref+0x2f/0xa0       jffs2_scan_medium.cold+0x3713/0x4794       jffs2_do_mount_fs.cold+0xa7/0x2253       jffs2_do_fill_super+0x383/0xc30       jffs2_fill_super+0x2ea/0x4c0      [...]

     Freed by task 719:
      kmem_cache_free+0xcc/0x7b0       jffs2_free_xattr_ref+0x78/0x98       jffs2_clear_xattr_subsystem+0xa1/0x6ac       jffs2_do_mount_fs.cold+0x5e6/0x2253       jffs2_do_fill_super+0x383/0xc30       jffs2_fill_super+0x2ea/0x4c0      [...]

     The buggy address belongs to the object at ffff8881243384b8       which belongs to the cache jffs2_xattr_ref of size 48      The buggy address is located 40 bytes inside of       48-byte region [ffff8881243384b8, ffff8881243384e8)      [...]      ==================================================================

    The triggering of the BUG is shown in the following stack:
    -----------------------------------------------------------     jffs2_fill_super       jffs2_do_fill_super         jffs2_do_mount_fs           jffs2_build_filesystem             jffs2_scan_medium               jffs2_scan_eraseblock        <--- ERROR             jffs2_clear_xattr_subsystem    <--- free         jffs2_clear_xattr_subsystem        <--- free again
    -----------------------------------------------------------

    An error is returned in jffs2_do_mount_fs(). If the error is returned     by jffs2_sum_init(), the jffs2_clear_xattr_subsystem() does not need to     be executed. If the error is returned by jffs2_build_filesystem(), the     jffs2_clear_xattr_subsystem() also does not need to be executed again.
    So move jffs2_clear_xattr_subsystem() from 'out_inohash' to 'out_root'     to fix this UAF problem.

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

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

    jffs2: fix use-after-free in jffs2_clear_xattr_subsystem

    When we mount a jffs2 image, assume that the first few blocks of     the image are normal and contain at least one xattr-related inode,     but the next block is abnormal. As a result, an error is returned     in jffs2_scan_eraseblock(). jffs2_clear_xattr_subsystem() is then     called in jffs2_build_filesystem() and then again in     jffs2_do_fill_super().

    Finally we can observe the following report:
     ==================================================================      BUG: KASAN: use-after-free in jffs2_clear_xattr_subsystem+0x95/0x6ac      Read of size 8 at addr ffff8881243384e0 by task mount/719

     Call Trace:
      dump_stack+0x115/0x16b       jffs2_clear_xattr_subsystem+0x95/0x6ac       jffs2_do_fill_super+0x84f/0xc30       jffs2_fill_super+0x2ea/0x4c0       mtd_get_sb+0x254/0x400       mtd_get_sb_by_nr+0x4f/0xd0       get_tree_mtd+0x498/0x840       jffs2_get_tree+0x25/0x30       vfs_get_tree+0x8d/0x2e0       path_mount+0x50f/0x1e50       do_mount+0x107/0x130
      __se_sys_mount+0x1c5/0x2f0
      __x64_sys_mount+0xc7/0x160       do_syscall_64+0x45/0x70       entry_SYSCALL_64_after_hwframe+0x44/0xa9

     Allocated by task 719:
      kasan_save_stack+0x23/0x60
      __kasan_kmalloc.constprop.0+0x10b/0x120       kasan_slab_alloc+0x12/0x20       kmem_cache_alloc+0x1c0/0x870       jffs2_alloc_xattr_ref+0x2f/0xa0       jffs2_scan_medium.cold+0x3713/0x4794       jffs2_do_mount_fs.cold+0xa7/0x2253       jffs2_do_fill_super+0x383/0xc30       jffs2_fill_super+0x2ea/0x4c0      [...]

     Freed by task 719:
      kmem_cache_free+0xcc/0x7b0       jffs2_free_xattr_ref+0x78/0x98       jffs2_clear_xattr_subsystem+0xa1/0x6ac       jffs2_do_mount_fs.cold+0x5e6/0x2253       jffs2_do_fill_super+0x383/0xc30       jffs2_fill_super+0x2ea/0x4c0      [...]

     The buggy address belongs to the object at ffff8881243384b8       which belongs to the cache jffs2_xattr_ref of size 48      The buggy address is located 40 bytes inside of       48-byte region [ffff8881243384b8, ffff8881243384e8)      [...]      ==================================================================

    The triggering of the BUG is shown in the following stack:
    -----------------------------------------------------------     jffs2_fill_super       jffs2_do_fill_super         jffs2_do_mount_fs           jffs2_build_filesystem             jffs2_scan_medium               jffs2_scan_eraseblock        <--- ERROR             jffs2_clear_xattr_subsystem    <--- free         jffs2_clear_xattr_subsystem        <--- free again
    -----------------------------------------------------------

    An error is returned in jffs2_do_mount_fs(). If the error is returned     by jffs2_sum_init(), the jffs2_clear_xattr_subsystem() does not need to     be executed. If the error is returned by jffs2_build_filesystem(), the     jffs2_clear_xattr_subsystem() also does not need to be executed again.
    So move jffs2_clear_xattr_subsystem() from 'out_inohash' to 'out_root'     to fix this UAF problem.

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.

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.

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

  - jffs2: fix use-after-free in jffs2_clear_xattr_subsystem When we mount a jffs2 image, assume that the     first few blocks of the image are normal and contain at least one xattr-related inode, but the next block     is abnormal. As a result, an error is returned in jffs2_scan_eraseblock(). jffs2_clear_xattr_subsystem()     is then called in jffs2_build_filesystem() and then again in jffs2_do_fill_super(). Finally we can observe     the following report: ================================================================== BUG: KASAN: use-     after-free in jffs2_clear_xattr_subsystem+0x95/0x6ac Read of size 8 at addr ffff8881243384e0 by task     mount/719 Call Trace: dump_stack+0x115/0x16b jffs2_clear_xattr_subsystem+0x95/0x6ac     jffs2_do_fill_super+0x84f/0xc30 jffs2_fill_super+0x2ea/0x4c0 mtd_get_sb+0x254/0x400     mtd_get_sb_by_nr+0x4f/0xd0 get_tree_mtd+0x498/0x840 jffs2_get_tree+0x25/0x30 vfs_get_tree+0x8d/0x2e0     path_mount+0x50f/0x1e50 do_mount+0x107/0x130 __se_sys_mount+0x1c5/0x2f0 __x64_sys_mount+0xc7/0x160     do_syscall_64+0x45/0x70 entry_SYSCALL_64_after_hwframe+0x44/0xa9 Allocated by task 719:
    kasan_save_stack+0x23/0x60 __kasan_kmalloc.constprop.0+0x10b/0x120 kasan_slab_alloc+0x12/0x20     kmem_cache_alloc+0x1c0/0x870 jffs2_alloc_xattr_ref+0x2f/0xa0 jffs2_scan_medium.cold+0x3713/0x4794     jffs2_do_mount_fs.cold+0xa7/0x2253 jffs2_do_fill_super+0x383/0xc30 jffs2_fill_super+0x2ea/0x4c0 [...]     Freed by task 719: kmem_cache_free+0xcc/0x7b0 jffs2_free_xattr_ref+0x78/0x98     jffs2_clear_xattr_subsystem+0xa1/0x6ac jffs2_do_mount_fs.cold+0x5e6/0x2253 jffs2_do_fill_super+0x383/0xc30     jffs2_fill_super+0x2ea/0x4c0 [...] The buggy address belongs to the object at ffff8881243384b8 which     belongs to the cache jffs2_xattr_ref of size 48 The buggy address is located 40 bytes inside of 48-byte     region [ffff8881243384b8, ffff8881243384e8) [...]     ================================================================== The triggering of the BUG is shown in     the following stack: ----------------------------------------------------------- jffs2_fill_super     jffs2_do_fill_super jffs2_do_mount_fs jffs2_build_filesystem jffs2_scan_medium jffs2_scan_eraseblock <---     ERROR jffs2_clear_xattr_subsystem <--- free jffs2_clear_xattr_subsystem <--- free again
    ----------------------------------------------------------- An error is returned in jffs2_do_mount_fs().
    If the error is returned by jffs2_sum_init(), the jffs2_clear_xattr_subsystem() does not need to be     executed. If the error is returned by jffs2_build_filesystem(), the jffs2_clear_xattr_subsystem() also     does not need to be executed again. So move jffs2_clear_xattr_subsystem() from 'out_inohash' to 'out_root'     to fix this UAF problem. (CVE-2021-47656)

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

ID	Name	Product	Family	Severity
273689	Unity Linux 20.1070a Security Update: kernel (UTSA-2025-989825)	Nessus	Unity Linux Local Security Checks	high
268432	Unity Linux 20.1070e Security Update: kernel (UTSA-2025-987398)	Nessus	Unity Linux Local Security Checks	high
234407	SUSE SLES15 Security Update : kernel (SUSE-SU-2025:1241-1)	Nessus	SuSE Local Security Checks	high
233410	SUSE SLES15 Security Update : kernel (SUSE-SU-2025:1027-1)	Nessus	SuSE Local Security Checks	high
224374	Linux Distros Unpatched Vulnerability : CVE-2021-47656	Nessus	Misc.	high

Detections

Analytics

CVE-2021-47656

high

Tenable Plugins

high

high

high

high

high