Ryan Mallon <rmal...@gmail.com> writes: > The only remaining problem is kernel/module.c:module_sect_show() which > is used to write the sysfs files in /sys/module/<modname>/sections/. > Those files are actually are really good target for leaking %pK values > via setuid binaries. The problem is that the module_sect_show() function > isn't passed information about who opened the sysfs file. I don't think > this information is available in general for sysfs files either. Also, > I can't actually see how module_sect_show() gets called? > > I'm a bit stuck on how to solve this. Any ideas?
I haven't yet had a chance to review the patches but there are patches to make sysfs files seq files in Greg's driver core tree. Eric -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
