CVE-2026-104591

Description

A flaw was found in libosmocore. A buffer overflow vulnerability exists in the osmo_iuup_compute_payload_crc() function during payload checksum calculation. A remote attacker could exploit this flaw to crash the application, resulting in a Denial of Service (DoS).

Statement

This vulnerability is rated Important because unauthenticated remote network traffic can cause an immediate denial of service across systems utilizing libosmocore for cellular protocol handling. While the defect allows unauthenticated crashes over the network without user interaction, libosmocore is not included or supported in Red Hat Enterprise Linux products. Consequently, standard enterprise deployments are not exposed to this issue.

Mitigation

--- CME Mitigation Guidance (2026-11-02) ---
Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure.

The highest-value action is to enforce payload size bounds checking prior to unpacking IuUP frames in services using libosmocore: upgrade to the fixed Libosmocore builds, which increases stack buffer size to accommodate 1500 bytes, explicitly rejects payloads exceeding this limit, and handles negative return values in iuup_verify_pdu(), closing crafted IuUP PDU with payload length exceeding buffer capacity. Until patched, this is a concern on Systems running network services utilizing libosmocore for IuUP cellular protocol processing, so restrict unauthenticated remote network reachability to services performing libosmocore IuUP protocol handling. These controls limit blast radius and contain exploitation, but they do not fix the underlying stack buffer overflow defect — apply the upstream patch to fully remediate.

Understanding the Weakness (CWE)

Integrity

Technical Impact: Modify Memory; Execute Unauthorized Code or Commands

Write operations could cause memory corruption. In some cases, an adversary can modify control data such as return addresses in order to execute unexpected code.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

Attempting to access out-of-range, invalid, or unauthorized memory could cause the product to crash.

Other

Technical Impact: Unexpected State

Subsequent write operations can produce undefined or unexpected results.

Frequently Asked Questions

Want to get errata notifications? Sign up here.