{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2023-54091 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2023-54091 is a memory corruption vulnerability in Linux, published on 24 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-54091 and fix it if it is affected.\n\nWhat it is: CVE-2023-54091 is a memory corruption vulnerability in Linux, published on 24 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-54091 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-54091/ (Markdown: https://insights.sbomify.com/CVE-2023-54091/index.md)","id":"CVE-2023-54091","markdown":"https://insights.sbomify.com/CVE-2023-54091/index.md","name":"CVE-2023-54091","record":{"aliases":["BELL-CVE-2023-54091","DEBIAN-CVE-2023-54091","GHSA-h228-354g-ppq4","UBUNTU-CVE-2023-54091"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel DRM","requires_auth":"none","summary":"A memory leak in the Linux kernel DRM client allows local attackers to exhaust system memory, potentially causing a 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\ndrm/client: Fix memory leak in drm_client_target_cloned\n\ndmt_mode is allocated and never freed in this function.\nIt was found with the ast driver, but most drivers using generic fbdev\nsetup are probably affected.\n\nThis fixes the following kmemleak report:\n  backtrace:\n    [\u003c00000000b391296d\u003e] drm_mode_duplicate+0x45/0x220 [drm]\n    [\u003c00000000e45bb5b3\u003e] drm_client_target_cloned.constprop.0+0x27b/0x480 [drm]\n    [\u003c00000000ed2d3a37\u003e] drm_client_modeset_probe+0x6bd/0xf50 [drm]\n    [\u003c0000000010e5cc9d\u003e] __drm_fb_helper_initial_config_and_unlock+0xb4/0x2c0 [drm_kms_helper]\n    [\u003c00000000909f82ca\u003e] drm_fbdev_client_hotplug+0x2bc/0x4d0 [drm_kms_helper]\n    [\u003c00000000063a69aa\u003e] drm_client_register+0x169/0x240 [drm]\n    [\u003c00000000a8c61525\u003e] ast_pci_probe+0x142/0x190 [ast]\n    [\u003c00000000987f19bb\u003e] local_pci_probe+0xdc/0x180\n    [\u003c000000004fca231b\u003e] work_for_cpu_fn+0x4e/0xa0\n    [\u003c0000000000b85301\u003e] process_one_work+0x8b7/0x1540\n    [\u003c000000003375b17c\u003e] worker_thread+0x70a/0xed0\n    [\u003c00000000b0d43cd9\u003e] kthread+0x29f/0x340\n    [\u003c000000008d770833\u003e] ret_from_fork+0x1f/0x30\nunreferenced object 0xff11000333089a00 (size 128):","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":"drm/client: Fix memory leak in drm_client_target_cloned","id":"CVE-2023-54091","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2023"},"n_packages":0,"n_references":8,"next":{"headline":"KVM: s390: pv: fix index value of replaced ASCE","id":"CVE-2023-54092"},"packages":[],"prev":{"headline":"ixgbe: Fix panic during XDP_TX with \u003e 64 CPUs","id":"CVE-2023-54090"},"products":["Linux"],"published":"2025-12-24","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 DRM client allows local attackers to exhaust system memory, potentially causing a denial of service.","url":"https://insights.sbomify.com/CVE-2023-54091/"}