{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-72168 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-72168 is a 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-72168 and fix it if it is affected.\n\nWhat it is: CVE-2026-72168 is a 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-72168 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-72168/ (Markdown: https://insights.sbomify.com/CVE-2026-72168/index.md)","id":"CVE-2026-72168","markdown":"https://insights.sbomify.com/CVE-2026-72168/index.md","name":"CVE-2026-72168","record":{"aliases":["BELL-CVE-2026-72168","DEBIAN-CVE-2026-72168","GHSA-24w7-qc46-mvh6","UBUNTU-CVE-2026-72168"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_read","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"A local attacker can trigger a kernel fault and potentially read uninitialized memory in the vmu-flash driver due to improper allocation.","user_interaction":"not_required","vuln_class":"information_disclosure"},"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\nmtd: maps: vmu-flash: fix fault in unaligned fixup\n\nUse kzalloc_obj() / kzalloc_objs() to allocate the memcard structs,\ninstead of kmalloc_obj() / kmalloc_objs() to prevent access to\nuninitialized data.\n\nFixes runtime error: Fault in unaligned fixup: 0000 [#1] at\nmtd_get_fact_prot_info.","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":"mtd: maps: vmu-flash: fix fault in unaligned fixup","id":"CVE-2026-72168","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"kho: make sure scratch size is always aligned by CMA_MIN_ALIGNMENT_BYTES","id":"CVE-2026-72169"},"packages":[],"prev":{"headline":"mtd: rawnand: pl353: fix probe resource allocation","id":"CVE-2026-72167"},"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-10-21","vendors":["Linux"]},"summary":"A local attacker can trigger a kernel fault and potentially read uninitialized memory in the vmu-flash driver due to improper allocation.","url":"https://insights.sbomify.com/CVE-2026-72168/"}