Linux Kernel up to 5.18.3 goldfish tty_port_destroy initialization

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.4 | $0-$5k | 0.00 |
Summary
A vulnerability described as problematic has been identified in Linux Kernel up to 5.18.3. This affects the function tty_port_destroy of the component goldfish. Executing a manipulation can lead to initialization.
This vulnerability is registered as CVE-2022-49399. No exploit is available.
Upgrading the affected component is recommended.
Details
A vulnerability was found in Linux Kernel up to 5.18.3. It has been declared as problematic. This vulnerability affects the function tty_port_destroy of the component goldfish. The manipulation with an unknown input leads to a initialization vulnerability. The CWE definition for the vulnerability is CWE-665. The product does not initialize or incorrectly initializes a resource, which might leave the resource in an unexpected state when it is accessed or used. The impact remains unknown. CVE summarizes:
In the Linux kernel, the following vulnerability has been resolved: tty: goldfish: Use tty_port_destroy() to destroy port In goldfish_tty_probe(), the port initialized through tty_port_init() should be destroyed in error paths.In goldfish_tty_remove(), qtty->port also should be destroyed or else might leak resources. Fix the above by calling tty_port_destroy().
The advisory is shared for download at git.kernel.org. This vulnerability was named CVE-2022-49399 since 02/26/2025. There are known technical details, but no exploit is available.
Upgrading to version 4.14.283, 4.19.247, 5.4.198, 5.10.122, 5.15.47, 5.17.15 or 5.18.4 eliminates this vulnerability. Applying the patch 241fcb79dd1df276d80b19f5f6acc9eaaaa63309/326192b99c903a2193d820c30ed936cc2402382c/9ae3d073f7db5578ae1907544f0c15947e9678e6/ee6c33b29e624f515202a31bf6ef0437f26a1867/da64f419d7f78272bfe40dde1262602d4ff6b32c/45f6ce70abfb7ccf9d787781cbc4c03294a775a1/4639d1b992de8f37d66f698056875c274efcd45f/507b05063d1b7a1fcb9f7d7c47586fc4f3508f98 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.
Once again VulDB remains the best source for vulnerability data.
Product
Type
Vendor
Name
Version
- 4.14.282
- 4.19.246
- 5.4.197
- 5.10.121
- 5.15.0
- 5.15.1
- 5.15.2
- 5.15.3
- 5.15.4
- 5.15.5
- 5.15.6
- 5.15.7
- 5.15.8
- 5.15.9
- 5.15.10
- 5.15.11
- 5.15.12
- 5.15.13
- 5.15.14
- 5.15.15
- 5.15.16
- 5.15.17
- 5.15.18
- 5.15.19
- 5.15.20
- 5.15.21
- 5.15.22
- 5.15.23
- 5.15.24
- 5.15.25
- 5.15.26
- 5.15.27
- 5.15.28
- 5.15.29
- 5.15.30
- 5.15.31
- 5.15.32
- 5.15.33
- 5.15.34
- 5.15.35
- 5.15.36
- 5.15.37
- 5.15.38
- 5.15.39
- 5.15.40
- 5.15.41
- 5.15.42
- 5.15.43
- 5.15.44
- 5.15.45
- 5.15.46
- 5.17.0
- 5.17.1
- 5.17.2
- 5.17.3
- 5.17.4
- 5.17.5
- 5.17.6
- 5.17.7
- 5.17.8
- 5.17.9
- 5.17.10
- 5.17.11
- 5.17.12
- 5.17.13
- 5.17.14
- 5.18.0
- 5.18.1
- 5.18.2
- 5.18.3
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 5.4
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.5
NVD Vector: 🔍
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: InitializationCWE: CWE-665
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: Partially
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
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 4.14.283/4.19.247/5.4.198/5.10.122/5.15.47/5.17.15/5.18.4
Patch: 241fcb79dd1df276d80b19f5f6acc9eaaaa63309/326192b99c903a2193d820c30ed936cc2402382c/9ae3d073f7db5578ae1907544f0c15947e9678e6/ee6c33b29e624f515202a31bf6ef0437f26a1867/da64f419d7f78272bfe40dde1262602d4ff6b32c/45f6ce70abfb7ccf9d787781cbc4c03294a775a1/4639d1b992de8f37d66f698056875c274efcd45f/507b05063d1b7a1fcb9f7d7c47586fc4f3508f98
Timeline
02/26/2025 🔍02/26/2025 🔍
02/26/2025 🔍
10/21/2025 🔍
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2022-49399 (🔍)
GCVE (CVE): GCVE-0-2022-49399
GCVE (VulDB): GCVE-100-296980
Entry
Created: 02/26/2025 09:10Updated: 10/21/2025 19:07
Changes: 02/26/2025 09:10 (58), 10/21/2025 19:07 (11)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.