dpll: fix pin dump crash for rebound module
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:
dpll: fix pin dump crash for rebound module
When a kernel module is unbound but the pin resources were not entirely freed (other kernel module instance of the same PCI device have had kept the reference to that pin), and kernel module is again bound, the pin properties would not be updated (the properties are only assigned when memory for the pin is allocated), prop pointer still points to the kernel module memory of the kernel module which was deallocated on the unbind.
If the pin dump is invoked in this state, the result is a kernel crash. Prevent the crash by storing persistent pin properties in dpll subsystem, copy the content from the kernel module when pin is allocated, instead of using memory of the kernel module.
From the CVE record · Linux
The Linux kernel's dpll subsystem can retain a pointer to memory freed when a module is unbound. If another module instance keeps a reference to the pin, rebinding the module and invoking a pin dump can crash the kernel. The input does not specify whether triggering this requires local or network access, authentication, or user interaction.
Teams running the Linux kernel should check for affected versions; none are specified in the input.