CVE-2026-48983: pam_usb: TOCTOU race condition in pad directory creation allows symlink substitution
pamusb provides hardware authentication for Linux using ordinary removable media. In versions prior to 0.9.2, a symlink race condition exists in per-device and per-user pad directory creation. pamusb uses a check-then-act pattern: it calls lstat() to test for existence and then calls mkdir() separately to create the directory. A local attacker can win the race between these calls by replacing the target path with a symlink to a directory they control. If successful, one-time pad files may be written to an attacker-controlled location, potentially exposing future pad values before use or disrupting authentication. This issue has been fixed in version 0.9.2.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
pam_usbto a version that resolves this vulnerability.Fixed in 0.9.2
Event History
Frequently Asked Questions
What is the severity of CVE-2026-48983?
The severity of CVE-2026-48983 is rated as medium with a score of 5.8.
What is the risk associated with CVE-2026-48983?
CVE-2026-48983 has a risk score of 45, indicating a moderate level of concern.
How do I fix CVE-2026-48983?
To mitigate CVE-2026-48983, upgrade to pam_usb version 0.9.2 or later where the issue is resolved.
What type of vulnerability is CVE-2026-48983?
CVE-2026-48983 is classified as a race condition vulnerability.
How does CVE-2026-48983 affect pam_usb users?
CVE-2026-48983 allows a symlink substitution due to a TOCTOU race condition in pad directory creation, impacting users' security.