{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2023-53700 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2023-53700 is a memory corruption vulnerability in Linux, published on 22 Oct 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-53700 and fix it if it is affected.\n\nWhat it is: CVE-2023-53700 is a memory corruption vulnerability in Linux, published on 22 Oct 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-53700 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-53700/ (Markdown: https://insights.sbomify.com/CVE-2023-53700/index.md)","id":"CVE-2023-53700","markdown":"https://insights.sbomify.com/CVE-2023-53700/index.md","name":"CVE-2023-53700","record":{"aliases":["BELL-CVE-2023-53700","DEBIAN-CVE-2023-53700","GHSA-9vc2-g7hx-x44h","UBUNTU-CVE-2023-53700"],"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 max9286 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: max9286: Fix memleak in max9286_v4l2_register()\n\nThere is a kmemleak when testing the media/i2c/max9286.c with bpf mock\ndevice:\n\nkmemleak: 5 new suspected memory leaks (see /sys/kernel/debug/kmemleak)\n\nunreferenced object 0xffff88810defc400 (size 256):\n  comm \"python3\", pid 278, jiffies 4294737563 (age 31.978s)\n  hex dump (first 32 bytes):\n    28 06 a7 0a 81 88 ff ff 00 fe 22 12 81 88 ff ff  (.........\".....\n    10 c4 ef 0d 81 88 ff ff 10 c4 ef 0d 81 88 ff ff  ................\n  backtrace:\n    [\u003c00000000191de6a7\u003e] __kmalloc_node+0x44/0x1b0\n    [\u003c000000002f4912b7\u003e] kvmalloc_node+0x34/0x180\n    [\u003c0000000057dc4cae\u003e] v4l2_ctrl_new+0x325/0x10f0 [videodev]\n    [\u003c0000000026030272\u003e] v4l2_ctrl_new_std+0x16f/0x210 [videodev]\n    [\u003c00000000f0d9ea2f\u003e] max9286_probe+0x76e/0xbff [max9286]\n    [\u003c00000000ea8f6455\u003e] i2c_device_probe+0x28d/0x680\n    [\u003c0000000087529af3\u003e] really_probe+0x17c/0x3f0\n    [\u003c00000000b08be526\u003e] __driver_probe_device+0xe3/0x170\n    [\u003c000000004382edea\u003e] driver_probe_device+0x49/0x120\n    [\u003c000000007bde528a\u003e] __device_attach_driver+0xf7/0x150\n    [\u003c000000009f9c6ab4\u003e] bus_for_each_drv+0x114/0x180\n    [\u003c00000000c8aaf588\u003e] __device_attach+0x1e5/0x2d0\n    [\u003c0000000041cc06b9\u003e] bus_probe_device+0x126/0x140\n    [\u003c000000002309860d\u003e] device_add+0x810/0x1130\n    [\u003c000000002827bf98\u003e] i2c_new_client_device+0x359/0x4f0\n    [\u003c00000000593bdc85\u003e] of_i2c_register_device+0xf1/0x110\n\nmax9286_v4l2_register() calls v4l2_ctrl_new_std(), but won't free the\ncreated v412_ctrl when fwnode_graph_get_endpoint_by_id() failed, which\ncauses the memleak. Call v4l2_ctrl_handler_free() to free the v412_ctrl.","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: max9286: Fix memleak in max9286_v4l2_register()","id":"CVE-2023-53700","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2023"},"n_packages":0,"n_references":5,"next":{"headline":"This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.","id":"CVE-2023-53701"},"packages":[],"prev":{"headline":"riscv: move memblock_allow_resize() after linear mapping is ready","id":"CVE-2023-53699"},"products":["Linux"],"published":"2025-10-22","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 max9286 driver allows local attackers to cause resource exhaustion and denial of service.","url":"https://insights.sbomify.com/CVE-2023-53700/"}