Skip to main content

Linux Kernel CVE-2026-63857

| EUVDEUVD-2026-45541 CRITICAL
2026-07-19 Linux GHSA-93j7-q4pr-7pmf
Critical
Disputed · 9.8 Vendor: Linux
Share

Severity by source

Sources disagree (Medium–Critical)
Vendor (Linux) PRIMARY
9.8 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
vuln.today AI
2.5 LOW

Local transmit path on specific hardware (AV:L), requires driving fragmented TX and hitting an unmapped page (AC:H, PR:L); no data impact since values are never used, only a possible crash (C:N/I:N/A:L).

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

vuln.today treats the vendor’s rating as authoritative. A higher third-party CVSS (e.g. CISA-ADP) is shown for transparency but does not drive the headline severity.

CVSS VectorVendor: Linux

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

Lifecycle Timeline

4
Analysis Generated
Jul 20, 2026 - 15:57 vuln.today
CVSS changed
Jul 20, 2026 - 15:22 NVD
9.8 (CRITICAL)
CVE Published
Jul 19, 2026 - 14:04 cve.org
CRITICAL 9.8
CVE Published
Jul 19, 2026 - 14:04 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

In the Linux kernel, the following vulnerability has been resolved:

net: airoha: Do not read uninitialized fragment address in airoha_dev_xmit()

The transmit loop in airoha_dev_xmit() reads fragment address and length during its final iteration, when the loop index equals skb_shinfo(skb)->nr_frags, at which point the fragment data is uninitialized. While these values are never consumed, the read itself is unsafe and may trigger a page fault. Fix this by avoiding the fragment read on the last iteration. Additionally, move the skb pointer from the first to the last used packet descriptor, so that airoha_qdma_tx_napi_poll() defers freeing the skb until the final descriptor is processed.

AnalysisAI

An uninitialized-memory read in the Airoha ethernet driver (airoha_dev_xmit) of the Linux kernel affects systems using MediaTek/Airoha EN7581-class networking SoCs, where the transmit loop reads a fragment address and length on its final iteration before that descriptor data is initialized. Although the read values are never consumed, the access itself is unsafe and can trigger a page fault, potentially crashing the kernel during packet transmission. EPSS is low (0.15%, 5th percentile), there is no public exploit identified at time of analysis, and it is not listed in CISA KEV. Note: the auto-assigned CVSS of 9.8 (AV:N/C:H/I:H/A:H) appears substantially inflated for what is a local transmit-path bug with availability-only impact.

Technical ContextAI

The flaw resides in the airoha_eth driver, which supports the packet-processing engine (PPE/QDMA) on Airoha/MediaTek EN7581 and related router-class SoCs. In airoha_dev_xmit() the scatter-gather transmit loop iterates over skb_shinfo(skb)->nr_frags fragments; on the terminating iteration (index == nr_frags) it dereferences fragment metadata that has not yet been populated, reading an uninitialized DMA/fragment address. The fix avoids the fragment read on the last iteration and moves the skb pointer from the first to the last used TX descriptor so airoha_qdma_tx_napi_poll() defers freeing the skb until the final descriptor is processed, preventing both the bad read and premature buffer release. The root cause is a classic use-of-uninitialized/out-of-bounds-adjacent read (CWE-457/CWE-125 class); the CWE field in the source data is N/A. Despite the 'Information Disclosure' tag, the description states the values are never consumed, so the practical impact is a potential page fault rather than data leakage.

RemediationAI

Apply the vendor-released patch by upgrading to a fixed Linux stable kernel - 6.18.33 or 7.0.10 (or later), or the 7.1 line - which corresponds to upstream commits f670fa4b, d78c8ab7, and bde34e84 available at git.kernel.org/stable. Because the bug lives only in the airoha_eth driver, systems that do not use Airoha/EN7581 networking hardware are effectively unaffected and can patch on their normal cadence. Where immediate kernel upgrade is not possible on affected hardware, the only meaningful compensating control is to unload or disable the airoha_eth module (blacklist it), which eliminates the code path but also disables the associated network interface - an acceptable trade-off only on systems that do not depend on that NIC. There are no relevant configuration-level workarounds; rebuilding with the patched driver is the correct fix.

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Not-Affected
SUSE Linux Enterprise Desktop 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 16.0 Not-Affected

Share

CVE-2026-63857 vulnerability details – vuln.today

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