Strix
26.1K

CVE-2023-54050

HIGHCVSS 7.8/10EPSS 0.22%

Last modified

CVE-2023-54050 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. 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 that old index inserting is put behind of add_idx_dirt(), old index is used in layout_leb_in_gaps(), so the two processes do not depend on each other.. EPSS estimates a 0.22% chance of exploitation in the next 30 days.

Description

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 that old index inserting is put behind of add_idx_dirt(), old index is used in layout_leb_in_gaps(), so the two processes do not depend on each other.

Metrics

CVSS 3.1
7.8/10

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS Probability
0.22%

13.3th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 1e51764a3c2ac05a23a22b2a95ddee4d9bffb16d, < cc29c7216d7f057eb0613b97dc38c7e1962a88d2; >= 1e51764a3c2ac05a23a22b2a95ddee4d9bffb16d, < 6f2eee5457bc48b0426dedfd78cdbdea241a6edb; >= 1e51764a3c2ac05a23a22b2a95ddee4d9bffb16d, < 66e9f2fb3e753f820bec2a98e8c6387029988320; >= 1e51764a3c2ac05a23a22b2a95ddee4d9bffb16d, < 3ae75f82c33fa1b4ca2006b55c84f4ef4a428d4d; >= 1e51764a3c2ac05a23a22b2a95ddee4d9bffb16d, < ef9aac603659e9ffe7d69ae16e3f0fc0991a965b; >= 1e51764a3c2ac05a23a22b2a95ddee4d9bffb16d, < 79079cebbeed624b9d01cfcf1e3254ae1a1f6e14; >= 1e51764a3c2ac05a23a22b2a95ddee4d9bffb16d, < a6da0ab9847779e05a7416c7a98148b549de69ef; >= 1e51764a3c2ac05a23a22b2a95ddee4d9bffb16d, < b5fda08ef213352ac2df7447611eb4d383cce929
LinuxLinux2.6.27

References

Timeline

Published
Last Modified
Status
Deferred

Frequently Asked Questions

What is CVE-2023-54050?
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 that old index inserting is put behind of add_idx_dirt(), old index is used in layout_leb_in_gaps(), so the two processes do not depend on each other.
How severe is CVE-2023-54050?
CVE-2023-54050 has a CVSS score of 7.8/10 (HIGH severity). The EPSS model estimates a 0.22% probability of exploitation in the next 30 days.
How do I fix CVE-2023-54050?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2023

View all 2023CVEs →

Are you affected by CVE-2023-54050?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST