{"api_version":"1","generated_at":"2026-10-01T19:08:35+00:00","cve":"CVE-2026-72018","urls":{"html":"https://cve.report/CVE-2026-72018","api":"https://cve.report/api/cve/CVE-2026-72018.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-72018","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-72018"},"summary":{"title":"dibs: loopback: validate offset and size in move_data()","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.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-08-15 06:21:00","updated_at":"2026-08-17 06:17:59"},"problem_types":[],"metrics":[{"version":"3.1","source":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","type":"Secondary","score":"7.8","severity":"HIGH","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","data":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","baseScore":7.8,"baseSeverity":"HIGH","attackVector":"LOCAL","attackComplexity":"LOW","privilegesRequired":"LOW","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"HIGH","availabilityImpact":"HIGH"}},{"version":"3.1","source":"CNA","type":"DECLARED","score":"7.8","severity":"HIGH","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","data":{"baseScore":7.8,"baseSeverity":"HIGH","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"}}],"references":[{"url":"https://git.kernel.org/stable/c/b2f426a9a22886071966432ede8fceafffe12b8c","name":"https://git.kernel.org/stable/c/b2f426a9a22886071966432ede8fceafffe12b8c","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/78237e3c0720fcc6eb9b87e90fd70f63eeca886f","name":"https://git.kernel.org/stable/c/78237e3c0720fcc6eb9b87e90fd70f63eeca886f","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/94fe0ab01b480b52bd8f977edbd845ef375d69fd","name":"https://git.kernel.org/stable/c/94fe0ab01b480b52bd8f977edbd845ef375d69fd","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/ee188a6b264b71315a67f1b9470faad308b730d2","name":"https://git.kernel.org/stable/c/ee188a6b264b71315a67f1b9470faad308b730d2","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-72018","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72018","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected f7a22071dbf316c982fb44308874bd7ad9ac2091 ee188a6b264b71315a67f1b9470faad308b730d2 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected f7a22071dbf316c982fb44308874bd7ad9ac2091 b2f426a9a22886071966432ede8fceafffe12b8c git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected f7a22071dbf316c982fb44308874bd7ad9ac2091 94fe0ab01b480b52bd8f977edbd845ef375d69fd git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected f7a22071dbf316c982fb44308874bd7ad9ac2091 78237e3c0720fcc6eb9b87e90fd70f63eeca886f git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.10","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.10 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12.97 6.12.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.40 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.1.5 7.1.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"72018","cve":"CVE-2026-72018","epss":"0.001630000","percentile":"0.060140000","score_date":"2026-08-17","updated_at":"2026-08-18 00:11:47"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["drivers/dibs/dibs_loopback.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"ee188a6b264b71315a67f1b9470faad308b730d2","status":"affected","version":"f7a22071dbf316c982fb44308874bd7ad9ac2091","versionType":"git"},{"lessThan":"b2f426a9a22886071966432ede8fceafffe12b8c","status":"affected","version":"f7a22071dbf316c982fb44308874bd7ad9ac2091","versionType":"git"},{"lessThan":"94fe0ab01b480b52bd8f977edbd845ef375d69fd","status":"affected","version":"f7a22071dbf316c982fb44308874bd7ad9ac2091","versionType":"git"},{"lessThan":"78237e3c0720fcc6eb9b87e90fd70f63eeca886f","status":"affected","version":"f7a22071dbf316c982fb44308874bd7ad9ac2091","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["drivers/dibs/dibs_loopback.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.10"},{"lessThan":"6.10","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.12.*","status":"unaffected","version":"6.12.97","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.40","versionType":"semver"},{"lessThanOrEqual":"7.1.*","status":"unaffected","version":"7.1.5","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.2","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.12.97","versionStartIncluding":"6.10","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.40","versionStartIncluding":"6.10","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.1.5","versionStartIncluding":"6.10","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2","versionStartIncluding":"6.10","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"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."}],"metrics":[{"cvssV3_1":{"baseScore":7.8,"baseSeverity":"HIGH","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"scenarios":[{"lang":"en","value":"AV:L - The flaw is only reachable via loopback-ISM (intra-OS DIBS), which requires matching local GID and shared kernel; exploitation is through AF_SMC sendmsg after SMC-D handshake, not remote packet handling on a network-facing stack path.\nAC:L - A malicious SMC-D peer can supply crafted CLC dmbe_idx/dmbe_size values and send patterns that drive move_data() with attacker-controlled offset and size; no race or uncontrollable memory layout is required once loopback-ISM is active.\nPR:L - Exploitation requires only an unprivileged local account able to open AF_SMC sockets and complete an SMC-D loopback handshake (no CAP_NET_ADMIN or root); the SMC CLC path performs no authentication beyond standard socket access controls.\nUI:N - No victim user action is needed when a malicious peer initiates an inbound SMC-D connection to a listening service; the attacker can trigger the OOB write by sending SMC-D data after handshake completion.\nS:U - The OOB write corrupts kernel heap memory within the same kernel security authority; successful exploitation yields local privilege escalation, not cross-VM, container-boundary, or IOMMU bypass scope change.\nC:H - An out-of-bounds kernel heap write past the folio-allocated DMB buffer can corrupt adjacent kernel objects and be leveraged for arbitrary kernel memory disclosure, not merely a bounded leak or pure crash.\nI:H - The unchecked memcpy() allows controlled out-of-bounds writes beyond the registered DMB allocation, enabling heap corruption and potential arbitrary kernel code execution or control-flow hijacking.\nA:H - Writing past the allocated DMB folio can immediately corrupt critical kernel structures and cause kernel oops, panic, or hang; heap corruption from the OOB write itself constitutes high availability impact."}]}],"providerMetadata":{"dateUpdated":"2026-08-17T05:39:27.125Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/ee188a6b264b71315a67f1b9470faad308b730d2"},{"url":"https://git.kernel.org/stable/c/b2f426a9a22886071966432ede8fceafffe12b8c"},{"url":"https://git.kernel.org/stable/c/94fe0ab01b480b52bd8f977edbd845ef375d69fd"},{"url":"https://git.kernel.org/stable/c/78237e3c0720fcc6eb9b87e90fd70f63eeca886f"}],"title":"dibs: loopback: validate offset and size in move_data()","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-72018","datePublished":"2026-08-15T05:51:45.360Z","dateReserved":"2026-08-09T03:40:39.900Z","dateUpdated":"2026-08-17T05:39:27.125Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-08-15 06:21:00","lastModifiedDate":"2026-08-17 06:17:59","problem_types":[],"metrics":{"cvssMetricV31":[{"source":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","type":"Secondary","cvssData":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","baseScore":7.8,"baseSeverity":"HIGH","attackVector":"LOCAL","attackComplexity":"LOW","privilegesRequired":"LOW","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"HIGH","availabilityImpact":"HIGH"},"exploitabilityScore":1.8,"impactScore":5.9}]},"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"72018","Ordinal":"1","Title":"dibs: loopback: validate offset and size in move_data()","CVE":"CVE-2026-72018","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"72018","Ordinal":"1","NoteData":"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.","Type":"Description","Title":"dibs: loopback: validate offset and size in move_data()"}]}}}