Skip to main content
VulnerabilityPublished Updated

CVE-2026-98755: Linux kernel · tty: vcc: zero-initialize control packet in vcc_send_ctl()

Source GCVE Database

0
Authoritative record:CVE-2026-98755· Medium

Not known to be exploited · fixed in 4335278d0e75395cbfaf71c84b521df56d69e936 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 13:47 UTC

Severity
Medium

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS
0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4335278d0e75395cbfaf71c84b521df56d69e936, 399aa38af1d78001612e3130b2056ea392a355ca, 6f1a08ef02825b440126c406ea63ef6128888e15 +2

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 8868e44a56160328cd4003d95f4083f64b136e33, < 4335278d0e75395cbfaf71c84b521df56d69e936
Fixed in
  • 4335278d0e75395cbfaf71c84b521df56d69e936
LinuxLinuxAffected
  • ≥ 8868e44a56160328cd4003d95f4083f64b136e33, < 399aa38af1d78001612e3130b2056ea392a355ca
Fixed in
  • 399aa38af1d78001612e3130b2056ea392a355ca
LinuxLinuxAffected
  • ≥ 8868e44a56160328cd4003d95f4083f64b136e33, < 6f1a08ef02825b440126c406ea63ef6128888e15
Fixed in
  • 6f1a08ef02825b440126c406ea63ef6128888e15
LinuxLinuxAffected
  • ≥ 8868e44a56160328cd4003d95f4083f64b136e33, < 4b59afc8af3143ae03e4f9b81ca66aa5a1c1ebed
Fixed in
  • 4b59afc8af3143ae03e4f9b81ca66aa5a1c1ebed
LinuxLinuxAffected
  • ≥ 8868e44a56160328cd4003d95f4083f64b136e33, < 1f71f565e3585da1098ff19ca3c24687dab59185
Fixed in
  • 1f71f565e3585da1098ff19ca3c24687dab59185
LinuxLinuxAffected
  • =4.14
Fixed in–

AI-suggested

A fix has been implemented in the Linux kernel to zero-initialize the control packet in the vcc_send_ctl() function, eliminating the uninitialized memory leak. Users should apply the official kernel updates that include this patch once available. Patch status is not explicitly confirmed in the provided data; therefore, check the vendor advisory for current remediation guidance.

Description

A vulnerability in the Linux kernel's tty vcc component involved a stack-allocated control packet structure that was only partially initialized. Specifically, the tag.stype_env field was left uninitialized before being sent via ldc_write(), which could lead to leakage of kernel stack data to the LDC peer. This issue has been resolved by zero-initializing the control packet in the vcc_send_ctl() function.

References

Community reviews

Loading reviews…