Jump to content

Recommended Posts

Posted

Hello,

I attempted to port the dirty COW fix (https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=19be0eaffa3ac7d8eb6784ad9bdbc7d67ed8e619) for 3.4.112, and came up with this: https://github.com/SvenKayser/Sambooca-Kernel-H3/commit/543472582a6adcef12fae4ad11da72a62f29fb74.patch

Apparently it solves the issue, but to be sure maybe some of you guys can give it a test. If it checks out please do commit it in the right places for Armbian - which I wouldn't know (Armbian has so many kernel patch folders, I don't wanna mess things up)

Regards

Sven

Posted

I can confirm this fixes the issue, using my own Debian image that uses Sven's kernel by default. The file that was being modified remains the same after running the exploit. Good job!

 

-Olgierd

Posted

Rebuilding Armbian = up to 10 hours :)  :huh: ... I am doing some other urgent fixes on the way.  Pine64 patch needs some adjustments and few checks, testing repository is currently building and if things goes well it will be pushed to main repository. If this would be only one kernel with only this change ... it would be already done.

 

Problems in yesterday build:

http://beta.armbian.com/buildlogs/

Posted

Do I understand correctly: The image I find in linux-image-sun8i_5.23_armhf.deb (timestamp 23rd Oct) contains the kernel image with the Dirty Cow patch? I still get 3.4.112 as new kernel version. Was this a "silent patch", without increasing the version number?

 

PS: Thanks for your work! Without the Armbian Project I could not even remotely hope to find fixes for such vulnerabilities.

Posted

If you did apt-get update and apt-get upgrade, you have nothing to worry  :P

 

Thanks.

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines