From: Joachim Wiberg <troglobit@gmail.com>
To: buildroot@buildroot.org
Cc: Fiona Klute <fiona.klute@gmx.de>, Joachim Wiberg <troglobit@gmail.com>
Subject: [Buildroot] [PATCH 0/2] package/lldpd: security bump to 1.0.22
Date: Mon, 14 Sep 2026 17:53:50 +0200 [thread overview]
Message-ID: <20260914155352.1331991-1-troglobit@gmail.com> (raw)
Bump lldpd to 1.0.22, fixing CVE-2026-46433, an out-of-bound read when
removing the VLAN tag. 1.0.21 is picked up along the way, fixing path
traversal and arbitrary file deletion in the privileged process.
No packaging changes were needed: the configure options are identical
between 1.0.20 and 1.0.22, and the LICENSE hash still matches. The
tarball signature checks out against the key already recorded in the
hash file.
The second patch is independent of the bump. check-package had six
warnings on S60lldpd, and rewriting it after the S01syslogd reference
also fixes start and stop always reporting success, and stop not
waiting for the daemon to exit before a restart races it.
Best regards
/Joachim
Joachim Wiberg (2):
package/lldpd: security bump to version 1.0.22
package/lldpd: rework start script
package/lldpd/S60lldpd | 80 +++++++++++++++++++++++++++++-----------
package/lldpd/lldpd.hash | 6 +--
package/lldpd/lldpd.mk | 2 +-
3 files changed, 62 insertions(+), 26 deletions(-)
--
2.43.0
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2026-09-14 15:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-14 15:53 Joachim Wiberg [this message]
2026-09-14 15:53 ` [Buildroot] [PATCH 1/2] package/lldpd: security bump to version 1.0.22 Joachim Wiberg
2026-09-14 19:47 ` Julien Olivain via buildroot
2026-09-25 14:44 ` Raphaël Mélotte via buildroot
2026-09-14 15:53 ` [Buildroot] [PATCH 2/2] package/lldpd: rework start script Joachim Wiberg
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=20260914155352.1331991-1-troglobit@gmail.com \
--to=troglobit@gmail.com \
--cc=buildroot@buildroot.org \
--cc=fiona.klute@gmx.de \
/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