A Signed Length Overflow in Erlang/OTP's inet TCP Driver Overflows the Receive Buffer Into BEAM VM Memory From an Unauthenticated Peer (CVE-2026-75538) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-75538

A Signed Length Overflow in Erlang/OTP's inet TCP Driver Overflows the Receive Buffer Into BEAM VM Memory From an Unauthenticated Peer

Answer in brief

CVE-2026-75538 records a Unknown severity vulnerability in A Signed Length Overflow in Erlang/OTP's inet TCP Driver Overflows the Receive Buffer Into BEAM VM Memory From an Unauthenticated Peer. The current sources do not mark it as known exploited. The current feed maps Erlang/OTP (generic), Erlang/OTP (generic), Erlang/OTP (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 Sep 1, 2026Updated Sep 1, 2026Source checked Sep 1, 2026First seen by HOL Sep 1, 2026Material review Sep 1, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 3 mapped packages or products
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 Erlang/OTP (generic), Erlang/OTP (generic), Erlang/OTP (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Erlang/OTPgeneric	>=17.0 <27.3.4.17 \|\| >=28.0 <28.5.0.6 \|\| >=29.0 <29.0.6	27.3.4.17, 28.5.0.6, 29.0.6
Erlang/OTPgeneric	>=6.0 <15.2.7.13 \|\| >=16.0 <16.4.0.6 \|\| >=17.0 <17.0.6	15.2.7.13, 16.4.0.6, 17.0.6
Erlang/OTPgeneric	>=84adefa331c4159d432d22840663c38f155cd4c1 <08e8efdba8500d2d6f54c6b1de1492b228017c9b	08e8efdba8500d2d6f54c6b1de1492b228017c9b

Recommended response

Check inventory. Check lockfiles and deployed manifests for Erlang/OTP, Erlang/OTP, Erlang/OTP.
Review the reported fix. Update Erlang/OTP to 27.3.4.17; Erlang/OTP to 15.2.7.13; Erlang/OTP to 08e8efdba8500d2d6f54c6b1de1492b228017c9b if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

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

Sources and claim methodology

Upstream source description

An attacker that connects to an open Erlang TCP port that uses the inet driver with {packet,4} mode can use a signed overflow in an incorrect packet length calculation to overflow the receive buffer into the VM allocator area and beyond up to about 2 GB. This would easily trash the allocated block's allocator metadata footer, and the next block, if any, and most likely cause the BEAM VM to crash. Utilizing this with precision enough to achieve Remote Code Execution would be extremely unfeasible. This issue affects OTP from OTP 17.0 before OTP 27.3.4.17, from OTP 28.0 before OTP 28.5.0.6, and from OTP 29.0 before OTP 29.0.6, corresponding to erts from 6.0 before 15.2.7.13, from 16.0 before 16.4.0.6, and from 17.0 before 17.0.6. Whether OTP before OTP 17.0, corresponding to erts before 6.0, is affected is unknown.

Quoted source text, attributed separately from HOL analysis.