[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <167046481660.18277.3545657496706146746.git-patchwork-notify@kernel.org>
Date: Thu, 08 Dec 2022 02:00:16 +0000
From: patchwork-bot+chrome-platform@...nel.org
To: Victor Ding <victording@...omium.org>
Cc: linux-kernel@...r.kernel.org, chrome-platform@...ts.linux.dev,
pmalani@...omium.org, groeck@...omium.org, dustin@...ett.net,
gustavoars@...nel.org, gregkh@...uxfoundation.org,
sebastian.reichel@...labora.com, dnojiri@...omium.org,
lee.jones@...aro.org, bleung@...omium.org,
tinghan.shen@...iatek.com, tzungbi@...nel.org,
enric.balletbo@...labora.com, heikki.krogerus@...ux.intel.com
Subject: Re: [PATCH v2] platform/chrome: cros_ec_typec: zero out stale pointers
Hello:
This patch was applied to chrome-platform/linux.git (for-next)
by Tzung-Bi Shih <tzungbi@...nel.org>:
On Wed, 7 Dec 2022 09:39:40 +0000 you wrote:
> `cros_typec_get_switch_handles` allocates four pointers when obtaining
> type-c switch handles. These pointers are all freed if failing to obtain
> any of them; therefore, pointers in `port` become stale. The stale
> pointers eventually cause use-after-free or double free in later code
> paths. Zeroing out all pointer fields after freeing to eliminate these
> stale pointers.
>
> [...]
Here is the summary with links:
- [v2] platform/chrome: cros_ec_typec: zero out stale pointers
https://git.kernel.org/chrome-platform/c/9a8aadcf0b45
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists