From: Jakub Kicinski <kuba@kernel.org>
To: Jamal Hadi Salim <jhs@mojatatu.com>
Cc: netdev@vger.kernel.org, jiri@resnulli.us,
xiyou.wangcong@gmail.com, davem@davemloft.net,
edumazet@google.com, petrm@mellanox.com, security@kernel.org
Subject: Re: [PATCH net 1/1] net: sched: fix ets qdisc OOB Indexing
Date: Fri, 10 Jan 2025 15:50:55 -0800 [thread overview]
Message-ID: <20250110155055.04ddaa2d@kernel.org> (raw)
In-Reply-To: <20250110153546.41344-1-jhs@mojatatu.com>
On Fri, 10 Jan 2025 10:35:46 -0500 Jamal Hadi Salim wrote:
> Haowei Yan <g1042620637@gmail.com> found that ets_class_from_arg() can
> index an Out-Of-Bound class in ets_class_from_arg() when passed clid of
> 0. The overflow may cause local privilege escalation.
ets_class_leaf() does not nul-check the result, which crashes
the kernel during selftests.
--
pw-bot: cr
next prev parent reply other threads:[~2025-01-10 23:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-10 15:35 [PATCH net 1/1] net: sched: fix ets qdisc OOB Indexing Jamal Hadi Salim
2025-01-10 15:48 ` Petr Machata
2025-01-10 16:24 ` Eric Dumazet
2025-01-10 23:50 ` Jakub Kicinski [this message]
2025-01-11 12:59 ` Jamal Hadi Salim
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=20250110155055.04ddaa2d@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=petrm@mellanox.com \
--cc=security@kernel.org \
--cc=xiyou.wangcong@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).