{"answers":{"affected":"","exploited":"There is no known exploitation of openSUSE-SU-2026:21325-1 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"openSUSE-SU-2026:21325-1 is a vulnerability in cryptsetup, published on 13 Jul 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 openSUSE-SU-2026:21325-1 and fix it if it is affected.\n\nWhat it is: openSUSE-SU-2026:21325-1 is a vulnerability in cryptsetup, published on 13 Jul 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 openSUSE-SU-2026:21325-1 in the wild and no public exploit code.\n\nAffected product: cryptsetup. 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/openSUSE-SU-2026-21325-1/ (Markdown: https://insights.sbomify.com/openSUSE-SU-2026-21325-1/index.md)","id":"openSUSE-SU-2026:21325-1","markdown":"https://insights.sbomify.com/openSUSE-SU-2026-21325-1/index.md","name":"openSUSE-SU-2026:21325-1","record":{"aliases":[],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux disk encryption","requires_auth":"none","summary":"An attacker with local access could potentially read encrypted volume keys due to improper keyring handling in cryptsetup.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"This update for cryptsetup fixes the following issues:\n\nChanges in cryptsetup:\n\n- Fix for (bsc#1270254) to avoid undesired pinning of all volume\n  keys (via the thread keyring) through the caller's credentials\n  when the kernel opens a file. This is due to the refactoring in\n  kernel commit a28d893eb327 (\"md: port block device access to file\")\n  that accidentally causes the caller's thread keyring to be kept\n  alive long beyond the caller's lifetime, the kernel part is tracked\n  in (bsc#1270252).\n\n  * Add keyring key type. [b6fb6fc0]\n  * Load volume keys in intermediary keyring linked in thread\n    keyring. [413a3dd0]\n  * Use unique intermediary keyring name per device. [04ef07a7]\n  * Add regression tests. [bfcb0c38, bb5e8e9f, e6573494, aa214c09]","ecosystems":["openSUSE:Leap 16.0"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"Security update for cryptsetup","id":"openSUSE-SU-2026:21325-1","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"openSUSE:Leap 16.0","fixed":["2.8.4-160000.2.1"],"introduced":["0"],"last_affected":[],"package":"cryptsetup","purl":"pkg:rpm/opensuse/cryptsetup\u0026distro=openSUSE%20Leap%2016.0","source":"openSUSE-SU-2026:21325-1"}],"products":null,"published":"2026-07-13","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"SUSE","prefix":"openSUSE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"An attacker with local access could potentially read encrypted volume keys due to improper keyring handling in cryptsetup.","url":"https://insights.sbomify.com/openSUSE-SU-2026-21325-1/"}