Skip to content
TrackCVE
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2023-54087

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

Not scoredEPSS 0.22%
Published
Updated
Reserved
Assigned by
Linux

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 5 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.

EPSS (exploitation in 30 days)
0.22% · top 87% of all CVEs (7 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 801c135ce73d5df1caf3eca35b66a10824ae0707 – < 5558bcf1c58720ca6e9d6198d921cb3aa337f038
    • affected 801c135ce73d5df1caf3eca35b66a10824ae0707 – < 45b2c5ca4d2edae70f19fdb086bd927840c4c309
    • affected 801c135ce73d5df1caf3eca35b66a10824ae0707 – < 234c53e57424992e657e6f4acc00d3df0983176f
    • affected 801c135ce73d5df1caf3eca35b66a10824ae0707 – < fcbc795abe7897da4b5d2a6ab5010e36774b00c2
    • affected 801c135ce73d5df1caf3eca35b66a10824ae0707 – < 5ec4c8aca5a221756a9007deadfea92795319fee
    • affected 801c135ce73d5df1caf3eca35b66a10824ae0707 – < 2ea7195b195009ecf0046e55361f393ba96d02db
    • affected 801c135ce73d5df1caf3eca35b66a10824ae0707 – < 9eccdb0760cbcb4427b5303a83a3007de998af51
    • affected 801c135ce73d5df1caf3eca35b66a10824ae0707 – < c15859bfd326c10230f09cb48a17f8a35f190342
  • Linux · Linux

    • affected 2.6.22
    • unaffected < 2.6.22
    • unaffected 4.14.308 – ≤ 4.14.*
    • unaffected 4.19.276 – ≤ 4.19.*
    • unaffected 5.4.235 – ≤ 5.4.*
    • unaffected 5.10.173 – ≤ 5.10.*
    • unaffected 5.15.100 – ≤ 5.15.*
    • unaffected 6.1.18 – ≤ 6.1.*
    • unaffected 6.2.5 – ≤ 6.2.*
    • unaffected 6.3 – ≤ *

References (8)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2023-54087 badge
[![CVE-2023-54087](https://trackcve.app/badge/CVE-2023-54087.svg)](https://trackcve.app/cve/CVE-2023-54087)

Record last updated .