MEDIUM 5.5

CVE-2026-53338: Linux Kernel Airoha NULL Pointer Dereference – Patch & Detection Guide

A flaw in the Linux kernel's Airoha network driver can cause the system to crash if a device tree configuration is missing or misconfigured. When the driver initializes certain hardware queues, it looks up a reserved memory region but fails to verify that the lookup succeeded before using the result. This gap allows a local attacker or misconfiguration to trigger a kernel panic, denying service to the system.

Source data · NVD / CISA · public domain

CVSS
3.1 · 5.5 MEDIUM · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weaknesses (CWE)
CWE-476
Affected products
8 configuration(s)
Published / Modified
2026-07-01 / 2026-07-23

NVD description (verbatim)

In the Linux kernel, the following vulnerability has been resolved: net: airoha: Add NULL check for of_reserved_mem_lookup() in airoha_qdma_init_hfwd_queues() of_reserved_mem_lookup() may return NULL if the reserved memory region referenced by the "memory-region" phandle is not found in the reserved memory table (e.g. due to a misconfigured DTS or a removed memory-region node). The current code dereferences the returned pointer without checking for NULL, leading to a kernel NULL pointer dereference at the following lines: dma_addr = rmem->base; // line 1156 num_desc = div_u64(rmem->size, buf_size); // line 1160 Add a NULL check after of_reserved_mem_lookup() and return -ENODEV if the lookup fails, which is consistent with the existing error handling for of_parse_phandle() failure in the same code block.

3 reference(s) · View on NVD →

SEC.co analysis · AI-assisted, reviewed against source

Technical summary

CVE-2026-53338 is a NULL pointer dereference vulnerability in the Airoha QDMA driver (net/airoha) within the Linux kernel. The function airoha_qdma_init_hfwd_queues() calls of_reserved_mem_lookup() to retrieve a reserved memory region descriptor, but does not validate the returned pointer before dereferencing it at lines 1156 and 1160. If the device tree specifies a "memory-region" phandle that does not exist in the reserved memory table—due to misconfiguration, incomplete DTS, or node removal—the lookup returns NULL, leading to a kernel oops. The fix adds explicit NULL checking and returns -ENODEV on failure, mirroring existing error handling patterns in the same code path.

Business impact

This vulnerability creates a denial-of-service vector for systems running affected Airoha-based hardware. Because the flaw is triggered during driver initialization (via device tree configuration), the impact is primarily localized to platforms using this network interface. In production environments, a misconfigured or tampered device tree could crash the kernel at boot or during driver reload. While not a confidentiality or integrity issue, availability impact on critical network infrastructure could be significant. The attack requires local access or the ability to modify boot configuration, limiting external exploitation.

Affected systems

Linux kernel versions containing the Airoha QDMA driver without the NULL check patch are affected. This is typically found on networking devices or SoCs that integrate Airoha network interfaces. The vulnerability surfaces when the device tree references a reserved memory region that is not properly defined. Standard desktop and server deployments are unlikely to be impacted unless they deploy Airoha-based network hardware; embedded and edge devices are at higher risk.

Exploitability

Exploitability is constrained to local attack vectors. An attacker must either (1) have write access to modify or corrupt the device tree before kernel boot, (2) trigger driver reload with a malformed configuration, or (3) rely on a misconfigured deployment. There is no remote exploitation path. The CVSS score of 5.5 (Medium) reflects the local privilege requirement and the availability-only impact. Public exploit code is unlikely to emerge given the configuration-dependent nature of the trigger.

Remediation

Apply the Linux kernel patch that adds NULL pointer validation to of_reserved_mem_lookup() in airoha_qdma_init_hfwd_queues(). The fix is minimal and non-invasive: check the returned pointer and return -ENODEV if NULL. Additionally, audit device tree configurations to ensure all referenced reserved memory regions are properly declared. Organizations should verify that their Airoha device tree overlays and base device trees are consistent and complete.

Patch guidance

Check the Linux kernel upstream repository and your distribution's security advisories for kernel versions that include the fix to net/airoha for CVE-2026-53338. The patch should apply cleanly to any kernel version with the Airoha driver. If you maintain a custom or vendor kernel, ensure the fix is backported. Test the patched kernel in a non-production environment with your specific Airoha hardware and device tree configuration to confirm stability before broad deployment.

Detection guidance

Monitor kernel logs (dmesg, journalctl) for NULL pointer dereference panics originating from airoha_qdma_init_hfwd_queues() or the airoha driver initialization path. Kernel crash dumps will show a call stack pointing to net/airoha code. On systems where this driver is loaded, validate device tree configurations using device tree compiler (dtc) to ensure all phandle references are satisfied. Automated configuration auditing can flag orphaned memory-region phandles in device trees.

Why prioritize this

Although the CVSS score is Medium, prioritization should account for asset criticality. Systems using Airoha network hardware in production environments—particularly in telecom, networking, or edge computing roles—should prioritize patching to prevent unexpected kernel crashes. The local-only attack surface and configuration-dependent trigger reduce urgency for general deployments, but the availability impact justifies timely remediation for affected infrastructure. Organizations not using Airoha hardware can deprioritize.

Risk score, explained

The CVSS 3.1 score of 5.5 reflects a local attack vector (AV:L), low complexity (AC:L), low privilege requirement (PR:L), no user interaction (UI:N), and high availability impact (A:H) within the unchanged scope (S:U). There is no confidentiality or integrity impact. The Medium severity rating is appropriate for a local denial-of-service vulnerability. However, real-world risk depends on whether your infrastructure includes Airoha hardware; if you do not, the actual risk to your environment is zero.

Frequently asked questions

Who should patch for CVE-2026-53338?

Organizations deploying Airoha network adapters or SoCs in their infrastructure should apply this patch. This includes telecom vendors, networking equipment manufacturers, and edge computing platforms that integrate Airoha interfaces. If you do not use Airoha hardware, this CVE does not apply to your environment.

Can this vulnerability be exploited remotely?

No. The flaw requires local access to modify or corrupt the device tree before kernel boot, or the ability to reload the driver with a malicious configuration. Remote exploitation is not possible.

What triggers the NULL pointer dereference?

The crash occurs when the device tree references a reserved memory region via a "memory-region" phandle, but that region is not defined in the kernel's reserved memory table. This typically happens due to incomplete or misconfigured device tree source files, missing overlays, or incomplete merging of device tree fragments.

Does this vulnerability require a reboot to fix?

Yes, patching requires a kernel update and reboot (or driver reload on systems where the driver is modular). Since the flaw occurs during driver initialization, a simple security patch without a reboot will not mitigate the risk if the driver is already loaded or will be loaded on next boot.

This analysis is based on publicly available vulnerability data and the provided CVE record. Patch version numbers, affected kernel versions, and specific vendor advisories should be verified against official Linux kernel upstream repositories and your distribution's security bulletins before deployment. SEC.co does not produce or distribute exploit code for this or any vulnerability. Organizations are encouraged to conduct their own risk assessment based on their specific use of Airoha hardware and device tree configurations. This summary is provided for informational purposes and does not constitute security advice. Source: NVD (public-domain), retrieved 2026-08-10. Analysis generated by SEC.co (claude-haiku-4-5).