From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Thomas Perale <thomas.perale@mind.be>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/wireshark: security bump to v4.4.13
Date: Wed, 25 Feb 2026 21:44:54 +0100 [thread overview]
Message-ID: <c89a9587c18dad4c2df30a7cbbbaa595@free.fr> (raw)
In-Reply-To: <20260225091006.238395-1-thomas.perale@mind.be>
On 25/02/2026 10:10, Thomas Perale via buildroot wrote:
> For more information on the version bump, see:
> - https://www.wireshark.org/docs/relnotes/wireshark-4.4.13.html
> - https://www.wireshark.org/docs/relnotes/wireshark-4.4.12.html
> - https://www.wireshark.org/docs/relnotes/wireshark-4.4.11.html
> - https://www.wireshark.org/docs/relnotes/wireshark-4.4.10.html
>
> Fixes the following vulnerabilities:
>
> - CVE-2025-11626:
> MONGO dissector infinite loop in Wireshark 4.4.0 to 4.4.9 and 4.2.0
> to
> 4.2.13 allows denial of service
>
> https://www.cve.org/CVERecord?id=CVE-2025-11626
>
> - CVE-2025-13499:
> Kafka dissector crash in Wireshark 4.6.0 and 4.4.0 to 4.4.10 allows
> denial of service
>
> https://www.cve.org/CVERecord?id=CVE-2025-13499
>
> - CVE-2025-13946:
> MEGACO dissector infinite loop in Wireshark 4.6.0 to 4.6.1 and
> 4.4.0
> to 4.4.11 allows denial of service
>
> https://www.cve.org/CVERecord?id=CVE-2025-13946
>
> - CVE-2026-0959:
> IEEE 802.11 protocol dissector crash in Wireshark 4.6.0 to 4.6.2
> and
> 4.4.0 to 4.4.12 allows denial of service
>
> https://www.cve.org/CVERecord?id=CVE-2026-0959
>
> - CVE-2026-0960:
> HTTP3 protocol dissector infinite loop in Wireshark 4.6.0 to 4.6.2
> allows denial of service
>
> https://www.cve.org/CVERecord?id=CVE-2026-0960
>
> - CVE-2026-0961:
> BLF file parser crash in Wireshark 4.6.0 to 4.6.2 and 4.4.0 to
> 4.4.12
> allows denial of service
>
> https://www.cve.org/CVERecord?id=CVE-2026-0961
>
> - CVE-2026-0962:
> SOME/IP-SD protocol dissector crash in Wireshark 4.6.0 to 4.6.2 and
> 4.4.0 to 4.4.12 allows denial of service
>
> https://www.cve.org/CVERecord?id=CVE-2026-0962
>
> 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 20:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-25 9:10 [Buildroot] [PATCH] package/wireshark: security bump to v4.4.13 Thomas Perale via buildroot
2026-02-25 20:44 ` Julien Olivain via buildroot [this message]
2026-03-06 19:53 ` Thomas Perale via buildroot
-- strict thread matches above, loose matches on Subject: below --
2026-02-25 9:48 [Buildroot] [PATCH 1/1] package/containerd: security bump to v2.0.7 Thomas Perale via buildroot
2026-02-25 9:48 ` [Buildroot] [PATCH] package/wireshark: security bump to v4.4.13 Thomas Perale via buildroot
2026-02-25 9:57 ` 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=c89a9587c18dad4c2df30a7cbbbaa595@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