{"api_version":"1","generated_at":"2026-10-01T19:48:53+00:00","cve":"CVE-2026-97589","urls":{"html":"https://cve.report/CVE-2026-97589","api":"https://cve.report/api/cve/CVE-2026-97589.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-97589","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-97589"},"summary":{"title":"s390/crypto: Fix wrong return code to engine in asynch callbacks","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ns390/crypto: Fix wrong return code to engine in asynch callbacks\n\nWhen crypto_finalize_hash_request() or\ncrypto_finalize_skcipher_request() explicitly completes a request, the\ndo_one_request callback must return 0 to indicate successful\nhandling. Returning a negative error code causes the crypto engine to\nassume the driver failed to take ownership and triggers a second\ncompletion via crypto_request_complete(), resulting in a double\ncompletion. This pattern occurs in paes_s390.c 4 times and once in\nphmac_s390.c.\n\nFixed in phmac_do_one_request() and all four paes do_one_request\ncallbacks (ecb, cbc, ctr, xts) by returning 0 after explicit\nfinalization instead of propagating the error code.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-09-25 11:17:10","updated_at":"2026-09-25 15:18:00"},"problem_types":[],"metrics":[{"version":"3.1","source":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","type":"Secondary","score":"7","severity":"HIGH","vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","data":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","baseScore":7,"baseSeverity":"HIGH","attackVector":"LOCAL","attackComplexity":"HIGH","privilegesRequired":"LOW","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"HIGH","availabilityImpact":"HIGH"}},{"version":"3.1","source":"CNA","type":"DECLARED","score":"7","severity":"HIGH","vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","data":{"baseScore":7,"baseSeverity":"HIGH","vectorString":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"}}],"references":[{"url":"https://git.kernel.org/stable/c/972e0d9b7d1d112240ccde1f1be85bf9ffaa1720","name":"https://git.kernel.org/stable/c/972e0d9b7d1d112240ccde1f1be85bf9ffaa1720","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/5480291aa848e19e61175abfd457933516db70c6","name":"https://git.kernel.org/stable/c/5480291aa848e19e61175abfd457933516db70c6","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/ac1481320110b803ab9b79ab4d2ca11a74fc05f2","name":"https://git.kernel.org/stable/c/ac1481320110b803ab9b79ab4d2ca11a74fc05f2","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-97589","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-97589","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6cd87cb5ef6ca50ae17c371482ceaab1d635e232 972e0d9b7d1d112240ccde1f1be85bf9ffaa1720 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6cd87cb5ef6ca50ae17c371482ceaab1d635e232 5480291aa848e19e61175abfd457933516db70c6 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6cd87cb5ef6ca50ae17c371482ceaab1d635e232 ac1481320110b803ab9b79ab4d2ca11a74fc05f2 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.16","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.16 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.53 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2.7 7.2.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3-rc3 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"97589","cve":"CVE-2026-97589","epss":"0.001430000","percentile":"0.029650000","score_date":"2026-09-27","updated_at":"2026-09-28 00:02:23"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["arch/s390/crypto/paes_s390.c","arch/s390/crypto/phmac_s390.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"972e0d9b7d1d112240ccde1f1be85bf9ffaa1720","status":"affected","version":"6cd87cb5ef6ca50ae17c371482ceaab1d635e232","versionType":"git"},{"lessThan":"5480291aa848e19e61175abfd457933516db70c6","status":"affected","version":"6cd87cb5ef6ca50ae17c371482ceaab1d635e232","versionType":"git"},{"lessThan":"ac1481320110b803ab9b79ab4d2ca11a74fc05f2","status":"affected","version":"6cd87cb5ef6ca50ae17c371482ceaab1d635e232","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["arch/s390/crypto/paes_s390.c","arch/s390/crypto/phmac_s390.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.16"},{"lessThan":"6.16","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.53","versionType":"semver"},{"lessThanOrEqual":"7.2.*","status":"unaffected","version":"7.2.7","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.3-rc3","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.53","versionStartIncluding":"6.16","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2.7","versionStartIncluding":"6.16","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3-rc3","versionStartIncluding":"6.16","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\ns390/crypto: Fix wrong return code to engine in asynch callbacks\n\nWhen crypto_finalize_hash_request() or\ncrypto_finalize_skcipher_request() explicitly completes a request, the\ndo_one_request callback must return 0 to indicate successful\nhandling. Returning a negative error code causes the crypto engine to\nassume the driver failed to take ownership and triggers a second\ncompletion via crypto_request_complete(), resulting in a double\ncompletion. This pattern occurs in paes_s390.c 4 times and once in\nphmac_s390.c.\n\nFixed in phmac_do_one_request() and all four paes do_one_request\ncallbacks (ecb, cbc, ctr, xts) by returning 0 after explicit\nfinalization instead of propagating the error code."}],"metrics":[{"cvssV3_1":{"baseScore":7,"baseSeverity":"HIGH","vectorString":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"scenarios":[{"lang":"en","value":"AV:L - The faulty return is in ecb/cbc/ctr/xts_paes_do_one_request() and phmac_do_one_request(), which run in the crypto engine worker. They are reached through local crypto API users: AF_ALG sockets binding \"ecb(paes)\" etc. (algif_skcipher recvmsg -> ecb_paes_crypt -> engine) or dm-crypt. No remote peer supplies the data that causes the failure.\nAC:H - The double completion fires only when the engine path returns an error. That needs the protected key to be invalidated (-EKEYEXPIRED, e.g. the wrapping key changed) and then re-conversion to fail in paes_convert_key() because the card is busy or offline. AF_ALG blocks setkey while op sockets exist, so the attacker cannot force this state.\nPR:L - AF_ALG socket creation and binding the paes/phmac algorithms need no capability, so a local unprivileged user holding usable key material can push requests through the paes engine path.\nUI:N - No victim action is needed. Once the engine-side failure condition exists, the attacker's own AF_ALG requests (or ordinary dm-crypt I/O) hit the double completion.\nS:U - The corruption stays within the kernel's own security authority. There is no guest-to-host or other boundary crossing.\nC:H - crypto_pump_requests() calls crypto_request_complete() a second time after crypto_finalize_skcipher_request(). In AF_ALG the extra complete of ctx->wait lets a later request's areq be freed while the engine still processes it, so the engine keeps reading freed memory (use-after-free).\nI:H - The engine's skcipher walk and cpacf output keep writing into the freed request and scatterlist memory. For dm-crypt, the same bio completes twice. Both are use-after-free writes that can be used for heap corruption.\nA:H - The double completion corrupts request/bio lifetime (double bio end or a use-after-free on the areq), which can crash the kernel or corrupt dm-crypt I/O."}]}],"providerMetadata":{"dateUpdated":"2026-09-25T14:41:26.725Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/972e0d9b7d1d112240ccde1f1be85bf9ffaa1720"},{"url":"https://git.kernel.org/stable/c/5480291aa848e19e61175abfd457933516db70c6"},{"url":"https://git.kernel.org/stable/c/ac1481320110b803ab9b79ab4d2ca11a74fc05f2"}],"title":"s390/crypto: Fix wrong return code to engine in asynch callbacks","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-97589","datePublished":"2026-09-25T10:22:07.441Z","dateReserved":"2026-09-24T16:01:01.157Z","dateUpdated":"2026-09-25T14:41:26.725Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-09-25 11:17:10","lastModifiedDate":"2026-09-25 15:18:00","problem_types":[],"metrics":{"cvssMetricV31":[{"source":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","type":"Secondary","cvssData":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","baseScore":7,"baseSeverity":"HIGH","attackVector":"LOCAL","attackComplexity":"HIGH","privilegesRequired":"LOW","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"HIGH","availabilityImpact":"HIGH"},"exploitabilityScore":1,"impactScore":5.9}]},"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"97589","Ordinal":"1","Title":"s390/crypto: Fix wrong return code to engine in asynch callbacks","CVE":"CVE-2026-97589","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"97589","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\ns390/crypto: Fix wrong return code to engine in asynch callbacks\n\nWhen crypto_finalize_hash_request() or\ncrypto_finalize_skcipher_request() explicitly completes a request, the\ndo_one_request callback must return 0 to indicate successful\nhandling. Returning a negative error code causes the crypto engine to\nassume the driver failed to take ownership and triggers a second\ncompletion via crypto_request_complete(), resulting in a double\ncompletion. This pattern occurs in paes_s390.c 4 times and once in\nphmac_s390.c.\n\nFixed in phmac_do_one_request() and all four paes do_one_request\ncallbacks (ecb, cbc, ctr, xts) by returning 0 after explicit\nfinalization instead of propagating the error code.","Type":"Description","Title":"s390/crypto: Fix wrong return code to engine in asynch callbacks"}]}}}