CVE-2026-90155 json
ksmbd: detach blocked lock requests before freeing
published 2026-09-17 52 d ago modified 2026-10-30 9 d ago also EUVD-2026-81748
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 11%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: detach blocked lock requests before freeing
A file_lock 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 flc_blocked_requests. The ksmbd_file reference count does not cover that graph.
Both __ksmbd_close_fd() and the cross-request unlock path free these retained file_lock objects directly. If a dependent waiter is still attached, locks_release_private() hits BUG_ON(!list_empty(&flc->flc_blocked_requests)). The same lifetime mismatch can leave a freed ksmbd_lock reachable through its request-local llist.
Detach the file_lock from the blocked-request graph before freeing it in the close, cross-request unlock, and rollback paths. locks_delete_block() also wakes requests chained below the object. Remove llist when a completed lock is published so a globally visible ksmbd_lock no longer points into the submitting worker's stack.
Patch / fix
- Linux Linux 6.1.191, 6.6.160, 6.12.114, 6.18.57, 7.2.6, 7.3
- linux Debian 13 6.12.115-2
- linux Debian 14 7.2.6-1
debian advisories DEBIAN-CVE-2026-90155
- kernel-source openSUSE Tumbleweed 7.2.7-1.1
opensuse advisories openSUSE-SU-2026:11880-1
- kernel Azure Linux 3.0 6.6.161.1-1
azure linux advisories AZL-102578
Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT
- git.kernel.org/stable/c/4e8b69c06bd6583ec11abef4fae50c2c8d5f3679 commit
- git.kernel.org/stable/c/d20d3f6ad8b0b6f4e1bb32cdf7eca251962e8f04 commit
- git.kernel.org/stable/c/d31db79cfaa9fce6649772ad279779473ba8aef9 commit
- git.kernel.org/stable/c/f77d2accafca529e0ea3f979eb6e6cf1dac05c90 commit
- git.kernel.org/stable/c/514a0b2bc949963497e66cacd433f65dc768a71d commit
- git.kernel.org/stable/c/215e8816b1ac25176d911abb8704390413ccee4b commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-90155 updated cvss 5.5
kernel: ksmbd: detach blocked lock requests before freeing
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernel Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-8, openshift/ose-rhel-coreos-9not affected: vulnerable code not present
+1 more productsfewer
Red Hat OpenShift Container Platform 5 openshift/ose-rhel-coreos-9
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.21% chance of exploitation in the next 30 days, higher than 11% of all scored CVEs (FIRST EPSS, 2026-11-08).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/4e8b69c06bd6583ec11abef4fae50c2c8d5f3679
- git.kernel.org /stable/c/d20d3f6ad8b0b6f4e1bb32cdf7eca251962e8f04
- git.kernel.org /stable/c/d31db79cfaa9fce6649772ad279779473ba8aef9
- git.kernel.org /stable/c/f77d2accafca529e0ea3f979eb6e6cf1dac05c90
- git.kernel.org /stable/c/514a0b2bc949963497e66cacd433f65dc768a71d
- git.kernel.org /stable/c/215e8816b1ac25176d911abb8704390413ccee4b
Sources
- CVE List CVE-2026-90155
- NVD CVE-2026-90155
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.