Linux
ksmbd: validate owner of durable handle on reconnect
In the Linux kernel, the following vulnerability has been resolved: ksmbd: validate owner of durable handle on reconnect Currently, ksmbd does not verify if the user attempting to reconnect to a durable handle is the same user who originally opened the file. This allows any authenticated user to hijack an orphaned durable handle by predicting or brute-forcing the persistent ID. According to MS-SMB2, the server MUST verify that the SecurityContext of the reconnect request matches the SecurityContext associated with the existing open. Add a durable_owner structure to ksmbd_file to store the original opener's UID, GID, and account name. and catpure the owner information when a file handle becomes orphaned. and implementing ksmbd_vfs_compare_durable_owner() to validate the identity of the requester during SMB2_CREATE (DHnC).
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 8df4bcdb0a4232192b2445256c39b787d58ef14d, < 712cdf917e77a6444ce3836874829d770db20ee6
- >= c8efcc786146a951091588e5fa7e3c754850cb3c, < c7f0f0d01c88bdcb8b1694d7d321670013f7ed7d
- >= c8efcc786146a951091588e5fa7e3c754850cb3c, < 00ce8d6789dae72d042a4522264964c72891ca37
- >= c8efcc786146a951091588e5fa7e3c754850cb3c, < c908c853f304a4969b5aa10eba0b50350cc65b80
- >= c8efcc786146a951091588e5fa7e3c754850cb3c, < 49110a8ce654bbe56bef7c5e44cce31f4b102b8a
- >= 6.6.32, < 6.6.142
Fixed in 712cdf917e77a6444ce3836874829d770db20ee6, c7f0f0d01c88bdcb8b1694d7d321670013f7ed7d, 00ce8d6789dae72d042a4522264964c72891ca37, c908c853f304a4969b5aa10eba0b50350cc65b80, 49110a8ce654bbe56bef7c5e44cce31f4b102b8a, 6.6.142
- 6.9
Fixed in 0, 6.6.142, 6.12.92, 6.18.25, 7.0.2, 7.1
Mitigation
Upgrade Linux to 712cdf917e77a6444ce3836874829d770db20ee6 or c7f0f0d01c88bdcb8b1694d7d321670013f7ed7d or 00ce8d6789dae72d042a4522264964c72891ca37 or c908c853f304a4969b5aa10eba0b50350cc65b80 or 49110a8ce654bbe56bef7c5e44cce31f4b102b8a or 6.6.142 or later.
Upgrade Linux to 0 or 6.6.142 or 6.12.92 or 6.18.25 or 7.0.2 or 7.1 or later.
Timeline
Days relative to CVE publicationFirst public PoC 3.3 days after publication; not in CISA KEV. First PoC: TurtleARM/ksmbrace (created 4 May 2026, found by us: backfilled).
PoC repositories
Found on GitHub.1 PoCs
PoCs 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| TurtleARM/ksmbrace | 4 May 2026 +3.3 d | 5 | PoC via PoC Index |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.