Skip to main content
VulnerabilityPublished

CVE-2026-99496: Linux kernel · s390/vmcp: Initialize full session info to zero

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-99496· High

Not known to be exploited · fixed in f63eb4ee4a30fc5d8de07a229d92310e3c8d560c : patch Linux kernel soon.

Data as of 19 Nov 2026, 16:57 UTC

Severity
High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in f63eb4ee4a30fc5d8de07a229d92310e3c8d560c, 35254c6be12fb439be34a67dcba120bcb4542b3f, 1653ab681d830fcc20d69334f36808765b4de3fd +4

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • <6.12.118
  • <6.18.64
  • <7.3.2
Fixed in
  • f63eb4ee4a30fc5d8de07a229d92310e3c8d560c
  • 35254c6be12fb439be34a67dcba120bcb4542b3f
  • 1653ab681d830fcc20d69334f36808765b4de3fd
  • 041c5072258525fd54a15247e6a59446a34a5a76
  • 7.3.2
  • 6.18.64
  • 6.12.118

AI-suggested

A fix has been implemented in the Linux kernel to initialize the full session info to zero, resolving the issue. Users should apply the official kernel updates that include this fix.

Description

A vulnerability in the Linux kernel's s390/vmcp component involves uninitialized session information that can lead to kernel stack data leakage to users with CAP_SYS_ADMIN privileges. The issue arises because the cma_alloc bit and response may contain stale data, and cma_release may fail to free allocated memory, potentially exposing sensitive kernel information.

References

Community reviews

Loading reviews…