# Linux Kernel Virtualization Boundary Disclosure Record

Date: 2026-06-15

Status: sanitized public disclosure record in the responsible-disclosure lane.

## Summary

This is the public accountability record for a Linux kernel disclosure thread
that passed the 14-day no-response review date under our responsible-disclosure
rules.

Technical details are withheld here. This record exists so the disclosure
timeline is visible without publishing a reproduction recipe, private
correspondence, or raw technical material.

## What Was Reported Privately

- Reported area: Linux UML vector transport.
- Reported class: incomplete initialization around GRE header handling with an
  out-of-bounds write concern.
- Public status: no maintainer acknowledgement or routing response is visible in
  the receipt source used for this lane.

The private report is about a specific UML networking path and a specific
write-boundary concern. This public record does not include the triggering
input shape, command line, file names, offsets, logs, or reproduction packet.

## Public Evidence

This record is backed by a metadata-only sent-email receipt and the canonical
cyber ledger. The email body and technical packet are not published here.

- Receipt ID: `gmail-sent-linux-uml-gre-oob-write-20260527`.
- Canonical ledger row: `LINUX-KERNEL-UML-GRE-INCOMPLETE-INIT-20260527`.
- Sent date recorded in Gmail metadata: 2026-05-27.
- Sent subject recorded in metadata: `[PRIVATE REPORT] UML vector transport:
  incomplete init can drive GRE header OOB write`.
- Recipient label hash:
  `d82d74e586500f5e5b2e3cb386889168c9f208ce73ec2450c41bc93ce1a24dee`.
- Subject hash:
  `8d464ed97129b43901981f3e48ae8f6aff7f3e98228fb5287ffe9b61fb21485a`.
- Visible thread-reply signal: no visible inbox label on the sent thread in the
  Gmail metadata seed.
- Gmail metadata source SHA-256:
  `059c2676fb828ec3388033369db2b8cdffda19b58604df90006ba722601013d4`.
- Sent-list image SHA-256:
  `01a1a3f2ac0862bf2677a2346252c7731de9c1d5f9af8dbc643b42c839d6bfbb`.
- Cyber ledger SHA-256 at publication time:
  `eef59c2a0433ff46aeb4ce163525284509319999055345b9ca1ed46ffa719675`.

## Evidence Boundary

The public evidence proves a disclosure record exists, identifies the reported
component and issue class, and records the no-response timing basis. It does not
publish the private email body, command line, input shape, offsets, raw logs, or
technical packet.

## Timeline

- First disclosure email sent: 2026-05-27.
- 14-day no-response review date: 2026-06-10.
- Published as a sanitized public disclosure record: 2026-06-15.

## What We Are Asking For

- Acknowledge receipt or point to the correct Linux security handling route.
- State whether this is already known, fixed, duplicate, out of scope, or needs
  the private packet resent.
- If more time is needed, say so and the public record can note that engagement
  has started.

## Rules Applied

- The first disclosure email starts the review clock.
- If there is no acknowledgement or reply after 14 days, a sanitized public
  record may be published after review.
- More detailed technical disclosure still requires separate human review.
- Private technical material remains reserved for an authorized security
  responder.

## Limits

This public record establishes the disclosure timeline. Untrusted control is not
proven in this public record. Current-version behavior is not proven in this
public record. Maintainer validation, remediation status, final severity, and
affected-version scope are not proven in this public record. Private technical
material is retained for authorized responders.