md: call __md_stop_writes in md_stop
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 48df498daf62e1292868005675331929305067f0 · < f42a9819ba84bed2e609a4dff56af37063dcabdc| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
md: call __md_stop_writes in md_stop
From the link [1], we can see raid1d was running even after the path raid_dtr -> md_stop -> __md_stop.
Let's stop write first in destructor to align with normal md-raid to fix the KASAN issue.
[1]. https://lore.kernel.org/linux-raid/CAPhsuW5gc4AakdGNdF8ubpezAuDLFOYUO_sfMZcec6hQFm8nhg@mail.gmail.com/T/#m7f12bf90481c02c6d2da68c64aeed4779b7df74a
From the CVE record · Linux
The Linux kernel's md_stop path can leave raid1d running after the stop sequence, causing a KASAN issue. The input does not establish what an attacker can do or specify network or local access, authentication, or user-interaction conditions.
Engineers running the Linux kernel should check their systems; affected versions are not specified.