fbdev: defio: Disconnect deferred I/O from the lifetime of struct fb_info
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 60b59beafba875aef6d378078bce0baf2287ae14 · < a0aafb421dd15e935d81543152617f2742cefa70| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
fbdev: defio: Disconnect deferred I/O from the lifetime of struct fb_info
Hold state of deferred I/O in struct fb_deferred_io_state. Allocate an instance as part of initializing deferred I/O and remove it only after the final mapping has been closed. If the fb_info and the contained deferred I/O meanwhile goes away, clear struct fb_deferred_io_state.info to invalidate the mapping. Any access will then result in a SIGBUS signal.
Fixes a long-standing problem, where a device hot-unplug happens while user space still has an active mapping of the graphics memory. The hot- unplug frees the instance of struct fb_info. Accessing the memory will operate on undefined state.
From the CVE record · Linux
The Linux kernel’s fbdev deferred I/O can outlive its fb_info structure when a device is hot-unplugged while user space still has an active graphics-memory mapping. Subsequent access to that mapping can operate on undefined state; this requires a local user-space mapping and a hot-unplug event.
Engineers running Linux kernels with fbdev deferred I/O should check their kernel against the vendor advisory; affected versions were not specified.