linux-kernel - Re: Potential info leak: Kernel pointer leak?

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: <3409b71f-9b92-5e53-e87e-1486f493a55e@free.fr>
Date:   Wed, 23 Jan 2019 16:01:14 +0100
From:   Marc Gonzalez <marc.w.gonzalez@...e.fr>
To:     Vinod Koul <vkoul@...nel.org>,
        Fuqian Huang <huangfq.daxian@...il.com>
Cc:     LKML <linux-kernel@...r.kernel.org>,
        MSM <linux-arm-msm@...r.kernel.org>,
        DMA <dmaengine@...r.kernel.org>
Subject: Re: Potential info leak: Kernel pointer leak?

On 23/01/2019 13:24, Vinod Koul wrote:

> On 22-01-19, 21:25, Fuqian Huang wrote:
>
>> Recently I came across some code and it seems to be able to leak kernel address?
>> Is the following code cause info leak in the Linux kernel?
>> linux-4.14.90
> 
> Doesn't %p not print kernel addresses anymore, see
> Documentation/core-api/printk-formats.rst

Commit ad67b74d2469d9b82aaa ("printk: hash addresses printed with %p")
was merged in v4.15-rc2 and not backported to v4.14 AFAICT.

Regards.