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-64360hfs/hfsplus: zero-initialize buffer in hfs_bnode_read

Description

In the Linux kernel, the following vulnerability has been resolved: hfs/hfsplus: zero-initialize buffer in hfs_bnode_read hfs_bnode_read() can return early without writing to the output buffer when is_bnode_offset_valid() fails or when check_and_correct_requested_ length() corrects the length to zero. Callers such as hfs_bnode_read_ u16() and hfs_bnode_read_u8() pass stack-allocated buffers and use the result unconditionally, leading to KMSAN uninit-value reports. Rather than initializing at each individual call site, zero the buffer at the start of hfs_bnode_read() before any validation checks. This ensures all callers in both hfs and hfsplus get a deterministic zero value regardless of which early-return path is taken.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 23 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-64360, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.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.12% · top 98% of all CVEs (13 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 67ecc81f6492275c9c54280532f558483c99c90e – < 34684a04777358b2b40ac729e54c8e45359e46b3
    • affected a1a60e79502279f996e55052f50cc14919020475 – < 0b189b2204f1a2612dc68f8d139fb5b80539e710
    • affected fe2891a9c43ab87d1a210d61e6438ca6936e2f62 – < 8f72fd25a57a457866350359ddd27a43caa62c95
    • affected 384a66b89f9540a9a8cb0f48807697dfabaece4c – < 16ca053c2be5f4f3044dccf7fc19237dc820d394
    • affected efc095b35b23297e419c2ab4fc1ed1a8f0781a29 – < d2afc7ecee476f9251dd87444f7fb6a424410922
    • affected a431930c9bac518bf99d6b1da526a7f37ddee8d8 – < f3461b84a4865d9b5e70fbb71da72ae044a3bcd2
    • affected a431930c9bac518bf99d6b1da526a7f37ddee8d8 – < d5b45bad75cd2730b8452aed4d3b20a2b2a12576
    • affected a431930c9bac518bf99d6b1da526a7f37ddee8d8 – < d67aadee19ffdf3cc8520c5a4f4d5b2916d30baf
    • affected e7d2dc2421e821e4045775e6dc226378328de6f6
    • affected fc7f732984ec91f30be3e574e0644066d07f2b78
    • affected eec522fd0d28106b14a59ab2d658605febe4a3bb
    • affected 5.10.241 – < 5.10.261
    • affected 5.15.190 – < 5.15.212
    • affected 6.1.149 – < 6.1.178
    • affected 6.6.103 – < 6.6.145
    • affected 6.12.43 – < 6.12.96
    • affected 5.4.297 – < 5.5
    • affected 6.15.11 – < 6.16
    • affected 6.16.2 – < 6.17
  • Linux · Linux

    • affected 6.17
    • unaffected < 6.17
    • unaffected 5.10.261 – ≤ 5.10.*
    • unaffected 5.15.212 – ≤ 5.15.*
    • unaffected 6.1.178 – ≤ 6.1.*
    • unaffected 6.6.145 – ≤ 6.6.*
    • unaffected 6.12.96 – ≤ 6.12.*
    • unaffected 6.18.39 – ≤ 6.18.*
    • unaffected 7.1.4 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .