rapidio: clear mport->net when rio_add_net() fails
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ e842f9a1edf306bf36fe2a4d847a0b0d458770de · < 44a37264b26911e13d0a4f5630751c4157ed0354| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
rapidio: clear mport->net when rio_add_net() fails
rio_alloc_net() stores the newly allocated rio_net in mport->net before rio_scan_alloc_net() registers the device.
If rio_add_net() fails, rio_scan_alloc_net() drops the device reference with put_device(), which releases the rio_net through the device release callback. However, mport->net is left pointing at the freed object.
A later mport unregister path can then dereference the dangling mport->net pointer and may try to free the same rio_net again.
Clear mport->net in the rio_add_net() failure path, matching the cleanup done for the destID table allocation failure path.
From the CVE record · Linux
The Linux kernel’s RapidIO code can leave a pointer to freed memory when rio_add_net() fails. A later mport unregister can dereference that pointer and may try to free the same object again. The input does not establish how an attacker could trigger this condition or whether access or user interaction is required.
Engineers running Linux kernels with RapidIO support should check their versions; affected versions were not provided.