{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-72269 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-72269 is a memory corruption vulnerability in Linux, published on 15 Aug 2026. 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-2026-72269 and fix it if it is affected.\n\nWhat it is: CVE-2026-72269 is a memory corruption vulnerability in Linux, published on 15 Aug 2026. 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-2026-72269 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-2026-72269/ (Markdown: https://insights.sbomify.com/CVE-2026-72269/index.md)","id":"CVE-2026-72269","markdown":"https://insights.sbomify.com/CVE-2026-72269/index.md","name":"CVE-2026-72269","record":{"aliases":["BELL-CVE-2026-72269","DEBIAN-CVE-2026-72269","GHSA-w6jh-456j-h9m3","UBUNTU-CVE-2026-72269"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"A memory leak in the Linux kernel's uvesafb driver can lead to 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\nfbdev: uvesafb: fix potential memory leak in uvesafb_probe()\n\nDue to an incorrect goto label, memory allocated for modedb and modelist\nin uvesafb_vbe_init() is not freed in some error paths. Fix this by\nupdating the goto label.","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":"fbdev: uvesafb: fix potential memory leak in uvesafb_probe()","id":"CVE-2026-72269","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"fbdev: s3fb: fix potential memory leak in s3_pci_probe()","id":"CVE-2026-72270"},"packages":[],"prev":{"headline":"fbdev: tdfxfb: fix potential memory leak in tdfxfb_probe()","id":"CVE-2026-72268"},"products":["Linux"],"published":"2026-08-15","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-08-17","vendors":["Linux"]},"summary":"A memory leak in the Linux kernel's uvesafb driver can lead to resource exhaustion and denial of service.","url":"https://insights.sbomify.com/CVE-2026-72269/"}