From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Thomas Perale <thomas.perale@mind.be>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/patch: add patches for CVE-2018-6952 & CVE-2019-20633
Date: Wed, 25 Feb 2026 22:15:14 +0100 [thread overview]
Message-ID: <f4d801f64fd87c62a25bd406ea37af51@free.fr> (raw)
In-Reply-To: <20260225202847.385468-1-thomas.perale@mind.be>
On 25/02/2026 21:28, Thomas Perale via buildroot wrote:
> Fixes the following vulnerabilities:
>
> - CVE-2018-6952:
> A double free exists in the another_hunk function in pch.c in GNU
> patch through 2.7.6.
>
> For more information, see:
> - https://www.cve.org/CVERecord?id=CVE-2018-6952
> -
> https://cgit.git.savannah.gnu.org/cgit/patch.git/commit/?id=9c986353e420ead6e706262bf204d6e03322c300
>
> - CVE-2019-20633:
> GNU patch through 2.7.6 contains a free(p_line[p_end]) Double Free
> vulnerability in the function another_hunk in pch.c that can cause
> a
> denial of service via a crafted patch file. NOTE: this issue exists
> because of an incomplete fix for CVE-2018-6952.
>
> For more information, see:
> - https://www.cve.org/CVERecord?id=CVE-2019-20633
> -
> https://cgit.git.savannah.gnu.org/cgit/patch.git/commit/?id=15b158db3ae11cb835f2eb8d2eb48e09d1a4af48
>
> Signed-off-by: Thomas Perale <thomas.perale@mind.be>
Applied to master, thanks.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-02-25 21:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-25 20:28 [Buildroot] [PATCH] package/patch: add patches for CVE-2018-6952 & CVE-2019-20633 Thomas Perale via buildroot
2026-02-25 21:15 ` Julien Olivain via buildroot [this message]
2026-03-06 19:53 ` Thomas Perale 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=f4d801f64fd87c62a25bd406ea37af51@free.fr \
--to=buildroot@buildroot.org \
--cc=ju.o@free.fr \
--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