staging: bcm2835-camera: Initialise dev in v4l2_dev
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.12.296.14.76.15In the Linux kernel, the following vulnerability has been resolved:
staging: bcm2835-camera: Initialise dev in v4l2_dev
Commit 42a2f6664e18 ("staging: vc04_services: Move global g_state to vchiq_state") changed mmal_init to pass dev->v4l2_dev.dev to vchiq_mmal_init, however nothing iniitialised dev->v4l2_dev, so we got a NULL pointer dereference.
Set dev->v4l2_dev.dev during bcm2835_mmal_probe. The device pointer could be passed into v4l2_device_register to set it, however that also has other effects that would need additional changes.
From the CVE record · Linux
The Linux kernel's bcm2835-camera driver can dereference a NULL pointer because its V4L2 device pointer is not initialized before use. The issue occurs during camera initialization; the input does not specify whether an attacker can trigger it, or any access or user-interaction requirements.
Engineers running Linux kernels with the bcm2835-camera driver should check their installations; affected versions are not specified.