News for hackers. Stuff that matters.
Re:Linux Kernel Use-After-Free Remote Code Execution Vulnera... by mkj on Tuesday October 04, 2016 @09:30PM (#12641006)
What circumstances are needed for this to be exploitable? Wondering if iptables could mitigate for systems where upgrading the kernel is non-trivial.
Re:Linux Kernel Use-After-Free Remote Code Execution Vulnera... by zzzcpan on Tuesday October 04, 2016 @09:43PM (#12641053)
Haven't looked at this too closely, but iptables are unlikely to help. The bug appears to be in the recvmmsg() syscall, which is where the packet leaves the kernel and enters the userspace. The syscall itself is not that widely used, only for some unusually optimized UDP servers, you are unlikely to have one running. But you can check with strace just to be sure.
Re:Linux Kernel Use-After-Free Remote Code Execution Vulnera... by caf on Wednesday October 05, 2016 @01:36AM (#12641756)
https://codesearch.debian.net/search?q=[^_]recvmmsg\%28[^\%2...

(Many of the results are for code like language runtimes and debugging tools that don't actually use recvmmsg() themselves)

Re:Linux Kernel Use-After-Free Remote Code Execution Vulnera... by ajb on Wednesday October 05, 2016 @09:13AM (#12643485)
Ouch, it's in chromium though.
Re:Linux Kernel Use-After-Free Remote Code Execution Vulnera... by mkj on Tuesday October 04, 2016 @09:55PM (#12641099)
Yep. Though I assume this needs some interesting network traffic to trigger it.
Re:Linux Kernel Use-After-Free Remote Code Execution Vulnera... by startling on Thursday October 06, 2016 @06:48PM (#12656778)
I wrote a bit about it: https://blog.lizzie.io/notes-about-cve-2016-7117.html

tl;dr looks like it'd function well a local privilege exploit. not an expert, but as a remote exploit think it would need 1) a service running recvmmsg (which is kind of unlikely) 2) a way to cause recvmsg to error, and 3) a way to cause the service to close its socket in the middle of the recvmmsg call.

Re:Linux Kernel Use-After-Free Remote Code Execution Vulnera... by vzcx on Wednesday October 19, 2016 @05:31PM (#12747873)
Nice writeup!

I was just starting to look into this since people were claiming it was pretty severe and yet I hadn't seen any POC's. Have you made any more progress?

For whatever my opinion is worth (i.e. not much), I would agree with you that remote exploitation of this particular bug would be really difficult.