public inbox for buildroot@busybox.net
 help / color / mirror / Atom feed
From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Thomas Perale <thomas.perale@mind.be>
Cc: buildroot@buildroot.org, Fabrice Fontaine <fontaine.fabrice@gmail.com>
Subject: Re: [Buildroot] [PATCH] package/rtl_433: add patch for CVE-2025-34450
Date: Sat, 28 Feb 2026 22:04:10 +0100	[thread overview]
Message-ID: <208db4fb6e6404701f0ea3d374294f24@free.fr> (raw)
In-Reply-To: <20260228202847.96486-1-thomas.perale@mind.be>

On 28/02/2026 21:28, Thomas Perale via buildroot wrote:
> Fixes the following vulnerability:
> 
> - CVE-2025-34450:
>     merbanan/rtl_433 versions up to and including 25.02 and prior to
>     commit 25e47f8 contain a stack-based buffer overflow vulnerability 
> in
>     the function parse_rfraw() located in src/rfraw.c. When processing
>     crafted or excessively large raw RF input data, the application may
>     write beyond the bounds of a stack buffer, resulting in memory
>     corruption or a crash. This vulnerability can be exploited to cause 
> a
>     denial of service and, under certain conditions, may be leveraged 
> for
>     further exploitation depending on the execution environment and
>     available mitigations.
> 
> For mroe information, see:
>   - https://www.cve.org/CVERecord?id=CVE-2025-34450
>   - 
> https://github.com/merbanan/rtl_433/commit/25e47f8932f0401392ef1d3c8cc9ed5595bc894a
> 
> 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

  reply	other threads:[~2026-02-28 21:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-28 20:28 [Buildroot] [PATCH] package/rtl_433: add patch for CVE-2025-34450 Thomas Perale via buildroot
2026-02-28 21:04 ` 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=208db4fb6e6404701f0ea3d374294f24@free.fr \
    --to=buildroot@buildroot.org \
    --cc=fontaine.fabrice@gmail.com \
    --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