linux-kernel - Re: Crash during resume of pcie bridge due to infinite loop in ACPICA

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: <b1fadb15d1869bde81315be7488c50dbbc9f7dbd.camel@web.de>
Date: Mon, 24 Nov 2025 23:34:37 +0100
From: Bert Karwatzki <spasswolf@....de>
To: "Rafael J. Wysocki" <rafael@...nel.org>
Cc: Christian König <christian.koenig@....com>, "Mario
 Limonciello (AMD) (kernel.org)"	 <superm1@...nel.org>,
 linux-kernel@...r.kernel.org, linux-next@...r.kernel.org, 
	regressions@...ts.linux.dev, linux-pci@...r.kernel.org, 
	linux-acpi@...r.kernel.org, "Rafael J . Wysocki"
 <rafael.j.wysocki@...el.com>, 	acpica-devel@...ts.linux.dev, Robert Moore
 <robert.moore@...el.com>, Saket Dumbre <saket.dumbre@...el.com>,
 spasswolf@....de
Subject: Re: Crash during resume of pcie bridge due to infinite loop in
 ACPICA

Am Montag, dem 17.11.2025 um 17:40 +0100 schrieb Rafael J. Wysocki:
> 
> Well, what you have found appears to be an issue in the AML bytecode
> interpreter which may be one of two things: (1) a bug in the
> interpreter itself or (2) a bytecode issue that causes the interpreter
> to crash (eventually) and the latter is quite a bit more likely.
> 
> I'd suggest opening a new issue at
> https://github.com/acpica/acpica/issues and attaching the acpidump
> output from the affected system, to start with.

I've reported the bug to ACPICA github:
https://github.com/acpica/acpica/issues/1060

There's no "infinite" loop, but a loop running for 5051 (0x13BB) iteration until its timeout
counter reaches Zero (most likely because the hardware is unresponsive). Soon (only a
handfull of iterations in the walk loop in acpi_ps_parse_aml()) the crash happens. I think
the crash actually occurs inside acpi_ps_parse_loop(), so I wouldn't rule out an interpreter
bug just yet.
 The crash also always happens (if it happens ...) in the 30592th iteration of the walk loop,
so I'm now monitoring the internal of acpi_ps_parse_loop() only in this iteration of the walk
loop. (I've tried to monitor the parse loop before, but that only led to excessive memory
consumption and an activated OOM killer). The debugging code can be found here:
https://gitlab.freedesktop.org/spasswolf/linux-stable/-/commits/amdgpu_suspend_resume?ref_type=heads

So far I've had no crash with this.

Bert Karwatzki