Medium [CVE-2026-96417] Denial of Service via malformed RF4CE packet
This medium-severity Red Hat Linux advisory covers CVE-2026-96417; 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 malformed RF4CE packet. Red Hat rates this moderate (CVSS 5.5).
Weakness: CWE-476.
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 RF4CE dissector in Wireshark or tshark to prevent processing of malformed packets: 1. Graphical user interface: Navigate to Analyze -> Enabled Protocols, search for "RF4CE", uncheck the checkbox, and click OK. 2. Command-line interface (tshark): Invoke tshark with the protocol disabled: ``` tshark --disable-protocol rf4ce -r <capture_file> ``` 3. Configuration file: Add the protocol identifier to the disabled protocols configuration file: ``` echo "rf4ce" >> ~/.config/wireshark/disabled_protos ``` Caveats: Disabling the RF4CE dissector prevents Wireshark from decoding RF4CE frames, displaying them only as raw payload data. Active Wireshark processes must be restarted for configuration file changes to take effect. As a general operational security practice, do not run Wireshark or tshark with elevated (root) privileges when inspecting untrusted capture files.
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.