linux-kernel - Re: shouldn't a non-privileged malformed sprintf crashes the kernel

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: <CAFLxGvw09tuOcwXN2kD0kH=SJ_-ho52aDS6Sut-z8dknGkPiqA@mail.gmail.com>
Date:	Sun, 17 Feb 2013 12:58:13 +0100
From:	richard -rw- weinberger <richard.weinberger@...il.com>
To:	Toralf Förster <toralf.foerster@....de>
Cc:	Linux Kernel <linux-kernel@...r.kernel.org>,
	boinc_dev@....berkeley.edu
Subject: Re: shouldn't a non-privileged malformed sprintf crashes the kernel

On Sun, Feb 17, 2013 at 11:42 AM, Toralf Förster <toralf.foerster@....de> wrote:
> This is the 2nd time in a row that a stable kernel (3.7.8 currently) crashes in such a way
> that even the sys-rq key doesn't work any longer.
> Found nothing in the log. The screen shot is here [1]. First time this issue was reported in [2].
>
> The bug seems to be triggered by the BOINC client - I'm running the alpha version of it [3].
>
> I'm wondering whether the sprintf issue discussed in [4] is the trigger for the bug
> (I attached that message here b/c the BOINC devs doesn't allow just even read access
> to the mail archive w/o registering).

Why "non-privileged malformed sprintf"? This makes no sense to me.
Your kernel crashed both times while reading from /proc/interrupts.

-- 
Thanks,
//richard
--
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/