s390/vfio_ccw: Free all memory if cp_init() fails
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 8b515be512a2435bb8aedc6390cbe140167f9eb9 · < 32e3d364a7b8295120d37e6a6bd433d2de26f748| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
s390/vfio_ccw: Free all memory if cp_init() fails
The routine cp_free() is called to unpin/free any memory once an I/O is completed successfully, or if cp_prefetch() fails. But if cp_init() fails, and cp->initialized is not enabled, the same routine cannot be used to free all the memory.
An attempt to address this exists in ccwchain_handle_ccw(), where a single call to ccwchain_free() is made for the currently-processed CCW segment. But this will leak other segments (created as a result of a Transfer in Channel) that had been allocated as part of the same channel program.
Address this by performing the cleanup outside of the recursive ccwchain_handle_ccw()/ccwchain_loop_tic() logic.
From the CVE record · Linux
The Linux kernel’s s390/vfio_ccw code can leak allocated channel-program segments if cp_init() fails. The input does not specify whether an attacker can trigger the failure, or any network, authentication, or user-interaction requirements.
Engineers running Linux systems that use s390/vfio_ccw should check their kernel; affected versions were not provided.