CVE-2026-90156: Linux kernel · ksmbd: safely discard unregistered deferred locks
Source GCVE Database
Not known to be exploited · fixed in ecdcfa15b3d799476c685cecd433ebefc93015c8 : update Linux kernel when convenient.
Data as of 30 Oct 2026, 19:05 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in ecdcfa15b3d799476c685cecd433ebefc93015c8, d09af9a35ff7b77a950b507133d9092aadbfeff4, aaa51ac0d934cb4e2ab96e150fccc934e822009b +3
Exploitation evidence
Disclosed: evidence found.
CVE published 17 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
AI-suggested
A fix has been implemented to address this issue by modifying the lock handling logic. Users should apply the official Linux kernel updates that include this fix once available.
Description
A vulnerability in the Linux kernel's ksmbd component involves unsafe handling of unregistered deferred locks. Specifically, if asynchronous work setup fails after deferring a lock, the rollback process may dereference a NULL pointer and leave the deferred lock linked in the VFS blocked-lock state while freeing it. This issue has been resolved by ensuring the lock is only added to the rollback list after successful async setup and properly unblocking and waking the deferred lock on failure.
References
- nvd.nist.gov/vuln/detail/CVE-2026-90156 (opens in a new tab)
- git.kernel.org/stable/c/054bcca4cd9f00719b01f7108b51a2168fb94f15 (opens in a new tab)
- git.kernel.org/stable/c/52b91bc5253bb83665f3ea70565d0b2487dae643 (opens in a new tab)
- git.kernel.org/stable/c/77413400f083a959724de6f36348c9677ef9873a (opens in a new tab)
- git.kernel.org/stable/c/aaa51ac0d934cb4e2ab96e150fccc934e822009b (opens in a new tab)
- git.kernel.org/stable/c/d09af9a35ff7b77a950b507133d9092aadbfeff4 (opens in a new tab)
- git.kernel.org/stable/c/ecdcfa15b3d799476c685cecd433ebefc93015c8 (opens in a new tab)