{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-72018 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-72018 is a high-severity 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-72018 and fix it if it is affected.\n\nWhat it is: CVE-2026-72018 is a high-severity 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-72018 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-72018/ (Markdown: https://insights.sbomify.com/CVE-2026-72018/index.md)","id":"CVE-2026-72018","markdown":"https://insights.sbomify.com/CVE-2026-72018/index.md","name":"CVE-2026-72018","record":{"aliases":["BELL-CVE-2026-72018","DEBIAN-CVE-2026-72018","GHSA-96mx-hwj9-j649","UBUNTU-CVE-2026-72018"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"An out-of-bounds write in the Linux kernel's dibs loopback driver allows attackers to corrupt memory, potentially leading to code execution or privilege escalation.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\ndibs: loopback: validate offset and size in move_data()\n\nThe loopback move_data() performs a memcpy into the registered DMB\nwithout checking whether offset + size exceeds the DMB length.  Unlike\nreal ISM hardware, which enforces memory region bounds natively, the\nsoftware loopback has no such protection.\n\nA peer-supplied out-of-bounds offset or oversized write would result in\nan OOB write past the allocated kernel buffer.  Add an explicit bounds\ncheck before the memcpy to reject such requests with -EINVAL.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-09-30","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-09-30T11:00:10Z","kind":"github_poc","ref":"https://github.com/0xredash/CVE-2026-72018","stars":0,"title":"CVE-2026-72018"}],"tier":"poc_unverified"},"has_fix":true,"headline":"dibs: loopback: validate offset and size in move_data()","id":"CVE-2026-72018","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"macsec: don't read an unset MAC header in macsec_encrypt()","id":"CVE-2026-72019"},"packages":[],"prev":{"headline":"net: macb: drop in-flight Tx SKBs on close","id":"CVE-2026-72017"},"products":["Linux"],"published":"2026-08-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-16","vendors":["Linux"]},"summary":"An out-of-bounds write in the Linux kernel's dibs loopback driver allows attackers to corrupt memory, potentially leading to code execution or privilege escalation.","url":"https://insights.sbomify.com/CVE-2026-72018/"}