From: Nix <nix@esperi.org.uk>
To: David Miller <davem@davemloft.net>
Cc: linux-kernel@vger.kernel.org, nhorman@redhat.com
Subject: Re: unhelpful and somewhat scary r8169 boot message in 2.6.33.2 regarding a security fix
Date: Fri, 02 Apr 2010 23:03:44 +0100 [thread overview]
Message-ID: <87aatl7br3.fsf@spindle.srvr.nix> (raw)
In-Reply-To: <20100402.143627.11964909.davem@davemloft.net> (David Miller's message of "Fri, 02 Apr 2010 14:36:27 -0700 (PDT)")
On 2 Apr 2010, David Miller verbalised:
>> but it does not explain *why* changing the MTU is suddenly so bad,
>> when it's worked forever before now without flaw, with no sign of
>> any sort of corruption. Why should we be confined to non-jumbo
>> frames? What are the effects if we do change MTU?
>
> Have a look at CVE-2009-4537
>
> It's a remotely exploitable memory corruptor and potential
> root hole.
That's what I thought, *if* the attackers can inject crafted Ethernet
frames onto your local network. (i.e., they need a crafted Ethernet
frame, not just crafted packet contents.)
prev parent reply other threads:[~2010-04-02 22:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-02 15:19 unhelpful and somewhat scary r8169 boot message in 2.6.33.2 regarding a security fix Nix
2010-04-02 21:36 ` David Miller
2010-04-02 22:03 ` Nix [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=87aatl7br3.fsf@spindle.srvr.nix \
--to=nix@esperi.org.uk \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=nhorman@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.