{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-72101 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-72101 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-72101 and fix it if it is affected.\n\nWhat it is: CVE-2026-72101 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-72101 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-72101/ (Markdown: https://insights.sbomify.com/CVE-2026-72101/index.md)","id":"CVE-2026-72101","markdown":"https://insights.sbomify.com/CVE-2026-72101/index.md","name":"CVE-2026-72101","record":{"aliases":["BELL-CVE-2026-72101","DEBIAN-CVE-2026-72101","GHSA-hxqh-5f52-gjp9","UBUNTU-CVE-2026-72101"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"A bug in the Linux kernel dm-integrity module fails to zero memory, allowing local attackers to read uninitialized kernel memory.","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\ndm-integrity: fix leaking uninitialized kernel memory\n\nIf hash size is less than device's tuple size, dm-integrity is supposed\nto zero the remaining space. There was a bug in the code that zeroing\ndidn't work. This commit fixes it.","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":"dm-integrity: fix leaking uninitialized kernel memory","id":"CVE-2026-72101","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"dm_early_create: fix freeing used table on dm_resume failure","id":"CVE-2026-72102"},"packages":[],"prev":{"headline":"dm-integrity: fix a bug if the bio is out of limits","id":"CVE-2026-72100"},"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 bug in the Linux kernel dm-integrity module fails to zero memory, allowing local attackers to read uninitialized kernel memory.","url":"https://insights.sbomify.com/CVE-2026-72101/"}