From: Paul Barker <paul@pbarker.dev>
To: Venkata.Navuduri@windriver.com, "MacLeod,
Randy" <Randy.MacLeod@windriver.com>,
"yocto@lists.yoctoproject.org" <yocto@lists.yoctoproject.org>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>,
"linux-yocto@lists.yoctoproject.org"
<linux-yocto@lists.yoctoproject.org>
Cc: "Korovkin, Dmitriy" <Dmitriy.Korovkin@windriver.com>
Subject: Re: [OE-core] [yocto] linux-yocto CVEs in need of triage
Date: Fri, 24 Jul 2026 15:18:37 +0100 [thread overview]
Message-ID: <8caf4e5c11f6df7fcc9d52b69f9edbac8f0373cf.camel@pbarker.dev> (raw)
In-Reply-To: <1ab8694b-1f76-4059-b0ce-6604bbef3d2f@windriver.com>
[-- Attachment #1: Type: text/plain, Size: 891 bytes --]
On Thu, 2026-07-23 at 12:15 +0000, Navuduri, Venkata Adhitya via
lists.openembedded.org wrote:
> Hello,
>
> Regarding CVE-2023-3640 (x86 cpu_entry_area KASLR bypass, CVSS 7.8):
> The mainline fix is commit 97e3d26b5e5f ("x86/mm: Randomize per-cpu entry area") by Peter Zijlstra, merged in v6.2-rc1 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=97e3d26b5e5f
>
>
> So, for Yocto releases shipping kernel >=6.2 version this fix is already present. This fix needs back porting to kernel <6.2
>
> For now, I can prepare a patch to add this CVE in the cve-exclusion.inc to stop the CVE tool from reporting on this.
>
Hi Adhitya,
Please send a patch to update cve-exclusion.inc, in the commit message
please include any information or references you have to to identify
commit 97e3d26b5e5f as the fix.
Best regards,
--
Paul Barker
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
next prev parent reply other threads:[~2026-07-24 14:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-29 19:33 linux-yocto CVEs in need of triage Paul Barker
2026-07-22 14:45 ` [yocto] " Randy MacLeod
2026-07-23 12:15 ` Navuduri, Venkata Adhitya
2026-07-24 14:18 ` Paul Barker [this message]
2026-08-02 14:33 ` Junjie Cao
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=8caf4e5c11f6df7fcc9d52b69f9edbac8f0373cf.camel@pbarker.dev \
--to=paul@pbarker.dev \
--cc=Dmitriy.Korovkin@windriver.com \
--cc=Randy.MacLeod@windriver.com \
--cc=Venkata.Navuduri@windriver.com \
--cc=linux-yocto@lists.yoctoproject.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=yocto@lists.yoctoproject.org \
/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