mcdope pam_usb up to 0.9.1 on Linux Removable Media xfree compiler removal of code to clear buffers
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.5 | $0-$5k | 2.64 |
Summary
A vulnerability was found in mcdope pam_usb up to 0.9.1 on Linux. It has been rated as problematic. This affects the function xfree of the component Removable Media Handler. This manipulation causes compiler removal of code to clear buffers.
This vulnerability appears as CVE-2026-48984. The attack requires local access. There is no available exploit.
Upgrading the affected component is advised.
Details
A vulnerability has been found in mcdope pam_usb up to 0.9.1 on Linux and classified as problematic. Affected by this vulnerability is the function xfree of the component Removable Media Handler. The manipulation with an unknown input leads to a compiler removal of code to clear buffers vulnerability. The CWE definition for the vulnerability is CWE-14. Sensitive memory is cleared according to the source code, but compiler optimizations leave the memory untouched when it is not read from again, aka "dead store removal." As an impact it is known to affect confidentiality. The summary by CVE is:
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).
The advisory is shared at github.com. This vulnerability is known as CVE-2026-48984 since 05/27/2026. The exploitation appears to be difficult. An attack has to be approached locally. Technical details are known, but no exploit is available.
Upgrading to version 0.9.2 eliminates this vulnerability.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
Website
- Product: https://github.com/mcdope/pam_usb/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.6VulDB Meta Temp Score: 3.5
VulDB Base Score: 2.5
VulDB Temp Score: 2.4
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 4.7
CNA Vector (GitHub_M): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Compiler removal of code to clear buffersCWE: CWE-14
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: pam_usb 0.9.2
Timeline
05/27/2026 CVE reserved06/18/2026 Advisory disclosed
06/18/2026 VulDB entry created
06/18/2026 VulDB entry last update
Sources
Product: github.comAdvisory: github.com
Status: Confirmed
CVE: CVE-2026-48984 (🔒)
GCVE (CVE): GCVE-0-2026-48984
GCVE (VulDB): GCVE-100-372253
Entry
Created: 06/18/2026 19:56Changes: 06/18/2026 19:56 (65)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.