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: <c8f837f5-16b1-a5da-c687-a95d2ec42fa0@gmail.com>
Date: Wed, 10 Jul 2024 12:15:18 +0300
From: Sergei Shtylyov <sergei.shtylyov@...il.com>
To: Wolfram Sang <wsa+renesas@...g-engineering.com>,
 linux-renesas-soc@...r.kernel.org
Cc: Pierre-Yves MORDRET <pierre-yves.mordret@...com>,
 Alain Volmat <alain.volmat@...com>, linux-i2c@...r.kernel.org,
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH] i2c: mark HostNotify target address as used

On 7/10/24 11:55 AM, Wolfram Sang wrote:

> I2C core handles the local target for receiving HostNotify alerts. There
> is no separate driver bound to that address. That means userspace can
> access it if desired, leading to further complications if controllers
> are not capable of reading their own local target. Bind the local target
> to the dummy driver so it will marked as "handled by the kernel" if the
                                ^ be? :-)

> HostNotify feature is used. That protects aginst userspace access and
> prevents other drivers binding to it.
> 
> Fixes: 2a71593da34d ("i2c: smbus: add core function handling SMBus host-notify")
> Signed-off-by: Wolfram Sang <wsa+renesas@...g-engineering.com>
[...]

MBR, Sergey

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ