From: "Yoann Congal" <yoann.congal@smile.fr>
To: "Yoann Congal" <yoann.congal@smile.fr>,
"Paul Barker" <paul@pbarker.dev>,
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core][scarthgap 21/25] improve_kernel_cve_report: add script for postprocesing of kernel CVE data
Date: Tue, 10 Feb 2026 11:46:59 +0100 [thread overview]
Message-ID: <DGB802Q1LFPJ.2VTMZ8JDI9O9M@smile.fr> (raw)
In-Reply-To: <DGB6HIM1ZK8A.2S3O9NW59L2DC@smile.fr>
On Tue Feb 10, 2026 at 10:35 AM CET, Yoann Congal wrote:
> On Mon Feb 9, 2026 at 11:58 AM CET, Paul Barker wrote:
>> On Mon, 2026-02-09 at 10:29 +0100, Yoann Congal via
>> lists.openembedded.org wrote:
>>> From: Daniel Turull <daniel.turull@ericsson.com>
>>>
>>> Adding postprocessing script to process data from linux CNA that includes more accurate metadata and it is updated directly by the source.
>>>
>>> Example of enhanced CVE from a report from cve-check:
>>>
>>> {
>>> "id": "CVE-2024-26710",
>>> "status": "Ignored",
>>> "link": "https://nvd.nist.gov/vuln/detail/CVE-2024-26710",
>>> "summary": "In the Linux kernel, the following vulnerability [...]",
>>> "scorev2": "0.0",
>>> "scorev3": "5.5",
>>> "scorev4": "0.0",
>>> "modified": "2025-03-17T15:36:11.620",
>>> "vector": "LOCAL",
>>> "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
>>> "detail": "not-applicable-config",
>>> "description": "Source code not compiled by config. ['arch/powerpc/include/asm/thread_info.h']"
>>> },
>>>
>>> And same from a report generated with vex:
>>> {
>>> "id": "CVE-2024-26710",
>>> "status": "Ignored",
>>> "link": "https://nvd.nist.gov/vuln/detail/CVE-2024-26710",
>>> "detail": "not-applicable-config",
>>> "description": "Source code not compiled by config. ['arch/powerpc/include/asm/thread_info.h']"
>>> },
>>>
>>> For unpatched CVEs, provide more context in the description:
>>> Tested with 6.12.22 kernel
>>> {
>>> "id": "CVE-2025-39728",
>>> "status": "Unpatched",
>>> "link": "https://nvd.nist.gov/vuln/detail/CVE-2025-39728",
>>> "summary": "In the Linux kernel, the following vulnerability has been [...],
>>> "scorev2": "0.0",
>>> "scorev3": "0.0",
>>> "scorev4": "0.0",
>>> "modified": "2025-04-21T14:23:45.950",
>>> "vector": "UNKNOWN",
>>> "vectorString": "UNKNOWN",
>>> "detail": "version-in-range",
>>> "description": "Needs backporting (fixed from 6.12.23)"
>>> },
>>>
>>> CC: Peter Marko <peter.marko@siemens.com>
>>> CC: Marta Rybczynska <rybczynska@gmail.com>
>>> Signed-off-by: Daniel Turull <daniel.turull@ericsson.com>
>>> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
>>> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
>>> (cherry picked from commit e60b1759c1aea5b8f5317e46608f0a3e782ecf57)
>>> Signed-off-by: Suresh H A <suresh.ha@bmwtechworks.in>
>>> Signed-off-by: Yoann Congal <yoann.congal@smile.fr>
>>
>> This looks like a backport of a new feature, if we're making an
>> exception to allow this to be backported then we should document the
>> reason why (apologies if this is somewhere on the list and I've missed
>> it).
>
> I've talked about it briefly there:
> https://lore.kernel.org/openembedded-core/CAMSfU+6DXfuaG0uyPtEg5hE7oHqP=8pRhSttciF+NHcwr0Hpjg@mail.gmail.com/t/#u
> Mainly, since this is "contrib/", I don't mind relaxing rules a bit.
> @Paul, do you think this is reasonable?
>
> I agree that this exception should be documented (I will add a note in the
> commit message)
@Paul, see the update commit message in
https://git.openembedded.org/openembedded-core-contrib/commit/?h=stable/scarthgap-nut&id=26138b9f4c1cfe4718f719ea7710c80290d9a8da :
> [Yoann: Stable policy exception: This change is clearly a new feature
> and thus should be rejected from stables by policy. But, since this is
> contrib/ an exception can be made]
> Signed-off-by: Yoann Congal <yoann.congal@smile.fr>
>> If we do take this, we should also consider the other changes made to
>> this script since it was added to master.
>
> Yes, if I accept this one, I would also accept further updates on this
> script.
>
> Cheers,
--
Yoann Congal
Smile ECS
next prev parent reply other threads:[~2026-02-10 10:47 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-09 9:28 [OE-core][scarthgap 00/25] Patch review Yoann Congal
2026-02-09 9:28 ` [OE-core][scarthgap 01/25] curl: fix CVE-2025-10148 Yoann Congal
2026-02-09 9:28 ` [OE-core][scarthgap 02/25] curl: patch CVE-2025-14524 Yoann Congal
2026-02-09 9:28 ` [OE-core][scarthgap 03/25] expat: patch CVE-2026-24515 Yoann Congal
2026-02-09 9:28 ` [OE-core][scarthgap 04/25] expat: patch CVE-2026-25210 Yoann Congal
2026-02-09 9:28 ` [OE-core][scarthgap 05/25] glib-2.0: patch CVE-2026-0988 Yoann Congal
2026-02-09 9:28 ` [OE-core][scarthgap 06/25] inetutils: Fix CVE-2026-24061 Yoann Congal
2026-02-09 9:28 ` [OE-core][scarthgap 07/25] libpng: patch CVE-2026-22695 Yoann Congal
2026-02-09 9:28 ` [OE-core][scarthgap 08/25] libpng: patch CVE-2026-22801 Yoann Congal
2026-02-09 9:28 ` [OE-core][scarthgap 09/25] libtasn1: Fix CVE-2025-13151 Yoann Congal
2026-02-09 9:28 ` [OE-core][scarthgap 10/25] libxml2: patch CVE-2026-0989 Yoann Congal
2026-02-09 9:28 ` [OE-core][scarthgap 11/25] libxml2: patch CVE-2026-0990 Yoann Congal
2026-02-09 9:28 ` [OE-core][scarthgap 12/25] libxml2: patch CVE-2026-0992 Yoann Congal
2026-02-09 9:28 ` [OE-core][scarthgap 13/25] libxml2: add follow-up patch for CVE-2026-0992 Yoann Congal
2026-02-09 9:28 ` [OE-core][scarthgap 14/25] python3: patch CVE-2025-13837 Yoann Congal
2026-02-09 9:28 ` [OE-core][scarthgap 15/25] python-urllib3: Backport fix for CVE-2026-21441 Yoann Congal
2026-02-09 9:28 ` [OE-core][scarthgap 16/25] zlib: ignore CVE-2026-22184 Yoann Congal
2026-02-09 10:49 ` Paul Barker
2026-02-10 10:45 ` Yoann Congal
2026-02-09 9:29 ` [OE-core][scarthgap 17/25] ffmpeg: upgrade 6.1.3 -> 6.1.4 Yoann Congal
2026-02-09 9:29 ` [OE-core][scarthgap 18/25] ffmpeg: ignore CVE-2025-25469 Yoann Congal
2026-02-09 9:29 ` [OE-core][scarthgap 19/25] glibc: stable 2.39 branch updates Yoann Congal
2026-02-10 15:38 ` Yoann Congal
2026-02-09 9:29 ` [OE-core][scarthgap 20/25] meta/classes: fix missing vardeps for CVE status variables Yoann Congal
2026-02-09 9:29 ` [OE-core][scarthgap 21/25] improve_kernel_cve_report: add script for postprocesing of kernel CVE data Yoann Congal
2026-02-09 10:58 ` Paul Barker
2026-02-10 9:35 ` Yoann Congal
2026-02-10 10:46 ` Yoann Congal [this message]
2026-02-09 9:29 ` [OE-core][scarthgap 22/25] lighttpd: Fix trailing slash on files in mod_dirlisting Yoann Congal
2026-02-09 9:29 ` [OE-core][scarthgap 23/25] docbook-xml-dtd4: fix the fetching failure Yoann Congal
2026-02-09 9:29 ` [OE-core][scarthgap 24/25] pseudo: Update to 1.9.3 release Yoann Congal
2026-02-09 9:29 ` [OE-core][scarthgap 25/25] libtheora: set CVE_PRODUCT Yoann Congal
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=DGB802Q1LFPJ.2VTMZ8JDI9O9M@smile.fr \
--to=yoann.congal@smile.fr \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul@pbarker.dev \
/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