CVE-2025-68266

UnknownEPSS 0.16%

Last modified

CVE-2025-68266 is a vulnerability of currently unknown severity. 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).. EPSS estimates a 0.16% chance of exploitation in the next 30 days.

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).

Metrics

EPSS Probability
0.16%

5.7th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < d0c5ec1f57d8fbb953f166a27d9d32473dc8f3e4; >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < aeccd6743ee4fdd1ab8cfcbb5b9a20b613418f6d; >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 8f73336b75bd3457b6f9410f2a0601a238f32238; >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < a9f626396bfe66f49b743601e862767928237cc0; >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 77899444d46162aeb65f229590c26ba266864223; >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < a8cb796e7e2cb7971311ba236922f5e7e1be77e6; >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 34ab4c75588c07cca12884f2bf6b0347c7a13872
LinuxLinux2.6.12

References

Timeline

Published
Last Modified
Status
Deferred

Frequently Asked Questions

What is CVE-2025-68266?
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).
How severe is CVE-2025-68266?
Severity scoring for CVE-2025-68266 is pending analysis. The EPSS model estimates a 0.16% probability of exploitation in the next 30 days.
How do I fix CVE-2025-68266?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2025

Are you affected by CVE-2025-68266?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST