Vulnerability · Published Oct 7, 2025 · Assigned by Linux

CVE-2023-53637media: i2c: ov772x: Fix memleak in ov772x_probe()

Medium 5.5

In plain English

A medium-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 10% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS NVD)5.5Medium
Exploit odds (30 days)0.2%top 89.7% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official description

In the Linux kernel, the following vulnerability has been resolved: media: i2c: ov772x: Fix memleak in ov772x_probe() A memory leak was reported when testing ov772x with bpf mock device: AssertionError: unreferenced object 0xffff888109afa7a8 (size 8): comm "python3", pid 279, jiffies 4294805921 (age 20.681s) hex dump (first 8 bytes): 80 22 88 15 81 88 ff ff ."...... backtrace: [<000000009990b438>] __kmalloc_node+0x44/0x1b0 [<000000009e32f7d7>] kvmalloc_node+0x34/0x180 [<00000000faf48134>] v4l2_ctrl_handler_init_class+0x11d/0x180 [videodev] [<00000000da376937>] ov772x_probe+0x1c3/0x68c [ov772x] [<000000003f0d225e>] i2c_device_probe+0x28d/0x680 [<00000000e0b6db89>] really_probe+0x17c/0x3f0 [<000000001b19fcee>] __driver_probe_device+0xe3/0x170 [<0000000048370519>] driver_probe_device+0x49/0x120 [<000000005ead07a0>] __device_attach_driver+0xf7/0x150 [<0000000043f452b8>] bus_for_each_drv+0x114/0x180 [<00000000358e5596>] __device_attach+0x1e5/0x2d0 [<0000000043f83c5d>] bus_probe_device+0x126/0x140 [<00000000ee0f3046>] device_add+0x810/0x1130 [<00000000e0278184>] i2c_new_client_device+0x359/0x4f0 [<0000000070baf34f>] of_i2c_register_device+0xf1/0x110 [<00000000a9f2159d>] of_i2c_notify+0x100/0x160 unreferenced object 0xffff888119825c00 (size 256): comm "python3", pid 279, jiffies 4294805921 (age 20.681s) hex dump (first 32 bytes): 00 b4 a5 17 81 88 ff ff 00 5e 82 19 81 88 ff ff .........^...... 10 5c 82 19 81 88 ff ff 10 5c 82 19 81 88 ff ff .\.......\...... backtrace: [<000000009990b438>] __kmalloc_node+0x44/0x1b0 [<000000009e32f7d7>] kvmalloc_node+0x34/0x180 [<0000000073d88e0b>] v4l2_ctrl_new.cold+0x19b/0x86f [videodev] [<00000000b1f576fb>] v4l2_ctrl_new_std+0x16f/0x210 [videodev] [<00000000caf7ac99>] ov772x_probe+0x1fa/0x68c [ov772x] [<000000003f0d225e>] i2c_device_probe+0x28d/0x680 [<00000000e0b6db89>] really_probe+0x17c/0x3f0 [<000000001b19fcee>] __driver_probe_device+0xe3/0x170 [<0000000048370519>] driver_probe_device+0x49/0x120 [<000000005ead07a0>] __device_attach_driver+0xf7/0x150 [<0000000043f452b8>] bus_for_each_drv+0x114/0x180 [<00000000358e5596>] __device_attach+0x1e5/0x2d0 [<0000000043f83c5d>] bus_probe_device+0x126/0x140 [<00000000ee0f3046>] device_add+0x810/0x1130 [<00000000e0278184>] i2c_new_client_device+0x359/0x4f0 [<0000000070baf34f>] of_i2c_register_device+0xf1/0x110 The reason is that if priv->hdl.error is set, ov772x_probe() jumps to the error_mutex_destroy without doing v4l2_ctrl_handler_free(), and all resources allocated in v4l2_ctrl_handler_init() and v4l2_ctrl_new_std() are leaked.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linux6.1.20-1DEBIAN-CVE-2023-53637
Debian:13linux6.1.20-1DEBIAN-CVE-2023-53637
Debian:14linux6.1.20-1DEBIAN-CVE-2023-53637
Ubuntu:22.04:LTSlinux5.15.0-75.82UBUNTU-CVE-2023-53637
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2023-53637
Ubuntu:22.04:LTSlinux-aws5.15.0-1038.43UBUNTU-CVE-2023-53637
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2023-53637
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2023-53637
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2023-53637
Ubuntu:22.04:LTSlinux-azure5.15.0-1040.47UBUNTU-CVE-2023-53637
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2023-53637
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2023-53637
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2023-53637
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2023-53637
Ubuntu:22.04:LTSlinux-azure-fde5.15.0-1041.48.1UBUNTU-CVE-2023-53637
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2023-53637
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2023-53637
Ubuntu:22.04:LTSlinux-gcp5.15.0-1036.44UBUNTU-CVE-2023-53637
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2023-53637
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2023-53637
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2023-53637
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2023-53637
Ubuntu:22.04:LTSlinux-gke5.15.0-1036.41UBUNTU-CVE-2023-53637
Ubuntu:22.04:LTSlinux-gkeop5.15.0-1022.27UBUNTU-CVE-2023-53637
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2023-53637
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2023-53637
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2023-53637
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2023-53637
Ubuntu:22.04:LTSlinux-ibm5.15.0-1032.35UBUNTU-CVE-2023-53637
Ubuntu:24.04:LTSlinux-intelno fix listedUBUNTU-CVE-2023-53637
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2023-53637
Ubuntu:22.04:LTSlinux-intel-iotg5.15.0-1033.38UBUNTU-CVE-2023-53637
Ubuntu:22.04:LTSlinux-kvm5.15.0-1035.40UBUNTU-CVE-2023-53637
Ubuntu:22.04:LTSlinux-lowlatency5.15.0-75.82UBUNTU-CVE-2023-53637
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2023-53637
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2023-53637
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2023-53637
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2023-53637
Ubuntu:22.04:LTSlinux-nvidia5.15.0-1027.27UBUNTU-CVE-2023-53637
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2023-53637
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2023-53637
Ubuntu:22.04:LTSlinux-nvidia-tegra5.15.0-1015.15UBUNTU-CVE-2023-53637
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2023-53637
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2023-53637
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2023-53637
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2023-53637
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2023-53637
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2023-53637
Ubuntu:22.04:LTSlinux-oracle5.15.0-1037.43UBUNTU-CVE-2023-53637
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2023-53637
Ubuntu:22.04:LTSlinux-raspi5.15.0-1032.35UBUNTU-CVE-2023-53637
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2023-53637
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2023-53637
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2023-53637
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2023-53637
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2023-53637
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2023-53637
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2023-53637
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2023-53637
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2023-53637
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2023-53637

Affected products (as reported)

VendorProductVersions
Linux Linux 1112babde21483d86ed3fbad1320b0ddf9ab2ece – before cc3b6011d7a9f149489eb9420c6305a779162c571112babde21483d86ed3fbad1320b0ddf9ab2ece – before 448ce1cd50387b1345ec14eb191ef05f7afc2a261112babde21483d86ed3fbad1320b0ddf9ab2ece – before dfaafeb8e9537969e8dba75491f732478c7fa9d61112babde21483d86ed3fbad1320b0ddf9ab2ece – before 1da495101ef7507eb4f4b1dbec2874d740eff2511112babde21483d86ed3fbad1320b0ddf9ab2ece – before ac93f8ac66e60227bed42d5a023f0e6c15b52c0a1112babde21483d86ed3fbad1320b0ddf9ab2ece – before c86d760c1c6855a6131e78d0ddacc48c79324ac31112babde21483d86ed3fbad1320b0ddf9ab2ece – before 7485edb2b6ca5960205c0a49bedfd09bba30e521
Linux Linux 4.17

References