CVE-2026-68332: net: airoha: Fix potential use-after-free in airoha_ppe_deinit()

Published Aug 10, 2026
·
Updated

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

net: airoha: Fix potential use-after-free in airohappedeinit()

airohappedeinit() replaces the NPU pointer with NULL via rcureplacepointer() but does not wait for existing RCU readers to exit before calling ppedeinit() and airohanpuput(). This can cause a use-after-free if a reader in an RCU read-side critical section still holds a reference to the NPU when it is freed.

The init path (airohappeinit) already calls synchronizercu() after rcuassignpointer(), but the deinit path introduced in commit 6abcf751bc08 ("net: airoha: Fix schedule while atomic in airohappedeinit()") omitted the matching barrier when switching from rcureadlock()/rcudereference() to rcureplacepointer().

Add synchronizercu() before ppedeinit() to ensure all existing RCU readers have completed before the NPU resources are released.

Affected Software

1 affected component
Linux Kernel

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    Update the deinit path (airoha_ppe_deinit()) to invoke synchronize_rcu() before calling ppe_deinit() / airoha_npu_put() so that all RCU readers have exited prior to releasing NPU resources. (Use case: match the init path that already calls synchronize_rcu(); ensure the barrier is present when switching the NPU pointer to NULL via rcu_replace_pointer()/rcu_assign_pointer.)

    Linux kernel (net: airoha: airoha_ppe_deinit) RCU synchronization ordering (synchronize_rcu before ppe_deinit) = Call synchronize_rcu() before releasing NPU resources in airoha_ppe_deinit() so RCU readers complete before ppe_deinit() and airoha_npu_put() free resources

Event History

Aug 10, 2026
CVE Published
via MITRE·12:03 PM
Data Sourced
via MITRE·12:03 PM
Description
Data Sourced
via NVD·01:20 PM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-68332?

The severity of CVE-2026-68332 is rated at risk level 44, indicating a significant security concern.

2

How do I fix CVE-2026-68332?

To fix CVE-2026-68332, apply the latest patches or updates recommended for the Linux kernel that address this use-after-free vulnerability.

3

What type of vulnerability is CVE-2026-68332?

CVE-2026-68332 is categorized as a 'Use After Free' vulnerability in the Linux kernel.

4

What impact does CVE-2026-68332 have on system security?

CVE-2026-68332 may lead to potential system crashes or execution of arbitrary code due to the improper handling of memory.

5

In which component of the Linux kernel does CVE-2026-68332 occur?

CVE-2026-68332 occurs in the net: airoha component of the Linux kernel.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203