CVE-2026-64667
pam_usb provides hardware authentication for Linux using removable media.
Impact
pam_usb provides hardware authentication for Linux using removable media. Prior to version 0.9.3, src/local.c (pusb_get_tty_from_display_server) allocates a 4096-byte cmdline buffer, reads up to 4096 bytes from /proc//cmdline, then replaces every NUL separator with a space. When read(2) returns exactly 4096 bytes for any process the function inspects, the buffer ends without a terminator and the subsequent strstr() calls scan past the allocation boundary. The function is invoked during normal PAM authentication when DISPLAY is set, so the read fires for every process at auth time. Consequences are bounded: strstr output is a Boolean substring match (limited info-disclosure surface) but a hostile heap layout can produce a SIGSEGV that terminates the host PAM process. This issue has been patched in version 0.9.3.
An attacker can exploit this with local access to the system, with a regular user account, without any action by a user. If it succeeds: low risk of data being read, low risk of outages.
Affected products · Mcdope
| Product | Affected versions |
|---|---|
| Pam Usb | before 0.9.3 Version < 0.9.3 |
Weakness classification
References
- NVD record
- CVE.org record
- https://github.com/mcdope/pam_usb/security/advisories/GHSA-gc6f-5hpq-ghxh
- https://github.com/mcdope/pam_usb/issues/411
- https://github.com/mcdope/pam_usb/pull/426
- https://github.com/mcdope/pam_usb/commit/d0a2e716241304cdb069adfaf54d2ede629d57fa
- https://github.com/mcdope/pam_usb/releases/tag/0.9.3