[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <15fb6eed-e107-4ef7-a569-3328a02e2c39@huaweicloud.com>
Date: Thu, 27 Nov 2025 21:22:42 +0800
From: Zheng Qixing <zhengqixing@...weicloud.com>
To: gregkh@...uxfoundation.org
Cc: cve@...nel.org, gregkh@...nel.org, linux-cve-announce@...r.kernel.org,
linux-kernel@...r.kernel.org, yukuai@...as.com, ming.lei@...hat.com,
Nilay Shroff <nilay@...ux.ibm.com>, "zhangyi (F)" <yi.zhang@...wei.com>,
yangerkun <yangerkun@...wei.com>, Hou Tao <houtao1@...wei.com>
Subject: Re: CVE-2025-40146: blk-mq: fix potential deadlock while nr_requests
grown
Hi,
Commit b86433721f46 ("blk-mq: fix potential deadlock while nr_requests
grown") aims to avoid a deadlock issue when the queue is frozen and
memory reclaim is triggered.
However, the sysfs nr_requests update path is already under a
memalloc_noio_save() region while the queue is frozen (via
blk_mq_freeze_queue()).
Would it be possible to reject this CVE, or clarify why it needs CVE
assignment in this case?
Any feedback or further explanation would be appreciated.
Best regards,
Qixing
Powered by blists - more mailing lists