disclosures/linux-kernel-virtualization-boundary-disclosure-20260615.md

# 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 follow-up review 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.

## Basis For This Public Record

- A private disclosure email was sent on 2026-05-27.
- The public record maps to the cyber-ledger row
  `LINUX-KERNEL-UML-GRE-INCOMPLETE-INIT-20260527`.
- No reply or routing acknowledgement is visible in the local follow-up review
  used for this lane.
- The 14-day no-response review date passed on 2026-06-10.
- The private technical packet remains available for authorized security
  responders.

This public record identifies the reported component and issue class, records
the no-response timing basis, and states what is being asked of maintainers. 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 the report 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.