From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Thomas Perale <thomas.perale@mind.be>
Cc: buildroot@buildroot.org,
"Flávio Tapajós" <flavio.tapajos@newtesc.com.br>
Subject: Re: [Buildroot] [PATCH] package/rsyslog: upstream patch CVE-2026-19654
Date: Wed, 26 Aug 2026 22:56:30 +0200 [thread overview]
Message-ID: <8f56f3a9640df87ef4255bc6c84000e2@free.fr> (raw)
In-Reply-To: <20260826191159.711051-1-thomas.perale@mind.be>
On 26/08/2026 21:11, Thomas Perale via buildroot wrote:
> - CVE-2026-19654:
> A unauthenticated remote peer may lead rsyslogd to crash due to a
> flaw
> in the optional imptcp module. A crafted input sequence during
> oversize-frame recovery can cause an invalid internal message
> length
> and terminate rsyslogd. No confidentiality or integrity impact,
> privilege escalation, or code execution has been identified. imtcp
> and
> the default imptcp framing modes are not affected.
>
> For more information, see:
> - https://www.cve.org/CVERecord?id=CVE-2026-19654
> -
> https://github.com/rsyslog/rsyslog/commit/07b3c40a5a78c79ed9109251f842ca7e955dd586
>
> 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-08-26 20:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-26 19:11 [Buildroot] [PATCH] package/rsyslog: upstream patch CVE-2026-19654 Thomas Perale via buildroot
2026-08-26 20:56 ` Julien Olivain via buildroot [this message]
2026-09-04 12:18 ` 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=8f56f3a9640df87ef4255bc6c84000e2@free.fr \
--to=buildroot@buildroot.org \
--cc=flavio.tapajos@newtesc.com.br \
--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 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.