Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
Medium

Heap out-of-bounds write in OpenSSL BIO_f_linebuffer on short writes

IdentifiersCVE-2025-68160CWE-122

CVE-2025-68160 is a low-severity memory corruption vulnerability in OpenSSL's line-buffering BIO filter, BIO_f_linebuffer. When large newline-free data is written into a BIO chain using BIO_f_linebuffer and the next BIO in the chain performs short writes, OpenSSL can trigger a heap-based out-of-bounds write. The flaw affects OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1, and 1.0.2. The issue is outside the OpenSSL FIPS module boundary, so the FIPS modules for 3.6, 3.5, 3.4, 3.3, and 3.0 are not affected. The vulnerable condition is not part of the default TLS/SSL data path; the BIO_f_linebuffer filter is typically only used when applications explicitly add it to a BIO chain, and in OpenSSL command-line applications it is generally only pushed onto stdout/stderr on VMS systems.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful triggering causes a heap out-of-bounds write and resulting memory corruption. Based on the provided advisory text, the typical outcome is application crash and denial of service. Although memory corruption primitives can sometimes have broader consequences, the supplied material characterizes the practical impact here as usually a crash/DoS and assesses the issue as Low severity because attacker control over the required conditions is considered unlikely.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, avoid using BIO_f_linebuffer in BIO chains where the downstream BIO can short-write. Do not pass large, newline-free, attacker-influenced data through BIO_f_linebuffer. Prefer removing the line-buffering filter from such paths or ensuring only curated/validated output is processed through it. Because the filter is not used by default in normal TLS/SSL data paths, reducing or eliminating explicit application use of BIO_f_linebuffer materially lowers exposure.

Remediation

Patch, then assume compromise.

Upgrade to a fixed OpenSSL release. The provided content indicates fixes were released on 2026-01-27 in OpenSSL 3.6.1, 3.5.5, 3.4.4, 3.3.6, 3.0.19, 1.1.1ze, and 1.0.2zn. Downstream vendors may also have shipped remediated packages incorporating these fixes. For affected products embedding OpenSSL, apply the vendor-provided update that includes the corrected OpenSSL version or backported patch.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
FreebsdFreebsdapplication
OpenSSL Software FoundationOpensslapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity17

Community discussion across Reddit, Mastodon, and other social sources.