ubi: Fix UAF wear-leveling entry in eraseblk_count_seq_show()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 801c135ce73d5df1caf3eca35b66a10824ae0707 · < 84253f3c2dad6be10d30c92626c763d9a9f512ad| No fix yet |
| Linux Linux |
|
|
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].
From the CVE record · Linux
The Linux kernel's UBI code can access a freed wear-leveling entry in eraseblk_count_seq_show() when an erase worker frees it concurrently. The input does not specify attacker capabilities, authentication requirements, or user interaction.
Engineers running Linux kernels with the affected UBI code should check their versions; no affected versions are specified.