Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-46169hfsplus: fix uninit-value by validating catalog record size

Description

In the Linux kernel, the following vulnerability has been resolved: hfsplus: fix uninit-value by validating catalog record size Syzbot reported a KMSAN uninit-value issue in hfsplus_strcasecmp(). The root cause is that hfs_brec_read() doesn't validate that the on-disk record size matches the expected size for the record type being read. When mounting a corrupted filesystem, hfs_brec_read() may read less data than expected. For example, when reading a catalog thread record, the debug output showed: HFSPLUS_BREC_READ: rec_len=520, fd->entrylength=26 HFSPLUS_BREC_READ: WARNING - entrylength (26) < rec_len (520) - PARTIAL READ! hfs_brec_read() only validates that entrylength is not greater than the buffer size, but doesn't check if it's less than expected. It successfully reads 26 bytes into a 520-byte structure and returns success, leaving 494 bytes uninitialized. This uninitialized data in tmp.thread.nodeName then gets copied by hfsplus_cat_build_key_uni() and used by hfsplus_strcasecmp(), triggering the KMSAN warning when the uninitialized bytes are used as array indices in case_fold(). Fix by introducing hfsplus_brec_read_cat() wrapper that: 1. Calls hfs_brec_read() to read the data 2. Validates the record size based on the type field: - Fixed size for folder and file records - Variable size for thread records (depends on string length) 3. Returns -EIO if size doesn't match expected For thread records, check against HFSPLUS_MIN_THREAD_SZ before reading nodeName.length to avoid reading uninitialized data at call sites that don't zero-initialize the entry structure. Also initialize the tmp variable in hfsplus_find_cat() as defensive programming to ensure no uninitialized data even if validation is bypassed.

Timeline

  1. ID reserved

    By Linux

  2. · 15 days later

    Published

  3. · 22 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-46169, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.13% · top 97% of all CVEs (16 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 3003dbf62d151d47a6b90f71655292a51a05f244
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 8be69532e399eec9d9d990f6958b4ff2383b19b3
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 3bc337697c66db2e2a4a94f0509c282c1a014b86
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 61a790974ff7e533acbceca06c7d02f22bf96d4d
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < c91bbd6193c70a02c50c22e0fb1f60c3c5bd053a
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < a420904450962a562ad053a41a53a27755021b48
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 93e8d613f1a01b6637f387cc93f184cf7fb881d6
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < b6b592275aeff184aa82fcf6abccd833fb71b393
  • Linux · Linux

    • affected 2.6.12
    • unaffected < 2.6.12
    • unaffected 5.10.259 – ≤ 5.10.*
    • unaffected 5.15.210 – ≤ 5.15.*
    • unaffected 6.1.176 – ≤ 6.1.*
    • unaffected 6.6.140 – ≤ 6.6.*
    • unaffected 6.12.88 – ≤ 6.12.*
    • unaffected 6.18.30 – ≤ 6.18.*
    • unaffected 7.0.7 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-46169 badge
[![CVE-2026-46169](https://cveledger.app/badge/CVE-2026-46169.svg)](https://cveledger.app/cve/CVE-2026-46169)

Record last updated .