Remote DOS via uninitialized memory access in KTLS receive (CVE-2026-49423) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-49423

Remote DOS via uninitialized memory access in KTLS receive

Answer in brief

CVE-2026-49423 records a Unknown severity vulnerability in Remote DOS via uninitialized memory access in KTLS receive. The current sources do not mark it as known exploited. The current feed maps FreeBSD/FreeBSD (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 19, 2026Updated Aug 19, 2026Source checked Aug 19, 2026First seen by HOL Aug 19, 2026Material review Aug 19, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. 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.

Affected scope and exposure questions

The current feed maps FreeBSD/FreeBSD (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
FreeBSD/FreeBSDgeneric	>=15.1-RELEASE <p1 \|\| >=15.0-RELEASE <p11 \|\| >=14.4-RELEASE <p7 \|\| >=14.3-RELEASE <p16	p1, p11, p7, p16

Recommended response

Check inventory. Check lockfiles and deployed manifests for FreeBSD/FreeBSD.
Review the reported fix. Update FreeBSD/FreeBSD to p1 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Aug 19, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Aug 19, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Aug 19, 2026

Sources and claim methodology

Source referencesecurity.freebsd.org

Upstream source description

When building the iovec array for a received TLS 1.2 CBC record, ktls_ocf_tls_cbc_decrypt() incremented the iovec index for every mbuf in the chain, including mbufs that were skipped because they contained only TLS header bytes. This left uninitialized entries in the iovec array. The iovec array was allocated without zeroing. A remote TLS peer can cause the kernel to read from uninitialized iovec entries during HMAC computation, resulting in a kernel panic. The peer must be able to control TCP segmentation such that the first mbuf of a CBC record contains only the 5-byte TLS record header.

Quoted source text, attributed separately from HOL analysis.