Fuzz job issue: fuzz-2025-10-19-11765202823.pcap
Problems have been found with the following capture file:
https://www.wireshark.org/download/automated/captures/fuzz-2025-10-19-11765202823.pcap.gz
stderr:
Branch: master
Input file: /var/menagerie/menagerie/5603-obex_spp_dun.cap
CI job name: Valgrind Menagerie Fuzz, ID: 11765202823
CI job URL: https://gitlab.com/wireshark/wireshark/-/jobs/11765202823
Return value: 0
Dissector bug: 0
Valgrind error count: 1
Date and time: Sun Oct 19 08:25:59 AM UTC 2025
Commits in the last 48 hours:
653c35ddaa Netlogon: add dissection of dsraddresstositenames[ex]w
4e0a8945d8 ui: Make the text encoding tables "static".
845c005ab8 extcap: Do not try to read c:\etc\ssh\ssh_config on Windows
a3beec6d88 ORAN FH CUS: Getting ready to decompress modulation compression
7878316b92 Simplify and consolidate some "application flavor" functionality.
40b552fee6 Move the compressed file writing to libwsutil.
6e05d4e7b4 headers: Stop shipping broken headers
6a342cea31 ORAN FH CUS: Fix a clang uninitialised warning
8ded5ea9e4 tls: Abbreviated Handshake Using New Session Ticket
d99b02bc30 test: don't check the Lrexlib version.
68e8f8df5b wsutil: Call SHGetKnownFolderPath on Windows
07f5ddf675 Qt: Fix compilation with clang-cl
f45a52cc33 Give detect_bad_proto_tree_add.py execute permission
f2a672f2a6 decode_as: Abstract "reset all" call for DCE/RPC
c76c3b7ce3 Bluetooth: Register Bluetooth UUID type
491b3cabba Add tool for detecting bad proto_tree_add_* calls and fix known instances.
49090b3a34 wsutil: Use a common struct for SI/IEC prefixes.
Build host information:
Linux 6.8.0-85-generic #85~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 19 16:18:59 UTC 2 x86_64
Distributor ID: Ubuntu
Description: Ubuntu 24.04.3 LTS
Release: 24.04
Codename: noble
Command and args: ./tools/valgrind-wireshark.sh -b /builds/wireshark/wireshark/_install/bin
==18984== Memcheck, a memory error detector
==18984== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al.
==18984== Using Valgrind-3.22.0 and LibVEX; rerun with -h for copyright info
==18984== Command: /builds/wireshark/wireshark/_install/bin/tshark -nr /tmp/fuzz/fuzz-2025-10-19-11765202823.pcap
==18984==
Running as user "root" and group "root". This could be dangerous.
==18984== Use of uninitialised value of size 8
==18984== at 0xD2BC068: wmem_map_lookup (wsutil/wmem/wmem_map.c:379)
==18984== by 0x91B74B2: uuid_type_lookup (epan/uuid_types.c:102)
==18984== by 0x757103E: bluetooth_get_custom_uuid_description (epan/dissectors/packet-bluetooth.c:264)
==18984== by 0x7571AAC: print_bluetooth_uuid (epan/dissectors/packet-bluetooth.c:693)
==18984== by 0x76619CC: dissect_protocol_descriptor_list (epan/dissectors/packet-btsdp.c:2031)
==18984== by 0x765EB9E: dissect_sdp_type (epan/dissectors/packet-btsdp.c:3344)
==18984== by 0x7663409: dissect_sdp_service_attribute (epan/dissectors/packet-btsdp.c:3838)
==18984== by 0x7663AA2: dissect_sdp_service_attribute_list (epan/dissectors/packet-btsdp.c:4001)
==18984== by 0x7657BD2: dissect_sdp_service_attribute_response (epan/dissectors/packet-btsdp.c:4347)
==18984== by 0x7656D96: dissect_btsdp (epan/dissectors/packet-btsdp.c:4564)
==18984== by 0x914054B: call_dissector_through_handle (epan/packet.c:939)
==18984== by 0x913B9AC: call_dissector_work (epan/packet.c:1030)
==18984==
==18984==
==18984== HEAP SUMMARY:
==18984== in use at exit: 69,502 bytes in 381 blocks
==18984== total heap usage: 150,812 allocs, 150,431 frees, 52,269,799 bytes allocated
==18984==
==18984== LEAK SUMMARY:
==18984== definitely lost: 0 bytes in 0 blocks
==18984== indirectly lost: 0 bytes in 0 blocks
==18984== possibly lost: 0 bytes in 0 blocks
==18984== still reachable: 52,214 bytes in 361 blocks
==18984== suppressed: 17,288 bytes in 20 blocks
==18984== Rerun with --leak-check=full to see details of leaked memory
==18984==
==18984== Use --track-origins=yes to see where uninitialised values come from
==18984== For lists of detected and suppressed errors, rerun with: -s
==18984== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)
fuzz-test.sh stderr:
Running as user "root" and group "root". This could be dangerous.no debug trace