In the Linux kernel, the following vulnerability has been resolved:
crypto: nx - fix nxcryptoctx_exit argument
nxcryptoctxshashexit calls nxcryptoctxexit with cryptoshashctx(...) but cryptoshashctx gives a nxcryptoctx *, not a cryptotfm *.
Fix the type in nxcryptoctxexit and drop the bogus cryptotfm_ctx call.
This fixes the following oops:
BUG: Unable to handle kernel data access at 0xc0403effffffffc8 Faulting instruction address: 0xc000000000396cb4 Oops: Kernel access of bad area, sig: 11 [#15] Call Trace: nxcryptoctxshashexit+0x24/0x60 cryptoshashexittfm+0x28/0x40 cryptodestroytfm+0x98/0x140 cryptoexitahashusingshash+0x20/0x40 cryptodestroytfm+0x98/0x140 hashrelease+0x1c/0x30 algsockdestruct+0x38/0x60 __skdestruct+0x48/0x2b0 afalg_release+0x58/0xb0 __sockrelease+0x68/0x150 sockclose+0x20/0x40 _fput+0x110/0x3a0 sysclose+0x48/0xa0 systemcallexception+0x140/0x2d0 systemcallcommon+0xf4/0x258
.. which came from hardlink(1) opportunistically using AF_ALG.
The same problem exists with nxcryptoctxskcipherexit getting a context it wasn't expecting, but apparently nobody hit that for years.
{
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/63xxx/CVE-2026-63805.json",
"cna_assigner": "Linux"
}