CVE-2026-63805Disclosure(linux / linux_kernel)

LOWCVSS 7.8 · HIGH

Signal is active with 1 mentions in latest observed window

Immediate actions

  • Track advisory updates for patch or workaround availability

Recommended action window: Monitor and triage in normal cycle

NVD description

In the Linux kernel, the following vulnerability has been resolved: crypto: nx - fix nx_crypto_ctx_exit argument nx_crypto_ctx_shash_exit calls nx_crypto_ctx_exit with crypto_shash_ctx(...) but crypto_shash_ctx gives a nx_crypto_ctx *, not a crypto_tfm *. Fix the type in nx_crypto_ctx_exit and drop the bogus crypto_tfm_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: nx_crypto_ctx_shash_exit+0x24/0x60 crypto_shash_exit_tfm+0x28/0x40 crypto_destroy_tfm+0x98/0x140 crypto_exit_ahash_using_shash+0x20/0x40 crypto_destroy_tfm+0x98/0x140 hash_release+0x1c/0x30 alg_sock_destruct+0x38/0x60 __sk_destruct+0x48/0x2b0 af_alg_release+0x58/0xb0 __sock_release+0x68/0x150 sock_close+0x20/0x40 __fput+0x110/0x3a0 sys_close+0x48/0xa0 system_call_exception+0x140/0x2d0 system_call_common+0xf4/0x258 .. which came from hardlink(1) opportunistically using AF_ALG. The same problem exists with nx_crypto_ctx_skcipher_exit getting a context it wasn't expecting, but apparently nobody hit that for years.

0.0/ 10 priority

Sources & remediation

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

AVAILABLE

Momentum

STABLE

Are you affected?

If you run products in this scope, you should treat this CVE as relevant to your environment.

  • linux_kernel

Threat summary

  • 2 mentions across 2 observed days
  • Momentum state: stable

What's happening

  • Technical details provided in 2 signals
  • Disclosure: 2 classified signals
  • Peaked 1d ago at 1 mentions (2026-07-19); latest day: 1
  • 2 total mentions across 2 days

Affected systems

Vendors
Products
linux_kernel

Deep dive

Activity timeline2 mentions / 2d
00111Mentions · 2026-07-19: 1Mentions · 2026-07-20: 1Technical Details · 2026-07-19: 1Technical Details · 2026-07-20: 107-1907-20
Signal classification1 categories
Disclosure
2100.0%
Referenced assets2 URLs
Full discourse2 posts
  • Windows Forum@windowsforum
    Disclosure

    🪟 CVE-2026-63805 crashes a Linux crypto driver on IBM PowerPC—not your Windows PC, Server, or usual WSL 2 setup. A kernel panic, but thankfully not one Microsoft users need to lose sleep over. https://windowsforum.com/threads/cve-2026-63805-fixes-ibm-power-linux-nx-crypto-kernel-crash.439560/?utm_source=x&utm_medium=social&utm_campaign=news_node84 #WindowsSecurity #LinuxKernel #IbmPowerpc #NxCrypto https://t.co/SKHnGahrGu

    Post summary

    The post announces that CVE-2026-63805 triggers a kernel panic on IBM PowerPC Linux systems via the Nx Crypto driver. No PoC, exploit details, or patch are mentioned, merely the existence of the vulnerability.

    0000040
    1.3K followersView on X
  • Vulmon Vulnerability Feed@VulmonFeeds
    Disclosure

    CVE-2026-63805 Linux Kernel Crypto NX Type Mismatch in Context Exit Functions https://vulmon.com/vulnerabilitydetails?qid=CVE-2026-63805

    Post summary

    The post identifies and briefly describes CVE‑2026‑63805, a Linux kernel crypto context exit function type mismatch, but does not provide PoC, exploit details, or mitigation information.

    0000098
    4.1K followersView on X
CPE platform detail1 entries

1 of 1 entries

PartVendorProductVersionTarget SWTarget HW
OSlinuxlinux_kernel---

Explore more