Software component issue could make the service unavailable
TLS 1.3 embeds the actual record type as the last non-zero byte of the decrypted payload, optionally followed by zero padding.
What happened
- 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).Security Advisory CVE-2026-101302
- 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…Advisory description (CVE-2026-101302)
Contributing factors stated by the source
- 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…
The failure pattern
Watch the pattern: Retry amplification and runaway resource consumption
Related standards
CollectSEA's mapping through this incident's failure pattern; not an official determination by the standards bodies.
Building something similar?
Describe your design and see every precedent that applies, with safeguards you can hand to your coding agent.
Incidents with the same pattern
Third-party storage outage behind Workers KV takes down many Cloudflare services (2025)
Workers KV relied on a central data store, partly backed by a third-party cloud provider; when that provider had an outage, cold reads and writes to KV failed.
Holiday traffic surge overloads a Transit Gateway and stalls autoscaling provisioning (Slack, 2021)
After the holidays, an unusual surge of traffic from clients with cold caches overloaded one of Slack's AWS Transit Gateways.
Design reference: AWS guidance on timeouts, retries and backoff with jitter
AWS describes retries as powerful but dangerous: when a dependency is struggling, too many retries can amplify load and turn a partial failure into a retry storm.
Software component issue could make the service unavailable
A public security advisory describes this issue. Review the linked source for the technical details and remediation guidance.
Software component issue could make the service unavailable
A public security advisory describes this issue. Review the linked source for the technical details and remediation guidance.
Software component issue could make the service unavailable
pupnp is an SDK for development of UPnP device and control point applications. Prior to 2.0.2, rawtoint in upnp/src/genlib/net/http/httpparser.c parses Content-Length with strtol and casts the resulting long to a 32-bit…