View Issue Details

IDProjectCategoryView StatusLast Update
0009962Kali LinuxKali Package Bugpublic2026-11-07 14:38
ReporterReginaSomnia Assigned To 
PrioritynormalSeverityminorReproducibilityhave not tried
Status newResolutionopen 
Summary0009962: linux-rpi stuck at 6.12.34 since July 2025, missing CVE-2026-98432 and later fixes
Description

The Raspberry Pi kernel in kali-rolling, linux-rpi 1:6.12.34-1+rpt1+0kali2, was last imported on 2025-07-23 and hasn't been updated. raspi-firmware does keep getting imported (1:1.20260915-1~bookworm is in kali-rolling), but the kernel doesn't

Raspberry Pi's own archive has 1:6.12.115-1+rpt1 (bookworm) and 1:6.18.60-1+rpt1 (trixie) already

Kali on a Raspberry Pi is missing about 15 months of kernel fixes, including CVE-2026-98432 (IPv4 TCP use-after-free, CVSS 9.8, reachable through any listening TCP port), which was fixed upstream in 6.12.113 and 6.18.56

Fresh installs are also affected, kali-linux-2026.3-raspberry-pi-arm64.img installs linux-image-rpi-v8 from kali-rolling, and it boots 6.12.34

Could linux-rpi be refreshed to a current Raspberry Pi release? 6.18.y packages from Raspberry Pi's trixie already use the t64 libraries and gcc-14 that kali-rolling has. If the package isn't maintained anymore, it would help if the Raspberry Pi docs says something about what Pi users should do instead

The mitigation I'm using until a fixed kernel is available, just in case it helps someone finding this (but as you should expect, is a temporary thing): dropping incoming IPv4 TCP that has IP options (-A ufw-before-input -p tcp -m u32 --u32 "0>>24&0x0F=6:15" -j DROP in /etc/ufw/before.rules) and net.mptcp.enabled = 0

Refreshed linux-headers-rpi-v8 would be needed too, because DKMS drivers like realtek-rtl8814au and brcmfmac-nexmon-dkms builds with it

Activities

There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
2026-11-07 14:38 ReginaSomnia New Issue