From: Paul Moore <paul@paul-moore.com>
To: Ondrej Mosnacek <omosnace@redhat.com>
Cc: netdev@vger.kernel.org, linux-security-module@vger.kernel.org
Subject: Re: [PATCH 1/2] cipso: fix total option length computation
Date: Tue, 16 Apr 2024 14:39:37 -0400 [thread overview]
Message-ID: <0a814ce3acdea2c07cef6f7c31008e19@paul-moore.com> (raw)
In-Reply-To: <20240416152913.1527166-2-omosnace@redhat.com>
On Apr 16, 2024 Ondrej Mosnacek <omosnace@redhat.com> wrote:
>
> As evident from the definition of ip_options_get(), the IP option
> IPOPT_END is used to pad the IP option data array, not IPOPT_NOP. Yet
> the loop that walks the IP options to determine the total IP options
> length in cipso_v4_delopt() doesn't take it into account.
>
> Fix it by recognizing the IPOPT_END value as the end of actual options.
> Also add safety checks in case the options are invalid/corrupted.
>
> Fixes: 014ab19a69c3 ("selinux: Set socket NetLabel based on connection endpoint")
> Signed-off-by: Ondrej Mosnacek <omosnace@redhat.com>
> ---
> net/ipv4/cipso_ipv4.c | 19 ++++++++++++++-----
> 1 file changed, 14 insertions(+), 5 deletions(-)
>
> diff --git a/net/ipv4/cipso_ipv4.c b/net/ipv4/cipso_ipv4.c
> index 8b17d83e5fde4..75b5e3c35f9bf 100644
> --- a/net/ipv4/cipso_ipv4.c
> +++ b/net/ipv4/cipso_ipv4.c
> @@ -2012,12 +2012,21 @@ static int cipso_v4_delopt(struct ip_options_rcu __rcu **opt_ptr)
> * from there we can determine the new total option length */
> iter = 0;
> optlen_new = 0;
> - while (iter < opt->opt.optlen)
> - if (opt->opt.__data[iter] != IPOPT_NOP) {
> - iter += opt->opt.__data[iter + 1];
> - optlen_new = iter;
> - } else
> + while (iter < opt->opt.optlen) {
> + if (opt->opt.__data[iter] == IPOPT_END) {
> + break;
> + } else if (opt->opt.__data[iter] == IPOPT_NOP) {
> iter++;
> + } else {
> + if (WARN_ON(opt->opt.__data[iter + 1] < 2))
> + iter += 2;
> + else
> + iter += opt->opt.__data[iter + 1];
> + optlen_new = iter;
I worry that WARN_ON(), especially in conjunction with the one below,
could generate a lot of noise on the console and system logs, let's
be a bit more selective about what we check and report on. Presumably
the options have already gone through a basic sanity check so there
shouldn't be anything too scary in there.
if (opt == IPOPT_END) {
/* ... */
} else if (opt == IPOPT_NOP) {
/* ... */
} else {
iter += opt[iter + 1];
optlen_new = iter;
}
> + }
> + }
> + if (WARN_ON(optlen_new > opt->opt.optlen))
> + optlen_new = opt->opt.optlen;
This is also probably not really necessary, but it bothers me less.
> hdr_delta = opt->opt.optlen;
> opt->opt.optlen = (optlen_new + 3) & ~3;
> hdr_delta -= opt->opt.optlen;
> --
> 2.44.0
--
paul-moore.com
next prev parent reply other threads:[~2024-04-16 18:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-16 15:29 [PATCH 0/2] cipso: make cipso_v4_skbuff_delattr() fully remove the CIPSO options Ondrej Mosnacek
2024-04-16 15:29 ` [PATCH 1/2] cipso: fix total option length computation Ondrej Mosnacek
2024-04-16 18:39 ` Paul Moore [this message]
2024-04-17 12:49 ` Ondrej Mosnacek
2024-04-25 21:15 ` Paul Moore
2024-04-16 15:29 ` [PATCH 2/2] cipso: make cipso_v4_skbuff_delattr() fully remove the CIPSO options Ondrej Mosnacek
2024-04-16 18:39 ` Paul Moore
2024-04-17 13:03 ` Ondrej Mosnacek
2024-04-25 21:48 ` Paul Moore
2024-05-14 11:29 ` Ondrej Mosnacek
2024-05-17 19:49 ` Paul Moore
2024-06-07 15:47 ` Ondrej Mosnacek
2024-06-11 21:01 ` Paul Moore
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=0a814ce3acdea2c07cef6f7c31008e19@paul-moore.com \
--to=paul@paul-moore.com \
--cc=linux-security-module@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=omosnace@redhat.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).