CVE-2026-48986
Received Received - Intake
Infinite Loop DoS in pam_usb Authentication

Publication date: 2026-06-18

Last updated on: 2026-06-18

Assigner: GitHub, Inc.

Description
pam_usb provides hardware authentication for Linux using removable media. In pam_usb 0.9.1 and earlier, usb_get_process_parent_id() can cause an infinite loop DoS because it does not initialize *ppid on failure. In pusb_local_login(), the same variable is reused as input and output in a process-tree while loop; if /proc/<pid>/stat cannot be read (for example, when an ancestor process exits during authentication), the PID is not updated and the loop does not terminate. This hangs the authenticating process (such as sudo, sshd, or login) until it is forcibly terminated. This issue has been fixed in version 0.9.2.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-18
Last Modified
2026-06-18
Generated
2026-06-19
AI Q&A
2026-06-18
EPSS Evaluated
N/A
NVD
EUVD
Affected Vendors & Products
Showing 2 associated CPEs
Vendor Product Version / Range
pam_usb pam_usb to 0.9.2 (exc)
pam_usb pam_usb 0.9.2
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-835 The product contains an iteration or loop with an exit condition that cannot be reached, i.e., an infinite loop.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

CVE-2026-48986 is a medium-severity vulnerability in the pam_usb software, affecting versions 0.9.1 and earlier. It involves an infinite loop denial-of-service (DoS) condition during the authentication process.

The flaw occurs in the function usb_get_process_parent_id() when it fails to initialize the ppid variable upon failure. This causes a process-tree walk loop in pusb_local_login() to never terminate if an ancestor process exits during authentication, because the PID is not updated.

As a result, the authenticating process (such as sudo, sshd, or login) hangs indefinitely until it is forcibly terminated.

Mitigation Strategies

The immediate mitigation step is to upgrade pam_usb to version 0.9.2 or later, where the issue has been fixed by initializing the parent process ID variable to prevent the infinite loop.

Until the upgrade can be applied, monitor authentication processes for hangs and forcibly terminate any stuck processes to maintain system availability.

Additionally, consider limiting the use of pam_usb on busy systems where short-lived processes frequently appear in the ancestor chain of authentication calls.

Impact Analysis

This vulnerability can cause the authentication process on a Linux system using pam_usb to hang indefinitely, resulting in a denial-of-service condition.

Specifically, processes like sudo, sshd, or login may become unresponsive, requiring manual termination.

On busy systems where short-lived processes frequently appear in the ancestor chain, this issue is more likely to be triggered.

The overall impact is a disruption of availability, potentially affecting system access and operations.

Detection Guidance

This vulnerability causes an infinite loop denial-of-service (DoS) condition during authentication processes such as sudo, sshd, or login, resulting in those processes hanging until forcibly terminated.

To detect this vulnerability on your system, monitor for authentication processes that become unresponsive or hang unexpectedly.

You can use commands to identify hung authentication processes, for example:

  • Use `ps` to find stuck authentication processes: `ps -eo pid,ppid,cmd | grep -E 'sudo|sshd|login'` and look for processes with unusually long runtimes.
  • Use `strace` on suspected hung processes to observe if they are stuck in a loop: `strace -p <pid>`.
  • Check system logs (e.g., `/var/log/auth.log` or `/var/log/secure`) for repeated authentication attempts or errors related to PAM or usb authentication.
Compliance Impact

The provided information does not specify any direct impact of this vulnerability on compliance with common standards and regulations such as GDPR or HIPAA.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-48986. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart