I added code to Linux to help KASAN detect specific types of UAFs more reliably (https://git.kernel.org/pub/scm/linux/kernel/git/vbabka/slab.git/commit/?h=slab/for-6.12/rcu_barriers&id=b8c8ba73c68bb3c3e9dad22f488b86c540c839f9), it's been in the linux-next integration tree for, I don't know, a month or so maybe (though it's not in the mainline tree yet), and still there are zero hits on LKML of bugs caught where the stack trace involves my detection...
It's nice that there apparently aren't a lot of easy-to-find bugs of this type around but it's also a little disappointing to not immediately get some nice results from my work...
=> More informations about this toot | More toots from jann@infosec.exchange
@jann the defenders' dilemma...
=> More informations about this toot | More toots from djm@cybervillains.com
@djm if it's not blowing up before the change, and it's not blowing up after the change, has anything really changed
=> More informations about this toot | More toots from jann@infosec.exchange
@jann @djm defense work sucks in that regard :-( on the flip-side, you can take pride in knowing that future kernels will never have that kind of simple uaf bugs. ever. 😊
=> More informations about this toot | More toots from freddy@security.plumbing
@freddy @djm the detection is not that good, sadly...
=> More informations about this toot | More toots from jann@infosec.exchange
text/gemini
This content has been proxied by September (3851b).