Skip to main content

Linux Kernel CVE-2026-53082

| EUVDEUVD-2026-38950 MEDIUM
Use of Uninitialized Resource (CWE-908)
2026-06-24 Linux GHSA-33fq-h3x2-m8v9
5.5
CVSS 3.1 · NVD
Share

Severity by source

NVD PRIMARY
5.5 MEDIUM
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
vuln.today AI
5.5 MEDIUM

Local TTY device access requires low-privilege local session; only kernel availability (crash) is impacted, with no confidentiality or integrity effect.

3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
4.0 AV:L/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
SUSE
3.3 LOW
AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Primary rating from NVD.

CVSS VectorNVD

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Lifecycle Timeline

5
Analysis Generated
Jul 23, 2026 - 18:54 vuln.today
CVSS changed
Jul 23, 2026 - 18:53 NVD
5.5 (MEDIUM)
Patch available
Jun 24, 2026 - 18:02 EUVD
CVE Published
Jun 24, 2026 - 16:30 nvd
MEDIUM 5.5
CVE Published
Jun 24, 2026 - 16:30 cve.org
UNKNOWN (no severity yet)

DescriptionNVD

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.

AnalysisAI

Uninitialized memory read in the Linux kernel's hamradio 6pack TTY driver (net/hamradio/6pack.c) allows a local low-privileged user to crash the kernel, causing a denial of service. The flaw exists across a broad range of stable kernel branches from 2.6.12 through at least 7.0, and patches have been issued across eight stable series. No public exploit code exists and no active exploitation has been reported; with an EPSS of 0.16% at the 6th percentile, real-world risk is constrained by the highly niche deployment context of amateur-radio 6pack hardware.

Technical ContextAI

The 6pack protocol (CWE-908: Use of Uninitialized Resource) is an AX.25-based framing protocol used over amateur radio links, implemented in drivers/net/hamradio/6pack.c. The TTY subsystem passes received data to line-discipline receive callbacks as two parallel buffers: a data buffer (cp) and a per-byte flag buffer (fp). Flags indicate TTY-layer errors (parity, framing, etc.) and the convention across all other SLIP-family drivers (slip_receive_buf, mkiss_receive_buf) is to iterate both buffers in lockstep, skipping data bytes whose corresponding flag is set. In the vulnerable code, the while loop correctly iterates fp but never advances cp, so sixpack_decode() is called with the original unfiltered data buffer and the original byte count - causing it to consume positions marked as erroneous by the TTY layer. Because the TTY layer provides no guarantee that cp[i] holds a meaningful value when fp[i] is non-zero, KMSAN (Kernel Memory Sanitizer) detects an uninit-value read at those positions. CPE data (cpe:2.3:a:linux:linux) confirms the affected product is the mainline Linux kernel.

RemediationAI

The primary fix is to update to a patched kernel version: 5.10.258 or later on the 5.10 LTS branch, 5.15.209 or later on 5.15, 6.1.175 or later on 6.1, 6.6.141 or later on 6.6, 6.12.91 or later on 6.12, 6.18.33 or later on 6.18, 7.0.10 or later on 7.0, or any 7.1+ release. Upstream fix commits are available at https://git.kernel.org/stable/c/1d3abf0c3dde (and the other branch-specific commits referenced above). Ubuntu users should apply USN-8566-1, USN-8567-1, or USN-8568-1 as appropriate for their kernel flavor. As a compensating control, systems that do not use amateur radio 6pack hardware can unload or blacklist the 6pack kernel module (modprobe -r 6pack; echo 'blacklist 6pack' >> /etc/modprobe.d/blacklist.conf) - this eliminates the attack surface entirely with no operational impact on non-hamradio hosts. No side effects from blacklisting apply to standard server, desktop, or cloud deployments.

Vendor StatusVendor

SUSE

Severity: Low
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 16.0 Affected

Share

CVE-2026-53082 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy