Answer in brief
CVE-2023-54050 records a High severity (CVSS 7.8) vulnerability in ubifs: Fix memleak when insert_old_idx() failed. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2023-54050 records a High severity (CVSS 7.8) vulnerability in ubifs: Fix memleak when insert_old_idx() failed. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1e51764a3c2ac05a23a22b2a95ddee4d9bffb16d <cc29c7216d7f057eb0613b97dc38c7e1962a88d2 || >=1e51764a3c2ac05a23a22b2a95ddee4d9bffb16d <6f2eee5457bc48b0426dedfd78cdbdea241a6edb || >=1e51764a3c2ac05a23a22b2a95ddee4d9bffb16d <66e9f2fb3e753f820bec2a98e8c6387029988320 || >=1e51764a3c2ac05a23a22b2a95ddee4d9bffb16d <3ae75f82c33fa1b4ca2006b55c84f4ef4a428d4d || >=1e51764a3c2ac05a23a22b2a95ddee4d9bffb16d <ef9aac603659e9ffe7d69ae16e3f0fc0991a965b || >=1e51764a3c2ac05a23a22b2a95ddee4d9bffb16d <79079cebbeed624b9d01cfcf1e3254ae1a1f6e14 || >=1e51764a3c2ac05a23a22b2a95ddee4d9bffb16d <a6da0ab9847779e05a7416c7a98148b549de69ef || >=1e51764a3c2ac05a23a22b2a95ddee4d9bffb16d <b5fda08ef213352ac2df7447611eb4d383cce929 | cc29c7216d7f057eb0613b97dc38c7e1962a88d2, 6f2eee5457bc48b0426dedfd78cdbdea241a6edb, 66e9f2fb3e753f820bec2a98e8c6387029988320, 3ae75f82c33fa1b4ca2006b55c84f4ef4a428d4d, ef9aac603659e9ffe7d69ae16e3f0fc0991a965b, 79079cebbeed624b9d01cfcf1e3254ae1a1f6e14, a6da0ab9847779e05a7416c7a98148b549de69ef, b5fda08ef213352ac2df7447611eb4d383cce929 |
| Linux/Linuxgeneric | 2.6.27 | Not reported |
Published upstream
Dec 24, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
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.
Quoted source text, attributed separately from HOL analysis.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1e51764a3c2ac05a23a22b2a95ddee4d9bffb16d <cc29c7216d7f057eb0613b97dc38c7e1962a88d2 || >=1e51764a3c2ac05a23a22b2a95ddee4d9bffb16d <6f2eee5457bc48b0426dedfd78cdbdea241a6edb || >=1e51764a3c2ac05a23a22b2a95ddee4d9bffb16d <66e9f2fb3e753f820bec2a98e8c6387029988320 || >=1e51764a3c2ac05a23a22b2a95ddee4d9bffb16d <3ae75f82c33fa1b4ca2006b55c84f4ef4a428d4d || >=1e51764a3c2ac05a23a22b2a95ddee4d9bffb16d <ef9aac603659e9ffe7d69ae16e3f0fc0991a965b || >=1e51764a3c2ac05a23a22b2a95ddee4d9bffb16d <79079cebbeed624b9d01cfcf1e3254ae1a1f6e14 || >=1e51764a3c2ac05a23a22b2a95ddee4d9bffb16d <a6da0ab9847779e05a7416c7a98148b549de69ef || >=1e51764a3c2ac05a23a22b2a95ddee4d9bffb16d <b5fda08ef213352ac2df7447611eb4d383cce929 | cc29c7216d7f057eb0613b97dc38c7e1962a88d2, 6f2eee5457bc48b0426dedfd78cdbdea241a6edb, 66e9f2fb3e753f820bec2a98e8c6387029988320, 3ae75f82c33fa1b4ca2006b55c84f4ef4a428d4d, ef9aac603659e9ffe7d69ae16e3f0fc0991a965b, 79079cebbeed624b9d01cfcf1e3254ae1a1f6e14, a6da0ab9847779e05a7416c7a98148b549de69ef, b5fda08ef213352ac2df7447611eb4d383cce929 |
| Linux/Linuxgeneric | 2.6.27 | Not reported |
Published upstream
Dec 24, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
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.
Quoted source text, attributed separately from HOL analysis.