linux-kernel - Re: [PATCH] riscv: kprobes: Fix probe address validation

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: 
 <176006323925.354358.7825559946978649755.git-patchwork-notify@kernel.org>
Date: Fri, 10 Oct 2025 02:27:19 +0000
From: patchwork-bot+linux-riscv@...nel.org
To: Fabian Vogt <fvogt@...e.de>
Cc: linux-riscv@...ts.infradead.org, linux-kernel@...r.kernel.org,
 guoren@...nel.org, marvin.friedrich@...e.com, alex@...ti.fr,
 aou@...s.berkeley.edu, palmer@...belt.com, paul.walmsley@...ive.com,
 bjorn@...nel.org
Subject: Re: [PATCH] riscv: kprobes: Fix probe address validation

Hello:

This patch was applied to riscv/linux.git (fixes)
by Paul Walmsley <pjw@...nel.org>:

On Wed, 10 Sep 2025 17:25:13 +0200 you wrote:
> When adding a kprobe such as "p:probe/tcp_sendmsg _text+15392192",
> arch_check_kprobe would start iterating all instructions starting from
> _text until the probed address. Not only is this very inefficient, but
> literal values in there (e.g. left by function patching) are
> misinterpreted in a way that causes a desync.
> 
> Fix this by doing it like x86: start the iteration at the closest
> preceding symbol instead of the given starting point.
> 
> [...]

Here is the summary with links:
  - riscv: kprobes: Fix probe address validation
    https://git.kernel.org/riscv/c/9e68bd803fac

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html