Reachable assertion at ranap_handle_co_dt()

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.

Affected scope and exposure questions

The current feed maps Osmocom/osmo-bsc (generic), Osmocom/osmo-iuh (generic). Check affected ranges and fixed versions before updating.

Recommended response

1. 1Check inventory. Check lockfiles and deployed manifests for Osmocom/osmo-bsc, Osmocom/osmo-iuh.
2. 2Review the reported fix. Update Osmocom/osmo-bsc to 1.14.5; Osmocom/osmo-iuh to 1.8.0 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

1. Published upstream

   Sep 18, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

2. Source modified

   Sep 18, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

3. First seen by HOL

   Sep 18, 2026

Sources and claim methodology

• Source referencecgit.osmocom.org

Related CVEs

• Suricata ippair: hash collision can cause incorrect state reuse across IPv4 and IPv6Same generic ecosystem
• Suricata windows: unquoted LocalSystem service ImagePath can allow local privilege escalationSame generic ecosystem
• Suricata dhcp: unbounded transactions in unidirectional traffic can lead to resource exhaustionSame generic ecosystem
• Suricata datasets: NULL pointer dereference in JSON/NDJSON dataset loadingSame generic ecosystem
• Suricata swf: heap buffer overflow in SWF decompression depth handlingSame generic ecosystem
• Suricata mqtt: unbounded resource consumption from repeated pubrec and pubrel messagesSame generic ecosystem