{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-97591 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-97591 is a denial of service vulnerability in Linux, published on 25 Sep 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-97591 and fix it if it is affected.\n\nWhat it is: CVE-2026-97591 is a denial of service vulnerability in Linux, published on 25 Sep 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-97591 in the wild and no public exploit code.\n\nAffected product: Linux. 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-97591/ (Markdown: https://insights.sbomify.com/CVE-2026-97591/index.md)","id":"CVE-2026-97591","markdown":"https://insights.sbomify.com/CVE-2026-97591/index.md","name":"CVE-2026-97591","record":{"aliases":["BELL-CVE-2026-97591","DEBIAN-CVE-2026-97591","GHSA-48x9-wv7p-5368","UBUNTU-CVE-2026-97591"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"A missing EBUSY handling in the s390 PHMAC crypto driver can cause denial of service when requests are pushed to the crypto engine.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\ns390/crypto: Fix handling of EBUSY in PHMAC when req is pushed to crypto engine\n\nWhen a request is transferred to the engine via\ncrypto_transfer_hash_request_to_engine() there are two return codes\nsignaling a successful transfer: EINPROGRESS and EBUSY. However the\ncorrect handling of EBUSY was missing and has been added as a return\ncode indicating a successful transfer to the crypto engine.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"s390/crypto: Fix handling of EBUSY in PHMAC when req is pushed to crypto engine","id":"CVE-2026-97591","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"s390/crypto: Fix missing scrub of temp buffers with AES ctr and gcm algorithm","id":"CVE-2026-97592"},"packages":[],"prev":{"headline":"s390/crypto: Fix missing scrub of temp buffers with PAES algorithm","id":"CVE-2026-97590"},"products":["Linux"],"published":"2026-09-25","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A missing EBUSY handling in the s390 PHMAC crypto driver can cause denial of service when requests are pushed to the crypto engine.","url":"https://insights.sbomify.com/CVE-2026-97591/"}