media: atomisp: gc2235: fix UAF and memory leak
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ ad85094b293e40e7a2f831b0311a389d952ebd5e · < f614bf0a64aa1cb7444d152a96798a6bf1d49e1f| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
media: atomisp: gc2235: fix UAF and memory leak
gc2235_probe() handles its error paths incorrectly.
If media_entity_pads_init() fails, gc2235_remove() is called, which tears down the subdev and frees dev, but then still falls through to atomisp_register_i2c_module(). This results in use-after-free.
If atomisp_register_i2c_module() fails, the media entity and control handler are left initialized and dev is leaked.
gc2235_remove() unconditionally calls media_entity_cleanup() and v4l2_ctrl_handler_free(), but these are not initialized at every error path in gc2235_probe().
Replace gc2235_remove() calls in the probe error paths with explicit unwind labels that free only the resources initialized at each point of failure, in reverse order of initialization.
From the CVE record · Linux
The Linux kernel’s atomisp gc2235 probe has incorrect error handling. If media_entity_pads_init() fails, it can use freed memory; if atomisp_register_i2c_module() fails, it can leak memory. The input does not establish whether an attacker can trigger these failures or what access would be required.
Engineers running Linux kernels with the atomisp gc2235 driver should check their builds; affected versions are not specified.