Calling redirect from a React Server Component to an intercepted route causes infinite rerendering loop

Link to the code that reproduces this issue

https://github.com/denexapp/redirect-from-rsc-to-intercepted-route-bug

To Reproduce

1. Start the dev server
2. Open the main page and click on the Link
3. Wait for 30 seconds
4. Watch the terminal and the browser console for a list of errors / rerender messages

Current vs. Expected behavior

Expected behaviour:

A component from the intercepted route renders once

1. Current behaviour:

Component gets rerendered in a loop

1. Navigation works incorrectly, causing weird errors and sometimes crashing the app

Provide environment information

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 24.1.0: Thu Oct 10 21:06:57 PDT 2024; root:xnu-11215.41.3~3/RELEASE_ARM64_T6041
  Available memory (MB): 36864
  Available CPU cores: 14
Binaries:
  Node: 22.9.0
  npm: 10.8.3
  Yarn: N/A
  pnpm: 9.12.1
Relevant Packages:
  next: 15.1.6 // Latest available version is detected (15.1.6).
  eslint-config-next: 15.1.2
  react: 19.0.0
  react-dom: 19.0.0
  typescript: 5.7.3
Next.js Config:
  output: N/A

Which area(s) are affected? (Select all that apply)

Redirects

Which stage(s) are affected? (Select all that apply)

next dev (local), next build (local), next start (local), Other (Deployed), Vercel (Deployed)

Additional context

Original issue https://github.com/vercel/next.js/issues/61341

Recreating it as it's a critical problem that makes redirect function very dangerous to use in Next 15.

Start with the linked reproduction repository and follow its redirect from the React Server Component to the intercepted route while running the dev server. Compare the behavior with original issue #61341; done means the intercepted component renders once, navigation completes, and the terminal and browser show no rerender loop or related errors.