{ "dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": { "cveId": "CVE-2026-97589", "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "state": "PUBLISHED", "assignerShortName": "Linux", "dateReserved": "2026-09-24T16:01:01.157Z", "datePublished": "2026-09-25T10:22:07.441Z", "dateUpdated": "2026-10-19T09:09:53.140Z" }, "containers": { "cna": { "providerMetadata": { "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "shortName": "Linux", "dateUpdated": "2026-10-19T09:09:53.140Z" }, "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": { "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" }, "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." } ] } ], "affected": [ { "product": "Linux", "vendor": "Linux", "defaultStatus": "unaffected", "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "programFiles": [ "arch/s390/crypto/paes_s390.c", "arch/s390/crypto/phmac_s390.c" ], "versions": [ { "version": "6cd87cb5ef6ca50ae17c371482ceaab1d635e232", "lessThan": "972e0d9b7d1d112240ccde1f1be85bf9ffaa1720", "status": "affected", "versionType": "git" }, { "version": "6cd87cb5ef6ca50ae17c371482ceaab1d635e232", "lessThan": "5480291aa848e19e61175abfd457933516db70c6", "status": "affected", "versionType": "git" }, { "version": "6cd87cb5ef6ca50ae17c371482ceaab1d635e232", "lessThan": "ac1481320110b803ab9b79ab4d2ca11a74fc05f2", "status": "affected", "versionType": "git" } ] }, { "product": "Linux", "vendor": "Linux", "defaultStatus": "affected", "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "programFiles": [ "arch/s390/crypto/paes_s390.c", "arch/s390/crypto/phmac_s390.c" ], "versions": [ { "version": "6.16", "status": "affected" }, { "version": "0", "lessThan": "6.16", "status": "unaffected", "versionType": "semver" }, { "version": "6.18.53", "lessThanOrEqual": "6.18.*", "status": "unaffected", "versionType": "semver" }, { "version": "7.2.7", "lessThanOrEqual": "7.2.*", "status": "unaffected", "versionType": "semver" }, { "version": "7.3", "lessThanOrEqual": "*", "status": "unaffected", "versionType": "original_commit_for_fix" } ] } ], "cpeApplicability": [ { "nodes": [ { "operator": "OR", "negate": false, "cpeMatch": [ { "vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "6.16", "versionEndExcluding": "6.18.53" }, { "vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "6.16", "versionEndExcluding": "7.2.7" }, { "vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "6.16", "versionEndExcluding": "7.3" } ] } ] } ], "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" } } } }