From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, hadess@hadess.net
Subject: RE: bap: Fix stack buffer overflow in BlueZ LE Audio BASE parser
Date: Thu, 27 Aug 2026 09:17:07 -0700 (PDT) [thread overview]
Message-ID: <6a906303.28258500.8013d.3be4@mx.google.com> (raw)
In-Reply-To: <20260827145807.1568199-1-hadess@hadess.net>
[-- Attachment #1: Type: text/plain, Size: 3574 bytes --]
This is automated email and please do not reply to this email!
Dear submitter,
Thank you for submitting the patches to the linux bluetooth mailing list.
This is a CI test results with your patch series:
PW Link:https://patchwork.kernel.org/project/bluetooth/list/?series=1152690
---Test result---
Test Summary:
CheckPatch FAIL 0.49 seconds
GitLint FAIL 0.34 seconds
BuildEll PASS 20.40 seconds
BluezMake PASS 555.72 seconds
MakeCheck PASS 12.86 seconds
MakeDistcheck PASS 156.34 seconds
CheckValgrind PASS 204.05 seconds
CheckSmatch WARNING 299.86 seconds
bluezmakeextell PASS 97.06 seconds
IncrementalBuild PASS 569.54 seconds
ScanBuild PASS 898.11 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
bap: Fix stack buffer overflow in BlueZ LE Audio BASE parser
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#63:
A second identical instance exists in bap_sink_get_allocation() at line 2558.
WARNING:BAD_SIGN_OFF: Non-standard signature: Co-Authored-by:
#70:
Co-Authored-by: @thaidn and @bronson-calif of Calif.io in collaboration with
WARNING:BAD_SIGN_OFF: 'Co-authored-by:' is the preferred signature form
#70:
Co-Authored-by: @thaidn and @bronson-calif of Calif.io in collaboration with
ERROR:BAD_SIGN_OFF: Unrecognized email address: '@thaidn and @bronson-calif of Calif.io in collaboration with'
#70:
Co-Authored-by: @thaidn and @bronson-calif of Calif.io in collaboration with
ERROR:BAD_SIGN_OFF: Unrecognized email address: '@thaidn and @bronson-calif of Calif.io in collaboration with'
#72:
Reported-by: @thaidn and @bronson-calif of Calif.io in collaboration with
/github/workspace/src/patch/14771430.patch total: 2 errors, 3 warnings, 16 lines checked
NOTE: For some of the reported defects, checkpatch may be able to
mechanically convert to the typical style using --fix or --fix-inplace.
/github/workspace/src/patch/14771430.patch has style problems, please review.
NOTE: Ignored message types: COMMIT_MESSAGE COMPLEX_MACRO CONST_STRUCT FILE_PATH_CHANGES MISSING_SIGN_OFF PREFER_PACKED SPDX_LICENSE_TAG SPLIT_STRING SSCANF_TO_KSTRTO
NOTE: If any of the errors are false positives, please report
them to the maintainer, see CHECKPATCH in MAINTAINERS.
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
bap: Fix stack buffer overflow in BlueZ LE Audio BASE parser
13: B3 Line contains hard tab characters (\t): " // src/shared/bap.c:7767"
14: B3 Line contains hard tab characters (\t): " memcpy(&location32, v, l); // l attacker-controlled, no upper bound"
##############################
Test: CheckSmatch - WARNING
Desc: Run smatch tool with source
Output:
src/shared/bap.c:318:25: warning: array of flexible structuressrc/shared/bap.c: note: in included file:./src/shared/ascs.h:88:25: warning: array of flexible structuressrc/shared/bap.c:318:25: warning: array of flexible structuressrc/shared/bap.c: note: in included file:./src/shared/ascs.h:88:25: warning: array of flexible structuressrc/shared/bap.c:318:25: warning: array of flexible structuressrc/shared/bap.c: note: in included file:./src/shared/ascs.h:88:25: warning: array of flexible structures
https://github.com/bluez/bluez/pull/2443
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-08-27 16:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-27 14:58 [PATCH] bap: Fix stack buffer overflow in BlueZ LE Audio BASE parser Bastien Nocera
2026-08-27 16:17 ` bluez.test.bot [this message]
2026-08-27 17:10 ` patchwork-bot+bluetooth
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=6a906303.28258500.8013d.3be4@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=hadess@hadess.net \
--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.