CVE-2026-80617

net: airoha: fix foe_check_time allocation size

Published Aug 28, 2026 CVSS 3.1 · 9.8 Critical EPSS < 1% KEV · Not listed
Description
In the Linux kernel, the following vulnerability has been resolved:

net: airoha: fix foe_check_time allocation size

foe_check_time is declared as u16 pointer but was allocated with
only ppe_num_entries bytes instead of ppe_num_entries * sizeof(u16).

When airoha_ppe_foe_verify_entry() is called with hash >= ppe_num_entries/2,
it writes beyond the allocated buffer, causing heap buffer overflow and
potential kernel crash.

Analysis

AI-generated

Technical impact

In the Linux airoha network driver, a pointer declared as a 16‑bit unsigned integer array is allocated with only one byte per entry. The verification routine airoha_ppe_foe_verify_entry writes beyond the end of this buffer when the hash value is at least half the number of entries, corrupting kernel memory and causing a crash. Based on the description, it does not appear to provide privilege escalation or data exfiltration.

Affected Systems

All Linux kernel releases that include the airoha driver and have not yet incorporated the upstream patch referenced in the commit URLs are affected. Administrators should consult the kernel changelog for the airoha driver to determine if the fix has been applied in the kernel version they use.

Risk and Exploitability

The CVSS score of 9.8 indicates critical severity, while the EPSS score of less than 1% suggests low current exploitation activity and the vulnerability is not cited in the CISA KEV catalog. The likely attack vector is via crafted network traffic sent to an active airoha NIC; an attacker can trigger the overflow by invoking airoha_ppe_foe_verify_entry with the appropriate hash value, resulting in a kernel crash that can bring the system down.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the kernel to a release that includes the airoha driver patch.
  • If a kernel update is not yet available, manually apply the patch from the provided commit URLs to the airoha driver source and rebuild the kernel, ensuring the buffer allocation uses ppe_num_entries * sizeof(u16).
  • Until the patch is deployed, disabling the airoha NIC or removing it from the system configuration can prevent exposure to the overflow.

Generated by OpenCVE AI on September 1, 2026 at 17:41 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Ubuntu USN Ubuntu USN USN-8887-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8888-1 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-8889-1 Linux kernel (OEM) vulnerabilities
Ubuntu USN Ubuntu USN USN-8887-2 Linux kernel (AWS) vulnerabilities
Ubuntu USN Ubuntu USN USN-8888-2 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-8887-3 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9003-1 Linux kernel (NVIDIA) vulnerabilities
Ubuntu USN Ubuntu USN USN-9043-1 Linux kernel (NVIDIA) vulnerabilities
History
Type Values Removed Values Added
Weaknesses CWE-119
CWE-787
Type Values Removed Values Added
Metrics cvssV3_1

{'score': 9.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}

Type Values Removed Values Added
Weaknesses CWE-119
CWE-787
Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: net: airoha: fix foe_check_time allocation size foe_check_time is declared as u16 pointer but was allocated with only ppe_num_entries bytes instead of ppe_num_entries * sizeof(u16). When airoha_ppe_foe_verify_entry() is called with hash >= ppe_num_entries/2, it writes beyond the allocated buffer, causing heap buffer overflow and potential kernel crash.
Title net: airoha: fix foe_check_time allocation size
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Aug 29, 2026, 6:21 AM
Reserved
Aug 26, 2026, 2:34 PM
Status
Received
Published
Aug 28, 2026, 8:16 AM
Modified
Aug 29, 2026, 7:16 AM
Severity
Moderate
Public date
Aug 28, 2026, 12:00 AM