CVE-2026-47271: pam_usb: OOM guards removed by -DNDEBUG cause NULL dereference and authentication process crash
pamusb provides hardware authentication for Linux using ordinary removable media. Prior to 0.9.0, src/mem.c implemented out-of-memory guards for xmalloc(), xrealloc(), and xstrdup() using assert(data != NULL). The C standard specifies that all assert() expressions are compiled out when NDEBUG is defined at build time. NDEBUG is commonly defined in release and packaging builds (Debian, Fedora, Arch package flags all define it via -DNDEBUG in CFLAGS). With the guard removed, xmalloc/xrealloc/xstrdup silently return NULL on allocation failure. Every caller in the codebase dereferences the return value without a NULL check -- this is the intended design, as the guard was supposed to abort before the dereference. With the guard gone, any allocation failure causes a NULL pointer dereference, crashing the PAM module. A crash in a PAM module loaded by sudo or login causes authentication to fail for the duration of the crash, creating a local denial-of-service condition. An attacker who can induce memory pressure at authentication time can lock all users out of sudo and login. This vulnerability is fixed in 0.9.0.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-47271?
CVE-2026-47271 has a medium severity rating of 5.1.
What kind of vulnerability is CVE-2026-47271?
CVE-2026-47271 is a null pointer dereference vulnerability in the pam_usb authentication module.
How does CVE-2026-47271 affect the pam_usb authentication process?
CVE-2026-47271 causes a crash in the authentication process due to a NULL dereference when out-of-memory guards are removed.
How do I fix CVE-2026-47271?
To fix CVE-2026-47271, upgrade pam_usb to version 0.9.0 or higher where the issue is addressed.
What systems are impacted by CVE-2026-47271?
CVE-2026-47271 impacts Linux systems using the pam_usb module for hardware-based authentication.