MEDIUM 5.5

CVE-2026-53298: Linux Kernel Airoha Driver NULL Pointer Dereference DoS

A flaw in the Linux kernel's Airoha network driver can cause the system to crash when the driver fails to properly initialize network queues during startup. The problem occurs because the driver marks a queue as initialized before it has actually finished setting up all the necessary memory structures. If something goes wrong during this initialization, the cleanup code assumes the queue is fully ready and tries to access memory that doesn't exist, crashing the kernel. This is a local vulnerability that requires an attacker to already have user-level access 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
1 configuration(s)
Published / Modified
2026-06-26 / 2026-07-08

NVD description (verbatim)

In the Linux kernel, the following vulnerability has been resolved: net: airoha: Move ndesc initialization at end of airoha_qdma_init_rx_queue() If queue entry or DMA descriptor list allocation fails in airoha_qdma_init_rx_queue routine, airoha_qdma_cleanup() will trigger a NULL pointer dereference running netif_napi_del() for RX queue NAPIs since netif_napi_add() has never been executed to this particular RX NAPI. The issue is due to the early ndesc initialization in airoha_qdma_init_rx_queue() since airoha_qdma_cleanup() relies on ndesc value to check if the queue is properly initialized. Fix the issue moving ndesc initialization at end of airoha_qdma_init_tx routine. Move page_pool allocation after descriptor list allocation in order to avoid memory leaks if desc allocation fails.

4 reference(s) · View on NVD →

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

Technical summary

CVE-2026-53298 is a NULL pointer dereference vulnerability in the Linux kernel's Airoha QDMA (Queue DMA) driver, specifically in the airoha_qdma_init_rx_queue() function. The vulnerability stems from premature initialization of the ndesc field, which is used as a flag to indicate whether a queue has been fully initialized. If memory allocation for queue entries or DMA descriptors fails partway through initialization, the cleanup path (airoha_qdma_cleanup()) calls netif_napi_del() on uninitialized NAPI structures because it relies on ndesc being set to determine if cleanup is needed. The fix involves deferring ndesc initialization until after all allocations succeed, and reordering page_pool allocation to occur after descriptor list allocation to prevent memory leaks. The vulnerability is classified as CWE-476 (NULL Pointer Dereference).

Business impact

This vulnerability allows a local attacker with user-level privileges to trigger a denial-of-service condition by crashing the kernel through manipulation of the Airoha network driver initialization. Systems using Airoha-based network interfaces could experience unexpected downtime. The impact is limited to availability; no data confidentiality or integrity compromise is possible. Organizations running affected Linux kernel versions on hardware with Airoha network controllers should prioritize patching to maintain system stability.

Affected systems

The vulnerability affects the Linux kernel across all versions containing the affected Airoha QDMA driver code. It impacts systems using Airoha network interface hardware. Check your kernel version and hardware vendor to determine if your system uses Airoha-based network controllers. The fix has been applied to the upstream Linux kernel; downstream distributions will incorporate the patch in their respective maintenance releases.

Exploitability

Exploitation requires local access to the affected system with unprivileged user privileges. The attack vector is local with low complexity—an attacker need only trigger the network queue initialization failure path, which could potentially be done through network driver reloading or manipulation of driver initialization parameters. However, the vulnerability is not remotely exploitable and does not provide privilege escalation. The CVSS 3.1 score of 5.5 (MEDIUM) reflects local-only access requirements and impact limited to availability.

Remediation

Apply the Linux kernel patch that moves ndesc initialization to the end of the airoha_qdma_init_tx routine and reorders page_pool allocation after descriptor list allocation. Verify the specific kernel version containing this patch against your distribution's security advisories. Most major Linux distributions will backport this fix to their maintained kernel branches. System administrators should update their kernel packages through their distribution's package management system once patches are available.

Patch guidance

Monitor your Linux distribution's kernel security advisories for updates incorporating this fix. Verify the patch is present by checking kernel release notes or git commit history for the Airoha driver. Test patched kernels in a non-production environment before deploying to production systems to ensure compatibility with your specific hardware and workloads. Coordinate kernel updates with maintenance windows to minimize service disruption.

Detection guidance

Monitor system logs for kernel panic or oops messages referencing the airoha driver, particularly those involving netif_napi_del() or NULL pointer dereferences in QDMA initialization code. If you control driver loading, observe for failures during network interface initialization. Kernel debugging tools and crash analysis can reveal whether a system has been affected. Proactive patching remains the most reliable mitigation.

Why prioritize this

While this is a MEDIUM-severity vulnerability limited to local denial-of-service, it merits timely patching because: (1) it affects system stability on hardware with Airoha network interfaces, (2) any user-level process can trigger it, and (3) unplanned kernel crashes disrupt operations and complicate incident response. Prioritize patches for production systems using Airoha hardware; systems without Airoha controllers are not affected.

Risk score, explained

The CVSS 3.1 score of 5.5 (MEDIUM) reflects a local-only attack vector (AV:L), low complexity (AC:L), no special privileges required (PR:L), no user interaction (UI:N), unchanged scope (S:U), and high impact to availability (A:H) with no confidentiality or integrity impact. The score appropriately captures that while the vulnerability is easily triggered by local users, it does not enable remote attacks or privilege escalation, and impact is limited to system availability.

Frequently asked questions

Can this vulnerability be exploited remotely?

No. The vulnerability requires local access to the system with user-level privileges. It cannot be exploited over the network.

Does this affect all Linux systems?

No. This vulnerability only affects systems using Airoha-based network hardware. Systems with other network interface vendors are not impacted. Check your hardware specifications and kernel configuration to determine if Airoha drivers are enabled.

What happens if the vulnerability is exploited?

An attacker can trigger a kernel crash (denial-of-service), causing the system to reboot or become unavailable. No data is stolen or corrupted, but system availability is compromised.

Is there a workaround if I cannot patch immediately?

The most practical workaround is to disable Airoha driver loading if your system does not require it, though this is only feasible in non-production or specialized environments. Primary mitigation is to apply the kernel patch as soon as your distribution releases it.

This analysis is based on vulnerability disclosures and kernel security advisories available as of the publication date. Vulnerability details, affected versions, and patch availability may change; consult your Linux distribution's official security advisories for authoritative guidance. Patch version numbers, specific affected kernel releases, and vendor advisory links should be verified against the distribution maintainer's official documentation. SEC.co provides this information for informational purposes to support security decision-making; organizations should conduct their own risk assessment based on their specific hardware and kernel configurations. Source: NVD (public-domain), retrieved 2026-08-05. Analysis generated by SEC.co (claude-haiku-4-5).