{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-47270 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-47270 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-47270 is a medium-severity vulnerability in mcdope pam_usb, published on 27 May 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-47270 and fix it if it is affected.\n\nWhat it is: CVE-2026-47270 is a medium-severity vulnerability in mcdope pam_usb, published on 27 May 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-47270 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-47270/ (Markdown: https://insights.sbomify.com/CVE-2026-47270/index.md)","id":"CVE-2026-47270","markdown":"https://insights.sbomify.com/CVE-2026-47270/index.md","name":"CVE-2026-47270","record":{"aliases":["GHSA-j3xw-vc43-x7jg"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux PAM module","requires_auth":"low_privilege","summary":"A race condition in pam_usb's remote session detection can allow attackers to bypass hardware authentication restrictions on Linux systems.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-362","name":"Concurrent Execution using Shared Resource with Improper Synchronization"}],"description":"pam_usb provides hardware authentication for Linux using ordinary removable media. Prior to 0.9.0, pam_usb is a PAM module loaded into the host process (sudo, login, GDM, GNOME Shell). Display managers such as GDM run multiple concurrent authentication threads. Three functions used by the deny_remote feature called the non-reentrant strtok(), which stores state in a single global pointer. If two authentications race, one thread's strtok() call can overwrite the other's in-progress tokenisation pointer, causing incorrect parsing of the tmux session data or the /proc environ scan that backs the remote-session detection logic. Additionally, pusb_tmux_get_client_tty() passed the raw pointer returned by getenv(TMUX) directly to strtok(). getenv() returns a pointer into the live process environment block; strtok() inserts NUL bytes into that block, permanently corrupting the TMUX variable for subsequent code running in the same process. In long-lived display managers this affects all future authentications in that process. The combined effect can cause deny_remote=true to return an incorrect decision for a remote session, or an incorrect decision for a local session, depending on thread interleaving. This vulnerability is fixed in 0.9.0.","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: strtok() race condition in multi-threaded PAM hosts can corrupt deny_remote result","id":"CVE-2026-47270","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"pam_usb: OOM guards removed by -DNDEBUG cause NULL dereference and authentication process crash","id":"CVE-2026-47271"},"packages":[],"prev":{"headline":"pam_usb: deny_remote feature incorrectly classifies IPv4-mapped IPv6 remote connections as local","id":"CVE-2026-47269"},"products":["pam_usb"],"published":"2026-05-27","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":"total"},"state":"PUBLISHED","updated":"2026-05-28","vendors":["mcdope"]},"summary":"A race condition in pam_usb's remote session detection can allow attackers to bypass hardware authentication restrictions on Linux systems.","url":"https://insights.sbomify.com/CVE-2026-47270/"}