Linux Kernel up to 6.12.112/6.18.55/7.2.9/7.3-rc5 VCC vcc_send_ctl tag.stype_env missing initialization

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 2.2 | $0-$5k | 0.89- |
Summary
A vulnerability, which was classified as problematic, has been found in Linux Kernel up to 6.12.112/6.18.55/7.2.9/7.3-rc5. Affected is the function vcc_send_ctl of the component VCC. The manipulation of the argument tag.stype_env leads to missing initialization.
This vulnerability is listed as CVE-2026-98755. The attack must be carried out locally. There is no available exploit.
It is advisable to upgrade the affected component.
Details
A vulnerability, which was classified as problematic, has been found in Linux Kernel up to 6.12.112/6.18.55/7.2.9/7.3-rc5. This issue affects the function vcc_send_ctl of the component VCC. The manipulation of the argument tag.stype_env with an unknown input leads to a missing initialization vulnerability. Using CWE to declare the problem leads to CWE-456. The product does not initialize critical variables, which causes the execution environment to use unexpected values. Impacted is confidentiality. The summary by CVE is:
In the Linux kernel, the following vulnerability has been resolved: tty: vcc: zero-initialize control packet in vcc_send_ctl() The stack-allocated struct vio_vcc pkt was partially initialized, leaving the tag.stype_env field uninitialized before being sent via ldc_write(), potentially leaking kernel stack data to the LDC peer.
It is possible to read the advisory at git.kernel.org. The identification of this vulnerability is CVE-2026-98755 since 09/25/2026. The exploitation is known to be easy. Attacking locally is a requirement. Additional levels of successful authentication are necessary for exploitation. Technical details of the vulnerability are known, but there is no available exploit.
Upgrading to version 6.12.113, 6.18.56, 7.2.10 or 7.3-rc6 eliminates this vulnerability. Applying the patch 6f1a08ef02825b440126c406ea63ef6128888e15/4335278d0e75395cbfaf71c84b521df56d69e936/399aa38af1d78001612e3130b2056ea392a355ca/1f71f565e3585da1098ff19ca3c24687dab59185 is able to eliminate this problem. The best possible mitigation is suggested to be upgrading to the latest version.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
Version
- 6.12.112
- 6.18.0
- 6.18.1
- 6.18.2
- 6.18.3
- 6.18.4
- 6.18.5
- 6.18.6
- 6.18.7
- 6.18.8
- 6.18.9
- 6.18.10
- 6.18.11
- 6.18.12
- 6.18.13
- 6.18.14
- 6.18.15
- 6.18.16
- 6.18.17
- 6.18.18
- 6.18.19
- 6.18.20
- 6.18.21
- 6.18.22
- 6.18.23
- 6.18.24
- 6.18.25
- 6.18.26
- 6.18.27
- 6.18.28
- 6.18.29
- 6.18.30
- 6.18.31
- 6.18.32
- 6.18.33
- 6.18.34
- 6.18.35
- 6.18.36
- 6.18.37
- 6.18.38
- 6.18.39
- 6.18.40
- 6.18.41
- 6.18.42
- 6.18.43
- 6.18.44
- 6.18.45
- 6.18.46
- 6.18.47
- 6.18.48
- 6.18.49
- 6.18.50
- 6.18.51
- 6.18.52
- 6.18.53
- 6.18.54
- 6.18.55
- 7.2.0
- 7.2.1
- 7.2.2
- 7.2.3
- 7.2.4
- 7.2.5
- 7.2.6
- 7.2.7
- 7.2.8
- 7.2.9
- 7.3-rc1
- 7.3-rc2
- 7.3-rc3
- 7.3-rc4
- 7.3-rc5
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 2.3VulDB Meta Temp Score: 2.2
VulDB Base Score: 2.3
VulDB Temp Score: 2.2
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Missing initializationCWE: CWE-456 / CWE-453
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Kernel 6.12.113/6.18.56/7.2.10/7.3-rc6
Patch: 6f1a08ef02825b440126c406ea63ef6128888e15/4335278d0e75395cbfaf71c84b521df56d69e936/399aa38af1d78001612e3130b2056ea392a355ca/1f71f565e3585da1098ff19ca3c24687dab59185
Timeline
09/25/2026 CVE reserved10/18/2026 Advisory disclosed
10/18/2026 VulDB entry created
10/18/2026 VulDB entry last update
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2026-98755 (🔒)
GCVE (CVE): GCVE-0-2026-98755
GCVE (VulDB): GCVE-100-422003
Entry
Created: 10/18/2026 19:46Changes: 10/18/2026 19:46 (60)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.