mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Guikun Yang <yangguikun19@qq.com>
Cc: "Peter Zijlstra (Intel)" <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Luis Chamberlain <mcgrof@kernel.org>,
	Petr Pavlu <petr.pavlu@suse.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	x86@kernel.org, linux-modules@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [Bug report] x86-64 apply_returns() decodes attacker-controlled addresses from unvalidated .return_sites entries - wild read on module load
Date: Fri, 13 Nov 2026 22:20:42 -0800	[thread overview]
Message-ID: <20261114062042.GAavf9ui9D9bThqdYy@fat_crate.local> (raw)
In-Reply-To: <tencent_4AF4D4976F851143A745D39A286A1FC2A807@qq.com>

On Sat, Nov 14, 2026 at 04:00:00PM +0800, Guikun Yang wrote:
> From: Guikun Yang <yangguikun19@qq.com>
> To: "Peter Zijlstra (Intel)" <peterz@infradead.org>,
>     Ingo Molnar <mingo@redhat.com>,
>     Arnaldo Carvalho de Melo <acme@kernel.org>
> Cc: Luis Chamberlain <mcgrof@kernel.org>, Petr Pavlu <petr.pavlu@suse.com>,
>     Thomas Gleixner <tglx@linutronix.de>, Borislav Petkov <bp@alien8.de>,
>     Dave Hansen <dave.hansen@linux.intel.com>, x86@kernel.org,
>     linux-modules@vger.kernel.org, linux-kernel@vger.kernel.org
> Subject: [Bug report] x86-64 apply_returns() decodes attacker-controlled
>  addresses from unvalidated .return_sites entries - wild read on module load
> 
> Hi Peter, Ingo,
> 
> The .return_sites section of a module is consumed by apply_returns()
> without any validation of the computed addresses. Each entry is an s32
> relative offset whose final value is fully attacker-controlled via the
> R_X86_64_PC32 relocation addend (that relocation path has no overflow

If you can load modules on a system, you've already won.

Why would you even do some silly exploit like that?

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette

  reply	other threads:[~2026-11-14  6:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mod-r-offset-oob-20261113@qq.com>
2026-11-14  2:00 ` [Bug report] srcu_module_coming() dereferences unvalidated ___srcu_struct_ptrs entries - wild kernel-memory write " Guikun Yang
     [not found] ` <srcu-struct-ptrs-wildwrite-20261114@qq.com>
2026-11-14  8:00   ` [Bug report] x86-64 apply_returns() decodes attacker-controlled addresses from unvalidated .return_sites entries - wild read " Guikun Yang
2026-11-14  6:20     ` Borislav Petkov [this message]
     [not found] ` <tencent_0836A27053A7BED946E49CE04D27A31E7D09@qq.com>
2026-11-16 18:11   ` [Bug report] srcu_module_coming() dereferences unvalidated ___srcu_struct_ptrs entries - wild kernel-memory write " Paul E. McKenney
2026-11-17  2:00   ` [PATCH] srcu: Validate ___srcu_struct_ptrs entries against the module range Guikun Yang
2026-11-17 16:24     ` Bradley Morgan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20261114062042.GAavf9ui9D9bThqdYy@fat_crate.local \
    --to=bp@alien8.de \
    --cc=acme@kernel.org \
    --cc=dave.hansen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-modules@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=petr.pavlu@suse.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    --cc=yangguikun19@qq.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®