CVE-2026-23292: Linux kernel · scsi: target: Fix recursive locking in __configfs_open_file()
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in e8ef82cb6443d5f3260b1b830e17f03dda4229ea : update Linux kernel when convenient.
Data as of 5 Nov 2026, 21:49 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
Thin evidence
One scorer or none- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-11-05.
- Patch
- Available – fixed in e8ef82cb6443d5f3260b1b830e17f03dda4229ea, 3161ef61f121d4573cad5b57c92188dcd9b284b3, 142eacb50fb903a4c10dee7e67b6e79ebb36a582 +6
Exploitation evidence
Disclosed: evidence found.
CVE published 25 Mar 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 5 Nov 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– |
Description
In the Linux kernel, the following vulnerability has been resolved: scsi: target: Fix recursive locking in __configfs_open_file() In flush_write_buffer, &p->frag_sem is acquired and then the loaded store function is called, which, here, is target_core_item_dbroot_store(). This function called filp_open(), following which these functions were called (in reverse order), according to the call trace: down_read __configfs_open_file do_dentry_open vfs_open do_open path_openat do_filp_open file_open_name filp_open target_core_item_dbroot_store flush_write_buffer configfs_write_iter target_core_item_dbroot_store() tries to validate the new file path by trying to open the file path provided to it; however, in this case, the bug report shows: db_root: not a directory: /sys/kernel/config/target/dbroot indicating that the same configfs file was tried to be opened, on which it is currently working on. Thus, it is trying to acquire frag_sem semaphore of the same file of which it already holds the semaphore obtained in flush_write_buffer(), leading to acquiring the semaphore in a nested manner and a possibility of recursive locking. Fix this by modifying target_core_item_dbroot_store() to use kern_path() instead of filp_open() to avoid opening the file using filesystem-specific function __configfs_open_file(), and further modifying it to make this fix compatible.
References
- git.kernel.org/stable/c/3161ef61f121d4573cad5b57c92188dcd9b284b3 (opens in a new tab)
- git.kernel.org/stable/c/e8ef82cb6443d5f3260b1b830e17f03dda4229ea (opens in a new tab)
- git.kernel.org/stable/c/4fcfa424a581d823cb1a9676e3eefe6ca17e453a (opens in a new tab)
- git.kernel.org/stable/c/9a5641024fbfd9b24fe65984ad85fea10a3ae438 (opens in a new tab)
- git.kernel.org/stable/c/142eacb50fb903a4c10dee7e67b6e79ebb36a582 (opens in a new tab)
- git.kernel.org/stable/c/14d4ac19d1895397532eec407433c5d74d9da53b (opens in a new tab)
- cert-portal.siemens.com/productcert/html/ssa-784472.html (opens in a new tab)