{
  "cveId": "CVE-2026-46169",
  "url": "https://patchblox.com/security/cve/CVE-2026-46169",
  "summary": "CVE-2026-46169 is fixed in linux on 1 platform, first by DEBIAN-CVE-2026-46169, released June 24, 2026. It is not reported as exploited. Patch Radar priority: Routine.",
  "title": "hfsplus: 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\u0027t 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-\u003Eentrylength=26   HFSPLUS_BREC_READ: WARNING - entrylength (26) \u003C rec_len (520) - PARTIAL READ!  hfs_brec_read() only validates that entrylength is not greater than the buffer size, but doesn\u0027t check if it\u0027s 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\u0027t 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\u0027t 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.",
  "published": "2026-05-28T10:16:32Z",
  "severity": "Low",
  "cvss": 5.5,
  "cvssVector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
  "epss": 0.0013,
  "epssPercentile": 0.02673,
  "priority": "Routine",
  "priorityTier": 4,
  "exploited": false,
  "vendorExploited": false,
  "disclosed": false,
  "vendorAdvisory": "https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-46169",
  "fixes": [
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 12.15 (bookworm)",
      "fixedVersion": "6.1.176-1",
      "fix": "DEBIAN-CVE-2026-46169",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2026-46169",
      "released": "2026-06-24T14:07:24Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 13.5 (trixie)",
      "fixedVersion": "6.12.88-1",
      "fix": "DEBIAN-CVE-2026-46169",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2026-46169",
      "released": "2026-06-24T14:07:24Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 14",
      "fixedVersion": "7.0.7-1",
      "fix": "DEBIAN-CVE-2026-46169",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2026-46169",
      "released": "2026-06-24T14:07:24Z"
    }
  ],
  "noFixYet": [],
  "dataAsOf": "2026-11-08T19:12:23Z",
  "attribution": {
    "text": "Data: Patchblox Patch Radar",
    "url": "https://patchblox.com/security/patch-radar",
    "terms": "https://patchblox.com/security/patch-radar/use-the-data"
  }
}