nvme: fix racy access to FDP placement id array
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 |
|
|
In the Linux kernel, the following vulnerability has been resolved:
nvme: fix racy access to FDP placement id array
nvme_query_fdp_info() is called per-path and therefore prone to races.
It populates head->nr_plids/head->plids for fdp registration. But nothing protects that pair from concurrent access - two paths scanning the same namespace can race to populate it.
Avoid the race by moving this initialization work to nvme_alloc_ns_head() which is called once per shared namespace.
From the CVE record · Linux
The Linux kernel can race when multiple NVMe paths scan the same namespace and populate its FDP placement ID array. The input does not specify an attacker action or whether exploitation requires network access, local access, authentication, or user interaction.
Engineers running the Linux kernel with NVMe FDP should check their versions; affected versions are not specified.