All reports
Low

kernel: ubi: Fix UAF wear-leveling entry in eraseblk_count_seq_show()

Affected versions

Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2023-53826

Probability of exploitation in the next 30 days: 0.27%

FIRST EPSS · 2026-11-18

Description

In the Linux kernel, the following vulnerability has been resolved: ubi: Fix UAF wear-leveling entry in eraseblk_count_seq_show() Wear-leveling entry could be freed in error path, which may be accessed again in eraseblk_count_seq_show(), for example: __erase_worker eraseblk_count_seq_show wl = ubi->lookuptbl[*block_number] if (wl) wl_entry_destroy ubi->lookuptbl[e->pnum] = NULL kmem_cache_free(ubi_wl_entry_slab, e) erase_count = wl->ec // UAF! Wear-leveling entry updating/accessing in ubi->lookuptbl should be protected by ubi->wl_lock, fix it by adding ubi->wl_lock to serialize wl entry accessing between wl_entry_destroy() and eraseblk_count_seq_show(). Fetch a reproducer in [Link].

A use-after-free vulnerability was found in the UBI (Unsorted Block Images) subsystem in the Linux kernel. In eraseblk_count_seq_show(), a wear-leveling entry can be accessed after it has been freed in __erase_worker(). The race occurs because ubi->lookuptbl access is not properly synchronized with wl_entry_destroy(), allowing the seq_show function to read from freed memory when displaying erase counts.