CVE-2026-93095

published 17 Sep 2026 · updated 19 Oct 2026

hfsplus: validate thread record before delete key rebuild

7.8HighCVSS 7.8EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 33cda0036bc683fc888c20b04a5fc030e3e8413b, Kernel 473ea7aa35615829f0de7a71e8691d69dc24e328, Kernel 7898beee166c1145c0bca364d687b8437435bf1a and 5 more.

In the Linux kernel, the following vulnerability has been resolved: hfsplus: validate thread record before delete key rebuild hfsplus_delete_cat() is called with str == NULL when the last open reference to an unlinked HFS+ hardlink backing inode is closed. In that case, the function finds the catalog thread by CNID and rebuilds the catalog key from thread.nodeName. That reconstruction path reads thread.nodeName.length directly from the catalog B-tree into fd.search_key and then copies length * 2 bytes into fd.search_key->cat.name.unicode. It does not first check that the found record is a thread record or that its size matches the thread name. A corrupted image can therefore provide an oversized thread name length and make hfs_bnode_read() write past the catalog search-key allocation. Read the CNID record through hfsplus_brec_read_cat(), which bounds the record read to sizeof(hfsplus_cat_entry) and verifies that a thread record's size exactly matches nodeName.length. Together, these checks ensure an accepted thread name fits HFSPLUS_MAX_STRLEN. Reject non-thread records before building the delete key from the validated thread name. Share the thread-record-type helper between hfsplus_find_cat() and hfsplus_delete_cat().

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=2.6.12, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <33cda0036bc683fc888c20b04a5fc030e3e8413b, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <473ea7aa35615829f0de7a71e8691d69dc24e328, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <7898beee166c1145c0bca364d687b8437435bf1a, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <af48abc1b00d865c3f4c4d76b901c44115cb7162, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b9729c51a8b67f8b20b8a8cf395da4be63a0c15b, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <e20f3b749ad241df77ec1c3e13a9c22209aa1eb3, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <e2ea5cac61acfc11dad22f1d2d4bc71d56c52a20, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <e31985c67ba00a59d9b1340af473c1dbe6c8785633cda0036bc683fc888c20b04a5fc030e3e8413b, 473ea7aa35615829f0de7a71e8691d69dc24e328, 7898beee166c1145c0bca364d687b8437435bf1a, af48abc1b00d865c3f4c4d76b901c44115cb7162, b9729c51a8b67f8b20b8a8cf395da4be63a0c15b, e20f3b749ad241df77ec1c3e13a9c22209aa1eb3, e2ea5cac61acfc11dad22f1d2d4bc71d56c52a20, e31985c67ba00a59d9b1340af473c1dbe6c87856

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-93095 severity on Zeptric[![CVE-2026-93095](https://zeptric.io/badge/cve/CVE-2026-93095.svg)](https://zeptric.io/cve/CVE-2026-93095)