Medium

CVE-2026-101302 — Remote DoS via receive-side kernel TLS

TLS 1.3 embeds the actual record type as the last non-zero byte of the decrypted payload, optionally followed by zero padding. The code which searches for the inner record type had an off-by-one bug which could be triggered by an invalid frame, leading to an underflow followed by an unconditional NULL pointer dereference, causing a kernel panic. A remote TLS 1.3 peer can send a specially crafted record to trigger a kernel panic, resulting in a Denial of Service (DoS).

Published Oct 15, 2026 · Updated Oct 15, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: freebsd

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

Technical severity (medium)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

—

No EPSS score.

Affects

Freebsd

CVSS base

6.5

Medium · 2 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation

None

none · proof-of-concept · active

Automatable

can an attacker script the kill-chain steps

Technical impact

Partial

partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Freebsd Freebsd).
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Freebsd	Freebsd	≥ 15.1-RELEASE and < p4≥ 15.0-RELEASE and < p14≥ 14.5-RELEASE and < p1≥ 14.4-RELEASE and < p10	Vulnerable	CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Network

Attack complexity

Low

Privileges required

Low

User interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Scored by
6.5	CVSS 3.1	Medium	2.8	3.6	134c704f-9b21-4f2e-91b3-4a467353bcc0 via NIST National Vulnerability Database
6.5	CVSS 3.1	Medium	—	—	CISA-ADP via CVE Program (cve.org) e CISA ADP

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H (score shown at the top: 134c704f-9b21-4f2e-91b3-4a467353bcc0)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-193

Other CVEs with this weakness →

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).

web/proxy/WAF logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first.

2026
Source status changed · Awaiting Analysis → Undergoing Analysis
Oct 15, 2026 · NIST National Vulnerability Database
Source status changed · Received → Awaiting Analysis
Oct 15, 2026 · NIST National Vulnerability Database
SSVC assessment updated
Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
CVSS changed · 6.5
Oct 15, 2026 · NIST National Vulnerability Database
Record published
Oct 15, 2026
Affected products added · freebsd/freebsd
Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
Source status changed · → Received
Oct 15, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 15, 2026 · Alertas do Telegram
CVE published
Oct 15, 2026 · freebsd

Source activity

Repeated readings are counted rather than listed.

1× References added · Oct 15, 2026 – Oct 15, 2026
1× Official description updated · Oct 15, 2026 – Oct 15, 2026

References

1 on the record

security.freebsd.org/advisories/FreeBSD-SA-26:67.ktls.asc
vendor-advisory, NIST National Vulnerability Database

Elsewhere on this site

Freebsd
every CVE for this vendor

CWE-193
other pages naming this weakness

Related CVEs (same products)

High CVE-2026-101311 Multiple vulnerabilities in bhyve device models 11h
High CVE-2026-101310 Multiple vulnerabilities in bhyve device models 11h
High CVE-2026-101309 Multiple vulnerabilities in bhyve device models 11h
Unknown CVE-2026-58099 Memory safety bugs in kqueue copy-on-fork implementation 12h
Unknown CVE-2026-58098 Heap out-of-bounds access in semop(2) 12h
Unknown CVE-2026-58100 Memory safety bugs in kqueue copy-on-fork implementation 12h

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No FIRST EPSS score.
No fixed version, patch or mitigation documented.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-101302 is "Remote DoS via receive-side kernel TLS", rated Medium. It affects Freebsd (Freebsd); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 6.5 describes technical severity. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.