CVE-2026-63805: crypto: nx - fix nx_crypto_ctx_exit argument
In the Linux kernel, the following vulnerability has been resolved:
crypto: nx - fix nxcryptoctxexit argument
nxcryptoctxshashexit calls nxcryptoctxexit with cryptoshashctx(...) but cryptoshashctx gives a nxcryptoctx , not a cryptotfm .
Fix the type in nxcryptoctxexit and drop the bogus cryptotfmctx 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 afalgrelease+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 AFALG.
The same problem exists with nxcryptoctxskcipherexit getting a context it wasn't expecting, but apparently nobody hit that for years.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Compensating control
If possible, avoid using AF_ALG (e.g., the hardlink opportunistic use noted in the incident) until the kernel fix is applied.
Event History
Frequently Asked Questions
What is the severity of CVE-2026-63805?
The severity of CVE-2026-63805 is high with a CVSS score of 7.8.
How do I fix CVE-2026-63805?
To fix CVE-2026-63805, apply the available patch provided in the upstream Linux kernel releases.
What are the potential impacts of CVE-2026-63805?
CVE-2026-63805 may lead to vulnerabilities in cryptographic processes, potentially compromising data integrity and confidentiality.
Which software is affected by CVE-2026-63805?
CVE-2026-63805 affects the Linux kernel.
When was CVE-2026-63805 reported?
CVE-2026-63805 was published on July 19, 2026.