CVE-2023-53271

published 16 Sep 2025 · updated 11 May 2026

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

5.5MediumCVSS 5.5EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 07b60f7452d2fa731737552937cb81821919f874, Kernel 09780a44093b53f9cbca76246af2e4ff0884e512, Kernel 1e591ea072df7211f64542a09482b5f81cb3ad27 and 5 more.

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

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=4.9, >=799dca34ac543485f581bd8464ec9b1c4f0f852a <07b60f7452d2fa731737552937cb81821919f874, >=799dca34ac543485f581bd8464ec9b1c4f0f852a <09780a44093b53f9cbca76246af2e4ff0884e512, >=799dca34ac543485f581bd8464ec9b1c4f0f852a <1e591ea072df7211f64542a09482b5f81cb3ad27, >=799dca34ac543485f581bd8464ec9b1c4f0f852a <26ec2d66aecab8ff997b912c20247fedba4f5740, >=799dca34ac543485f581bd8464ec9b1c4f0f852a <27b760b81951d8d5e5c952a696af8574052b0709, >=799dca34ac543485f581bd8464ec9b1c4f0f852a <31d60afe2cc2b712dbefcaab6b7d6a47036f844e, >=799dca34ac543485f581bd8464ec9b1c4f0f852a <5c0c81a313492b83bd0c038b8839b0e04eb87563, >=799dca34ac543485f581bd8464ec9b1c4f0f852a <95a72417dd13ebcdcb1bd0c5d4d15f7c5bfbb28807b60f7452d2fa731737552937cb81821919f874, 09780a44093b53f9cbca76246af2e4ff0884e512, 1e591ea072df7211f64542a09482b5f81cb3ad27, 26ec2d66aecab8ff997b912c20247fedba4f5740, 27b760b81951d8d5e5c952a696af8574052b0709, 31d60afe2cc2b712dbefcaab6b7d6a47036f844e, 5c0c81a313492b83bd0c038b8839b0e04eb87563, 95a72417dd13ebcdcb1bd0c5d4d15f7c5bfbb288

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2023-53271 severity on Zeptric[![CVE-2023-53271](https://zeptric.io/badge/cve/CVE-2023-53271.svg)](https://zeptric.io/cve/CVE-2023-53271)