From: howardchungg <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 557366: textfile: Fix possible bad memory access in find_key
Date: Fri, 01 Nov 2024 10:39:00 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/9e0bc3-557366@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: 5573661fc2a3e2458ef8cd29e00bea83bb67392e
https://github.com/bluez/bluez/commit/5573661fc2a3e2458ef8cd29e00bea83bb67392e
Author: Yun-Hao Chung <howardchung@google.com>
Date: 2024-11-01 (Fri, 01 Nov 2024)
Changed paths:
M src/textfile.c
Log Message:
-----------
textfile: Fix possible bad memory access in find_key
If the searched key is a prefix of the first key in the textfile,
the code will assume it's not the first line which is wrong.
The issue can be reproduced by a fuzzer. More context can be found in
https://issues.oss-fuzz.com/issues/42515619
To reproduce the issue, please kindly follow the instructions in
https://google.github.io/oss-fuzz/advanced-topics/reproducing/
Stack trace:
#0 0x55e1c450e7ce in find_key /src/bluez/src/textfile.c:133:9
#1 0x55e1c450e7ce in write_key /src/bluez/src/textfile.c:244:8
#2 0x55e1c450dc33 in LLVMFuzzerTestOneInput /src/fuzz_textfile.c:61:3
(...trace in fuzzer)
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2024-11-01 17:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bluez/bluez/push/refs/heads/master/9e0bc3-557366@github.com \
--to=noreply@github.com \
--cc=linux-bluetooth@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.