CVE-2023-54087

ubi: Fix possible null-ptr-deref in ubi_free_volume()

N/A
Published: December 24, 2025 at 01:06 PM UTC
Updated: June 17, 2026 at 06:46 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
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: ubi: Fix possible null-ptr-deref in ubi_free_volume() It willl cause null-ptr-deref in the following case: uif_init() ubi_add_volume() cdev_add() -> if it fails, call kill_volumes() device_register() kill_volumes() -> if ubi_add_volume() fails call this function ubi_free_volume() cdev_del() device_unregister() -> trying to delete a not added device, it causes null-ptr-deref So in ubi_free_volume(), it delete devices whether they are added or not, it will causes null-ptr-deref. Handle the error case whlie calling ubi_add_volume() to fix this problem. If add volume fails, set the corresponding vol to null, so it can not be accessed in kill_volumes() and release the resource in ubi_add_volume() error path.

Affected

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

2.6.22 ≤ v < 4.14.3082.6.22 ≤ v < 4.19.2762.6.22 ≤ v < 5.10.1732.6.22 ≤ v < 5.15.1002.6.22 ≤ v < 5.4.2352.6.22 ≤ v < 6.1.182.6.22 ≤ v < 6.2.52.6.22 ≤ v < 6.32.6.22801c135ce73d5df1caf3eca35b66a10824ae0707
Vendor states this is fixed in 234c53e57424992e657e6f4acc00d3df0983176f (fixed)
Vendor states this is fixed in 2ea7195b195009ecf0046e55361f393ba96d02db (fixed)
Vendor states this is fixed in 45b2c5ca4d2edae70f19fdb086bd927840c4c309 (fixed)
Vendor states this is fixed in 5558bcf1c58720ca6e9d6198d921cb3aa337f038 (fixed)
Vendor states this is fixed in 5ec4c8aca5a221756a9007deadfea92795319fee (fixed)
Vendor states this is fixed in 9eccdb0760cbcb4427b5303a83a3007de998af51 (fixed)
Vendor states this is fixed in c15859bfd326c10230f09cb48a17f8a35f190342 (fixed)
Vendor states this is fixed in fcbc795abe7897da4b5d2a6ab5010e36774b00c2 (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.

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