ммм.. owl? это случаем не древний лохматый Borland Object Windows Library? ;)

// wbr

Yes, and yes we are aware of these issues (and had plenty of advance
notification, along with other vendors).  While I do feel somewhat
guilty for not dedicating enough time to preparing an update before
this was made public, I do not consider these to be terribly bad
(compared to other crap I'm sure we still have in the kernel...)

The only confirmed impact is being able to read +s-r executables.  The
potential for a local root compromise is just theory at this point
(although there _might_ be a way to exploit one of the flaws in such a
way).

An updated -ow patch will be coming.  Whether I will put one out
really soon or whether I'll hold to also include some other fixes is
not decided yet.

FWIW, one of these bugs was fixed in 2.2.14-ow1+ and 2.2.15 official,
but the fix was never rolled into 2.4.x+ as it turns out.  I did not
check 2.2.x for the other bugs yet.