dm rq: don't queue request to blk-mq during DM suspend
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
5.10.2415.14.145.15In the Linux kernel, the following vulnerability has been resolved:
dm rq: don't queue request to blk-mq during DM suspend
DM uses blk-mq's quiesce/unquiesce to stop/start device mapper queue.
But blk-mq's unquiesce may come from outside events, such as elevator switch, updating nr_requests or others, and request may come during suspend, so simply ask for blk-mq to requeue it.
Fixes one kernel panic issue when running updating nr_requests and dm-mpath suspend/resume stress test.
From the CVE record · Linux
The Linux kernel can queue a device mapper request during suspend if an external event unquiesces the blk-mq queue. A kernel panic was observed while updating nr_requests during a dm-mpath suspend/resume stress test; the input does not establish attacker access requirements or user interaction.
Engineers running Linux kernel systems that use device mapper should check their kernel versions; affected versions were not provided.