In the Linux kernel, the following vulnerability has been resolved: ubifs: rename_whiteout: Fix double free for whiteout_ui->data 'whiteout_ui->data' will be freed twice if space budget fail for rename whiteout operation as following process: rename_whiteout dev = kmalloc whiteout_ui->data = dev kfree(whiteout_ui->data) // Free first time iput(whiteout) ubifs_free_inode kfree(ui->data) // Double free! KASAN reports: ================================================================== BUG: KASAN: double-free or invalid-free in ubifs_free_inode+0x4f/0x70 Call Trace: kfree+0x117/0x490 ubifs_free_inode+0x4f/0x70 [ubifs] i_callback+0x30/0x60 rcu_do_batch+0x366/0xac0 __do_softirq+0x133/0x57f Allocated by task 1506: kmem_cache_alloc_trace+0x3c2/0x7a0 do_rename+0x9b7/0x1150 [ubifs] ubifs_rename+0x106/0x1f0 [ubifs] do_syscall_64+0x35/0x80 Freed by task 1506: kfree+0x117/0x490 do_rename.cold+0x53/0x8a [ubifs] ubifs_rename+0x106/0x1f0 [ubifs] do_syscall_64+0x35/0x80 The buggy address belongs to the object at ffff88810238bed8 which belongs to the cache kmalloc-8 of size 8 ================================================================== Let ubifs_free_inode() free 'whiteout_ui->data'. BTW, delete unused assignment 'whiteout_ui->data_len = 0', process 'ubifs_evict_inode() -> ubifs_jnl_delete_inode() -> ubifs_jnl_write_inode()' doesn't need it (because 'inc_nlink(whiteout)' won't be excuted by 'goto out_release', and the nlink of whiteout inode is 0).

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

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

    ubifs: rename_whiteout: Fix double free for whiteout_ui->data

    'whiteout_ui->data' will be freed twice if space budget fail for     rename whiteout operation as following process:

    rename_whiteout       dev = kmalloc       whiteout_ui->data = dev       kfree(whiteout_ui->data)  // Free first time       iput(whiteout)         ubifs_free_inode           kfree(ui->data)       // Double free!

    KASAN reports:
    ==================================================================     BUG: KASAN: double-free or invalid-free in ubifs_free_inode+0x4f/0x70     Call Trace:
      kfree+0x117/0x490       ubifs_free_inode+0x4f/0x70 [ubifs]       i_callback+0x30/0x60       rcu_do_batch+0x366/0xac0
      __do_softirq+0x133/0x57f

    Allocated by task 1506:
      kmem_cache_alloc_trace+0x3c2/0x7a0       do_rename+0x9b7/0x1150 [ubifs]       ubifs_rename+0x106/0x1f0 [ubifs]       do_syscall_64+0x35/0x80

    Freed by task 1506:
      kfree+0x117/0x490       do_rename.cold+0x53/0x8a [ubifs]       ubifs_rename+0x106/0x1f0 [ubifs]       do_syscall_64+0x35/0x80

    The buggy address belongs to the object at ffff88810238bed8 which     belongs to the cache kmalloc-8 of size 8     ==================================================================

    Let ubifs_free_inode() free 'whiteout_ui->data'. BTW, delete unused     assignment 'whiteout_ui->data_len = 0', process 'ubifs_evict_inode()
    -> ubifs_jnl_delete_inode() -> ubifs_jnl_write_inode()' doesn't need it     (because 'inc_nlink(whiteout)' won't be excuted by 'goto out_release',      and the nlink of whiteout inode is 0).

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

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

    ubifs: rename_whiteout: Fix double free for whiteout_ui->data

    'whiteout_ui->data' will be freed twice if space budget fail for     rename whiteout operation as following process:

    rename_whiteout       dev = kmalloc       whiteout_ui->data = dev       kfree(whiteout_ui->data)  // Free first time       iput(whiteout)         ubifs_free_inode           kfree(ui->data)       // Double free!

    KASAN reports:
    ==================================================================     BUG: KASAN: double-free or invalid-free in ubifs_free_inode+0x4f/0x70     Call Trace:
      kfree+0x117/0x490       ubifs_free_inode+0x4f/0x70 [ubifs]       i_callback+0x30/0x60       rcu_do_batch+0x366/0xac0
      __do_softirq+0x133/0x57f

    Allocated by task 1506:
      kmem_cache_alloc_trace+0x3c2/0x7a0       do_rename+0x9b7/0x1150 [ubifs]       ubifs_rename+0x106/0x1f0 [ubifs]       do_syscall_64+0x35/0x80

    Freed by task 1506:
      kfree+0x117/0x490       do_rename.cold+0x53/0x8a [ubifs]       ubifs_rename+0x106/0x1f0 [ubifs]       do_syscall_64+0x35/0x80

    The buggy address belongs to the object at ffff88810238bed8 which     belongs to the cache kmalloc-8 of size 8     ==================================================================

    Let ubifs_free_inode() free 'whiteout_ui->data'. BTW, delete unused     assignment 'whiteout_ui->data_len = 0', process 'ubifs_evict_inode()
    -> ubifs_jnl_delete_inode() -> ubifs_jnl_write_inode()' doesn't need it     (because 'inc_nlink(whiteout)' won't be excuted by 'goto out_release',      and the nlink of whiteout inode is 0).

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.

  - In the Linux kernel, the following vulnerability has been resolved: ubifs: rename_whiteout: Fix double     free for whiteout_ui->data 'whiteout_ui->data' will be freed twice if space budget fail for rename     whiteout operation as following process: rename_whiteout dev = kmalloc whiteout_ui->data = dev     kfree(whiteout_ui->data) // Free first time iput(whiteout) ubifs_free_inode kfree(ui->data) // Double     free! KASAN reports: ================================================================== BUG: KASAN:
    double-free or invalid-free in ubifs_free_inode+0x4f/0x70 Call Trace: kfree+0x117/0x490     ubifs_free_inode+0x4f/0x70 [ubifs] i_callback+0x30/0x60 rcu_do_batch+0x366/0xac0 __do_softirq+0x133/0x57f     Allocated by task 1506: kmem_cache_alloc_trace+0x3c2/0x7a0 do_rename+0x9b7/0x1150 [ubifs]     ubifs_rename+0x106/0x1f0 [ubifs] do_syscall_64+0x35/0x80 Freed by task 1506: kfree+0x117/0x490     do_rename.cold+0x53/0x8a [ubifs] ubifs_rename+0x106/0x1f0 [ubifs] do_syscall_64+0x35/0x80 The buggy     address belongs to the object at ffff88810238bed8 which belongs to the cache kmalloc-8 of size 8     ================================================================== Let ubifs_free_inode() free     'whiteout_ui->data'. BTW, delete unused assignment 'whiteout_ui->data_len = 0', process     'ubifs_evict_inode() -> ubifs_jnl_delete_inode() -> ubifs_jnl_write_inode()' doesn't need it (because     'inc_nlink(whiteout)' won't be excuted by 'goto out_release', and the nlink of whiteout inode is 0).
    (CVE-2021-47638)

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

ID	Name	Product	Family	Severity
274056	Unity Linux 20.1070a Security Update: kernel (UTSA-2025-988837)	Nessus	Unity Linux Local Security Checks	medium
268489	Unity Linux 20.1070e Security Update: kernel (UTSA-2025-986804)	Nessus	Unity Linux Local Security Checks	medium
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
224467	Linux Distros Unpatched Vulnerability : CVE-2021-47638	Nessus	Misc.	medium

Detections

Analytics

CVE-2021-47638

medium

Tenable Plugins

medium

medium

high

high

medium