CVE-2026-23292 scsi: target: Fix recursive locking in __configfs_open_file()

Medium 5.5 Published Updated

A recursive locking bug in the Linux kernel SCSI target subsystem can cause a deadlock, leading to a denial of service.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Local or same network only
Victim action needed
Not needed
Fix
Available

What is CVE-2026-23292?

CVE-2026-23292 is a medium-severity denial of service vulnerability in Linux kernel, published on 25 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.

Official 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.

Weakness: CWE-674

Which versions are affected by CVE-2026-23292?

It affects 1 product.

Products include Linux kernel.

How do I fix CVE-2026-23292?

Apply the vendor's patch.

Upgrade, then put limits on request size, rate and nesting depth so one client cannot exhaust the service. More about Denial of service.

Is CVE-2026-23292 being exploited?

There is no known exploitation of CVE-2026-23292 in the wild and no public exploit code.

All Linux kernel vulnerabilities

Sources

Also known as AZL-80615, BELL-CVE-2026-23292, DEBIAN-CVE-2026-23292, GHSA-55fh-fmpq-w8h6, ROOT-OS-DEBIAN-11-CVE-2026-23292, ROOT-OS-DEBIAN-12-CVE-2026-23292 and 4 more.

Is CVE-2026-23292 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free