diff --git a/board/mister/de10nano/patches/linux/linux.hash b/board/mister/de10nano/patches/linux/linux.hash
index bd274e0d..a2428162 100644
--- a/board/mister/de10nano/patches/linux/linux.hash
+++ b/board/mister/de10nano/patches/linux/linux.hash
@@ -36,7 +36,7 @@
 # A kernel bump (manual, or Renovate under P4.7) MUST update this line from the
 # signed manifest for the new version, or the build will fail closed -- which is
 # the intended behaviour.
-sha256  ae826f33111fea6f1d279dde7299d7463c8dfd204aeb75a8fb5432bc60a28191  linux-6.18.49.tar.xz
+sha256  d2fc041dab4e11d9645e3ba53be058faa52b8ce28a8a97c889bb2cacee170461  linux-6.18.50.tar.xz
 
 # WHERE THE RT / BETA KERNEL HASH COMES FROM -- as of 2026-08-17, the SAME
 # signed-manifest rule as the stable pin above. This entry belongs to the RT
diff --git a/configs/fragments/de10nano.fragment b/configs/fragments/de10nano.fragment
index 8cde3d12..8225756a 100644
--- a/configs/fragments/de10nano.fragment
+++ b/configs/fragments/de10nano.fragment
@@ -27,7 +27,7 @@ BR2_GLOBAL_PATCH_DIR="$(BR2_EXTERNAL_MISTER_PATH)/board/mister/de10nano/patches"
 # --- Kernel stanza (docs/buildroot-config.md §3.4) ---
 # Renovate bumps the version line (renovate.json, kernel-longterm-6.18);
 # the tarball hash follows via .github/workflows/renovate-hash-sync.yml.
-BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="6.18.49"
+BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="6.18.50"
 BR2_LINUX_KERNEL_PATCH="$(BR2_EXTERNAL_MISTER_PATH)/board/mister/de10nano/linux-patches"
 BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG=y
 BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE="$(BR2_EXTERNAL_MISTER_PATH)/board/mister/de10nano/linux.config"