From: Siddh Raman Pant <siddh.raman.pant@oracle.com>
To: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Cc: "cve@kernel.org" <cve@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: CVE-2026-63985: ethtool: eeprom: add more safeties to EEPROM Netlink fallback
Date: Fri, 31 Jul 2026 07:11:10 +0000 [thread overview]
Message-ID: <70c354cc7a676402b25209499b57178766791165.camel@oracle.com> (raw)
In-Reply-To: <2026073151-overeager-wanting-5b0b@gregkh>
[-- Attachment #1: Type: text/plain, Size: 893 bytes --]
On Fri, Jul 31 2026 at 11:09:18 +0530, gregkh@linuxfoundation.org
wrote:
> On Fri, Jul 31, 2026 at 05:14:32AM +0000, Siddh Raman Pant wrote:
> > On Thu, Jul 30 2026 at 18:19:43 +0530, gregkh@linuxfoundation.org
> > wrote:
> >
> > > > IIUC this is a defensive fix. Does it fix any reported problem for it
> > > > to be a CVE?
> > >
> > > As-is, it seems to fix a vulnerability. Do you think that is not the
> > > case, and if so, why?
> >
> > I meant it closes potential only right? Or is there any driver in-tree
> > which had a surprise?
>
> Personally, I do not know, but this is hardware-dependent, right?
It's a generic layer so it should not be.
But looking at the code yet again closely, it seems driver like qede
seems to return success on read failure which would leak information.
Sorry for the noise. It wasn't obvious at start 😅.
Thanks,
Siddh
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2026-07-31 7:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2026071903-CVE-2026-63985-56d0@gregkh>
2026-07-30 12:45 ` Siddh Raman Pant
2026-07-30 12:49 ` gregkh
2026-07-31 5:14 ` Siddh Raman Pant
2026-07-31 5:39 ` gregkh
2026-07-31 7:11 ` Siddh Raman Pant [this message]
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=70c354cc7a676402b25209499b57178766791165.camel@oracle.com \
--to=siddh.raman.pant@oracle.com \
--cc=cve@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®