Linux Kernel up to 7.1.8 Virtual Terminal vt_k_ioctl permission

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.2 | $0-$5k | 0.43 |
Summary
A vulnerability identified as problematic has been detected in Linux Kernel up to 7.1.8. Affected is the function vt_k_ioctl of the component Virtual Terminal. This manipulation causes permission.
The identification of this vulnerability is CVE-2026-74676. The attack can only be executed locally. There is no exploit available.
Details
A vulnerability was found in Linux Kernel up to 7.1.8. It has been declared as problematic. Affected by this vulnerability is the function vt_k_ioctl of the component Virtual Terminal. The manipulation with an unknown input leads to a permission vulnerability. The CWE definition for the vulnerability is CWE-275. As an impact it is known to affect integrity, and availability. The summary by CVE is:
In the Linux kernel, the following vulnerability has been resolved: vt: add permission check for KDSKBMETA ioctl KDSKBMETA modifies keyboard meta mode but lacks the !perm check that all other keyboard setter ioctls in vt_k_ioctl() enforce, allowing a process to change meta mode on a non-controlling console without authorization.
It is possible to read the advisory at git.kernel.org. This vulnerability is known as CVE-2026-74676 since 08/15/2026. The exploitation appears to be easy. Attacking locally is a requirement. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 08/22/2026). The attack technique deployed by this issue is T1222 according to MITRE ATT&CK.
Upgrading to version 5.10.265, 5.15.216, 6.1.183, 6.6.152, 6.12.104, 6.18.45 or 7.1.9 eliminates this vulnerability. Applying the patch 9f8cbaf4b774694dcc292e60509762483ebfd9ae/ddc4a8303347114e945b9e6e81b81d77855f7358/1c5b67a1e2cb7d78dab321280f330b056e3bf437/d8ead5083b203d12b8319e7cb29cc6b8836e813f/4671c3b79e337bbae28c2d79023dc642df012bde/a1c31e026c93e378e297a8df8328983d3013a59f/7bf32337a7103ccb686cbd240324bf26225ef2d6/a7ad0034453ba4c353f9b8f810ee2569de33d283 is able to eliminate this problem.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
Version
- 5.10.264
- 5.15.215
- 6.1.182
- 6.6.151
- 6.12.103
- 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
- 7.1.0
- 7.1.1
- 7.1.2
- 7.1.3
- 7.1.4
- 7.1.5
- 7.1.6
- 7.1.7
- 7.1.8
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.4VulDB Meta Temp Score: 4.2
VulDB Base Score: 4.4
VulDB Temp Score: 4.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: PermissionCWE: CWE-275 / CWE-266
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 5.10.265/5.15.216/6.1.183/6.6.152/6.12.104/6.18.45/7.1.9
Patch: 9f8cbaf4b774694dcc292e60509762483ebfd9ae/ddc4a8303347114e945b9e6e81b81d77855f7358/1c5b67a1e2cb7d78dab321280f330b056e3bf437/d8ead5083b203d12b8319e7cb29cc6b8836e813f/4671c3b79e337bbae28c2d79023dc642df012bde/a1c31e026c93e378e297a8df8328983d3013a59f/7bf32337a7103ccb686cbd240324bf26225ef2d6/a7ad0034453ba4c353f9b8f810ee2569de33d283
Timeline
08/15/2026 CVE reserved08/22/2026 Advisory disclosed
08/22/2026 VulDB entry created
08/22/2026 VulDB entry last update
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2026-74676 (🔒)
GCVE (CVE): GCVE-0-2026-74676
GCVE (VulDB): GCVE-100-394459
Entry
Created: 08/22/2026 18:50Changes: 08/22/2026 18:50 (59)
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.