Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Thomas Perale <thomas.perale@mind.be>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/avahi: upstream patch for CVE-2026-34933
Date: Sun, 05 Jul 2026 11:51:59 +0200	[thread overview]
Message-ID: <b0a2bdc441d6466ea68ea416da9833d9@free.fr> (raw)
In-Reply-To: <20260626195937.49027-1-thomas.perale@mind.be>

On 26/06/2026 21:59, Thomas Perale via buildroot wrote:
> This fixes the following vulnerability:
> 
> - CVE-2026-34933:
>     Avahi is a system which facilitates service discovery on a local
>     network via the mDNS/DNS-SD protocol suite. Prior to version 
> 0.9-rc4,
>     any unprivileged local user can crash avahi-daemon by sending a 
> single
>     D-Bus method call with conflicting publish flags. This issue has 
> been
>     patched in version 0.9-rc4.
> 
> For more information, see:
>   - https://www.cve.org/CVERecord?id=CVE-2026-34933
>   - 
> https://github.com/avahi/avahi/commit/0be89b6bb5c3983837b5e0febcbbbf452ecf7675
> 
> 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-07-05  9:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-26 19:59 [Buildroot] [PATCH 1/1] package/avahi: upstream patch for CVE-2026-34933 Thomas Perale via buildroot
2026-07-05  9:51 ` Julien Olivain via buildroot [this message]
2026-07-10 13:51 ` 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=b0a2bdc441d6466ea68ea416da9833d9@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