linux-kernel - Re: unhelpful and somewhat scary r8169 boot message in 2.6.33.2 regarding a security fix

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <87aatl7br3.fsf@spindle.srvr.nix>
Date:	Fri, 02 Apr 2010 23:03:44 +0100
From:	Nix <nix@...eri.org.uk>
To:	David Miller <davem@...emloft.net>
Cc:	linux-kernel@...r.kernel.org, nhorman@...hat.com
Subject: Re: unhelpful and somewhat scary r8169 boot message in 2.6.33.2 regarding a security fix

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.)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/