Skip to contentSkip to conversation

OE-core CVE metrics for walnascar on Sun 11 May 2025 01:49:49 AM HST

DISCUSSION Applied [email protected] 3 participants 8 messages May 11, 2025 – May 14, 2025 1 message not in the archive

lore
Share & tools
lore
#0 lore raw

Branch: walnascar

New this week: 6 CVEs
CVE-2023-1386 (CVSS3: N/A): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1386 * CVE-2023-52904 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-52904 * CVE-2024-56406 (CVSS3: N/A): perl:perl-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-56406 * CVE-2024-58097 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-58097 * CVE-2025-32414 (CVSS3: N/A): libxml2:libxml2-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2025-32414 * CVE-2025-32415 (CVSS3: N/A): libxml2:libxml2-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2025-32415 *

Removed this week: 1 CVEs
CVE-2025-1153 (CVSS3: N/A): binutils:binutils-cross-x86_64:binutils-native:binutils-testsuite https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2025-1153 *

Full list: Found 32 unpatched CVEs
CVE-2019-14899 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-14899 * CVE-2021-3714 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3714 * CVE-2021-3864 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3864 * CVE-2022-0400 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0400 * CVE-2022-1247 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1247 * CVE-2022-38096 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-38096 * CVE-2022-4543 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-4543 * CVE-2023-1386 (CVSS3: N/A): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1386 * CVE-2023-3079 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3079 * CVE-2023-3397 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3397 * CVE-2023-3640 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3640 * CVE-2023-4010 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4010 * CVE-2023-52904 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-52904 * CVE-2023-6238 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-6238 * CVE-2023-6240 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-6240 * CVE-2023-6535 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-6535 * CVE-2024-50613 (CVSS3: N/A): libsndfile1 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-50613 * CVE-2024-56406 (CVSS3: N/A): perl:perl-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-56406 * CVE-2024-57995 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-57995 * CVE-2024-58097 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-58097 * CVE-2024-8354 (CVSS3: N/A): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-8354 * CVE-2025-21751 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2025-21751 * CVE-2025-21833 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2025-21833 * CVE-2025-21949 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2025-21949 * CVE-2025-23137 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2025-23137 * CVE-2025-29087 (CVSS3: N/A): sqlite3:sqlite3-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2025-29087 * CVE-2025-32414 (CVSS3: N/A): libxml2:libxml2-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2025-32414 * CVE-2025-32415 (CVSS3: N/A): libxml2:libxml2-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2025-32415 * CVE-2025-37838 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2025-37838 * CVE-2025-37860 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2025-37860 * CVE-2025-37925 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2025-37925 * CVE-2025-40014 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2025-40014 *

Summary of CVE counts by recipe:
linux-yocto: 25
libxml2:libxml2-native: 2
qemu:qemu-native:qemu-system-native: 2
libsndfile1: 1
perl:perl-native: 1
sqlite3:sqlite3-native: 1

For further information see: https://valkyrie.yocto.io/pub/non-release/patchmetrics/

#1 lore raw

Would be cool if also autobuilder/valkyrie metrics would include walnascar by now. Peter

Quoted 106 lines

-----Original Message-----
From: [email protected] <yocto- [email protected]> On Behalf Of Steve Sakoman via lists.yoctoproject.org
Sent: Sunday, May 11, 2025 13:53
To: [email protected]; yocto- [email protected]
Subject: [yocto-security] OE-core CVE metrics for walnascar on Sun 11 May 2025 01:49:49 AM HST

Branch: walnascar

New this week: 6 CVEs
CVE-2023-1386 (CVSS3: N/A): qemu:qemu-native:qemu-system-native
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1386 * CVE-2023-52904 (CVSS3: N/A): linux-yocto
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-52904 * CVE-2024-56406 (CVSS3: N/A): perl:perl-native
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-56406 * CVE-2024-58097 (CVSS3: N/A): linux-yocto
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-58097 * CVE-2025-32414 (CVSS3: N/A): libxml2:libxml2-native
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2025-32414 * CVE-2025-32415 (CVSS3: N/A): libxml2:libxml2-native
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2025-32415 *

Removed this week: 1 CVEs
CVE-2025-1153 (CVSS3: N/A): binutils:binutils-cross-x86_64:binutils- native:binutils-testsuite https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-
2025-1153 *

Full list: Found 32 unpatched CVEs
CVE-2019-14899 (CVSS3: N/A): linux-yocto
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-14899 * CVE-2021-3714 (CVSS3: N/A): linux-yocto
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3714 * CVE-2021-3864 (CVSS3: N/A): linux-yocto
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3864 * CVE-2022-0400 (CVSS3: N/A): linux-yocto
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0400 * CVE-2022-1247 (CVSS3: N/A): linux-yocto
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1247 * CVE-2022-38096 (CVSS3: N/A): linux-yocto
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-38096 * CVE-2022-4543 (CVSS3: N/A): linux-yocto
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-4543 * CVE-2023-1386 (CVSS3: N/A): qemu:qemu-native:qemu-system-native
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1386 * CVE-2023-3079 (CVSS3: N/A): linux-yocto
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3079 * CVE-2023-3397 (CVSS3: N/A): linux-yocto
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3397 * CVE-2023-3640 (CVSS3: N/A): linux-yocto
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3640 * CVE-2023-4010 (CVSS3: N/A): linux-yocto
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4010 * CVE-2023-52904 (CVSS3: N/A): linux-yocto
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-52904 * CVE-2023-6238 (CVSS3: N/A): linux-yocto
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-6238 * CVE-2023-6240 (CVSS3: N/A): linux-yocto
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-6240 * CVE-2023-6535 (CVSS3: N/A): linux-yocto
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-6535 * CVE-2024-50613 (CVSS3: N/A): libsndfile1
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-50613 * CVE-2024-56406 (CVSS3: N/A): perl:perl-native
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-56406 * CVE-2024-57995 (CVSS3: N/A): linux-yocto
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-57995 * CVE-2024-58097 (CVSS3: N/A): linux-yocto
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-58097 * CVE-2024-8354 (CVSS3: N/A): qemu:qemu-native:qemu-system-native
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-8354 * CVE-2025-21751 (CVSS3: N/A): linux-yocto
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2025-21751 * CVE-2025-21833 (CVSS3: N/A): linux-yocto
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2025-21833 * CVE-2025-21949 (CVSS3: N/A): linux-yocto
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2025-21949 * CVE-2025-23137 (CVSS3: N/A): linux-yocto
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2025-23137 * CVE-2025-29087 (CVSS3: N/A): sqlite3:sqlite3-native
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2025-29087 * CVE-2025-32414 (CVSS3: N/A): libxml2:libxml2-native
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2025-32414 * CVE-2025-32415 (CVSS3: N/A): libxml2:libxml2-native
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2025-32415 * CVE-2025-37838 (CVSS3: N/A): linux-yocto
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2025-37838 * CVE-2025-37860 (CVSS3: N/A): linux-yocto
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2025-37860 * CVE-2025-37925 (CVSS3: N/A): linux-yocto
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2025-37925 * CVE-2025-40014 (CVSS3: N/A): linux-yocto
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2025-40014 *

Summary of CVE counts by recipe:
linux-yocto: 25 libxml2:libxml2-native: 2 qemu:qemu-native:qemu-system-native: 2
libsndfile1: 1
perl:perl-native: 1 sqlite3:sqlite3-native: 1

For further information see: https://valkyrie.yocto.io/pub/non-release/patchmetrics/

#2 lore raw
Quoted 2 lines · Peter

Would be cool if also autobuilder/valkyrie metrics would include walnascar by now.

All the repos are public so anyone could send the appropriate patches...

Cheers,

Richard

#3 lore raw

Sure thing, I have sent 3 patches to yocto-patches on Sunday. So far they're not merged...

Peter

-----Original Message-----
From: Richard Purdie <[email protected]>
Sent: Sunday, May 11, 2025 20:44
To: Marko, Peter (FT D EU SK BFS1) <[email protected]>; [email protected]; [email protected]; [email protected]
Subject: Re: [yocto-security] OE-core CVE metrics for walnascar on Sun 11 May 2025 01:49:49 AM HST

Quoted 2 lines · Peter

Would be cool if also autobuilder/valkyrie metrics would include walnascar by now.

All the repos are public so anyone could send the appropriate patches...

Cheers,

Richard

#4 lore raw
Quoted 2 lines · Peter

Sure thing, I have sent 3 patches to yocto-patches on Sunday. So far they're not merged...

Sorry, I've been meaning to but there is a lot going on. I'm not sure we want to stop styhead metrics quite yet so that means one of them needs tweaking and I didn't want to push back and as for a new version...

Cheers,

Richard

#5 lore raw
Quoted 11 lines

-----Original Message-----
From: Richard Purdie <[email protected]>
Sent: Wednesday, May 14, 2025 8:46
To: Marko, Peter (FT D EU SK BFS1) <[email protected]>; [email protected]; [email protected]; yocto- [email protected]
Subject: Re: [yocto-security] OE-core CVE metrics for walnascar on Sun 11 May 2025 01:49:49 AM HST

Quoted 8 lines
Quoted 2 lines · Peter

Sure thing, I have sent 3 patches to yocto-patches on Sunday. So far they're not merged...

Sorry, I've been meaning to but there is a lot going on. I'm not sure we want to stop styhead metrics quite yet so that means one of them needs tweaking and I didn't want to push back and as for a new version.

I don't think that I have removed styhead metrics in my patches.
I have removed only check-layer-nightly and meta-oe-mirror jobs which are I think useless now as there are no new patches accepted. If those are to be kept, I need a guidance e.g. on when these jobs are to be run for walnascar as I am now reusing "newly free" time slots. If you have a suggestion, please comment on the patches so I know what to change.

Thanks,
Peter

..

Quoted 4 lines

Cheers,

Richard

#6 lore raw
Quoted 22 lines · Peter
Quoted 13 lines

-----Original Message-----
From: Richard Purdie <[email protected]>
Sent: Wednesday, May 14, 2025 8:46
To: Marko, Peter (FT D EU SK BFS1) <[email protected]>; [email protected]; [email protected]; yocto- [email protected]
Subject: Re: [yocto-security] OE-core CVE metrics for walnascar on Sun 11 May
2025 01:49:49 AM HST

On Wed, 2025-05-14 at 06:43 +0000, Marko, Peter wrote:

Quoted 8 lines
Quoted 2 lines

Sure thing, I have sent 3 patches to yocto-patches on Sunday. So far they're not merged...

Sorry, I've been meaning to but there is a lot going on. I'm not sure
we want to stop styhead metrics quite yet so that means one of them needs tweaking and I didn't want to push back and as for a new version.

Quoted 3 lines

I don't think that I have removed styhead metrics in my patches. I have removed only check-layer-nightly and meta-oe-mirror jobs which are I think useless now as there are no new patches accepted.

Which is the thing I'd like to see left so that we gather data about how these figures change after we stop accepting patches. That is useful information to encourage people to update for example.

Quoted 5 lines

If those are to be kept, I need a guidance e.g. on when these jobs are to be run for walnascar as I am now reusing "newly free" time slots.
If you have a suggestion, please comment on the patches so I know what to change.

In order to make those suggestions, I need to go and look at the timeslots and work this out, which is the thing I've been struggling to find the time to do. I didn't reply as I had a feeling this would be the push back so either I replied comprehensively, or I just tweaked the patch but a half reply doesn't help other that to show I'm overloaded. I will try and get to that this morning. Yes, I feel bad I don't get patches handled quickly enough.

Cheers,

Richard

A message that is not in the archive (sent off-list or not yet received): [email protected]

#8 lore raw
Quoted 37 lines · Richard Purdie via lists.yoctoproject.org
Quoted 22 lines · Peter
Quoted 13 lines

-----Original Message-----
From: Richard Purdie <[email protected]>
Sent: Wednesday, May 14, 2025 8:46
To: Marko, Peter (FT D EU SK BFS1) <[email protected]>; [email protected]; [email protected]; yocto- [email protected]
Subject: Re: [yocto-security] OE-core CVE metrics for walnascar on Sun 11 May
2025 01:49:49 AM HST

On Wed, 2025-05-14 at 06:43 +0000, Marko, Peter wrote:

Quoted 8 lines
Quoted 2 lines

Sure thing, I have sent 3 patches to yocto-patches on Sunday. So far they're not merged...

Sorry, I've been meaning to but there is a lot going on. I'm not sure
we want to stop styhead metrics quite yet so that means one of them needs tweaking and I didn't want to push back and as for a new version.

Quoted 3 lines

I don't think that I have removed styhead metrics in my patches. I have removed only check-layer-nightly and meta-oe-mirror jobs which are I think useless now as there are no new patches accepted.

Which is the thing I'd like to see left so that we gather data about how these figures change after we stop accepting patches. That is useful information to encourage people to update for example.

Quoted 5 lines

If those are to be kept, I need a guidance e.g. on when these jobs are to be run for walnascar as I am now reusing "newly free" time slots.
If you have a suggestion, please comment on the patches so I know what to change.

Quoted 7 lines

In order to make those suggestions, I need to go and look at the timeslots and work this out, which is the thing I've been struggling to find the time to do. I didn't reply as I had a feeling this would be the push back so either I replied comprehensively, or I just tweaked the patch but a half reply doesn't help other that to show I'm overloaded. I will try and get to that this morning. Yes, I feel bad I don't get patches handled quickly enough.

Just to follow up, your patches were correct and I had misread/misremembered something. It just shows review isn't easy, sorry about the delay and confusion and thanks for sending them.

I've merged them and restarted the appropriate services to allow things to update.

Cheers,

Richard