{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2023-54208 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2023-54208 is a memory corruption vulnerability in Linux, published on 30 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-54208 and fix it if it is affected.\n\nWhat it is: CVE-2023-54208 is a memory corruption vulnerability in Linux, published on 30 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-54208 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2023-54208/ (Markdown: https://insights.sbomify.com/CVE-2023-54208/index.md)","id":"CVE-2023-54208","markdown":"https://insights.sbomify.com/CVE-2023-54208/index.md","name":"CVE-2023-54208","record":{"aliases":["BELL-CVE-2023-54208","DEBIAN-CVE-2023-54208","GHSA-m6xf-27x7-x98g","UBUNTU-CVE-2023-54208"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"none","summary":"A memory leak in the Linux kernel ov5675 camera driver allows local attackers to cause resource exhaustion and denial of service.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nmedia: ov5675: Fix memleak in ov5675_init_controls()\n\nThere is a kmemleak when testing the media/i2c/ov5675.c with bpf mock\ndevice:\n\nAssertionError: unreferenced object 0xffff888107362160 (size 16):\n  comm \"python3\", pid 277, jiffies 4294832798 (age 20.722s)\n  hex dump (first 16 bytes):\n    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\n  backtrace:\n    [\u003c00000000abe7d67c\u003e] __kmalloc_node+0x44/0x1b0\n    [\u003c000000008a725aac\u003e] kvmalloc_node+0x34/0x180\n    [\u003c000000009a53cd11\u003e] v4l2_ctrl_handler_init_class+0x11d/0x180\n[videodev]\n    [\u003c0000000055b46db0\u003e] ov5675_probe+0x38b/0x897 [ov5675]\n    [\u003c00000000153d886c\u003e] i2c_device_probe+0x28d/0x680\n    [\u003c000000004afb7e8f\u003e] really_probe+0x17c/0x3f0\n    [\u003c00000000ff2f18e4\u003e] __driver_probe_device+0xe3/0x170\n    [\u003c000000000a001029\u003e] driver_probe_device+0x49/0x120\n    [\u003c00000000e39743c7\u003e] __device_attach_driver+0xf7/0x150\n    [\u003c00000000d32fd070\u003e] bus_for_each_drv+0x114/0x180\n    [\u003c000000009083ac41\u003e] __device_attach+0x1e5/0x2d0\n    [\u003c0000000015b4a830\u003e] bus_probe_device+0x126/0x140\n    [\u003c000000007813deaf\u003e] device_add+0x810/0x1130\n    [\u003c000000007becb867\u003e] i2c_new_client_device+0x386/0x540\n    [\u003c000000007f9cf4b4\u003e] of_i2c_register_device+0xf1/0x110\n    [\u003c00000000ebfdd032\u003e] of_i2c_notify+0xfc/0x1f0\n\nov5675_init_controls() won't clean all the allocated resources in fail\npath, which may causes the memleaks. Add v4l2_ctrl_handler_free() to\nprevent memleak.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"media: ov5675: Fix memleak in ov5675_init_controls()","id":"CVE-2023-54208","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2023"},"n_packages":0,"n_references":6,"next":{"headline":"block: fix blktrace debugfs entries leakage","id":"CVE-2023-54209"},"packages":[],"prev":{"headline":"HID: uclogic: Correct devm device reference for hidinput input_dev name","id":"CVE-2023-54207"},"products":["Linux"],"published":"2025-12-30","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-05-11","vendors":["Linux"]},"summary":"A memory leak in the Linux kernel ov5675 camera driver allows local attackers to cause resource exhaustion and denial of service.","url":"https://insights.sbomify.com/CVE-2023-54208/"}