CVE-2026-90155: ksmbd: detach blocked lock requests before freeing

Published Sep 17, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

ksmbd: detach blocked lock requests before freeing

A filelock retained by ksmbd for byte-range lock bookkeeping can still be part of the VFS blocked-request graph. In particular, the VFS can chain a new waiter below an already blocked request through flcblockedrequests. The ksmbdfile reference count does not cover that graph.

Both ksmbdclosefd() and the cross-request unlock path free these retained filelock objects directly. If a dependent waiter is still attached, locksreleaseprivate() hits BUGON(!listempty(&flc->flcblockedrequests)). The same lifetime mismatch can leave a freed ksmbdlock reachable through its request-local llist.

Detach the filelock from the blocked-request graph before freeing it in the close, cross-request unlock, and rollback paths. locksdeleteblock() also wakes requests chained below the object. Remove llist when a completed lock is published so a globally visible ksmbdlock no longer points into the submitting worker's stack.

Affected Software

1 affected component
Linux Kernel

Event History

Sep 17, 2026
CVE Published
via MITRE·04:06 PM
Data Sourced
via MITRE·04:06 PM
Description

Frequently Asked Questions

1

Which systems are exposed to this issue?

Systems using the Linux kernel's ksmbd SMB server are exposed when ksmbd retains byte-range lock state and blocked VFS lock requests can be chained beneath it. The affected paths include file-descriptor close, cross-request unlock, and lock rollback.

2

What conditions are needed to trigger the failure?

A dependent lock waiter must remain attached in the VFS blocked-request graph when ksmbd frees a retained file_lock. This can cause a BUG_ON when the lock is released and can also leave a freed ksmbd_lock reachable through a request-local list.

3

What does the fix change?

The fix detaches retained file_lock objects from the blocked-request graph before freeing them, including close, cross-request unlock, and rollback handling. It also removes completed published locks from the request-local list so globally visible lock state does not reference a submitting worker's stack.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203