The CVE is text is accurate, the commit is an abbreviation. I wish they would've included the CVE in the commit message though.
OpenBSD through 6.6 allows local users to escalate to root because a check for LD_LIBRARY_PATH in setuid programs can be defeated by setting a very small RLIMIT_DATA resource limit. When executing chpass or passwd (which are setuid root), _dl_setup_env in ld.so tries to strip LD_LIBRARY_PATH from the environment, but fails when it cannot allocate memory. Thus, the attacker is able to execute their own library code as root.
Also, certain system calls like set(e)[gu]id should be pledged() opt-out rather than opt-in. It's probably a breaking change in a lot of
software, but only some calls should ever be called in limited scopes where they're used and then prevented from being called ordinarily. You don't all the always doors unlocked, especially the ones that lead outside from the 11th floor without a fire escape, if you're only using a few of them.
OpenBSD through 6.6 allows local users to escalate to root because a check for LD_LIBRARY_PATH in setuid programs can be defeated by setting a very small RLIMIT_DATA resource limit. When executing chpass or passwd (which are setuid root), _dl_setup_env in ld.so tries to strip LD_LIBRARY_PATH from the environment, but fails when it cannot allocate memory. Thus, the attacker is able to execute their own library code as root.
Also, certain system calls like set(e)[gu]id should be pledged() opt-out rather than opt-in. It's probably a breaking change in a lot of software, but only some calls should ever be called in limited scopes where they're used and then prevented from being called ordinarily. You don't all the always doors unlocked, especially the ones that lead outside from the 11th floor without a fire escape, if you're only using a few of them.