SECUFOCUSNOW
Home›CVE index›CVE-2023-54050
Review reviewHigh

CVE-2023-54050

Linux

In the Linux kernel, the following vulnerability has been resolved: ubifs: Fix memleak when insert_old_idx() failed Following process will cause a memleak for copied up znode: dirty_cow_znode zn = copy_znode(c, znode); err = insert_old_idx(c, zbr->lnum, zbr->offs); if (unlikely(err)) return ERR_PTR(err); // No one refers to zn. Fetch a reproducer in [Link]. Function copy_znode() is split into 2 parts: resource allocation and znode replacement, insert_old_idx() is split in similar way, so resource cleanup could be done in error handling path without corrupting metadata(mem & disk). It's okay...

CVSS
7.8
EPSS
0.18%
7.22% percentile
CISA KEV
Not listed
Published
2025.12.24
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.18%
Technical severityCVSS 7.8

Vulnerability overview

In the Linux kernel, the following vulnerability has been resolved: ubifs: Fix memleak when insert_old_idx() failed Following process will cause a memleak for copied up znode: dirty_cow_znode zn = copy_znode(c, znode); err = insert_old_idx(c, zbr->lnum, zbr->offs); if (unlikely(err)) return ERR_PTR(err); // No one refers to zn. Fetch a reproducer in [Link]. Function copy_znode() is split into 2 parts: resource allocation and znode replacement, insert_old_idx() is split in similar way, so resource cleanup could be done in error handling path without corrupting metadata(mem & disk). It's okay...

Affected product and versions

Product
Linux
Affected versions
>= 1e51764a3c2ac05a23a22b2a95ddee4d9bffb16d < cc29c7216d7f057eb0613b97dc38c7e1962a88d2, >= 1e51764a3c2ac05a23a22b2a95ddee4d9bffb16d < 6f2eee5457bc48b0426dedfd78cdbdea241a6edb, >= 1e51764a3c2ac05a23a22b2a95ddee4d9bffb16d < 66e9f2fb3e753f820bec2a98e8c6387029988320, >= 1e51764a3c2ac05a23a22b2a95ddee4d9bffb16d < 3ae75f82c33fa1b4ca2006b55c84f4ef4a428d4d, >= 1e51764a3c2ac05a23a22b2a95ddee4d9bffb16d < ef9aac603659e9ffe7d69ae16e3f0fc0991a965b, >= 1e51764a3c2ac05a23a22b2a95ddee4d9bffb16d < 79079cebbeed624b9d01cfcf1e3254ae1a1f6e14, >= 1e51764a3c2ac05a23a22b2a95ddee4d9bffb16d < a6da0ab9847779e05a7416c7a98148b549de69ef, >= 1e51764a3c2ac05a23a22b2a95ddee4d9bffb16d < b5fda08ef213352ac2df7447611eb4d383cce929, >= 2.6.27
Fixed versions
No verified fixed-version field is available yet

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
Not available
CVE-2023-54050 — Linux | SECUFOCUS NOW