CVE-2023-54208

What it actually does

Memory leak occurs in ov5675_init_controls because v4l2_ctrl_handler resources allocated via v4l2_ctrl_handler_init_class are not freed on the failure path, leaving unreferenced kernel objects.

Why it matters to the business

Systems using the affected camera driver may experience gradual kernel memory exhaustion during repeated device probe attempts, potentially causing instability or reduced availability on embedded or IoT devices with this sensor.

How an attack unfolds

An attacker with local access triggers repeated probe operations on the ov5675 driver (for example via module reload or device hot-plug simulation) so that the init_controls failure path is exercised, accumulating leaked kernel memory over time.

How to fix it

Update the Linux kernel to a version containing commit 086a80b842bcb621d6c4eedad20683f1f674d0c2 which adds the missing v4l2_ctrl_handler_free call in the failure path of ov5675_init_controls.

How to confirm the fix worked

Confirm the presence of the fix commit in the running kernel source or verify that kmemleak no longer reports unreferenced objects from ov5675_init_controls after device probe.

Typical attack path

1. Obtain local access or ability to load/unload kernel modules or simulate device events
2. Trigger ov5675_probe repeatedly under conditions that cause v4l2_ctrl_handler_init_class to fail after partial allocation
3. Observe or accelerate memory consumption via the resulting unreferenced objects reported by kmemleak

How to detect it

Inspect kmemleak reports for allocations originating from v4l2_ctrl_handler_init_class called by ov5675_probe; check kernel logs for repeated i2c_device_probe entries involving ov5675 under error conditions.

What your security team should do

• Apply the kernel update containing the referenced commit at the earliest maintenance window
• Monitor kmemleak output on systems that use the ov5675 driver for signs of the leak until patched
• Limit local module loading privileges where possible to reduce the chance of repeated probe triggers