HID: picoLCD: check for fb_deferred_io_init() error
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel feade898fc958ff355101adf12d5632272e64220, Kernel 5.16, Kernel 14acfdfca5151537b623243a6c0e66a2e6fca7de and 5 more.
In the Linux kernel, the following vulnerability has been resolved: HID: picoLCD: check for fb_deferred_io_init() error fb_deferred_io_init() allocates deferred I/O state, populating info->fbdefio_state, or leaving it NULL if an error occurs. Currently picolcd_init_framebuffer() ignores its return value. Therefore if an error arises in fb_deferred_io_init() (for instance, due to an allocation failure) info->fbdefio_state is left NULL. When the file is subsequently opened, fb_open() will dereference a NULL pointer (calling fb_deferred_io_open()). Fix this by checking for the error. Also correct cleanup ordering - defio is initialised after the sysfs file, so cleanup defio first.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=56c134f7f1b58be08bdb0ca8372474a4a5165f31 <feade898fc958ff355101adf12d5632272e64220, >=5.15.149 <5.16, >=56c134f7f1b58be08bdb0ca8372474a4a5165f31 <14acfdfca5151537b623243a6c0e66a2e6fca7de, >=56c134f7f1b58be08bdb0ca8372474a4a5165f31 <28be73031ae5397a0592fa6308051f743fb428f7, >=56c134f7f1b58be08bdb0ca8372474a4a5165f31 <ebe54f9e793bf05c7bd82110fdab24f10b89eac3, =186b89659c4c67cccead52961eab0ca3b23951dc, =5.19 | feade898fc958ff355101adf12d5632272e64220, 5.16, 14acfdfca5151537b623243a6c0e66a2e6fca7de, 28be73031ae5397a0592fa6308051f743fb428f7, ebe54f9e793bf05c7bd82110fdab24f10b89eac3 |
| linux-kernel: Kernel | >=5.19.0 <6.12.117, >=6.13.0 <6.18.61, >=6.19.0 <7.3.2, >=5.15.149 <5.16 | 6.12.117, 6.18.61, 7.3.2, 5.16 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket