Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 2 months later

    Published

  3. · 8 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-23292, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.13% · top 97% of all CVEs (18 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected b0841eefd9693827afb9888235e26ddd098f9cef – < 3161ef61f121d4573cad5b57c92188dcd9b284b3
    • affected b0841eefd9693827afb9888235e26ddd098f9cef – < e8ef82cb6443d5f3260b1b830e17f03dda4229ea
    • affected b0841eefd9693827afb9888235e26ddd098f9cef – < 4fcfa424a581d823cb1a9676e3eefe6ca17e453a
    • affected b0841eefd9693827afb9888235e26ddd098f9cef – < 9a5641024fbfd9b24fe65984ad85fea10a3ae438
    • affected b0841eefd9693827afb9888235e26ddd098f9cef – < 142eacb50fb903a4c10dee7e67b6e79ebb36a582
    • affected b0841eefd9693827afb9888235e26ddd098f9cef – < 14d4ac19d1895397532eec407433c5d74d9da53b
    • affected 49824b5c875087a52672b0c8e8ecbefe6f773532
    • affected 09e21253d17f53bdb5aac0e0dbd057a29fcbe8d1
    • affected 0dfc45be875a378c2a3a4d6ed8e668ec8eb75073
    • affected 4.9.201 – < 4.10
    • affected 4.14.154 – < 4.15
    • affected 4.19.84 – < 4.20
  • Linux · Linux

    • affected 5.3
    • unaffected < 5.3
    • unaffected 6.1.167 – ≤ 6.1.*
    • unaffected 6.6.130 – ≤ 6.6.*
    • unaffected 6.12.77 – ≤ 6.12.*
    • unaffected 6.18.17 – ≤ 6.18.*
    • unaffected 6.19.7 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-23292 badge
[![CVE-2026-23292](https://cveledger.app/badge/CVE-2026-23292.svg)](https://cveledger.app/cve/CVE-2026-23292)

Record last updated .