linux-kernel - Re: [PATCH 02/11] ASoC: tlv320adcx140: fix null pointer

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: <0a1c34ae-16f2-4e03-b8e6-6a27c811a1e5@sirena.org.uk>
Date: Wed, 17 Dec 2025 13:58:09 +0000
From: Mark Brown <broonie@...nel.org>
To: Sascha Hauer <s.hauer@...gutronix.de>
Cc: Shenghao Ding <shenghao-ding@...com>, Kevin Lu <kevin-lu@...com>,
	Baojun Xu <baojun.xu@...com>, Liam Girdwood <lgirdwood@...il.com>,
	Jaroslav Kysela <perex@...ex.cz>, Takashi Iwai <tiwai@...e.com>,
	Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
	Clark Williams <clrkwllms@...nel.org>,
	Steven Rostedt <rostedt@...dmis.org>, Rob Herring <robh@...nel.org>,
	Krzysztof Kozlowski <krzk+dt@...nel.org>,
	Conor Dooley <conor+dt@...nel.org>, Andrew Davis <afd@...com>,
	Dan Murphy <dmurphy@...com>, linux-sound@...r.kernel.org,
	linux-kernel@...r.kernel.org, Kevin Lu <luminlong@....com>,
	linux-rt-devel@...ts.linux.dev, devicetree@...r.kernel.org,
	Emil Svendsen <emas@...g-olufsen.dk>
Subject: Re: [PATCH 02/11] ASoC: tlv320adcx140: fix null pointer

On Wed, Dec 17, 2025 at 02:54:52PM +0100, Sascha Hauer wrote:

> Kernel OOPS:
> [  438.223704] Unable to handle kernel read from unreadable memory at virtual address 0000000000000018
> [  438.232776] Mem abort info:
> [  438.235569]   ESR = 0x0000000096000004
> [  438.239326]   EC = 0x25: DABT (current EL), IL = 32 bits
> [  438.244646]   SET = 0, FnV = 0
> [  438.247764]   EA = 0, S1PTW = 0
> [  438.250906]   FSC = 0x04: level 0 translation fault

Please think hard before including complete backtraces in upstream
reports, they are very large and contain almost no useful information
relative to their size so often obscure the relevant content in your
message. If part of the backtrace is usefully illustrative (it often is
for search engines if nothing else) then it's usually better to pull out
the relevant sections.

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)