CVE-2026-68457
Linux kernel vulnerability
- Published15 Aug 2026
Description
In the Linux kernel, the following vulnerability has been resolved: ksmbd: use opener credentials for FSCTL mutations SET_SPARSE, SET_ZERO_DATA and SET_COMPRESSION operate on an open SMB handle but call VFS xattr, fallocate or fileattr helpers with the current ksmbd worker credentials. Those helpers can revalidate inode permissions, ownership and LSM policy independently of the SMB handle access mask. Run each operation with the credentials captured in the target file when the handle was opened. Keep credential handling local to these single-file FSCTLs rather than applying session credentials to the complete IOCTL handler, which also contains handle-less and multi-handle operations.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:HRemediation
No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.
References
- https://git.kernel.org/stable/c/1e112c47ec5dd1942e2d4ca6e8e9b712238e20c2
- https://git.kernel.org/stable/c/a8c18434e1f0d9f7989170bdb0490c0160baf065
- https://git.kernel.org/stable/c/c6394bcaf254c5baf9aff43376020be5db6d3316
- https://git.kernel.org/stable/c/cfb2c6f71d61ed807c9d7a7af331d406f1f31877
- https://git.kernel.org/stable/c/e205f3e7e8c31a47cd11efb6cf663a527177e432
- https://git.kernel.org/stable/c/fb1cae6302d58414ddf029e3f642711bd30243f7
Frequently asked
Is CVE-2026-68457 being actively exploited?
CVE-2026-68457 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.70%.
How severe is CVE-2026-68457?
CVE-2026-68457 has a CVSS 3.1 base score of 9.1, rated critical. EPSS estimates a 0.70% probability of exploitation.
How do I fix CVE-2026-68457?
Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-68457 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.