CVE-2025-68767
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.
Affected versions
Linux kernel versions
2.6.12
and later are affected. Fixed in
5.10.248,
5.15.198,
6.1.160,
6.6.120,
6.12.64,
6.18.3,
6.19
and their respective stable series.
References
The following references provide additional information about CVE-2025-68767 including vendor advisories, patch commits, exploit details, and third-party analysis. Links are sourced from the NIST NVD database.
-
PatchKernel patch commithttps://git.kernel.org/stable/c/001f44982587ad462b3002ee40c75e8df67d597d
-
PatchKernel patch commithttps://git.kernel.org/stable/c/005d4b0d33f6b4a23d382b7930f7a96b95b01f39
-
PatchKernel patch commithttps://git.kernel.org/stable/c/05ec9af3cc430683c97f76027e1c55ac6fd25c59
Frequently asked questions
-
What is CVE-2025-68767?
CVE-2025-68767 is a unscored severity Linux kernel vulnerability . It affects Linux kernel versions from 2.6.12 onward and has been patched in 5.10.248, 5.15.198, 6.1.160 and others. CVE-2025-68767 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
-
Is there a patch available for CVE-2025-68767?
Yes — CVE-2025-68767 has been patched. Fixed versions include 5.10.248, 5.15.198, 6.1.160 and others. If you are running Linux kernel 2.6.12 or later up to the fix versions, apply the relevant patch for your kernel branch.
-
Is CVE-2025-68767 actively exploited?
No — CVE-2025-68767 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.