Answer in brief
CVE-2026-72018 records a High severity (CVSS 7.8) vulnerability in dibs: loopback: validate offset and size in move_data(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=f7a22071dbf316c982fb44308874bd7ad9ac2091 <ee188a6b264b71315a67f1b9470faad308b730d2 || >=f7a22071dbf316c982fb44308874bd7ad9ac2091 <b2f426a9a22886071966432ede8fceafffe12b8c || >=f7a22071dbf316c982fb44308874bd7ad9ac2091 <94fe0ab01b480b52bd8f977edbd845ef375d69fd || >=f7a22071dbf316c982fb44308874bd7ad9ac2091 <78237e3c0720fcc6eb9b87e90fd70f63eeca886f | ee188a6b264b71315a67f1b9470faad308b730d2, b2f426a9a22886071966432ede8fceafffe12b8c, 94fe0ab01b480b52bd8f977edbd845ef375d69fd, 78237e3c0720fcc6eb9b87e90fd70f63eeca886f |
| Linux/Linuxgeneric | 6.10 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.