net: airoha: Fix potential use-after-free in airoha_ppe_deinit()
In the Linux kernel, the following vulnerability has been resolved: net: airoha: Fix potential use-after-free in airoha_ppe_deinit() airoha_ppe_deinit() replaces the NPU pointer with NULL via rcu_replace_pointer() but does not wait for existing RCU readers to exit before calling ppe_deinit() and airoha_npu_put(). 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 (airoha_ppe_init) already calls synchronize_rcu() after rcu_assign_pointer(), but the deinit path introduced in commit 6abcf751bc08 ("net: airoha: Fix schedule while atomic in airoha_ppe_deinit()") omitted the matching barrier when switching from rcu_read_lock()/rcu_dereference() to rcu_replace_pointer(). Add synchronize_rcu() before ppe_deinit() to ensure all existing RCU readers have completed before the NPU resources are released.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 6.18.42, 7.1.6
- CVEs
- CVE-2026-68332
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 4 Nov 2026, 17:28 UTC · Revision 1
Source evidence
net: airoha: Fix potential use-after-free in airoha_ppe_deinit()
core-osv · Original sourcePublished 10 Aug 2026, 12:03 UTC
In the Linux kernel, the following vulnerability has been resolved: net: airoha: Fix potential use-after-free in airoha_ppe_deinit() airoha_ppe_deinit() replaces the NPU pointer with NULL via rcu_replace_pointer() but does not wait for existing RCU readers to exit before calling ppe_deinit() and airoha_npu_put(). 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 (airoha_ppe_init) already calls synchronize_rcu() after rcu_assign_pointer(), but the deinit path introduced in commit 6abcf751bc08 ("net: airoha: Fix schedule while atomic in airoha_ppe_deinit()") omitted the matching barrier when switching from rcu_read_lock()/rcu_dereference() to rcu_replace_pointer(). Add synchronize_rcu() before ppe_deinit() to ensure all existing RCU readers have completed before the NPU resources are released.
osv:CVE-2026-68332
Kernel
Fixed versions: 6.18.42, 7.1.6
Complete source record
{
"id": "52f735552ddec83dd4f2d4394c729bf40c20d34d0e25e20697c8a58bbc05c9d8",
"url": "https://osv.dev/vulnerability/CVE-2026-68332",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "net: airoha: Fix potential use-after-free in airoha_ppe_deinit()",
"summary": "In the Linux kernel, the following vulnerability has been resolved: net: airoha: Fix potential use-after-free in airoha_ppe_deinit() airoha_ppe_deinit() replaces the NPU pointer with NULL via rcu_replace_pointer() but does not wait for existing RCU readers to exit before calling ppe_deinit() and airoha_npu_put(). 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 (airoha_ppe_init) already calls synchronize_rcu() after rcu_assign_pointer(), but the deinit path introduced in commit 6abcf751bc08 (\"net: airoha: Fix schedule while atomic in airoha_ppe_deinit()\") omitted the matching barrier when switching from rcu_read_lock()/rcu_dereference() to rcu_replace_pointer(). Add synchronize_rcu() before ppe_deinit() to ensure all existing RCU readers have completed before the NPU resources are released.",
"evidence": "osv:CVE-2026-68332",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "6.18.42",
"evidence": "/affected/1/ranges"
},
{
"value": "7.1.6",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2026-68332",
"aliases": [
"CVE-2026-68332"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "72f93dc6d1a6b157e0c3d247085c74935893cca0"
},
{
"fixed": "46e3bed4b071095ecc9384a7b349e1908728531f"
}
]
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "6abcf751bc084804a9e5b3051442e8a2ce67f48a"
},
{
"fixed": "ad28c4f9e0eae4993cb3fde3e7cea330acd8b97c"
},
{
"fixed": "2484568a335cd7bda951c75b3a7d95ea36161ae7"
}
]
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "6.18.6"
},
{
"fixed": "6.18.42"
}
]
}
],
"versions": [
"v6.18.41",
"v6.18.40",
"v6.18.39",
"v6.18.38",
"v6.18.37",
"v6.18.36",
"v6.18.35",
"v6.18.34",
"v6.18.33",
"v6.18.32",
"v6.18.31",
"v6.18.30",
"v6.18.29",
"v6.18.28",
"v6.18.27",
"v6.18.26",
"v6.18.25",
"v6.18.24",
"v6.18.23",
"v6.18.22",
"v6.18.21",
"v6.18.20",
"v6.18.19",
"v6.18.18",
"v6.18.17",
"v6.18.16",
"v6.18.15",
"v6.18.14",
"v6.18.13",
"v6.18.12",
"v6.18.11",
"v6.18.10",
"v6.18.9",
"v6.18.8",
"v6.18.7",
"v6.18.6"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-68332.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "0"
},
{
"fixed": "6.18.42"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.19.0"
},
{
"fixed": "7.1.6"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-68332.json"
}
}
],
"modified": "2026-10-28T02:30:37.775558438Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/2484568a335cd7bda951c75b3a7d95ea36161ae7",
"https://git.kernel.org/stable/c/46e3bed4b071095ecc9384a7b349e1908728531f",
"https://git.kernel.org/stable/c/ad28c4f9e0eae4993cb3fde3e7cea330acd8b97c",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/68xxx/CVE-2026-68332.json",
"https://nvd.nist.gov/vuln/detail/CVE-2026-68332",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/68xxx/CVE-2026-68332.json"
}
},
"related_cves": [
{
"value": "CVE-2026-68332",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 505328,
"published_at": "2026-08-10T12:03:08.525+00:00"
}