Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Thomas Perale via buildroot <buildroot@buildroot.org>
Cc: "Thomas Perale" <thomas.perale@mind.be>,
	"Raphaël Mélotte" <raphael.melotte@mind.be>,
	"Bernd Kuhls" <bernd@kuhls.net>,
	"Gilles Talis" <gilles.talis@gmail.com>,
	"Martin Kepplinger" <martink@posteo.de>,
	"Angelo Compagnucci" <angelo.compagnucci@gmail.com>,
	"Joachim Wiberg" <troglobit@gmail.com>,
	"Olivier Schonken" <olivier.schonken@gmail.com>
Subject: Re: [Buildroot] [PATCH 01/14] package/sox: add CVE trailer in patches
Date: Mon, 29 Dec 2025 15:12:59 +0100	[thread overview]
Message-ID: <20251229151259.37dfa7e8@windsurf> (raw)
In-Reply-To: <20251229090719.13291-1-thomas.perale@mind.be>

Hello Thomas,

On Mon, 29 Dec 2025 10:07:06 +0100
Thomas Perale via buildroot <buildroot@buildroot.org> wrote:

> Since Buildroot commit [1] the patches that fixes a security
> vulnerability needs to reference the fixed vulnerability.
> 
> This patch adds the relevant information to the patches header.
> 
> [1] 1167d0ff3d docs/manual: mention CVE trailer
> 
> Signed-off-by: Thomas Perale <thomas.perale@mind.be>
> ---
>  ...voc-word-width-should-never-be-0-to-avoid-division-b.patch | 2 ++
>  package/sox/0007-hcom-validate-dictsize.patch                 | 4 ++++
>  package/sox/0008-phere-avoid-integer-underflow.patch          | 1 +
>  ...formats-aiff-reject-implausibly-large-number-of-chan.patch | 2 ++
>  package/sox/0010-formats-reject-implausible-rate.patch        | 1 +
>  ...CVE-2023-32627-Filter-null-sampling-rate-in-VOC-code.patch | 1 +
>  6 files changed, 11 insertions(+)

Series applied, thanks!

Two notes:

- When you add the Upstream: header, make sure to update the
  .checkpackageignore file as well. You can run "make check-package",
  or have a Git commit hook that checks it for you.

- Also, when you add the Upstream: header, if there's already the same
  information in the patch, but in a non-machine parseable form, drop
  this additional info. For example in this series:

+CVE: CVE-2021-42260
+Upstream: https://sourceforge.net/p/tinyxml/git/merge-requests/1
 [Retrieved (and backported) from:
 https://sourceforge.net/p/tinyxml/git/merge-requests/1]

  You should drop the [Retrieved (and backported) from  ...], because
  that information is now provided by the Upstream: tag.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2025-12-29 14:13 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-29  9:07 [Buildroot] [PATCH 01/14] package/sox: add CVE trailer in patches Thomas Perale via buildroot
2025-12-29  9:07 ` [Buildroot] [PATCH 02/14] package/x11vnc: add CVE trailer in patch Thomas Perale via buildroot
2026-01-07 17:52   ` Arnout Vandecappelle via buildroot
2025-12-29  9:07 ` [Buildroot] [PATCH 03/14] package/tinyxml: " Thomas Perale via buildroot
2026-01-07 17:52   ` Arnout Vandecappelle via buildroot
2025-12-29  9:07 ` [Buildroot] [PATCH 04/14] package/opusfile: " Thomas Perale via buildroot
2026-01-07 17:51   ` Arnout Vandecappelle via buildroot
2025-12-29  9:07 ` [Buildroot] [PATCH 05/14] package/lua-http: " Thomas Perale via buildroot
2026-01-07 17:51   ` Arnout Vandecappelle via buildroot
2025-12-29  9:07 ` [Buildroot] [PATCH 06/14] package/dovecot: " Thomas Perale via buildroot
2026-01-07 17:51   ` Arnout Vandecappelle via buildroot
2025-12-29  9:07 ` [Buildroot] [PATCH 07/14] package/avahi: " Thomas Perale via buildroot
2026-01-07 17:51   ` Arnout Vandecappelle via buildroot
2025-12-29  9:07 ` [Buildroot] [PATCH 08/14] package/cups-filter: " Thomas Perale via buildroot
2026-01-07 17:51   ` Arnout Vandecappelle via buildroot
2025-12-29  9:07 ` [Buildroot] [PATCH 09/14] package/libconfuse: " Thomas Perale via buildroot
2026-01-07 17:51   ` Arnout Vandecappelle via buildroot
2026-01-07 18:25     ` Baruch Siach via buildroot
2026-01-08  7:54       ` Arnout Vandecappelle via buildroot
2025-12-29  9:07 ` [Buildroot] [PATCH 10/14] package/libtomcrypt: " Thomas Perale via buildroot
2026-01-07 17:51   ` Arnout Vandecappelle via buildroot
2025-12-29  9:07 ` [Buildroot] [PATCH 11/14] package/sdl: " Thomas Perale via buildroot
2026-01-07 17:51   ` Arnout Vandecappelle via buildroot
2025-12-29  9:07 ` [Buildroot] [PATCH 12/14] package/sdl: fix patch reference in IGNORE_CVES Thomas Perale via buildroot
2026-01-07 17:52   ` Arnout Vandecappelle via buildroot
2025-12-29  9:07 ` [Buildroot] [PATCH 13/14] package/pixman: " Thomas Perale via buildroot
2026-01-07 17:51   ` Arnout Vandecappelle via buildroot
2025-12-29  9:07 ` [Buildroot] [PATCH 14/14] package/mupdf: add CVE-2024-2425{8, 9} to IGNORE_CVES Thomas Perale via buildroot
2026-01-07 17:56   ` Arnout Vandecappelle via buildroot
2025-12-29 14:12 ` Thomas Petazzoni via buildroot [this message]
2025-12-29 17:34   ` [Buildroot] [PATCH 01/14] package/sox: add CVE trailer in patches Thomas Perale via buildroot
2026-01-07 17:52 ` Arnout Vandecappelle via buildroot

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=20251229151259.37dfa7e8@windsurf \
    --to=buildroot@buildroot.org \
    --cc=angelo.compagnucci@gmail.com \
    --cc=bernd@kuhls.net \
    --cc=gilles.talis@gmail.com \
    --cc=martink@posteo.de \
    --cc=olivier.schonken@gmail.com \
    --cc=raphael.melotte@mind.be \
    --cc=thomas.perale@mind.be \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=troglobit@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox