pam_usb provides hardware authentication for Linux using ordinary removable media. In versions prior to 0.9.2, when updating a one-time pad file, a temporary file is created using open() without the O_EXCL flag. Without O_EXCL, the create operation is not atomic: two concurrent processes racing to update the same pad may both succeed in opening the file, with the second write silently overwriting the first. The one-time pad is the core replay-prevention mechanism of pam_usb. A successful race could result in the stored pad value diverging from what either process expected, potentially causing authentication failures or, in a precisely timed attack, creating a window for pad reuse. This issue has been fixed in version 0.9.2.
{
"cna_assigner": "GitHub_M",
"cwe_ids": [
"CWE-362"
],
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/48xxx/CVE-2026-48982.json"
}"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-48982.json"
[
{
"deprecated": false,
"digest": {
"line_hashes": [
"207168628483260584139415185282640304588"
],
"threshold": 0.9
},
"id": "CVE-2026-48982-efc14bc2",
"signature_type": "Line",
"signature_version": "v1",
"source": "https://github.com/mcdope/pam_usb/commit/d4083e266b7e18e41e58b3392b5856941a3b5b1c",
"target": {
"file": "src/version.h"
}
}
]
"2026-08-12T16:25:30Z"