CVE-2026-72018 dibs: loopback: validate offset and size in move_data()
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.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-72018?
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.
Official description
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.
Weakness: CWE-787
Which versions are affected by CVE-2026-72018?
How do I fix CVE-2026-72018?
Apply the vendor's patch.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is CVE-2026-72018 being exploited?
There is no known exploitation of CVE-2026-72018 in the wild and no public exploit code.
Public exploit code: 1 proofs of concept on GitHub.
Sources
Also known as BELL-CVE-2026-72018, DEBIAN-CVE-2026-72018, GHSA-96mx-hwj9-j649, UBUNTU-CVE-2026-72018.