VYPR
Unrated severityNVD Advisory· Published Nov 12, 2025· Updated Apr 15, 2026

CVE-2025-40125

CVE-2025-40125

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.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

In the Linux kernel's blk-mq subsystem, a missing check for kobject state before deletion can trigger a kernel warning when sysfs registration fails.

Vulnerability

Overview

CVE-2025-40125 is a vulnerability in the Linux kernel's block multi-queue (blk-mq) subsystem. The root cause is that in blk_mq_unregister_hctx(), the function unconditionally calls kobject_del() without first verifying that the kobject was successfully created in sysfs. This occurs when __blk_mq_update_nr_hw_queues() calls blk_mq_sysfs_register_hctxs() but does not check its return value. If sysfs creation for a hardware context (hctx) fails, a subsequent operation to change the number of hardware queues or remove the disk will attempt to delete a non-existent sysfs directory, leading to a kernel warning [1].

Exploitation

Scenario

An attacker with the ability to trigger a failure in sysfs creation for an hctx, for example by exhausting system resources or through a race condition, can cause the kernel to reach the vulnerable code path. The attack surface is local; the attacker needs to be able to interact with the block layer, such as by using a driver like null_blk to dynamically change the number of hardware queues. No special privileges are required beyond the ability to trigger the relevant ioctl or sysfs store operations [1].

Impact

When the vulnerability is triggered, the kernel emits a warning message and a stack trace, but does not crash. The primary impact is a denial of service condition due to the warning and potential system instability. There is no evidence of memory corruption or privilege escalation from this bug [1].

Mitigation

The fix has been applied to the Linux kernel stable tree in commit 06c4826b1d900611096e4621e93133db57e13911 and backported to other stable branches [1][2][3]. Users should update their kernel to a version containing this patch. No workaround is available other than avoiding the triggering conditions.

AI Insight generated on May 19, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

2

Patches

8

Vulnerability mechanics

Generated on May 9, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.

References

8

News mentions

0

No linked articles in our index yet.