Conversation
kernellogger@fosstodon.org

Thorsten Leemhuis (acct. 1/4)

In case anyone wonders if the CVE team releases CVEs before the problem is fixed in stable and longterm series:

Yes, they sometimes do this when the fix hit the mainline ; not that often from a quick look, but yesterday I noticed two such cases by chance:

https://lore.kernel.org/all/2024040122-CVE-2024-26653-7903@gregkh/

https://lore.kernel.org/all/2024040142-CVE-2024-26654-aa6c@gregkh/

2
2
1
vbabka

Vlastimil Babka

Reply to @kernellogger@fosstodon.org
@kernellogger would you know if the fixes were in stable queues (not yet released) at the time?
1
0
0
kernellogger@fosstodon.org

Thorsten Leemhuis (acct. 1/4)

Reply to @vbabka

@vbabka

good question!

For those two linked above that was easy to check, as they still are in the stable queues right now.

For the others: no idea.

0
0
1
gregkh

Greg K-H

Reply to @kernellogger@fosstodon.org
@kernellogger When someone asks us for a CVE id for a valid issue, we assign it as the process is independent of stable kernel releases. For issues that are not yet in a Linus release, we usually just reserve the id and then publish it when it has hit a -rc release, like what happened for these two CVEs.

Now when stable releases happen, we go and updated all existing CVEs to add the needed information where the fix has landed in stable kernels, and push the updates to the cve.org website in json format.

So for CVE-2024-26653, on the cve.org site, you will see that the latest stable info is included, while the older email link you provided, only says that the -rc2 is covered. But if you look in the git archive, the mbox announcement is now updated: https://git.kernel.org/pub/scm/linux/security/vulns.git/tree/cve/published/2024/CVE-2024-26653.mbox

Such is the lifecycle of a kernel change, they get backported all the time...
1
4
10
aho@mastodon.social

Aho

Reply to @gregkh

@gregkh @kernellogger thanks Greg

0
0
0
About social.kernel.org

Terms of service

  1. Please do not use this service in violation of the Linux Kernel Code of Conduct. Doing so will result in your account suspension with the referral of the matter to the CoC committee.

  2. "Repeating"/"boosting" someone else's status on this platform will be treated as endorsement and will fall under rule #1.

  3. You are encouraged to use this platform to promote your work on the Linux Kernel, but there is no restriction on permitted topics (with the exception of anything covered by #1 above).

  4. There is no requirement to post in English, but it should be considered the primary language of communication on this platform.

Privacy notice

The admins of this service have access to all posted statuses. They aren't looking, but if it's something they shouldn't know about, then you should not post it on this platform.

Please see the Linux Foundation Privacy Policy, which applies to this platform as well.

Getting your own account

If you would like an account on this instance, please check that the following applies to you:

  • You are listed in MAINTAINERS or CREDITS

  • OR: You have a kernel.org account or email address

  • OR: You have a long and established history of involvement with the Linux Kernel

If the above is true and you agree with the Terms of Service and Privacy Notice listed above, please use these instructions to request an account: