{"dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": {"cveId": "CVE-2026-48982", "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "state": "PUBLISHED", "assignerShortName": "GitHub_M", "dateReserved": "2026-05-26T23:26:07.974Z", "datePublished": "2026-06-18T19:01:08.766Z", "dateUpdated": "2026-06-18T19:01:08.766Z"}, "containers": {"cna": {"title": "pam_usb: Missing O_EXCL on pad temp file creation allows concurrent update race", "problemTypes": [{"descriptions": [{"cweId": "CWE-362", "lang": "en", "description": "CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')", "type": "CWE"}]}], "metrics": [{"cvssV3_1": {"attackComplexity": "HIGH", "attackVector": "LOCAL", "availabilityImpact": "LOW", "baseScore": 5.8, "baseSeverity": "MEDIUM", "confidentialityImpact": "LOW", "integrityImpact": "HIGH", "privilegesRequired": "LOW", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:H/A:L", "version": "3.1"}}], "references": [{"name": "https://github.com/mcdope/pam_usb/security/advisories/GHSA-hxh6-9574-5vp6", "tags": ["x_refsource_CONFIRM"], "url": "https://github.com/mcdope/pam_usb/security/advisories/GHSA-hxh6-9574-5vp6"}, {"name": "https://github.com/mcdope/pam_usb/releases/tag/0.9.2", "tags": ["x_refsource_MISC"], "url": "https://github.com/mcdope/pam_usb/releases/tag/0.9.2"}], "affected": [{"vendor": "mcdope", "product": "pam_usb", "versions": [{"version": "< 0.9.2", "status": "affected"}]}], "providerMetadata": {"orgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "shortName": "GitHub_M", "dateUpdated": "2026-06-18T19:01:08.766Z"}, "descriptions": [{"lang": "en", "value": "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."}], "source": {"advisory": "GHSA-hxh6-9574-5vp6", "discovery": "UNKNOWN"}}}}

{}

{}

{}

{}