Wanted to download an ISO, ended up writing a kernel exploit
My TP-Link EAP770 v1 corrupts downloads over Wi-Fi and TP-Link EOL'd it before I unboxed it. The fix is two zeros in sysfs. TP-Link's shell won't let me write them, so I wrote a kernel exploit for my own fucking access point.
Summary
A developer stumbled upon a serious bug affecting multiple drivers, which works correctly on x86 but causes data corruption on ARM and other architectures. They’re seeking advice on how to handle these drivers and the implications for kernel development.
Comments (180 of ) ⌛