{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-48985 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-48985 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-48985 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-48985 and fix it if it is affected.\n\nWhat it is: CVE-2026-48985 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-48985 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-48985/ (Markdown: https://insights.sbomify.com/CVE-2026-48985/index.md)","id":"CVE-2026-48985","markdown":"https://insights.sbomify.com/CVE-2026-48985/index.md","name":"CVE-2026-48985","record":{"aliases":["GHSA-7j6h-wfc2-mg5q"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux PAM module","requires_auth":"low_privilege","summary":"A NULL dereference in pam_usb causes a crash when parsing empty loginctl output, potentially denying access to authentication services.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-476","name":"NULL Pointer Dereference"}],"description":"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\", \u0026saveptr) 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.","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: NULL Dereference Crash in pusb_is_loginctl_local when loginctl Returns Empty Remote Field","id":"CVE-2026-48985","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"pam_usb: Infinite loop DoS in process-tree walk when parent process exits during authentication","id":"CVE-2026-48986"},"packages":[],"prev":{"headline":"pam_usb: xfree() does not call explicit_bzero — sensitive cryptographic material may linger in freed heap","id":"CVE-2026-48984"},"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":"A NULL dereference in pam_usb causes a crash when parsing empty loginctl output, potentially denying access to authentication services.","url":"https://insights.sbomify.com/CVE-2026-48985/"}