From: Baruch Siach via buildroot <buildroot@buildroot.org>
To: Arnout Vandecappelle via buildroot <buildroot@buildroot.org>
Cc: Thomas Perale <thomas.perale@mind.be>
Subject: Re: [Buildroot] [PATCH 09/14] package/libconfuse: add CVE trailer in patch
Date: Wed, 07 Jan 2026 20:25:01 +0200 [thread overview]
Message-ID: <875x9d5lhe.fsf@tarshish> (raw)
In-Reply-To: <20260107175147.228330-1-arnout@rnout.be> (Arnout Vandecappelle via buildroot's message of "Wed, 7 Jan 2026 18:51:47 +0100")
Hi Arnout,
On Wed, Jan 07 2026, Arnout Vandecappelle via buildroot wrote:
> In reply of:
>> 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 patch header
>> and adds the `Upstream` trailer.
>>
>> [1] 1167d0ff3d docs/manual: mention CVE trailer
>>
>> Signed-off-by: Thomas Perale <thomas.perale@mind.be>
>
> Applied to 2025.02.x and 2025.11.x. Thanks
Not in 2025.11.x as of commit e98515299 ("package/mupdf: add
CVE-2024-2425{8, 9} to IGNORE_CVES").
baruch
>
>> ---
>> .../0001-Fix-163-unterminated-username-used-with-getpwnam.patch | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git
>> a/package/libconfuse/0001-Fix-163-unterminated-username-used-with-getpwnam.patch
>> b/package/libconfuse/0001-Fix-163-unterminated-username-used-with-getpwnam.patch
>> index 9ff3f5ec1c..4c2aa114aa 100644
>> --- a/package/libconfuse/0001-Fix-163-unterminated-username-used-with-getpwnam.patch
>> +++ b/package/libconfuse/0001-Fix-163-unterminated-username-used-with-getpwnam.patch
>> @@ -5,6 +5,8 @@ Subject: [PATCH] Fix #163: unterminated username used with getpwnam()
>>
>> Signed-off-by: Joachim Wiberg <troglobit@gmail.com>
>>
>> +CVE: CVE-2022-40320
>> +Upstream: https://github.com/libconfuse/libconfuse/commit/d73777c2c3566fb2647727bb56d9a2295b81669b
>> [Retrieved (and backported) from:
>> https://github.com/libconfuse/libconfuse/commit/d73777c2c3566fb2647727bb56d9a2295b81669b]
>> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
>> --
>> 2.52.0
>>
>> _______________________________________________
>> buildroot mailing list
>> buildroot@buildroot.org
>> https://lists.buildroot.org/mailman/listinfo/buildroot
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
--
~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch@tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-01-07 18:25 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 [this message]
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 ` [Buildroot] [PATCH 01/14] package/sox: add CVE trailer in patches Thomas Petazzoni via buildroot
2025-12-29 17:34 ` 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=875x9d5lhe.fsf@tarshish \
--to=buildroot@buildroot.org \
--cc=baruch@tkos.co.il \
--cc=thomas.perale@mind.be \
/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