Authentication denial via thread-unsafe logging pointer
Published May 27, 2026 · Updated May 27, 2026
Race condition in pam_usb before 0.9.1 allows local users to disrupt authentication by triggering concurrent PAM invocations. pusb_log_init stores each invocation's stack-local options address in a process-wide static pointer, so a racing thread can replace it or leave it dangling. Exploitation requires concurrent authentication in one process and can corrupt log output or crash that PAM client, interrupting its authentication service.
Summary
What happened
Race condition in pam_usb before 0.9.1 allows local users to disrupt authentication by triggering concurrent PAM invocations. pusb_log_init stores each invocation's stack-local options address in a process-wide static pointer, so a racing thread can replace it or leave it dangling. Exploitation requires concurrent authentication in one process and can corrupt log output or crash that PAM client, interrupting its authentication service.
The record
- CVE
- CVE-2026-48066
- Published
- May 27, 2026
- Updated
- May 27, 2026
- Vendor
- mcdope
- Product
- pam_usb
- Classifications
- CWE-362, CWE-476, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 27, 2026CVE publishedPublication date reported by the CVE source.
- May 27, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 0.9.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo