CVE-2025-68160: Heap out-of-bounds write in BIO_f_linebuffer on short writes
Issue summary: Writing large, newline-free data into a BIO chain using the
line-buffering filter where the next BIO performs short writes can trigger
a heap-based out-of-bounds write.
Impact summary: This out-of-bounds write can cause memory corruption which
typically results in a crash, leading to Denial of Service for an application.
The line-buffering BIO filter (BIO_f_linebuffer) is not used by default in
TLS/SSL data paths. In OpenSSL command-line applications, it is typically
only pushed onto stdout/stderr on VMS systems. Third-party applications that
explicitly use this filter with a BIO chain that can short-write and that
write large, newline-free data influenced by an attacker would be affected.
However, the circumstances where this could happen are unlikely to be under
attacker control, and BIO_f_linebuffer is unlikely to be handling non-curated
data controlled by an attacker. For that reason the issue was assessed as
Low severity.
The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue,
as the BIO implementation is outside the OpenSSL FIPS module boundary.
OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue.
Security readout for executives and security teams
Plain-English summary
This OpenSSL flaw can corrupt heap memory and usually crash an affected application. Exposure is narrow because the vulnerable line-buffering BIO filter is not used in normal TLS/SSL paths and requires unusual short-write conditions with large attacker-influenced data.
Executive priority
Treat this as routine patch management unless your software explicitly uses OpenSSL BIO_f_linebuffer in unusual output paths. Standard internet-facing TLS exposure alone is not enough evidence for urgency.
Technical view
BIO_f_linebuffer can perform a heap out-of-bounds write when large data without newlines passes through a BIO chain and the next BIO short-writes. Affected OpenSSL branches include 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1, and 1.0.2. The FIPS modules are not affected.
Likely exposure
Most organizations are unlikely to be exposed through standard TLS services. Risk is concentrated in applications that explicitly use BIO_f_linebuffer with short-writing downstream BIOs and process large newline-free attacker-influenced output.
Exploitation context
No active exploitation is indicated in the provided sources, and the CVE is not listed as KEV. Exploitation requires local, high-complexity conditions with low privileges and no user interaction according to the CVSS vector.
Researcher notes
The key triage question is not just OpenSSL version, but reachable use of BIO_f_linebuffer with short writes and attacker-influenced large newline-free data. Patch references exist for maintained 3.x branches; evidence for 1.1.1 and 1.0.2 fixes is incomplete here.
Mitigation direction
Upgrade affected OpenSSL 3.x branches to fixed vendor releases referenced by OpenSSL patches.
For OpenSSL 1.1.1 or 1.0.2, check vendor or support-channel guidance.
Identify applications explicitly using BIO_f_linebuffer and prioritize them for review.
Reduce attacker influence over large newline-free data written through line-buffered BIO chains.
Monitor OpenSSL and product vendor advisories for downstream package updates.
Validation and detection
Inventory OpenSSL versions across servers, containers, appliances, and embedded products.
Search application code and dependencies for explicit BIO_f_linebuffer usage.
Review whether downstream BIOs can perform short writes.
Check whether large newline-free output can be influenced by untrusted users.
Confirm deployed vendor products against relevant advisories, including Siemens where applicable.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-787: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-787 · source CWE mapping
Out-of-bounds Write
Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.