Linux Kernel up to 7.0.9 net sixpack_receive_buf infinite loop

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

Summaryinfo

A vulnerability was found in Linux Kernel up to 7.0.9. It has been classified as critical. This affects the function sixpack_receive_buf of the component net. This manipulation causes infinite loop. This vulnerability is handled as CVE-2026-53082. There is not any exploit available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability has been found in Linux Kernel up to 7.0.9 and classified as critical. Affected by this vulnerability is the function sixpack_receive_buf of the component net. The manipulation with an unknown input leads to a infinite loop vulnerability. The CWE definition for the vulnerability is CWE-835. The product contains an iteration or loop with an exit condition that cannot be reached, i.e., an infinite loop. As an impact it is known to affect availability. The summary by CVE is:

In the Linux kernel, the following vulnerability has been resolved: net: hamradio: 6pack: fix uninit-value in sixpack_receive_buf sixpack_receive_buf() does not properly skip bytes with TTY error flags. The while loop iterates through the flags buffer but never advances the data pointer (cp), and passes the original count (including error bytes) to sixpack_decode(). This causes sixpack_decode() to process bytes that should have been skipped due to TTY errors. The TTY layer does not guarantee that cp[i] holds a meaningful value when fp[i] is set, so passing those positions to sixpack_decode() results in KMSAN reporting an uninit-value read. Fix this by processing bytes one at a time, advancing cp on each iteration, and only passing valid (non-error) bytes to sixpack_decode(). This matches the pattern used by slip_receive_buf() and mkiss_receive_buf() for the same purpose.

The advisory is shared at git.kernel.org. This vulnerability is known as CVE-2026-53082 since 06/09/2026. Technical details are known, but no exploit is available.

The vulnerability scanner Nessus provides a plugin with the ID 322722 (Linux Distros Unpatched Vulnerability : CVE-2026-53082), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 5.10.258, 5.15.209, 6.1.175, 6.6.141, 6.12.91, 6.18.33 or 7.0.10 eliminates this vulnerability. Applying the patch 1d3abf0c3ddeefc6f6d913aa129acc06fce8240a/d4cceb5184538613572fb79319453f281b1eeacb/2951656b0de00153f2687f3a093890bce72b6215/e9cf4018d74237d142cd66243c821d13593270f0/d9ce2a4b679122397d7f35bad7be46913ad1ca80/987af7625ceb1ee59d70eb0abd7af11c75e45d79/578f3aba427c938fecfa0d8c83d9acb213a9b24a/bf9a38803b2626b01cc769aaf13485d8650f576f 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.

The vulnerability is also documented in the databases at Tenable (322722) and CERT Bund (WID-SEC-2026-2077). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Affected

  • Open Source Linux Kernel

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.7
VulDB Meta Temp Score: 5.5

VulDB Base Score: 5.7
VulDB Temp Score: 5.5
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Infinite loop
CWE: CWE-835 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Partially

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 322722
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2026-53082

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 5.10.258/5.15.209/6.1.175/6.6.141/6.12.91/6.18.33/7.0.10
Patch: 1d3abf0c3ddeefc6f6d913aa129acc06fce8240a/d4cceb5184538613572fb79319453f281b1eeacb/2951656b0de00153f2687f3a093890bce72b6215/e9cf4018d74237d142cd66243c821d13593270f0/d9ce2a4b679122397d7f35bad7be46913ad1ca80/987af7625ceb1ee59d70eb0abd7af11c75e45d79/578f3aba427c938fecfa0d8c83d9acb213a9b24a/bf9a38803b2626b01cc769aaf13485d8650f576f

Timelineinfo

06/09/2026 CVE reserved
06/24/2026 +15 days Advisory disclosed
06/24/2026 +0 days VulDB entry created
06/28/2026 +4 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-53082 (🔒)
GCVE (CVE): GCVE-0-2026-53082
GCVE (VulDB): GCVE-100-373441
CERT Bund: WID-SEC-2026-2077 - Linux Kernel: Mehrere Schwachstellen

Entryinfo

Created: 06/24/2026 21:11
Updated: 06/28/2026 03:00
Changes: 06/24/2026 21:11 (59), 06/25/2026 14:09 (2), 06/28/2026 03:00 (7)
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.

Do you want to use VulDB in your project?

Use the official API to access entries easily!