From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Stefan Agner <stefan@agner.ch>
Cc: giulio.benetti@benettiengineering.com, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2] package/openvmtools: fix local privilege escalation vulnerability
Date: Sun, 30 Oct 2022 22:24:32 +0100 [thread overview]
Message-ID: <20221030222432.26968da5@windsurf> (raw)
In-Reply-To: <7aeb69a91cab8b3e5fdcfc210c2f5a112490b0a0.1666169750.git.stefan@agner.ch>
Hello Stefan,
On Wed, 19 Oct 2022 10:56:16 +0200
Stefan Agner <stefan@agner.ch> wrote:
> Add a patch for CVE-2022-31676 (local privilege escalation
> vulnerability).
>
> Signed-off-by: Stefan Agner <stefan@agner.ch>
> ---
> v2: Actually make the patch apply
I've applied to master, but after:
(1) Adding a reference to the upstream location where the patch was
provided
(2) Adding a OPENVMTOOLS_IGNORE_CVES entry in the .mk file to ignore
the CVE now that it is fixed.
According to our CVE tracking infrastructure, there are 3 other CVEs
affecting openvmtools: CVE-2014-4199, CVE-2014-4200, CVE-2022-22943. Do
you think you could have a look?
Thanks a lot!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-10-30 21:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-19 8:56 [Buildroot] [PATCH v2] package/openvmtools: fix local privilege escalation vulnerability Stefan Agner
2022-10-30 21:24 ` Thomas Petazzoni via buildroot [this message]
2022-11-13 16:02 ` 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=20221030222432.26968da5@windsurf \
--to=buildroot@buildroot.org \
--cc=giulio.benetti@benettiengineering.com \
--cc=stefan@agner.ch \
--cc=thomas.petazzoni@bootlin.com \
/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