Approved changes feed: RSS · Atom
cpe:2.3:a:mcdope:pam_usb:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Mcdope (ee070db4-8c96-5d13-b625-3092a66ee8fb) |
|---|---|
| Product | Pam Usb (b096b83f-48b3-5923-a383-fdfdf724019c) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-48986 |
vulnerable | 2026-07-29 00:57:44.789815 |
pam_usb: Infinite loop DoS in process-tree walk when parent process exits during authentication
MEDIUM (4.7)
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.
Published: 2026-06-18T17:20:51.643Z
Updated: 2026-06-22T12:34:51.890Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-48985 |
vulnerable | 2026-07-29 00:57:44.789568 |
pam_usb: NULL Dereference Crash in pusb_is_loginctl_local when loginctl Returns Empty Remote Field
MEDIUM (5.5)
pam_usb provides hardware authentication for Linux using ordinary removable media. In versions 0.9.1 and below, pusb_is_loginctl_local() can cause a NULL dereference crash when parsing loginctl output. The function calls popen() and reads the result; if the Remote field is only a newline, fgets() succeeds but strtok_r(buf, "\n", &saveptr) returns NULL. A subsequent strcmp(is_remote, "no") then dereferences NULL, causing undefined behavior (typically SIGSEGV) and crashing the PAM module. This can crash the authenticating process (e.g., sudo, login) and, depending on PAM stack configuration, deny access for all users of the affected service. This issue has been fixed in version 0.9.2.
Published: 2026-06-18T17:30:31.873Z
Updated: 2026-06-18T19:13:33.772Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-48984 |
vulnerable | 2026-07-29 00:57:44.789214 |
pam_usb: xfree() does not call explicit_bzero — sensitive cryptographic material may linger in freed heap
MEDIUM (4.7)
pam_usb provides hardware authentication for Linux using ordinary removable media. In versions 0.9.1 and below, the xfree() memory release helper in calls free() without first zeroing the buffer contents, releasing heap-allocated buffers containing sensitive data — including one-time pad bytes read from disk — without clearing, leaving the sensitive content in freed heap memory until it happens to be overwritten by a subsequent allocation. On a system where a use-after-free condition exists, or where a heap inspection primitive becomes available, this could allow recovery of pad values or other authentication material from freed memory regions. This is a defence-in-depth requirement consistent with prior hardening work in this codebase (GHSA-vx6f-rrqr-j87c applied explicit_bzero to some pad paths; this issue generalises the pattern to the central deallocation helper).
Published: 2026-06-18T17:06:00.918Z
Updated: 2026-06-18T18:48:13.213Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-48983 |
vulnerable | 2026-07-29 00:57:44.788911 |
pam_usb: TOCTOU race condition in pad directory creation allows symlink substitution
MEDIUM (5.8)
pam_usb provides hardware authentication for Linux using ordinary removable media. In versions prior to 0.9.2, a symlink race condition exists in per-device and per-user pad directory creation. pam_usb uses a check-then-act pattern: it calls lstat() to test for existence and then calls mkdir() separately to create the directory. A local attacker can win the race between these calls by replacing the target path with a symlink to a directory they control. If successful, one-time pad files may be written to an attacker-controlled location, potentially exposing future pad values before use or disrupting authentication. This issue has been fixed in version 0.9.2.
Published: 2026-06-18T19:07:56.198Z
Updated: 2026-06-22T12:41:34.711Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-48982 |
vulnerable | 2026-07-29 00:57:44.788741 |
pam_usb: Missing O_EXCL on pad temp file creation allows concurrent update race
MEDIUM (5.8)
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.
Published: 2026-06-18T19:01:08.766Z
Updated: 2026-06-22T17:16:39.634Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-48981 |
vulnerable | 2026-07-29 00:57:44.788507 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-48980 |
vulnerable | 2026-07-29 00:57:44.787997 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-48792 |
vulnerable | 2026-06-08 08:05:12.319652 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-48066 |
vulnerable | 2026-06-08 08:05:12.243712 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-48065 |
vulnerable | 2026-06-08 08:05:12.243462 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-48064 |
vulnerable | 2026-06-08 08:05:12.243158 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-47274 |
vulnerable | 2026-06-08 08:05:12.190343 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-47273 |
vulnerable | 2026-06-08 08:05:12.190201 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-47272 |
vulnerable | 2026-06-08 08:05:12.190051 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-47271 |
vulnerable | 2026-06-08 08:05:12.189901 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-47270 |
vulnerable | 2026-06-08 08:05:12.189747 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-47269 |
vulnerable | 2026-06-08 08:05:12.189442 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-44713 |
vulnerable | 2026-06-08 08:05:11.281894 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-44712 |
vulnerable | 2026-06-08 08:05:11.281630 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-44711 |
vulnerable | 2026-06-08 08:05:11.281485 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-44710 |
vulnerable | 2026-06-08 08:05:11.281323 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-44709 |
vulnerable | 2026-06-08 08:05:11.281110 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.