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.
{
"cwe_ids": [
"CWE-367"
],
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/48xxx/CVE-2026-48983.json",
"cna_assigner": "GitHub_M"
}"2026-08-12T16:25:30Z"
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-48983.json"
[
{
"signature_version": "v1",
"source": "https://github.com/mcdope/pam_usb/commit/d4083e266b7e18e41e58b3392b5856941a3b5b1c",
"digest": {
"line_hashes": [
"207168628483260584139415185282640304588"
],
"threshold": 0.9
},
"deprecated": false,
"signature_type": "Line",
"id": "CVE-2026-48983-efc14bc2",
"target": {
"file": "src/version.h"
}
}
]