Finding and attribution
The SMC-D loopback path failed to bounds-check a peer-controlled memory offset before copying data, creating an out-of-bounds write. XBOW says its system handled threat modeling, code auditing, discovery and validation, with humans steering several research decisions and exploit development.
Product: Linux kernel SMC-D DIBS loopback transport. AI system: XBOW autonomous vulnerability research agents; model not publicly identified. Team / organization: XBOW and Linux kernel maintainers.
CVE identifiers: CVE-2026-72018.
AI and human contribution (source account): XBOW’s first-party case report says it discovered and validated this CVE and autonomously handled threat modeling, code auditing, vulnerability discovery and validation. It explicitly describes three human interventions steering the threat model and exploit strategy, so this is AI-assisted discovery, not autonomous end-to-end work.
Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.
Discovery context: XBOW reports it disclosed the issue to maintainers before CVE publication; no in-the-wild exploitation is stated.
Remediation status: fix documented. XBOW’s advisory lists Linux stable fixes; the kernel CVE notice is linked as vendor advisory. Check distribution-specific patch status before assuming a system is fixed.
A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.
Disclosed 17 Aug 2026. AI attribution dated 28 Sep 2026. Sources checked 14 Nov 2026; these are separate dates, not a live installation check.
Recorded CVSS: High · highest recorded score 7.8. Documented technical effects: other.
Severity, consequences and exploitation evidence
Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.
- CVE-2026-72018: CVSS 3.1 · 7.8 (High) ·
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H· Assessment scenarios: 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. AC: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. PR: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. UI: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. S: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. C: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. I: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. A: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.. Linux (CNA; CVE Program record) · checked 16 Nov 2026.
CVE-2026-72018: other.
Prerequisites / affected scope: A peer-supplied out-of-bounds offset/size causes an out-of-bounds write past the allocated kernel buffer in the software SMC-D loopback path. No further consequence is stated..
Exploitation evidence: Exploitation in the wild is not established by the cited description.. Impact source · checked 16 Nov 2026.
Documented fix: XBOW’s advisory lists Linux stable fixes; the kernel CVE notice is linked as vendor advisory. Check distribution-specific patch status before assuming a system is fixed.