An infinite loop in the MBIM protocol dissector causes Wireshark to consume resources until it becomes unresponsive, leading to a denial of service. The flaw is caused by an unreachable exit condition in the loop logic. The vulnerability is catalogued as CWE‑835 and can destroy service availability for any user running Wireshark with the affected MBIM dissector enabled.

The bug applies to Wireshark versions 4.6.0 through 4.6.4 and 4.4.0 through 4.4.14. Users of the Wireshark Foundation’s Wireshark product within these release ranges are at risk unless mitigated. No other vendors or product lines are listed as affected.

With a CVSS score of 5.5, the flaw represents a moderate severity risk. The EPSS score is not available, so the current likelihood of exploitation in the wild is unknown. The vulnerability is not listed in the CISA KEV catalog. Because the impact only arises when Wireshark parses network traffic containing the MBIM protocol, the likely attack vector is local: an attacker could supply or induce Wireshark to process a crafted MBIM capture, causing the loop to trigger. No conditions for remote exploitation or privilege escalation are described, so the scope is limited to the user’s environment.