From: patchwork-bot+bluetooth@kernel.org
To: Oliver Chang <ochang@google.com>
Cc: linux-bluetooth@vger.kernel.org, oss-fuzz-bugs@google.com
Subject: Re: [PATCH BlueZ v2 0/1] Fix heap-buffer-overflow in sdp_xml.c:compute_seq_size
Date: Tue, 19 Aug 2025 14:30:09 +0000 [thread overview]
Message-ID: <175561380923.3572360.4132650504542772239.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250813103459.3690107-1-ochang@google.com>
Hello:
This patch was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Wed, 13 Aug 2025 10:34:58 +0000 you wrote:
> This is a follow up to my first patch attempt. After scrutinizing this a
> bit more, it turns out my previous patch wasn't actually addresing the
> root cause.
>
> The ASan stacktrace (found by OSS-Fuzz) for this issue is:
>
> ```
> ==399==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x502000000218 at pc 0x5cffda946877 bp 0x7ffe90702810 sp 0x7ffe90702808
> READ of size 4 at 0x502000000218 thread T0
> #0 0x5cffda946876 in compute_seq_size bluez/src/sdp-xml.c:62:21
> #1 0x5cffda946876 in element_end bluez/src/sdp-xml.c:548:42
> #2 0x5cffda984416 in emit_end_element glib/glib/gmarkup.c:1045:5
> #3 0x5cffda983978 in g_markup_parse_context_parse glib/glib/gmarkup.c:1603:19
> #4 0x5cffda944c55 in sdp_xml_parse_record bluez/src/sdp-xml.c:621:6
> #5 0x5cffda949cf1 in LLVMFuzzerTestOneInput /src/fuzz_xml.c:30:9
> #6 0x5cffda7f9730 in fuzzer::Fuzzer::ExecuteCallback(unsigned char const*, unsigned long) /src/llvm-project/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:614:13
> #7 0x5cffda7e49a5 in fuzzer::RunOneTest(fuzzer::Fuzzer*, char const*, unsigned long) /src/llvm-project/compiler-rt/lib/fuzzer/FuzzerDriver.cpp:327:6
> #8 0x5cffda7ea43f in fuzzer::FuzzerDriver(int*, char***, int (*)(unsigned char const*, unsigned long)) /src/llvm-project/compiler-rt/lib/fuzzer/FuzzerDriver.cpp:862:9
> #9 0x5cffda8156e2 in main /src/llvm-project/compiler-rt/lib/fuzzer/FuzzerMain.cpp:20:10
> #10 0x7e0ccb446082 in __libc_start_main /build/glibc-LcI20x/glibc-2.31/csu/libc-start.c:308:16
> #11 0x5cffda7dcb8d in _start
> ```
>
> [...]
Here is the summary with links:
- [BlueZ,v2,1/1] Fix heap-buffer-overflow in sdp_xml.c:compute_seq_size
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=00eea35722b7
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-08-19 14:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-13 10:34 [PATCH BlueZ v2 0/1] Fix heap-buffer-overflow in sdp_xml.c:compute_seq_size Oliver Chang
2025-08-13 10:34 ` [PATCH BlueZ v2 1/1] " Oliver Chang
2025-08-13 10:49 ` Oliver Chang
2025-08-13 11:56 ` bluez.test.bot
2025-08-19 9:59 ` Oliver Chang
2025-08-19 14:30 ` patchwork-bot+bluetooth [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=175561380923.3572360.4132650504542772239.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=ochang@google.com \
--cc=oss-fuzz-bugs@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox