CVE-2026-68457: ksmbd: use opener credentials for FSCTL mutations
Noroxi assessment
Priority: Monitor (action score 36/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.70% (FIRST EPSS); higher than 53.5% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 1e112c47ec5dd1942e2d4ca6e8e9b712238e20c2, a8c18434e1f0d9f7989170bdb0490c0160baf065, c6394bcaf254c5baf9aff43376020be5db6d3316.
Low priority for now. Upgrade to Linux Linux 1e112c47ec5dd1942e2d4ca6e8e9b712238e20c2, a8c18434e1f0d9f7989170bdb0490c0160baf065, c6394bcaf254c5baf9aff43376020be5db6d3316 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Aug 15, 2026
- Updated
- Aug 18, 2026
- EPSS
- 0.7% · 53th percentile
- CWE
- —
Report tools
Action score
36
Monitor
Low priority for now.
- CVSS
- 36 / 40 · 9.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.7%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 9.1
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.15affected
- e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 and later · before a8c18434e1f0d9f7989170bdb0490c0160baf065affected · git
- e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 and later · before 1e112c47ec5dd1942e2d4ca6e8e9b712238e20c2affected · git
- e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 and later · before fb1cae6302d58414ddf029e3f642711bd30243f7affected · git
- e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 and later · before e205f3e7e8c31a47cd11efb6cf663a527177e432affected · git
- e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 and later · before cfb2c6f71d61ed807c9d7a7af331d406f1f31877affected · git
- e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 and later · before c6394bcaf254c5baf9aff43376020be5db6d3316affected · git
- before 5.15not affected · semver
- 6.1.178 and later · up to and including 6.1.*not affected · semver
- 6.6.145 and later · up to and including 6.6.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.180-1 | 6.1.180-1 |
| Debian:13 | linux | before 6.12.100-1 | 6.12.100-1 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-68454Aug 13, 2026 · KVM: s390: pci: Fix handling of AIF enable without AISB35Monitor
- ← EarlierCVE-2026-68455Aug 15, 2026 · liveupdate: validate session type before performing operation0Monitor
- Later →CVE-2026-68458Aug 15, 2026 · binder: cache secctx size before release zeroes it31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 1e112c47ec5dd1942e2d4ca6e8e9b712238e20c2 | Vendor (CNA) |
| Linux Linux | a8c18434e1f0d9f7989170bdb0490c0160baf065 | Vendor (CNA) |
| Linux Linux | c6394bcaf254c5baf9aff43376020be5db6d3316 | Vendor (CNA) |
| Linux Linux | cfb2c6f71d61ed807c9d7a7af331d406f1f31877 | Vendor (CNA) |
| Linux Linux | e205f3e7e8c31a47cd11efb6cf663a527177e432 | Vendor (CNA) |
| Linux Linux | fb1cae6302d58414ddf029e3f642711bd30243f7 | Vendor (CNA) |
| debian:linux | 6.1.180-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/a8c18434e1f0d9f7989170bdb0490c0160baf065
- git.kernel.org/stable/c/c6394bcaf254c5baf9aff43376020be5db6d3316
- git.kernel.org/stable/c/cfb2c6f71d61ed807c9d7a7af331d406f1f31877
- git.kernel.org/stable/c/e205f3e7e8c31a47cd11efb6cf663a527177e432
- git.kernel.org/stable/c/fb1cae6302d58414ddf029e3f642711bd30243f7
Vendor advisories and official records. Exploit/PoC links are deliberately left out.