All of lore.kernel.org
 help / color / mirror / Atom feed
From: hudsonzuo <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] e76177: gatt-server: Fix integer overflow and 3 CI VLA wan...
Date: Fri, 21 Aug 2026 04:01:49 -0700	[thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1149710/000000-e76177@github.com> (raw)

  Branch: refs/heads/1149710
  Home:   https://github.com/bluez/bluez
  Commit: e7617711ab38c02df60a53a3d51f5ca3c84909d6
      https://github.com/bluez/bluez/commit/e7617711ab38c02df60a53a3d51f5ca3c84909d6
  Author: zuohsh <zuohongsheng@kylinos.cn>
  Date:   2026-08-21 (Fri, 21 Aug 2026)

  Changed paths:
    M src/shared/gatt-server.c

  Log Message:
  -----------
  gatt-server: Fix integer overflow and 3 CI VLA wanings

By using size_t for realloc len and rejecting allocations exceeding
UINT16_MAX , to prevent truncation into the uint16_t field.

Fix CI warnings: Variable length array is used, use malloc/free instead.



To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications

                 reply	other threads:[~2026-08-21 11:01 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/1149710/000000-e76177@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.