Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.22% (FIRST EPSS).
  • Fixed version: Linux Linux 234c53e57424992e657e6f4acc00d3df0983176f, 2ea7195b195009ecf0046e55361f393ba96d02db, 45b2c5ca4d2edae70f19fdb086bd927840c4c309.

Low priority for now. Upgrade to Linux Linux 234c53e57424992e657e6f4acc00d3df0983176f, 2ea7195b195009ecf0046e55361f393ba96d02db, 45b2c5ca4d2edae70f19fdb086bd927840c4c309 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

—No exploit Fix available
Published
Dec 24, 2025
Updated
Jun 17, 2026
EPSS
0.2% · 12th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2023-54087

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 2.6.22affected
    • 801c135ce73d5df1caf3eca35b66a10824ae0707 and later · before 5558bcf1c58720ca6e9d6198d921cb3aa337f038affected · git
    • 801c135ce73d5df1caf3eca35b66a10824ae0707 and later · before 45b2c5ca4d2edae70f19fdb086bd927840c4c309affected · git
    • 801c135ce73d5df1caf3eca35b66a10824ae0707 and later · before 234c53e57424992e657e6f4acc00d3df0983176faffected · git
    • 801c135ce73d5df1caf3eca35b66a10824ae0707 and later · before fcbc795abe7897da4b5d2a6ab5010e36774b00c2affected · git
    • 801c135ce73d5df1caf3eca35b66a10824ae0707 and later · before 5ec4c8aca5a221756a9007deadfea92795319feeaffected · git
    • 801c135ce73d5df1caf3eca35b66a10824ae0707 and later · before 2ea7195b195009ecf0046e55361f393ba96d02dbaffected · git
    • 801c135ce73d5df1caf3eca35b66a10824ae0707 and later · before 9eccdb0760cbcb4427b5303a83a3007de998af51affected · git
    • 801c135ce73d5df1caf3eca35b66a10824ae0707 and later · before c15859bfd326c10230f09cb48a17f8a35f190342affected · git
    • before 2.6.22not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.20-16.1.20-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2023-54084Dec 24, 2025 · ALSA: firewire-digi00x: prevent potential use after free
    0Monitor
  • ← EarlierCVE-2023-54086Dec 24, 2025 · bpf: Add preempt_count_{sub,add} into btf id deny list
    0Monitor
  • Later →CVE-2023-54089Dec 24, 2025 · virtio_pmem: add the missing REQ_OP_WRITE for flush bio
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux234c53e57424992e657e6f4acc00d3df0983176fVendor (CNA)
Linux Linux2ea7195b195009ecf0046e55361f393ba96d02dbVendor (CNA)
Linux Linux45b2c5ca4d2edae70f19fdb086bd927840c4c309Vendor (CNA)
Linux Linux5558bcf1c58720ca6e9d6198d921cb3aa337f038Vendor (CNA)
Linux Linux5ec4c8aca5a221756a9007deadfea92795319feeVendor (CNA)
Linux Linux9eccdb0760cbcb4427b5303a83a3007de998af51Vendor (CNA)
Linux Linuxc15859bfd326c10230f09cb48a17f8a35f190342Vendor (CNA)
Linux Linuxfcbc795abe7897da4b5d2a6ab5010e36774b00c2Vendor (CNA)
debian:linux6.1.20-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records