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-2025-40125blk-mq: check kobject state_in_sysfs before deleting in blk_mq_unregister_hctx

Description

In the Linux kernel, the following vulnerability has been resolved: blk-mq: check kobject state_in_sysfs before deleting in blk_mq_unregister_hctx In __blk_mq_update_nr_hw_queues() the return value of blk_mq_sysfs_register_hctxs() is not checked. If sysfs creation for hctx fails, later changing the number of hw_queues or removing disk will trigger the following warning: kernfs: can not remove 'nr_tags', no directory WARNING: CPU: 2 PID: 637 at fs/kernfs/dir.c:1707 kernfs_remove_by_name_ns+0x13f/0x160 Call Trace: remove_files.isra.1+0x38/0xb0 sysfs_remove_group+0x4d/0x100 sysfs_remove_groups+0x31/0x60 __kobject_del+0x23/0xf0 kobject_del+0x17/0x40 blk_mq_unregister_hctx+0x5d/0x80 blk_mq_sysfs_unregister_hctxs+0x94/0xd0 blk_mq_update_nr_hw_queues+0x124/0x760 nullb_update_nr_hw_queues+0x71/0xf0 [null_blk] nullb_device_submit_queues_store+0x92/0x120 [null_blk] kobjct_del() was called unconditionally even if sysfs creation failed. Fix it by checkig the kobject creation statusbefore deleting it.

Timeline

  1. ID reserved

    By Linux

  2. · 7 months later

    Published

  3. · 6 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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.

EPSS (exploitation in 30 days)
0.23% · top 86% of all CVEs (17 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 477e19dedc9d3e1f4443a1d4ae00572a988120ea – < a8c53553f1833cc2d14175d2d72cf37193a01898
    • affected 477e19dedc9d3e1f4443a1d4ae00572a988120ea – < cc14ea21c4e658814d737ed4dedde6cd626a15ad
    • affected 477e19dedc9d3e1f4443a1d4ae00572a988120ea – < 4b97e99b87a773d52699521d40864f3ec888e9a6
    • affected 477e19dedc9d3e1f4443a1d4ae00572a988120ea – < 6e7dadc5763c48eb3b9b91265a21f312599ebb2c
    • affected 477e19dedc9d3e1f4443a1d4ae00572a988120ea – < 06c4826b1d900611096e4621e93133db57e13911
    • affected 477e19dedc9d3e1f4443a1d4ae00572a988120ea – < babc634e9fe2803962dba98a07587e835dbc0731
    • affected 477e19dedc9d3e1f4443a1d4ae00572a988120ea – < d5ddd76ee52bdc16e9f8b1e7791291e785dab032
    • affected 477e19dedc9d3e1f4443a1d4ae00572a988120ea – < 4c7ef92f6d4d08a27d676e4c348f4e2922cab3ed
  • Linux · Linux

    • affected 4.20
    • unaffected < 4.20
    • unaffected 5.4.301 – ≤ 5.4.*
    • unaffected 5.10.246 – ≤ 5.10.*
    • unaffected 5.15.195 – ≤ 5.15.*
    • unaffected 6.1.156 – ≤ 6.1.*
    • unaffected 6.6.112 – ≤ 6.6.*
    • unaffected 6.12.53 – ≤ 6.12.*
    • unaffected 6.17.3 – ≤ 6.17.*
    • unaffected 6.18 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .