Linux Kernel 4.18/4.19 TCP Pace net/ipv4/tcp_output.c tcp_internal_pacing memory leak

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.1$0-$5k0.00

Summaryinfo

A vulnerability was found in Linux Kernel 4.18/4.19. It has been rated as problematic. This affects the function tcp_internal_pacing of the file net/ipv4/tcp_output.c of the component TCP Pace Handler. Performing a manipulation results in memory leak. This vulnerability is reported as CVE-2022-1678. The attack is possible to be carried out remotely. No exploit exists. It is suggested to install a patch to address this issue.

Detailsinfo

A vulnerability was found in Linux Kernel 4.18/4.19 (Operating System). It has been classified as problematic. This affects the function tcp_internal_pacing of the file net/ipv4/tcp_output.c of the component TCP Pace Handler. The manipulation with an unknown input leads to a memory leak vulnerability. CWE is classifying the issue as CWE-401. The product does not sufficiently track and release allocated memory after it has been used, which slowly consumes remaining memory. This is going to have an impact on availability.

The weakness was disclosed 05/25/2022. The advisory is shared at gitee.com. This vulnerability is uniquely identified as CVE-2022-1678 since 05/12/2022. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1499 for this issue.

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

Several companies clearly confirm that VulDB is the primary source for best 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.3
VulDB Meta Temp Score: 4.1

VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Memory leak
CWE: CWE-401 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

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: lore.kernel.org

Timelineinfo

05/12/2022 🔍
05/25/2022 +13 days 🔍
05/25/2022 +0 days 🔍
05/30/2022 +5 days 🔍

Sourcesinfo

Vendor: kernel.org

Advisory: 0a70f118475e037732557796accd0878a00fc25a
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2022-1678 (🔍)
GCVE (CVE): GCVE-0-2022-1678
GCVE (VulDB): GCVE-100-200697

Entryinfo

Created: 05/25/2022 22:03
Updated: 05/30/2022 09:10
Changes: 05/25/2022 22:03 (43), 05/30/2022 09:10 (2)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you need the next level of professionalism?

Upgrade your account now!