misc/libmasm/module: Fix two use after free in ibmasm_init_one
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 736ce43295682d060f2b93624b4a339f9af6aab1 · < b9c87ce3bc6331f82811a8cf8e930423c22523a3| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
misc/libmasm/module: Fix two use after free in ibmasm_init_one
In ibmasm_init_one, it calls ibmasm_init_remote_input_dev(). Inside ibmasm_init_remote_input_dev, mouse_dev and keybd_dev are allocated by input_allocate_device(), and assigned to sp->remote.mouse_dev and sp->remote.keybd_dev respectively.
In the err_free_devices error branch of ibmasm_init_one, mouse_dev and keybd_dev are freed by input_free_device(), and return error. Then the execution runs into error_send_message error branch of ibmasm_init_one, where ibmasm_free_remote_input_dev(sp) is called to unregister the freed sp->remote.mouse_dev and sp->remote.keybd_dev.
My patch add a "error_init_remote" label to handle the error of ibmasm_init_remote_input_dev(), to avoid the uaf bugs.
From the CVE record · Linux
The Linux kernel's ibmasm module can use freed remote input devices when initialization fails and error handling attempts to unregister them. The input does not specify how an attacker could trigger this failure or whether access or user interaction is required.
Engineers running Linux kernels with the ibmasm module should check their versions; affected versions are not specified.