CVE-2023-53800

ubi: Fix use-after-free when volume resizing failed

HIGH
7.8
CVSS Score
Published: December 9, 2025 at 12:00 AM UTC
Updated: October 15, 2026 at 10:17 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.1%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: ubi: Fix use-after-free when volume resizing failed There is an use-after-free problem reported by KASAN: ================================================================== BUG: KASAN: use-after-free in ubi_eba_copy_table+0x11f/0x1c0 [ubi] Read of size 8 at addr ffff888101eec008 by task ubirsvol/4735 CPU: 2 PID: 4735 Comm: ubirsvol Not tainted 6.1.0-rc1-00003-g84fa3304a7fc-dirty #14 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-1.fc33 04/01/2014 Call Trace: <TASK> dump_stack_lvl+0x34/0x44 print_report+0x171/0x472 kasan_report+0xad/0x130 ubi_eba_copy_table+0x11f/0x1c0 [ubi] ubi_resize_volume+0x4f9/0xbc0 [ubi] ubi_cdev_ioctl+0x701/0x1850 [ubi] __x64_sys_ioctl+0x11d/0x170 do_syscall_64+0x35/0x80 entry_SYSCALL_64_after_hwframe+0x46/0xb0 </TASK> When ubi_change_vtbl_record() returns an error in ubi_resize_volume(), "new_eba_tbl" will be freed on error handing path, but it is holded by "vol->eba_tbl" in ubi_eba_replace_table(). It means that the liftcycle of "vol->eba_tbl" and "vol" are different, so when resizing volume in next time, it causing an use-after-free fault. Fix it by not freeing "new_eba_tbl" after it replaced in ubi_eba_replace_table(), while will be freed in next volume resizing.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

2.6.22801c135ce73d5df1caf3eca35b66a10824ae0707
Vendor states this is fixed in 35f8d4064e54c18424db2997059d4c0b1d13d093 (fixed)
Vendor states this is fixed in 3d6378f7056ac7350338f941001162a8f660853c (fixed)
Vendor states this is fixed in 53818746e549e61841428892a8d94344494be797 (fixed)
Vendor states this is fixed in 9af31d6ec1a4be4caab2550096c6bd2ba8fba472 (fixed)
Vendor states this is fixed in 9c8be1f165baee53b5a36ea0b3c9281d403a1d0b (fixed)
Vendor states this is fixed in b0c951742348d216f094d16ed4f70ae73db881c0 (fixed)
Vendor states this is fixed in bf795ebbb9995e2fe7945de71177f01c2f1215dc (fixed)
Vendor states this is fixed in bf9875aa7f7d624a8c084425b14bf7e5907ebc30 (fixed)
Vendor states this is fixed in 2.6.22 (unaffected)
Vendor states this is fixed in 4.14.308 (unaffected)
Vendor states this is fixed in 4.19.276 (unaffected)
Vendor states this is fixed in 5.10.173 (unaffected)
Vendor states this is fixed in 5.15.100 (unaffected)
Vendor states this is fixed in 5.4.235 (unaffected)
Vendor states this is fixed in 6.1.18 (unaffected)
Vendor states this is fixed in 6.2.5 (unaffected)
Vendor states this is fixed in 6.3 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusDEFERRED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card