linux-kernel - [PATCH 0/2] nvmem: Fix reading MAC address from OCOTP on i.MX

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

Message-ID: <20250711120110.12885-1-ceggers@arri.de>
Date: Fri, 11 Jul 2025 13:55:46 +0200
From: Christian Eggers <ceggers@...i.de>
To: Srinivas Kandagatla <srini@...nel.org>, Shawn Guo <shawnguo@...nel.org>,
	Sascha Hauer <s.hauer@...gutronix.de>, Dmitry Baryshkov <lumag@...nel.org>,
	Rafał Miłecki <rafal@...ecki.pl>
CC: Pengutronix Kernel Team <kernel@...gutronix.de>, Fabio Estevam
	<festevam@...il.com>, Greg Kroah-Hartman <gregkh@...uxfoundation.org>, Sasha
 Levin <sashal@...nel.org>, <imx@...ts.linux.dev>,
	<linux-arm-kernel@...ts.infradead.org>, <linux-kernel@...r.kernel.org>
Subject: [PATCH 0/2] nvmem: Fix reading MAC address from OCOTP on i.MX

There is a (minor?) regression (also propagated via -stable series)
which causes wrong Ethernet MAC addresses read from internal OTP.

Probably this doesn't affect many system as usually the MAC address is
already read from OTP (called OCOTP on i.MX) by the boot loader and
then passed verbatim to the kernel via device tree fixups. Only if the
MAC isn't present in the device tree, the kernel reads it from the OTP
itself.