* [bluez/bluez] 557366: textfile: Fix possible bad memory access in find_key
@ 2024-11-01 17:39 howardchungg
0 siblings, 0 replies; only message in thread
From: howardchungg @ 2024-11-01 17:39 UTC (permalink / raw)
To: linux-bluetooth
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2024-11-01 17:39 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-11-01 17:39 [bluez/bluez] 557366: textfile: Fix possible bad memory access in find_key howardchungg
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).