The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Attila Szasz <szasza.contact@gmail.com>
Cc: Theodore Ts'o <tytso@mit.edu>, Dmitry Vyukov <dvyukov@google.com>,
	cve@kernel.org, linux-cve-announce@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: REJECTED: CVE-2025-0927: heap overflow in the hfs and hfsplus filesystems with manually crafted filesystem
Date: Fri, 9 May 2025 15:37:24 +0200	[thread overview]
Message-ID: <2025050945-prompter-aerobics-136f@gregkh> (raw)
In-Reply-To: <6191c255-84cc-4721-91d1-1884472989f7@gmail.com>

On Fri, May 09, 2025 at 03:18:19PM +0200, Attila Szasz wrote:
> > I would invite that security researchers
> > file CVE's with the *product* as opposed to the upstream open source
> > project.
> 
> The CVE was originally filed for Ubuntu Linux ;)
> Namely, cpe:2.3:o:canonical:ubuntu_linux.
> 
> It was moved to kernel.org CNA territory due to some politics,

There was no "politics" here, no other CNA is allowed to assign bugs
against Linux without going through cve@kernel.org first.  That's just
how the CVE system works, Canonical should not have assigned that from
the beginning.

It happens at times, nothing special here, Oracle did it earlier this
week as well, and we had to reassign a CVE over to us.  Other CNAs have
done it in the past too when they forgot that Linux was a CNA.

> then it was rejected on the same day the bug was fixed upstream.

That was based on the request of the filesystem maintainers, which we
use as the final word on these things.

> Since then, I saw Canonical folks mention that they wanted to
> allocate a new one but needed to obfuscate the description so it no
> longer sounds like a kernel bug.

That's great to hear, please let me know when they do that so that we
all can report them for violating their CNA agreement with CVE.org :)

thanks,

greg k-h

  reply	other threads:[~2025-05-09 13:39 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2025040820-REJECTED-6695@gregkh>
2025-05-09  7:20 ` REJECTED: CVE-2025-0927: heap overflow in the hfs and hfsplus filesystems with manually crafted filesystem Dmitry Vyukov
2025-05-09  7:34   ` Greg KH
2025-05-09  7:47     ` Dmitry Vyukov
2025-05-09  7:55       ` Greg KH
2025-05-09  8:03         ` Dmitry Vyukov
2025-05-09 12:10           ` Theodore Ts'o
2025-05-09 13:18             ` Attila Szasz
2025-05-09 13:37               ` Greg KH [this message]
2025-05-09 14:17               ` Theodore Ts'o
2025-05-12 13:22             ` Dmitry Vyukov
2025-05-12 14:44               ` Theodore Ts'o
2025-05-12 17:17                 ` Attila Szasz
2025-05-13  7:09                 ` Dmitry Vyukov
2025-05-13 12:05                   ` Theodore Ts'o
2025-05-13 16:09                     ` Dmitry Vyukov
2025-05-13 21:43                       ` Theodore Ts'o
2025-05-14  4:53                         ` Dmitry Vyukov
2025-05-21  8:20         ` Dmitry Vyukov
2025-05-23 12:51           ` Greg KH
2025-05-09 14:05       ` Theodore Ts'o

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=2025050945-prompter-aerobics-136f@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=cve@kernel.org \
    --cc=dvyukov@google.com \
    --cc=linux-cve-announce@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=szasza.contact@gmail.com \
    --cc=tytso@mit.edu \
    /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