CVE-2025-40125

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