nday
CVE-2024-53171

ubifs: authentication: Fix use-after-free in ubifs_tnc_end_commit

Linux / Linux

Disclosed . nday has no fix record for it yet; that does not mean no patch exists. None of the four PoC sources lists it. Not in CISA KEV.

tags weakness typeuse-after-free accesslocalno user interaction productLinux kernel product typeoperating system
why these tags

nday derives these tags by fixed rules from the facts below; NVD, the CNA and other sources do not assign them. Vocabulary and rules: ~/tags.

use-after-free
CWE-416, stated by the ADP CISA-ADP, NVD's analysts, and NVD, republishing 134c704f-9b21-4f2e-91b3-4a467353bcc0
local
AV:L in CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (CVSS 3.1) from the CNA Linux
no user interaction
UI:N in CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (CVSS 3.1) from the CNA Linux
Linux kernel
affected products in the CVE record: Linux · LinuxCPE names NVD's analysts give as vulnerable: o:linux:linux_kernel
operating system
affected products in the CVE record: Linux · LinuxCPE names NVD's analysts give as vulnerable: o:linux:linux_kernelthe product type of Linux kernel in nday's product registry
stage
DIS
disclosed
cvss
7.8 HIGH v3.1

Lifecycle

x axis UTC; dot = exact minute, wide bar = date only, hollow = unknown or inferred.
time unknown
DISdisclosed
2024-12-27T13:49Z
PATpatch
no record yet
ANAanalysis
no record yet
POCPoC
no record yet
ITWexploited
no record yet
KEVKEV
no record yet

Summary

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

ubifs: authentication: Fix use-after-free in ubifs_tnc_end_commit

After an insertion in TNC, the tree might split and cause a node to change its znode->parent. A further deletion of other nodes in the tree (which also could free the nodes), the aforementioned node's znode->cparent could still point to a freed node. This znode->cparent may not be updated when getting nodes to commit in ubifs_tnc_start_commit(). This could then trigger a use-after-free when accessing the znode->cparent in write_index() in ubifs_tnc_end_commit().

This can be triggered by running

rm -f /etc/test-file.bin
dd if=/dev/urandom of=/etc/test-file.bin bs=1M count=60 conv=fsync

in a loop, and with CONFIG_UBIFS_FS_AUTHENTICATION. KASAN then reports:

BUG: KASAN: use-after-free in ubifs_tnc_end_commit+0xa5c/0x1950
Write of size 32 at addr ffffff800a3af86c by task ubifs_bgt0_20/153

Call trace:
 dump_backtrace+0x0/0x340
 show_stack+0x18/0x24
 dump_stack_lvl+0x9c/0xbc
 print_address_description.constprop.0+0x74/0x2b0
 kasan_report+0x1d8/0x1f0
 kasan_check_range+0xf8/0x1a0
 memcpy+0x84/0xf4
 ubifs_tnc_end_commit+0xa5c/0x1950
 do_commit+0x4e0/0x1340
 ubifs_bg_thread+0x234/0x2e0
 kthread+0x36c/0x410
 ret_from_fork+0x10/0x20

Allocated by task 401:
 kasan_save_stack+0x38/0x70
 __kasan_kmalloc+0x8c/0xd0
 __kmalloc+0x34c/0x5bc
 tnc_insert+0x140/0x16a4
 ubifs_tnc_add+0x370/0x52c
 ubifs_jnl_write_data+0x5d8/0x870
 do_writepage+0x36c/0x510
 ubifs_writepage+0x190/0x4dc
 __writepage+0x58/0x154
 write_cache_pages+0x394/0x830
 do_writepages+0x1f0/0x5b0
 filemap_fdatawrite_wbc+0x170/0x25c
 file_write_and_wait_range+0x140/0x190
 ubifs_fsync+0xe8/0x290
 vfs_fsync_range+0xc0/0x1e4
 do_fsync+0x40/0x90
 __arm64_sys_fsync+0x34/0x50
 invoke_syscall.constprop.0+0xa8/0x260
 do_el0_svc+0xc8/0x1f0
 el0_svc+0x34/0x70
 el0t_64_sync_handler+0x108/0x114
 el0t_64_sync+0x1a4/0x1a8

Freed by task 403:
 kasan_save_stack+0x38/0x70
 kasan_set_track+0x28/0x40
 kasan_set_free_info+0x28/0x4c
 __kasan_slab_free+0xd4/0x13c
 kfree+0xc4/0x3a0
 tnc_delete+0x3f4/0xe40
 ubifs_tnc_remove_range+0x368/0x73c
 ubifs_tnc_remove_ino+0x29c/0x2e0
 ubifs_jnl_delete_inode+0x150/0x260
 ubifs_evict_inode+0x1d4/0x2e4
 evict+0x1c8/0x450
 iput+0x2a0/0x3c4
 do_unlinkat+0x2cc/0x490
 __arm64_sys_unlinkat+0x90/0x100
 invoke_syscall.constprop.0+0xa8/0x260
 do_el0_svc+0xc8/0x1f0
 el0_svc+0x34/0x70
 el0t_64_sync_handler+0x108/0x114
 el0t_64_sync+0x1a4/0x1a8

The offending memcpy() in ubifs_copy_hash() has a use-after-free when a node becomes root in TNC but still has a cparent to an already freed node. More specifically, consider the following TNC:

     zroot
     /
    /
  zp1
  /
 /
zn

Inserting a new node zn_new with a key smaller then zn will trigger a split in tnc_insert() if zp1 is full:

       zroot
       /   \
      /     \
    zp1     zp2
    /         \
   /           \
zn_new          zn

zn->parent has now been moved to zp2, *but* zn->cparent still points to zp1.

Now, consider a removal of all the nodes _except_ zn. Just when tnc_delete() is about to delete zroot and zp2:

zroot
    \
     \
     zp2
       \
        \
        zn

zroot and zp2 get freed and the tree collapses:

zn

zn now becomes the new zroot.

get_znodes_to_commit() will now only find zn, the new zroot, and write_index() will check its znode->cparent that wrongly points to the already freed zp1. ubifs_copy_hash() thus gets wrongly called with znode->cparent->zbranch[znode->iip].hash that triggers the use-after-free!

Fix this by explicitly setting znode->cparent to NULL in get_znodes_to_commit() for the root node. The search for the dirty nodes ---truncated---

Original text of the CVE record (cvelist), shown as published.

Exploit conditions

What an attack needs, read from the CVSS vector.
Attack vector AV:L
Local: needs a local or SSH session, or a user tricked into acting on the machine
Attack complexity AC:L
Low: no special conditions; the attacker can expect repeatable success
Privileges required PR:L
Low: ordinary user privileges
User interaction UI:N
None: no action by anyone other than the attacker

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

CVSS 3.1 vector from the CVE record, scored by the CNA Linux.

Event log

+DISdisclosed

CVE record published by Linux. CVSS 7.8, high.

src cvelist · nday , bulk import · raw
{
  "id": 345852,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2024-53171",
  "occurred_at": "2024-12-27T13:49:16.423Z",
  "observed_at": "2026-11-13T05:38:43.790901Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "cvss": {
      "source": "cna",
      "vector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
      "version": "3.1",
      "base_score": 7.8,
      "base_severity": "HIGH"
    },
    "ssvc": {
      "timestamp": "2025-02-11T15:43:44.944550Z",
      "automatable": "no",
      "exploitation": "none",
      "technical_impact": "total"
    },
    "state": "PUBLISHED",
    "date_published": "2024-12-27T13:49:16.423Z",
    "assigner_short_name": "Linux"
  }
}

Report an error

report an error or omission

Something on this page wrong or missing? Tell the editors; if they accept it, this page's revision log says so publicly. Upstream data is not changed.

Researcher discussion

0 researchers mentioned this in the last 7 days

Posts on X by researchers on nday's list that mention this CVE, shown as posted. nday does not check them.

nday has not collected any post on X by listed researchers that mentions this CVE.

Discussion

0 comments

No comments yet.