From: Prabhakar Pujeri <prabhakar.pujeri@dell.com>
To: netdev@vger.kernel.org
Cc: Prabhakar Pujeri <prabhakar.pujeri@dell.com>,
Michal Kubecek <mkubecek@suse.cz>
Subject: [PATCH ethtool 0/2] harden module EEPROM length handling
Date: Mon, 31 Aug 2026 10:41:22 +0000 [thread overview]
Message-ID: <20260831104125.2203-1-prabhakar.pujeri@dell.com> (raw)
These patches keep module EEPROM reads within the lengths reported by the
kernel. The netlink path now limits its copy to the received attribute,
and the ioctl path validates offset and length arithmetic before allocating
its response buffer.
Tested with make check in the default and --disable-netlink builds.
Prabhakar Pujeri (2):
netlink: module-eeprom: clamp data length to attribute payload size
ethtool: validate module EEPROM offset and length
ethtool.c | 9 ++++++++-
netlink/module-eeprom.c | 8 ++++++++
2 files changed, 16 insertions(+), 1 deletion(-)
--
2.55.0
next reply other threads:[~2026-08-31 10:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 10:41 Prabhakar Pujeri [this message]
2026-08-31 10:41 ` [PATCH ethtool 1/2] netlink: module-eeprom: clamp data length to attribute payload size Prabhakar Pujeri
2026-08-31 10:41 ` [PATCH ethtool 2/2] ethtool: validate module EEPROM offset and length Prabhakar Pujeri
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=20260831104125.2203-1-prabhakar.pujeri@dell.com \
--to=prabhakar.pujeri@dell.com \
--cc=mkubecek@suse.cz \
--cc=netdev@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