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-2025-68767hfsplus: Verify inode mode when loading from disk

Description

In the Linux kernel, the following vulnerability has been resolved: hfsplus: Verify inode mode when loading from disk syzbot is reporting that S_IFMT bits of inode->i_mode can become bogus when the S_IFMT bits of the 16bits "mode" field loaded from disk are corrupted. According to [1], the permissions field was treated as reserved in Mac OS 8 and 9. According to [2], the reserved field was explicitly initialized with 0, and that field must remain 0 as long as reserved. Therefore, when the "mode" field is not 0 (i.e. no longer reserved), the file must be S_IFDIR if dir == 1, and the file must be one of S_IFREG/S_IFLNK/S_IFCHR/ S_IFBLK/S_IFIFO/S_IFSOCK if dir == 0.

Timeline

  1. ID reserved

    By Linux

  2. · 20 days later

    Published

  3. · 4 months 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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.

EPSS (exploitation in 30 days)
0.21% · top 89% 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: Not scored.

Affected products

  • Linux · Linux

    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 6f768724aabd5b321c5b8f15acdca11e4781cf32
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < d92333c7a35856e419500e7eed72dac1afa404a5
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 001f44982587ad462b3002ee40c75e8df67d597d
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 05ec9af3cc430683c97f76027e1c55ac6fd25c59
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < edfb2e602b5ba5ca6bf31cbac20b366efb72b156
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 91f114bffa36ce56d0e1f60a0a44fc09baaefc79
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 005d4b0d33f6b4a23d382b7930f7a96b95b01f39
  • Linux · Linux

    • affected 2.6.12
    • unaffected < 2.6.12
    • unaffected 5.10.248 – ≤ 5.10.*
    • unaffected 5.15.198 – ≤ 5.15.*
    • unaffected 6.1.160 – ≤ 6.1.*
    • unaffected 6.6.120 – ≤ 6.6.*
    • unaffected 6.12.64 – ≤ 6.12.*
    • unaffected 6.18.3 – ≤ 6.18.*
    • unaffected 6.19 – ≤ *

References

References7

Sources

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

Badge for a README or a ticket

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

Record last updated .