The only base system's program currently leveraging setcred(2) is mdo(1), so 
only those using it could stumble on the bug inadvertently (unless they have 
their own programs calling setcred(2)).

Of course, this does not preclude malicious people from trying to actively 
exploit that, either through mdo(1) or by calling setcred(2) directly.

As the reporter of this vulnerability, I am sharing a full write-up demonstrating LPE with SMAP/SMEP enabled: https://fatgid.io/



Reply via email to