nvme-multipath: set BLK_FEAT_ZONED only after the zone info is known
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-multipath: set BLK_FEAT_ZONED only after the zone info is known
The namespace head is marked zoned at allocation time based only on the command set identifier. If the zone info query reports a zero zone size, the path namespace is registered without zoned limits while the head still advertises the zoned capability with a zone size of zero, and reporting zones or writing to the head then shifts by ilog2(0).
Drop the zoned feature from the head allocation and let the head limits refresh stack it in from the path namespace instead.
From the CVE record · Linux
The Linux kernel's nvme-multipath namespace head can advertise zoned support before zone information is known. If a zone information query returns a zero zone size, reporting zones or writing to the head triggers a shift based on ilog2(0). The input does not describe an attacker path, authentication requirement, or user-interaction requirement.
Engineers running Linux kernels that use nvme-multipath should check their deployments; affected versions are not specified.