In the Linux kernel, the following vulnerability has been resolved: ubifs: Fix deadlock in concurrent rename whiteout and inode writeback Following hung tasks: [ 77.028764] task:kworker/u8:4 state:D stack: 0 pid: 132 [ 77.028820] Call Trace: [ 77.029027] schedule+0x8c/0x1b0 [ 77.029067] mutex_lock+0x50/0x60 [ 77.029074] ubifs_write_inode+0x68/0x1f0 [ubifs] [ 77.029117] __writeback_single_inode+0x43c/0x570 [ 77.029128] writeback_sb_inodes+0x259/0x740 [ 77.029148] wb_writeback+0x107/0x4d0 [ 77.029163] wb_workfn+0x162/0x7b0 [ 92.390442] task:aa state:D stack: 0 pid: 1506 [ 92.390448] Call Trace: [ 92.390458] schedule+0x8c/0x1b0 [ 92.390461] wb_wait_for_completion+0x82/0xd0 [ 92.390469] __writeback_inodes_sb_nr+0xb2/0x110 [ 92.390472] writeback_inodes_sb_nr+0x14/0x20 [ 92.390476] ubifs_budget_space+0x705/0xdd0 [ubifs] [ 92.390503] do_rename.cold+0x7f/0x187 [ubifs] [ 92.390549] ubifs_rename+0x8b/0x180 [ubifs] [ 92.390571] vfs_rename+0xdb2/0x1170 [ 92.390580] do_renameat2+0x554/0x770 , are caused by concurrent rename whiteout and inode writeback processes: rename_whiteout(Thread 1) wb_workfn(Thread2) ubifs_rename do_rename lock_4_inodes (Hold ui_mutex) ubifs_budget_space make_free_space shrink_liability __writeback_inodes_sb_nr bdi_split_work_to_wbs (Queue new wb work) wb_do_writeback(wb work) __writeback_single_inode ubifs_write_inode LOCK(ui_mutex) ↑ wb_wait_for_completion (Wait wb work) <-- deadlock! Reproducer (Detail program in [Link]): 1. SYS_renameat2("/mp/dir/file", "/mp/dir/whiteout", RENAME_WHITEOUT) 2. Consume out of space before kernel(mdelay) doing budget for whiteout Fix it by doing whiteout space budget before locking ubifs inodes. BTW, it also fixes wrong goto tag 'out_release' in whiteout budget error handling path(It should at least recover dir i_size and unlock 4 ubifs inodes).

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

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

    ubifs: Fix deadlock in concurrent rename whiteout and inode writeback

    Following hung tasks:
    [   77.028764] task:kworker/u8:4    state:D stack:    0 pid:  132     [   77.028820] Call Trace:
    [   77.029027]  schedule+0x8c/0x1b0     [   77.029067]  mutex_lock+0x50/0x60     [   77.029074]  ubifs_write_inode+0x68/0x1f0 [ubifs]     [   77.029117]  __writeback_single_inode+0x43c/0x570     [   77.029128]  writeback_sb_inodes+0x259/0x740     [   77.029148]  wb_writeback+0x107/0x4d0     [   77.029163]  wb_workfn+0x162/0x7b0

    [   92.390442] task:aa              state:D stack:    0 pid: 1506     [   92.390448] Call Trace:
    [   92.390458]  schedule+0x8c/0x1b0     [   92.390461]  wb_wait_for_completion+0x82/0xd0     [   92.390469]  __writeback_inodes_sb_nr+0xb2/0x110     [   92.390472]  writeback_inodes_sb_nr+0x14/0x20     [   92.390476]  ubifs_budget_space+0x705/0xdd0 [ubifs]     [   92.390503]  do_rename.cold+0x7f/0x187 [ubifs]     [   92.390549]  ubifs_rename+0x8b/0x180 [ubifs]     [   92.390571]  vfs_rename+0xdb2/0x1170     [   92.390580]  do_renameat2+0x554/0x770

    , are caused by concurrent rename whiteout and inode writeback processes:
            rename_whiteout(Thread 1)               wb_workfn(Thread2)     ubifs_rename       do_rename         lock_4_inodes (Hold ui_mutex)         ubifs_budget_space           make_free_space             shrink_liability
              __writeback_inodes_sb_nr                 bdi_split_work_to_wbs (Queue new wb work)                                                   wb_do_writeback(wb work)
                                                    __writeback_single_inode                                                       ubifs_write_inode                                                         LOCK(ui_mutex)                                                                                  wb_wait_for_completion (Wait wb work) <-- deadlock!

    Reproducer (Detail program in [Link]):
      1. SYS_renameat2(/mp/dir/file, /mp/dir/whiteout, RENAME_WHITEOUT)       2. Consume out of space before kernel(mdelay) doing budget for whiteout

    Fix it by doing whiteout space budget before locking ubifs inodes.
    BTW, it also fixes wrong goto tag 'out_release' in whiteout budget     error handling path(It should at least recover dir i_size and unlock     4 ubifs inodes).

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

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

    ubifs: Fix deadlock in concurrent rename whiteout and inode writeback

    Following hung tasks:
    [   77.028764] task:kworker/u8:4    state:D stack:    0 pid:  132     [   77.028820] Call Trace:
    [   77.029027]  schedule+0x8c/0x1b0     [   77.029067]  mutex_lock+0x50/0x60     [   77.029074]  ubifs_write_inode+0x68/0x1f0 [ubifs]     [   77.029117]  __writeback_single_inode+0x43c/0x570     [   77.029128]  writeback_sb_inodes+0x259/0x740     [   77.029148]  wb_writeback+0x107/0x4d0     [   77.029163]  wb_workfn+0x162/0x7b0

    [   92.390442] task:aa              state:D stack:    0 pid: 1506     [   92.390448] Call Trace:
    [   92.390458]  schedule+0x8c/0x1b0     [   92.390461]  wb_wait_for_completion+0x82/0xd0     [   92.390469]  __writeback_inodes_sb_nr+0xb2/0x110     [   92.390472]  writeback_inodes_sb_nr+0x14/0x20     [   92.390476]  ubifs_budget_space+0x705/0xdd0 [ubifs]     [   92.390503]  do_rename.cold+0x7f/0x187 [ubifs]     [   92.390549]  ubifs_rename+0x8b/0x180 [ubifs]     [   92.390571]  vfs_rename+0xdb2/0x1170     [   92.390580]  do_renameat2+0x554/0x770

    , are caused by concurrent rename whiteout and inode writeback processes:
            rename_whiteout(Thread 1)               wb_workfn(Thread2)     ubifs_rename       do_rename         lock_4_inodes (Hold ui_mutex)         ubifs_budget_space           make_free_space             shrink_liability
              __writeback_inodes_sb_nr                 bdi_split_work_to_wbs (Queue new wb work)                                                   wb_do_writeback(wb work)
                                                    __writeback_single_inode                                                       ubifs_write_inode                                                         LOCK(ui_mutex)                                                                                  wb_wait_for_completion (Wait wb work) <-- deadlock!

    Reproducer (Detail program in [Link]):
      1. SYS_renameat2(/mp/dir/file, /mp/dir/whiteout, RENAME_WHITEOUT)       2. Consume out of space before kernel(mdelay) doing budget for whiteout

    Fix it by doing whiteout space budget before locking ubifs inodes.
    BTW, it also fixes wrong goto tag 'out_release' in whiteout budget     error handling path(It should at least recover dir i_size and unlock     4 ubifs inodes).

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: Fix deadlock in concurrent     rename whiteout and inode writeback Following hung tasks: [ 77.028764] task:kworker/u8:4 state:D stack: 0     pid: 132 [ 77.028820] Call Trace: [ 77.029027] schedule+0x8c/0x1b0 [ 77.029067] mutex_lock+0x50/0x60 [     77.029074] ubifs_write_inode+0x68/0x1f0 [ubifs] [ 77.029117] __writeback_single_inode+0x43c/0x570 [     77.029128] writeback_sb_inodes+0x259/0x740 [ 77.029148] wb_writeback+0x107/0x4d0 [ 77.029163]     wb_workfn+0x162/0x7b0 [ 92.390442] task:aa state:D stack: 0 pid: 1506 [ 92.390448] Call Trace: [     92.390458] schedule+0x8c/0x1b0 [ 92.390461] wb_wait_for_completion+0x82/0xd0 [ 92.390469]
    __writeback_inodes_sb_nr+0xb2/0x110 [ 92.390472] writeback_inodes_sb_nr+0x14/0x20 [ 92.390476]     ubifs_budget_space+0x705/0xdd0 [ubifs] [ 92.390503] do_rename.cold+0x7f/0x187 [ubifs] [ 92.390549]     ubifs_rename+0x8b/0x180 [ubifs] [ 92.390571] vfs_rename+0xdb2/0x1170 [ 92.390580] do_renameat2+0x554/0x770     , are caused by concurrent rename whiteout and inode writeback processes: rename_whiteout(Thread 1)     wb_workfn(Thread2) ubifs_rename do_rename lock_4_inodes (Hold ui_mutex) ubifs_budget_space make_free_space     shrink_liability __writeback_inodes_sb_nr bdi_split_work_to_wbs (Queue new wb work) wb_do_writeback(wb     work) __writeback_single_inode ubifs_write_inode LOCK(ui_mutex)  wb_wait_for_completion (Wait wb work)     <-- deadlock! Reproducer (Detail program in [Link]): 1. SYS_renameat2(/mp/dir/file, /mp/dir/whiteout,     RENAME_WHITEOUT) 2. Consume out of space before kernel(mdelay) doing budget for whiteout Fix it by doing     whiteout space budget before locking ubifs inodes. BTW, it also fixes wrong goto tag 'out_release' in     whiteout budget error handling path(It should at least recover dir i_size and unlock 4 ubifs inodes).
    (CVE-2021-47637)

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

ID	Name	Product	Family	Severity
272989	Unity Linux 20.1070a Security Update: kernel (UTSA-2025-989766)	Nessus	Unity Linux Local Security Checks	medium
269032	Unity Linux 20.1070e Security Update: kernel (UTSA-2025-986880)	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
229809	Linux Distros Unpatched Vulnerability : CVE-2021-47637	Nessus	Misc.	medium

Detections

Analytics

CVE-2021-47637

medium

Tenable Plugins

medium

medium

high

high

medium