[Query] Looking for comments on CONFIG_SPI_SPIDEV and CONFIG_I2C_CHARDEV interfaces security
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: [Query] Looking for comments on CONFIG_SPI_SPIDEV and CONFIG_I2C_CHARDEV interfaces security
- From: Prasad Sodagudi <quic_psodagud@xxxxxxxxxxx>
- Date: Tue, 31 May 2022 08:25:26 -0700
- Cc: <linux-kernel@xxxxxxxxxxxxxxx>
- User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.8.1
Hi All,
I am working on an IoT solution and would like to understand security
impact of these two CONFIG_SPI_SPIDEV and CONFIG_I2C_CHARDEV interfaces
of Linux. If a driver is developed from userspace for /dev/spiX.Y or
/dev/i2c interfaces, are there any security concerns ?
Userspace driver is to control external SPI slave on board. I heard that
these interfaces allows access to any of these type of devices on board.
How to avoid accessing any of these type of unwanted device access
from userspace ? Can Selinux or any mechanism control access to other
these type of devices from user-space ?
Please share your comments/findings on these two interfaces related to
security. If community had posted any security related discussions with
these interfaces, please share details to improve understanding.
-Thanks, Prasad
[Index of Archives]
[Linux Kernel]
[Linux ARM (vger)]
[Linux ARM MSM]
[Linux Omap]
[Linux Arm]
[Linux Tegra]
[Fedora ARM]
[Linux for Samsung SOC]
[eCos]
[Linux Fastboot]
[Gcc Help]
[Git]
[DCCP]
[IETF Announce]
[Security]
[Linux MIPS]
[Yosemite Campsites]
|