CVE-2023-53271

ubi: Fix unreferenced object reported by kmemleak in ubi_resize_volume()

MEDIUM

5.5

CVSS Score

Published: September 16, 2025 at 08:07 AM UTC

Updated: June 17, 2026 at 06:44 AM 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

Start Free Sign In

Severity

MEDIUM5.5

Exploit prediction

EPSS 0.2%

SSVC

No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: ubi: Fix unreferenced object reported by kmemleak in ubi_resize_volume() There is a memory leaks problem reported by kmemleak: unreferenced object 0xffff888102007a00 (size 128): comm "ubirsvol", pid 32090, jiffies 4298464136 (age 2361.231s) hex dump (first 32 bytes): ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ backtrace: [<ffffffff8176cecd>] __kmalloc+0x4d/0x150 [<ffffffffa02a9a36>] ubi_eba_create_table+0x76/0x170 [ubi] [<ffffffffa029764e>] ubi_resize_volume+0x1be/0xbc0 [ubi] [<ffffffffa02a3321>] ubi_cdev_ioctl+0x701/0x1850 [ubi] [<ffffffff81975d2d>] __x64_sys_ioctl+0x11d/0x170 [<ffffffff83c142a5>] do_syscall_64+0x35/0x80 [<ffffffff83e0006a>] entry_SYSCALL_64_after_hwframe+0x46/0xb0 This is due to a mismatch between create and destroy interfaces, and in detail that "new_eba_tbl" created by ubi_eba_create_table() but destroyed by kfree(), while will causing "new_eba_tbl->entries" not freed. Fix it by replacing kfree(new_eba_tbl) with ubi_eba_destroy_table(new_eba_tbl)

Affected

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

Linux Kernel · Linux

95%

4.15 ≤ v < 4.19.2764.20 ≤ v < 5.4.2354.9 ≤ v < 4.14.3084.9 ≤ v < 4.19.2764.9 ≤ v < 5.10.1734.9 ≤ v < 5.15.1004.9 ≤ v < 5.4.2354.9 ≤ v < 6.1.184.9 ≤ v < 6.2.54.9 ≤ v < 6.35.11 ≤ v < 5.15.1005.16 ≤ v < 6.1.185.5 ≤ v < 5.10.1736.2 ≤ v < 6.2.54.9799dca34ac543485f581bd8464ec9b1c4f0f852a

Vendor states this is fixed in 07b60f7452d2fa731737552937cb81821919f874 (fixed)

Vendor states this is fixed in 09780a44093b53f9cbca76246af2e4ff0884e512 (fixed)

Vendor states this is fixed in 1e591ea072df7211f64542a09482b5f81cb3ad27 (fixed)

Vendor states this is fixed in 26ec2d66aecab8ff997b912c20247fedba4f5740 (fixed)

Vendor states this is fixed in 27b760b81951d8d5e5c952a696af8574052b0709 (fixed)

Vendor states this is fixed in 31d60afe2cc2b712dbefcaab6b7d6a47036f844e (fixed)

Vendor states this is fixed in 5c0c81a313492b83bd0c038b8839b0e04eb87563 (fixed)

Vendor states this is fixed in 95a72417dd13ebcdcb1bd0c5d4d15f7c5bfbb288 (fixed)

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 4.9 (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. What the record does show:

Patch and advisory references