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-68266bfs: Reconstruct file type when loading from disk

Description

In the Linux kernel, the following vulnerability has been resolved: bfs: Reconstruct file type 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 32bits "mode" field loaded from disk are corrupted or when the 32bits "attributes" field loaded from disk are corrupted. A documentation says that BFS uses only lower 9 bits of the "mode" field. But I can't find an explicit explanation that the unused upper 23 bits (especially, the S_IFMT bits) are initialized with 0. Therefore, ignore the S_IFMT bits of the "mode" field loaded from disk. Also, verify that the value of the "attributes" field loaded from disk is either BFS_VREG or BFS_VDIR (because BFS supports only regular files and the root directory).

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 11 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.23% · top 86% 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 – < d0c5ec1f57d8fbb953f166a27d9d32473dc8f3e4
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < aeccd6743ee4fdd1ab8cfcbb5b9a20b613418f6d
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 8f73336b75bd3457b6f9410f2a0601a238f32238
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < a9f626396bfe66f49b743601e862767928237cc0
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 77899444d46162aeb65f229590c26ba266864223
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < a8cb796e7e2cb7971311ba236922f5e7e1be77e6
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 34ab4c75588c07cca12884f2bf6b0347c7a13872
  • 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.62 – ≤ 6.12.*
    • unaffected 6.17.12 – ≤ 6.17.*
    • unaffected 6.18 – ≤ *

References

References9

Sources

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

Badge for a README or a ticket

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

Record last updated .