[<prev] [next>] [day] [month] [year] [list]
Message-Id: <20251001173908.905725-1-dave.hansen@linux.intel.com>
Date: Wed, 1 Oct 2025 10:39:08 -0700
From: Dave Hansen <dave.hansen@...ux.intel.com>
To: torvalds@...ux-foundation.org
Cc: x86@...nel.org,
linux-kernel@...r.kernel.org,
Dave Hansen <dave.hansen@...ux.intel.com>
Subject: [GIT PULL] x86/entry for 6.18-rc1
Hi Linus,
Please a pair of x86/entry changes for 6.18-rc1. The FRED one adjusts
the kernel to the latest spec. The spec change prevents attackers from
abusing kernel entry points.
The second one came about because of the LASS work[1]. It moves the
vsyscall emulation code away from depending on X86_PF_INSTR which is
not available on some CPUs. Those CPUs are pretty obscure these days,
but this still seems like the right thing to do. It also makes this
code consistent with some things that the LASS code is going to do.
1. https://lore.kernel.org/lkml/20250620135325.3300848-1-kirill.shutemov@linux.intel.com/
--
The following changes since commit 8f5ae30d69d7543eee0d70083daf4de8fe15d585:
Linux 6.17-rc1 (2025-08-10 19:41:16 +0300)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/x86_entry_for_6.18-rc1
for you to fetch changes up to 3da01ffe1aeaa0d427ab5235ba735226670a80d9:
x86/fred: Remove ENDBR64 from FRED entry points (2025-08-13 15:05:32 -0700)
----------------------------------------------------------------
- Use RIP instead of X86_PF_INSTR for vsyscall emulation
- Remove ENDBR64 from FRED entry points
----------------------------------------------------------------
Kirill A. Shutemov (1):
x86/vsyscall: Do not require X86_PF_INSTR to emulate vsyscall
Xin Li (Intel) (1):
x86/fred: Remove ENDBR64 from FRED entry points
arch/x86/entry/entry_64_fred.S | 2 +-
arch/x86/entry/vsyscall/vsyscall_64.c | 17 ++++++++++++++---
2 files changed, 15 insertions(+), 4 deletions(-)
Powered by blists - more mailing lists