CVE-2026-31717

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> ksmbd: validate owner of durable handle on reconnect<br /> <br /> Currently, ksmbd does not verify if the user attempting to reconnect<br /> to a durable handle is the same user who originally opened the file.<br /> This allows any authenticated user to hijack an orphaned durable handle<br /> by predicting or brute-forcing the persistent ID.<br /> <br /> According to MS-SMB2, the server MUST verify that the SecurityContext<br /> of the reconnect request matches the SecurityContext associated with<br /> the existing open.<br /> Add a durable_owner structure to ksmbd_file to store the original opener&amp;#39;s<br /> UID, GID, and account name. and catpure the owner information when a file<br /> handle becomes orphaned. and implementing ksmbd_vfs_compare_durable_owner()<br /> to validate the identity of the requester during SMB2_CREATE (DHnC).