Skip to main content

Boteraser | Website and Server Security Solutions

🛡️ CVE-2026-23292 — kernel

🟡 CVSS 5.5 — Medium ✅ No Known Exploit NVD
5.5
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

scsi: target: Fix recursive locking in __configfs_open_file()

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.

How this vulnerability can be exploited

This issue can be reached with local access to the system, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality none, integrity none, availability high.

Affected software

CVE-2026-23292 is recorded against 2 packages.

  • kernel (from 6.19.0 up to 6.19.7)
  • linux-kernel

Timeline and source

Published on 25 March 2026 and last revised on 12 August 2026. No public exploit is currently recorded for this entry. A vendor advisory or fix has been published. Record sourced from NVD.

References

git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
github.com (Advisory)
nvd.nist.gov (Advisory)
git.kernel.org (Package)

CVE-2026-23292 on other distributions

Each distribution ships its own build and its own fixed version. Pick the one you run:

Details

Severity Medium
CVSS Score 5.5
CVSS Vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CWE N/A
Public Exploit ✅ No
Source NVD
Published 2026-03-25
Updated 2026-08-20
Modified 2026-08-12

Affected Packages

Software From version Fixed in
kernel 6.19.0 6.19.7
linux-kernel

Similar Threats

Vulnerability Monitoring

Track new vulnerabilities in kernel

CVE-2026-23292 is rated CVSS 5.5 Medium. BotEraser monitors your WordPress installation and notifies you when software you use appears in our vulnerability database.

Set Up Free Alerts →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.