Linux Kernel up to 6.2.0-rc2 drivers/tty/vcc.c vcc_open use after free

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
4.7$0-$5k0.00

Summaryinfo

A vulnerability categorized as problematic has been discovered in Linux Kernel up to 6.2.0-rc2. Affected by this vulnerability is the function vcc_open of the file drivers/tty/vcc.c. The manipulation results in use after free. This vulnerability was named CVE-2023-23039. An attack on the physical device is feasible. There is no available exploit. It is advisable to implement a patch to correct this issue.

Detailsinfo

A vulnerability, which was classified as problematic, was found in Linux Kernel up to 6.2.0-rc2 (Operating System). Affected is the function vcc_open of the file drivers/tty/vcc.c. The manipulation with an unknown input leads to a use after free vulnerability. CWE is classifying the issue as CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. The impact remains unknown. CVE summarizes:

An issue was discovered in the Linux kernel through 6.2.0-rc2. drivers/tty/vcc.c has a race condition and resultant use-after-free if a physically proximate attacker removes a VCC device while calling open(), aka a race condition between vcc_open() and vcc_remove().

The weakness was presented 02/22/2023. The advisory is shared for download at lkml.org. This vulnerability is traded as CVE-2023-23039 since 01/11/2023. There are known technical details, but no exploit is available.

Applying a patch is able to eliminate this problem. The bugfix is ready for download at lkml.org.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2023-27139). Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.7
VulDB Meta Temp Score: 4.7

VulDB Base Score: 3.8
VulDB Temp Score: 3.7
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 5.7
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Use after free
CWE: CWE-416 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍

Physical: Yes
Local: Yes
Remote: No

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Patch
Status: 🔍

0-Day Time: 🔍

Patch: lkml.org

Timelineinfo

01/11/2023 🔍
02/22/2023 +42 days 🔍
02/22/2023 +0 days 🔍
10/06/2025 +957 days 🔍

Sourcesinfo

Vendor: kernel.org

Advisory: lkml.org
Status: Confirmed

CVE: CVE-2023-23039 (🔍)
GCVE (CVE): GCVE-0-2023-23039
GCVE (VulDB): GCVE-100-221628
EUVD: 🔍

Entryinfo

Created: 02/22/2023 18:46
Updated: 10/06/2025 07:59
Changes: 02/22/2023 18:46 (41), 03/21/2025 02:24 (25), 10/06/2025 07:59 (1)
Complete: 🔍
Cache ID: 216::103

Once again VulDB remains the best source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!