media: atomisp: ssh_css: Fix a null-pointer dereference in load_video_binaries
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ ad85094b293e40e7a2f831b0311a389d952ebd5e · < 69b27ff82f87379afeaaea4b2f339032fdd8486e| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
media: atomisp: ssh_css: Fix a null-pointer dereference in load_video_binaries
The allocation failure of mycs->yuv_scaler_binary in load_video_binaries() is followed with a dereference of mycs->yuv_scaler_binary after the following call chain:
sh_css_pipe_load_binaries() |-> load_video_binaries(mycs->yuv_scaler_binary == NULL) | |-> sh_css_pipe_unload_binaries() |-> unload_video_binaries()
In unload_video_binaries(), it calls to ia_css_binary_unload with argument &pipe->pipe_settings.video.yuv_scaler_binary[i], which refers to the same memory slot as mycs->yuv_scaler_binary. Thus, a null-pointer dereference is triggered.
From the CVE record · Linux
The Linux kernel’s atomisp ssh_css code can dereference a null pointer when allocation of yuv_scaler_binary fails during load_video_binaries() and the unload path accesses it. This can cause a crash; the input does not establish whether an attacker can trigger it or what access or interaction would be required.
Engineers running Linux kernels with the affected atomisp ssh_css code should check their kernel versions; the affected versions are not specified.