CVE-2025-40125

blk-mq: check kobject state_in_sysfs before deleting in blk_mq_unregister_hctx

N/A
Published: November 12, 2025 at 10:23 AM UTC
Updated: October 19, 2026 at 09:10 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.20477e19dedc9d3e1f4443a1d4ae00572a988120ea
Vendor states this is fixed in 06c4826b1d900611096e4621e93133db57e13911 (fixed)
Vendor states this is fixed in 4b97e99b87a773d52699521d40864f3ec888e9a6 (fixed)
Vendor states this is fixed in 4c7ef92f6d4d08a27d676e4c348f4e2922cab3ed (fixed)
Vendor states this is fixed in 6e7dadc5763c48eb3b9b91265a21f312599ebb2c (fixed)
Vendor states this is fixed in a8c53553f1833cc2d14175d2d72cf37193a01898 (fixed)
Vendor states this is fixed in babc634e9fe2803962dba98a07587e835dbc0731 (fixed)
Vendor states this is fixed in cc14ea21c4e658814d737ed4dedde6cd626a15ad (fixed)
Vendor states this is fixed in d5ddd76ee52bdc16e9f8b1e7791291e785dab032 (fixed)
Vendor states this is fixed in 4.20 (unaffected)
Vendor states this is fixed in 5.10.246 (unaffected)
Vendor states this is fixed in 5.15.195 (unaffected)
Vendor states this is fixed in 5.4.301 (unaffected)
Vendor states this is fixed in 6.1.156 (unaffected)
Vendor states this is fixed in 6.12.53 (unaffected)
Vendor states this is fixed in 6.17.3 (unaffected)
Vendor states this is fixed in 6.18 (unaffected)
Vendor states this is fixed in 6.6.112 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusDEFERRED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card