linux-kernel - Re: [PATCH v2] platform/x86: intel: punit

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: <176399165439.1782.14998465716898808944.b4-ty@linux.intel.com>
Date: Mon, 24 Nov 2025 15:40:54 +0200
From: Ilpo Järvinen <ilpo.jarvinen@...ux.intel.com>
To: Qipeng Zha <qipeng.zha@...el.com>, 
 Dan Carpenter <dan.carpenter@...aro.org>
Cc: Hans de Goede <hansg@...nel.org>, Darren Hart <dvhart@...ux.intel.com>, 
 Andy Shevchenko <andriy.shevchenko@...ux.intel.com>, 
 platform-driver-x86@...r.kernel.org, linux-kernel@...r.kernel.org, 
 kernel-janitors@...r.kernel.org
Subject: Re: [PATCH v2] platform/x86: intel: punit_ipc: fix memory
 corruption

On Fri, 21 Nov 2025 20:51:28 +0300, Dan Carpenter wrote:

> This passes the address of the pointer "&punit_ipcdev" when the intent
> was to pass the pointer itself "punit_ipcdev" (without the ampersand).
> This means that the:
> 
> 	complete(&ipcdev->cmd_complete);
> 
> in intel_punit_ioc() will write to a wrong memory address corrupting it.
> 
> [...]


Thank you for your contribution, it has been applied to my local
review-ilpo-fixes branch. Note it will show up in the public
platform-drivers-x86/review-ilpo-fixes branch only once I've pushed my
local branch there, which might take a while.

The list of commits applied:
[1/1] platform/x86: intel: punit_ipc: fix memory corruption
      commit: 9b9c0adbc3f8a524d291baccc9d0c04097fb4869

--
 i.