It's from bpfilter_umh which is a userspace process forked by bpfilter.ko. Since it's a userspace process writing messages directly to /dev/console, no kernel parameter would affect it... As a temporary workaround, you could just blacklist bpfilter. AFAIK, the userspace library for bpfilter is still under development, a normal user unlikely needs the module in the short term.