{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-48984 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-48984 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-48984 is a medium-severity vulnerability in mcdope pam_usb, published on 18 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-48984 and fix it if it is affected.\n\nWhat it is: CVE-2026-48984 is a medium-severity vulnerability in mcdope pam_usb, published on 18 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-48984 in the wild and no public exploit code.\n\nAffected product: mcdope pam_usb. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-48984/ (Markdown: https://insights.sbomify.com/CVE-2026-48984/index.md)","id":"CVE-2026-48984","markdown":"https://insights.sbomify.com/CVE-2026-48984/index.md","name":"CVE-2026-48984","record":{"aliases":["GHSA-rmp6-wfrq-wrrc"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux PAM module","requires_auth":"low_privilege","summary":"Failure to zero memory before freeing in pam_usb may allow recovery of sensitive authentication material from heap memory.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":4.7,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-226","name":"Sensitive Information in Resource Not Removed Before Reuse"},{"id":"CWE-14","name":"Compiler Removal of Code to Clear Buffers"}],"description":"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).","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"pam_usb: xfree() does not call explicit_bzero — sensitive cryptographic material may linger in freed heap","id":"CVE-2026-48984","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"pam_usb: NULL Dereference Crash in pusb_is_loginctl_local when loginctl Returns Empty Remote Field","id":"CVE-2026-48985"},"packages":[],"prev":{"headline":"pam_usb: TOCTOU race condition in pad directory creation allows symlink substitution","id":"CVE-2026-48983"},"products":["pam_usb"],"published":"2026-06-18","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-18","vendors":["mcdope"]},"summary":"Failure to zero memory before freeing in pam_usb may allow recovery of sensitive authentication material from heap memory.","url":"https://insights.sbomify.com/CVE-2026-48984/"}