CVE-2023-53650

What it actually does

Failure to release an allocated structure on error return from mipid_detect in the probe routine leaves kernel memory allocated with no reference, constituting a local memory leak.

Why it matters to the business

Repeated triggering of the probe path on systems using the affected framebuffer driver can gradually exhaust kernel memory, leading to degraded performance or denial of service for graphics and display functionality.

How an attack unfolds

An attacker with local access loads or triggers the omapfb lcd_mipid driver module under conditions where mipid_detect fails, causing the leak; repeated module load/unload cycles or device enumeration events accumulate the leaked memory until system resources are exhausted.

How to fix it

Update the Linux kernel to the commit d97840bf5a388c6cbf6e46216887bf17be62acc2 or later stable releases that include the fix; rebuild and deploy the updated kernel image on all affected systems; for publify_core update to version 8.0.1.

How to confirm the fix worked

Confirm the presence of the fix by inspecting the mipid_spi_probe function for the added kfree(md) call on the mipid_detect error path; verify the running kernel contains commit d97840bf5a388c6cbf6e46216887bf17be62acc2 via git log or kernel version string.

Typical attack path

1. Obtain local user or container access on a system with the vulnerable omapfb lcd_mipid driver present
2. Trigger driver probe via module load, device hotplug, or framebuffer initialization that reaches mipid_spi_probe
3. Force mipid_detect to return failure
4. Repeat the probe-failure sequence to accumulate unreleased allocations
5. Observe system-wide memory pressure or OOM conditions affecting availability

How to detect it

Review kernel logs for repeated mipid_spi_probe and mipid_detect error entries; inspect slab or kmalloc allocation patterns for growth in structures associated with the lcd_mipid driver; correlate with module load events in audit logs.

What your security team should do

• Prioritize kernel updates on systems exposing the omapfb lcd_mipid driver within the next maintenance window
• Audit kernel configurations to disable unused framebuffer drivers where possible
• Monitor memory usage metrics on graphics-enabled hosts for unexpected growth after driver initialization
• Include the fixed commit hash in automated kernel build and deployment pipelines