CVE-2026-48982: pam_usb: Missing O_EXCL on pad temp file creation allows concurrent update race
pamusb 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 OEXCL flag. Without OEXCL, 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 pamusb. 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.
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 risk level of CVE-2026-48982?
The risk level of CVE-2026-48982 is assessed at 45.
What is the severity score of CVE-2026-48982?
The severity score of CVE-2026-48982 is medium at 5.8.
What causes the vulnerability CVE-2026-48982?
CVE-2026-48982 is caused by the absence of the O_EXCL flag when creating a temporary pad file, leading to a race condition.
How can I remediate CVE-2026-48982?
To remediate CVE-2026-48982, upgrade to pam_usb version 0.9.2 or later.
What impact does CVE-2026-48982 have on security?
CVE-2026-48982 can lead to unauthorized access due to potential concurrent modifications of sensitive pad files.