s390/cio: Fix device lifecycle handling in css_alloc_subchannel()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
s390/cio: Fix device lifecycle handling in css_alloc_subchannel()
`css_alloc_subchannel()` calls `device_initialize()` before setting up the DMA masks. If `dma_set_coherent_mask()` or `dma_set_mask()` fails, the error path frees the subchannel structure directly, bypassing the device model reference counting.
Once `device_initialize()` has been called, the embedded struct device must be released via `put_device()`, allowing the release callback to free the container structure.
Fix the error path by dropping the initial device reference with `put_device()` instead of calling `kfree()` directly.
This ensures correct device lifetime handling and avoids potential use-after-free or double-free issues.
From the CVE record · Linux
In the Linux kernel, css_alloc_subchannel() can free a subchannel directly after device initialization if DMA mask setup fails, bypassing device reference counting. This can lead to potential use-after-free or double-free issues. The input does not describe an attacker path, authentication requirements, or user interaction.
Engineers running Linux kernels with the s390/cio component should check their exposure; affected versions are not specified.