From: "Vegard Nossum" <vegard.nossum@gmail.com>
To: "David S. Miller" <davem@davemloft.net>
Cc: "Thomas Graf" <tgraf@suug.ch>, "Eugene Teo" <eugeneteo@kernel.sg>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Al Viro" <viro@zeniv.linux.org.uk>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] netlink: fix (theoretical) overrun in message iteration
Date: Sun, 21 Dec 2008 15:44:40 +0100 [thread overview]
Message-ID: <19f34abd0812210644j6f11717bi84238d172feed8b6@mail.gmail.com> (raw)
In-Reply-To: <20081221134218.GA7959@localhost.localdomain>
On Sun, Dec 21, 2008 at 2:42 PM, Vegard Nossum <vegard.nossum@gmail.com> wrote:
> From bb805d89e84ddb11c9bb58afcfd9a6b37bbe5a9b Mon Sep 17 00:00:00 2001
> From: Vegard Nossum <vegard.nossum@gmail.com>
> Date: Sun, 21 Dec 2008 14:20:49 +0100
> Subject: [PATCH] netlink: fix (theoretical) overrun in message iteration
>
> See commit 1045b03e07d85f3545118510a587035536030c1c for a detailed
> explanation of why this patch is necessary.
>
> In short, nlmsg_next() can make "remaining" go negative, and the
> remaining >= sizeof(...) comparison will promote "remaining" to an
> unsigned type, which means that the expression will evaluate to
> true for negative numbers, even though it was not intended.
>
> I put "theoretical" in the title because I have no evidence that
> this can actually happen, but I suspect that a crafted netlink
> packet can trigger some badness.
nlmsg
--
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
-- E. W. Dijkstra, EWD1036
next prev parent reply other threads:[~2008-12-21 14:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-21 13:42 Vegard Nossum
2008-12-21 14:44 ` Vegard Nossum [this message]
2008-12-21 14:46 ` Vegard Nossum
2008-12-26 1:20 ` David Miller
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=19f34abd0812210644j6f11717bi84238d172feed8b6@mail.gmail.com \
--to=vegard.nossum@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=eugeneteo@kernel.sg \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tgraf@suug.ch \
--cc=viro@zeniv.linux.org.uk \
/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®