chore(deps): update all lvh-images main (main) (patch)

[cilium-renovate]

This PR contains the following updates:

Package	Update	Change
quay.io/lvh-images/kernel-images	patch	4.19-20251113.115124 → 4.19-20260112.013353
quay.io/lvh-images/kernel-images	patch	5.4-20251113.115124 → 5.4-20260112.013353
quay.io/lvh-images/kernel-images	patch	5.10-20251113.115124 → 5.10-20260112.013353
quay.io/lvh-images/kernel-images	patch	5.15-20251113.115124 → 5.15-20260112.013353
quay.io/lvh-images/kernel-images	patch	6.1-20251113.115124 → 6.1-20260112.013353
quay.io/lvh-images/kernel-images	patch	6.6-20251113.115124 → 6.6-20260112.013353
quay.io/lvh-images/kernel-images	patch	6.12-20251113.115124 → 6.12-20260112.013353
quay.io/lvh-images/kernel-images	patch	6.18-20260109.091250 → 6.18-20260112.013353
quay.io/lvh-images/kernel-images	patch	bpf-next-20251113.115124 → bpf-next-20260112.013353

---

Configuration

📅 Schedule: Branch creation - "on monday and friday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot.

[netlify]

✅ Deploy Preview for tetragon ready!

Name	Link
🔨 Latest commit	4730c2b
🔍 Latest deploy log	https://app.netlify.com/projects/tetragon/deploys/695d25259cfe3f0007cad86e
😎 Deploy Preview	https://deploy-preview-4353--tetragon.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[mtardy]

pkg.sensors.tracing.TestKprobeKernelStackTrace failed on bpf-next. I'll retry but that might be a real issue since it's only on bpf-next

[mtardy]

Failure on bpf-next has been investigated, it's related to the fact that the syscall call is missing from the kernel stacktrace.

On most kernels it looks like this:

"kernel_stack_trace": [
      {
        "offset": "5",
        "symbol": "__x64_sys_newuname"
      },
      {
        "offset": "53",
        "symbol": "do_syscall_64"
      },
      {
        "offset": "110",
        "symbol": "entry_SYSCALL_64_after_hwframe"
      }
    ],

But lately, on bpf-next, it looks like this:

"kernel_stack_trace": [
      {
        "offset": "164",
        "symbol": "do_syscall_64"
      },
      {
        "offset": "119",
        "symbol": "entry_SYSCALL_64_after_hwframe"
      }
    ],

Jiri thinks it's related to one of his recent patch

seems I broke it with 6d08340d1e35 Revert "perf/x86: Always store regs->ip in perf_callchain_kernel()" ... but I needed that to fix tracepoints 😕 seems 20a0bc10272f might be related..

To be continued... We might just disable it on bpf-next in the meantime.

[mtardy]

Should be good to go thanks to #4495