Use-after-free in INSTRUX array members in pybddisasm

Özet

Türkçe özeti yalnızca kritik ve yüksek önemdeki açıklar için hazırlıyoruz. Bu açık için kaynağın kendi açıklamasını gösteriyoruz.

A use-after-free vulnerability in the pybddisasm Python bindings affects array-valued members of INSTRUX objects, including ND_OPERAND arrays. These arrays are exposed as Python lists whose elements reference memory owned by the parent INSTRUX object. Retaining a list or an element does not keep the parent allocation alive. Accessing an element after the parent INSTRUX object has been freed therefore accesses freed memory. Depending on how the element is used and whether the freed allocation has been reused, this may expose process memory or cause the Python process to crash. Exploitation requires an application to retain and subsequently access an array element after the parent object has been freed. The pybddisasm package is no longer maintained.

Üreticinin çözüm notu (İngilizce)

Discontinue use of the unmaintained pybddisasm package. No fixed release has been identified for this draft.

Etkilenen sürümler1 yazılım

Kaynaklar3 kaynak

• CVE.org kaydı
• NVD kaydı
• pypi.org/project/pybddisasm Diğer

Kayıt geçmişi

1. 3 Kas 2026 12:00Yayımlandı

İlgili açıklar

• 6,9 CVE-2026-118448Uninitialized output buffer returned after nd_to_text failure in pybddisasm
• 4,8 CVE-2026-118447Uninitialized INSTRUX contents returned after decoding failure in pybddisasm
• 6,9 CVE-2026-118445Use-after-free in INSTRUX structure members in pybddisasm
• 4,8 CVE-2026-118444Out-of-bounds reads during instruction decoding in pybddisasm
• 7,5 CVE-2026-93424FastNetMon NetFlow/IPFIX şablon önbelleğinde serbest bırakılmış bellek erişimi (use-after-free)
• 9,8 CVE-2026-82418IBM Watson Speech Services Cartridge'da bellek serbest bırakma sonrası kullanım (use-after-free) açığı