All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Fiona Klute <fiona.klute@gmx.de>
Cc: buildroot@buildroot.org, Eric Le Bihan <eric.le.bihan.dev@free.fr>
Subject: Re: [Buildroot] [PATCH v2 1/2] package/p11-kit: security bump to version 0.26.5
Date: Sun, 18 Oct 2026 11:51:25 +0200	[thread overview]
Message-ID: <85f8f26ccbc830dfcb6fcfdf3cfc583c@free.fr> (raw)
In-Reply-To: <20261017140027.697390-1-fiona.klute@gmx.de>

On 17/10/2026 16:00, Fiona Klute via buildroot wrote:
> Security fixes by versions:
> 
> 0.26.5
> * CVE-2026-18938: rpc: guard against overflow when decoding nested
>   attributes
>   https://github.com/advisories/GHSA-6x8p-h5fj-5ppr
> 
> 0.26.3
> * CVE-2026-13757: server: fixed stack exhaustion via unbounded
>   recursion in RPC attribute parsing by enforcing a recursion depth
>   limit
>   https://github.com/advisories/GHSA-p2wm-69qx-x25w
> * various memory management fixes (including memory leaks) without
>   CVE or details on possible security impact
> 
> Full upstream changelog:
> https://github.com/p11-glue/p11-kit/blob/0.26.5/NEWS
> 
> Signed-off-by: Fiona Klute <fiona.klute@gmx.de>

Series applied to master, thanks.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2026-10-18  9:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-17 14:00 [Buildroot] [PATCH v2 1/2] package/p11-kit: security bump to version 0.26.5 Fiona Klute via buildroot
2026-10-17 14:00 ` [Buildroot] [PATCH v2 2/2] package/p11-kit: switch to meson build system Fiona Klute via buildroot
2026-10-18  9:51 ` Julien Olivain via buildroot [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=85f8f26ccbc830dfcb6fcfdf3cfc583c@free.fr \
    --to=buildroot@buildroot.org \
    --cc=eric.le.bihan.dev@free.fr \
    --cc=fiona.klute@gmx.de \
    --cc=ju.o@free.fr \
    /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.