Linux
dibs: loopback: validate offset and size in move_data()
In the Linux kernel, the following vulnerability has been resolved: dibs: loopback: validate offset and size in move_data() The loopback move_data() performs a memcpy into the registered DMB without checking whether offset + size exceeds the DMB length. Unlike real ISM hardware, which enforces memory region bounds natively, the software loopback has no such protection. A peer-supplied out-of-bounds offset or oversized write would result in an OOB write past the allocated kernel buffer. Add an explicit bounds check before the memcpy to reject such requests with -EINVAL.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= f7a22071dbf316c982fb44308874bd7ad9ac2091, < ee188a6b264b71315a67f1b9470faad308b730d2
- >= f7a22071dbf316c982fb44308874bd7ad9ac2091, < b2f426a9a22886071966432ede8fceafffe12b8c
- >= f7a22071dbf316c982fb44308874bd7ad9ac2091, < 94fe0ab01b480b52bd8f977edbd845ef375d69fd
- >= f7a22071dbf316c982fb44308874bd7ad9ac2091, < 78237e3c0720fcc6eb9b87e90fd70f63eeca886f
Fixed in ee188a6b264b71315a67f1b9470faad308b730d2, b2f426a9a22886071966432ede8fceafffe12b8c, 94fe0ab01b480b52bd8f977edbd845ef375d69fd, 78237e3c0720fcc6eb9b87e90fd70f63eeca886f
- 6.10
Fixed in 0, 6.12.97, 6.18.40, 7.1.5, 7.2
Mitigation
Upgrade Linux to ee188a6b264b71315a67f1b9470faad308b730d2 or b2f426a9a22886071966432ede8fceafffe12b8c or 94fe0ab01b480b52bd8f977edbd845ef375d69fd or 78237e3c0720fcc6eb9b87e90fd70f63eeca886f or later.
Upgrade Linux to 0 or 6.12.97 or 6.18.40 or 7.1.5 or 7.2 or later.
Timeline
Days relative to CVE publicationFirst public PoC 46 days after publication; not in CISA KEV. First PoC: 0xBlackash/CVE-2026-72018 (created 30 Sep 2026, found by us: backfilled).
PoC repositories
Found on GitHub.3 PoCs
PoCs 3
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| 0xBlackash/CVE-2026-72018 | 30 Sep 2026 +46 d | 0 | PoC via PoC Index |
| 0xredash/CVE-2026-72018 | 30 Sep 2026 +46 d | 0 | PoC via PoC Index |
| ashrafzaryouh/CVE-2026-72018 | 30 Sep 2026 +46 d | 0 | PoC via PoC Index |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.