CVE-2023-53271: ubi: Fix unreferenced object reported by kmemleak in ubi_resize_volume()
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)
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue is a local availability risk in the UBI flash-storage subsystem. A user with local privileges may trigger a memory leak while resizing a UBI volume, potentially degrading or exhausting system resources over time. It does not indicate data theft or data modification in the supplied sources.
Executive priority
Treat this as a normal patch-cycle kernel availability issue, with higher priority for embedded, appliance, or edge systems where downtime is costly and local access is shared or weakly controlled.
Technical view
ubi_resize_volume() creates a new EBA table with ubi_eba_create_table() but frees it with kfree(), leaving nested entries allocated. The fix replaces kfree(new_eba_tbl) with ubi_eba_destroy_table(new_eba_tbl). CVSS is 5.5: local attack vector, low complexity, low privileges, no user interaction, high availability impact.
Likely exposure
Exposure is most relevant to Linux systems using UBI, commonly embedded or flash-storage devices, where local users or services can perform UBI volume resize operations. Systems without UBI enabled or without reachable UBI management interfaces are less likely exposed.
Exploitation context
The source bundle does not show CISA KEV listing or active exploitation. The issue requires local access and low privileges per CVSS. Evidence supports resource exhaustion risk, not remote compromise or privilege escalation.
Researcher notes
The public description is concise and centered on a kmemleak finding. Affected-version detail in the bundle is incomplete and should be reconciled with Linux stable trees or downstream vendor advisories before asserting exact fleet exposure.
Mitigation direction
Apply a vendor kernel update containing the referenced stable fixes.
Check Linux distribution or device-vendor advisories for backported patches.
Restrict access to UBI device nodes and volume-management utilities.
Reduce unnecessary local shell or service access on affected devices.
Monitor memory pressure and unexplained availability degradation.
Validation and detection
Inventory Linux kernel versions on systems using UBI storage.
Confirm whether UBI modules, devices, or ubirsvol workflows are present.
Map installed kernels against vendor fixed packages or stable commits.
Review permissions on UBI character devices and management tools.
Check logs and monitoring for repeated resize operations or memory pressure.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-401: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.