From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/linuxptp: security bump version to 3.1.1
Date: Fri, 16 Jul 2021 23:30:58 +0200 [thread overview]
Message-ID: <20210716233058.26b0ed6c@windsurf> (raw)
In-Reply-To: <20210706091500.3236-1-heiko.thiery@gmail.com>
On Tue, 6 Jul 2021 11:15:01 +0200
Heiko Thiery <heiko.thiery@gmail.com> wrote:
> This fixes the following CVEs:
> - CVE-2021-3570 linuxptp: missing length check of forwarded messages
> - CVE-2021-3571 linuxptp: wrong length of one-step follow-up in transparent clock
>
> See mailing list post for details: https://sourceforge.net/p/linuxptp/mailman/message/37315519/
>
> Signed-off-by: Heiko Thiery <heiko.thiery@gmail.com>
> ---
> package/linuxptp/linuxptp.hash | 8 ++++----
> package/linuxptp/linuxptp.mk | 2 +-
> 2 files changed, 5 insertions(+), 5 deletions(-)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2021-07-16 21:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-06 9:15 [Buildroot] [PATCH] package/linuxptp: security bump version to 3.1.1 Heiko Thiery
2021-07-16 21:30 ` Thomas Petazzoni [this message]
2021-08-03 14:25 ` Peter Korsgaard
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=20210716233058.26b0ed6c@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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