CVE-2023-53650

fbdev: omapfb: lcd_mipid: Fix an error handling path in mipid_spi_probe()

MEDIUM

5.5

CVSS Score

Published: October 7, 2025 at 03:19 PM UTC

Updated: June 17, 2026 at 06:45 AM UTC

1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM5.5

Exploit prediction

EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: fbdev: omapfb: lcd_mipid: Fix an error handling path in mipid_spi_probe() If 'mipid_detect()' fails, we must free 'md' to avoid a memory leak.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel · Linux

95%

2.6.32 ≤ v < 4.14.3222.6.32 ≤ v < 4.19.2912.6.32 ≤ v < 5.10.1882.6.32 ≤ v < 5.15.1212.6.32 ≤ v < 5.4.2512.6.32 ≤ v < 6.1.392.6.32 ≤ v < 6.3.132.6.32 ≤ v < 6.4.42.6.32 ≤ v < 6.54.15 ≤ v < 4.19.2914.20 ≤ v < 5.4.2515.11 ≤ v < 5.15.1215.16 ≤ v < 6.1.395.5 ≤ v < 5.10.1886.2 ≤ v < 6.3.136.4 ≤ v < 6.4.42.6.3266d2f99d0bb5a2972fb5c1d88b61169510e540d6

Vendor states this is fixed in 09ea1ae4a2ec17774892cfcff50f6d33dfa1e06f (fixed)

Vendor states this is fixed in 3b4c21804076e461a6453ee4d09872172336aa1d (fixed)

Vendor states this is fixed in 716efd08985e3104031d1b655930b1f1c45fa8a7 (fixed)

Vendor states this is fixed in 79a3908d1ea6c35157a6d907b1a9d8ec06015e7a (fixed)

Vendor states this is fixed in 7a8f9293bee51183023c5e37e7ebf0543cd2a134 (fixed)

Vendor states this is fixed in 7cca0af3167dd9603da5fa6fff3392f8338e97e1 (fixed)

Vendor states this is fixed in 9e3858f82e3ced1e990ef7116c3a16c84e62093e (fixed)

Vendor states this is fixed in ce6e0434e502abdf966164b7c72523fb5fe54635 (fixed)

Vendor states this is fixed in d97840bf5a388c6cbf6e46216887bf17be62acc2 (fixed)

Vendor states this is fixed in 2.6.32 (unaffected)

Vendor states this is fixed in 4.14.322 (unaffected)

Vendor states this is fixed in 4.19.291 (unaffected)