linux-kernel - Re: [PATCH] pktgen: Remove a dangerous debug print.

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <20101027.123043.241428851.davem@davemloft.net>
Date:	Wed, 27 Oct 2010 12:30:43 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	nelhage@...lice.com
Cc:	robert.olsson@....uu.se, linux-kernel@...r.kernel.org,
	netdev@...r.kernel.org, eugene@...hat.com
Subject: Re: [PATCH] pktgen: Remove a dangerous debug print.

From: Nelson Elhage <nelhage@...lice.com>
Date: Wed, 27 Oct 2010 15:28:08 -0400

> How would you feel about limiting the debug print to at most, say, 512 or 1024
> bytes? Even if it's only accessible to root by default, I don't a userspace
> program should be able to accidentally corrupt the kernel stack by writing too
> many bytes to a file in /proc.

Why not?  He can just as easily "cat whatever >/dev/kmem" or similar?
And I'm sure there are other proc files that can cause similar damage
such as the PCI device control files.
--
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/