Medium [CVE-2026-96421] Denial of Service via USB HID dissector infinite loop
This medium-severity Red Hat Linux advisory covers CVE-2026-96421; related products: Red Hat Enterprise Linux 10, Red Hat package: wireshark.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.
Summary
Denial of Service via USB HID dissector infinite loop. Red Hat rates this moderate (CVSS 5.5).
Weakness: CWE-835.
Affected products named by the advisory: Red Hat Enterprise Linux 10; Red Hat package: wireshark.
Affected versions
No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.
Official advisory · high-confidence parse· fetched 2 days ago·verify at source
Fixed versions
No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.
Official advisory · high-confidence parse· fetched 2 days ago·verify at source
Mitigation checklist
- Disable the USB HID protocol dissector when USB HID traffic inspection is not required, or avoid processing capture files from untrusted sources. To disable the protocol dissector in TShark: ``` tshark --disable-protocol usbhid -r capture.pcap ``` To disable the dissector persistently in Wireshark: 1. Open the GUI and select Analyze -> Enabled Protocols. 2. Locate "USB HID" (filter name usbhid) and deselect it. Alternatively, append `usbhid` to the disabled protocols file located at `~/.config/wireshark/disabled_protos`. Caveat: Disabling the USB HID dissector prevents packet decoders from parsing USB HID payload structures, displaying affected packets only as raw USB data.
Official advisory · high-confidence parse· fetched 2 days ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.