CVE-2026-52945
published 2026-06-24CVE-2026-52945: In the Linux kernel, the following vulnerability has been resolved: Revert "wireguard: device: enable threaded NAPI" This reverts commit…
PriorityP341high7.5CVSS 3.1
AVNACLPRNUINSUCNINAH
EPSS
0.31%
23.2th percentile
In the Linux kernel, the following vulnerability has been resolved:
Revert "wireguard: device: enable threaded NAPI"
This reverts commit 933466fc50a8e4eb167acbd0d8ec96a078462e9c which is
commit db9ae3b6b43c79b1ba87eea849fd65efa05b4b2e upstream.
We have had three independent production user reports in combination
with Cilium utilizing WireGuard as encryption underneath that k8s Pod
E/W traffic to certain peer nodes fully stalled. The situation appears
as follows:
- Occurs very rarely but at random times under heavy networking load.
- Once the issue triggers the decryption side stops working completely
for that WireGuard peer, other peers keep working fine. The stall
happens also for newly initiated connections towards that particular
WireGuard peer.
- Only the decryption side is affected, never the encryption side.
- Once it triggers, it never recovers and remains in this state,
the CPU/mem on that node looks normal, no leak, busy loop or crash.
- bpftrace on the affected system shows that wg_prev_queue_enqueue
fails, thus the MAX_QUEUED_PACKETS (1024 skbs!) for the peer's
rx_queue is reached.
- Also, bpftrace shows that wg_packet_rx_poll for that peer is never
called again after reaching this state for that peer. For other
peers wg_packet_rx_poll does get called normally.
- Commit db9ae3b ("wireguard: device: enable threaded NAPI")
switched WireGuard to threaded NAPI by default. The default has
not been changed for triggering the issue, neither did CPU
hotplugging occur (i.e. 5bd8de2 ("wireguard: queueing: always
return valid online CPU in wg_cpumask_choose_online()")).
- The issue has been observed with stable kernels of v5.15 as well as
v6.1. It was reported to us that v5.10 stable is working fine, and
no report on v6.6 stable either (somewhat related discussion in [0]
though).
- In the WireGuard driver the only material difference between v5.10
stable and v5.15 stable is the switch to threaded NAPI by default.
[0] https://lore.kernel.org/netdev/CA+wXwBTT74RE
Affected
16 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| linux | linux | — | — |
| linux | linux | >= 18e65229a328304a7ef59899a30fd34ad73ed56b < cfdb22762f903d95c36ab91e9fe6167f22fa9f6d | cfdb22762f903d95c36ab91e9fe6167f22fa9f6d |
| linux | linux | >= 5.15.186 < 5.15.201 | 5.15.201 |
| linux | linux | >= 6.1.142 < 6.1.164 | 6.1.164 |
| linux | linux | >= 6.12.34 < 6.12.74 | 6.12.74 |
| linux | linux | >= 6.15.3 < 6.16 | 6.16 |
| linux | linux | >= 6.6.94 < 6.6.127 | 6.6.127 |
| linux | linux | >= 8c9e9cd398777fd60ba202211da1110614cb5bc5 < 168ee1549fa24fff2ab924a2ca7b1d85f30e062d | 168ee1549fa24fff2ab924a2ca7b1d85f30e062d |
| linux | linux | >= 933466fc50a8e4eb167acbd0d8ec96a078462e9c < e94b369ff82f9bc84f090f271bd78f41c9f6ab2f | e94b369ff82f9bc84f090f271bd78f41c9f6ab2f |
| linux | linux | >= fb978675ccfd4a93549e49624127d8332cc61cbf < 42bc3f45425b607a5ca7b7aaaab661b54407c8f8 | 42bc3f45425b607a5ca7b7aaaab661b54407c8f8 |
| linux | linux_kernel | — | — |
| linux | linux_kernel | >= 5.15.186 < 5.15.201 | 5.15.201 |
| linux | linux_kernel | >= 6.1.142 < 6.1.164 | 6.1.164 |
| linux | linux_kernel | >= 6.12.34 < 6.12.74 | 6.12.74 |
| linux | linux_kernel | >= 6.15.3 < 6.16 | 6.16 |
| linux | linux_kernel | >= 6.6.94 < 6.6.127 | 6.6.127 |
CVSS provenance
nvdv3.17.5HIGHCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
vendor_redhat7.0MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
VulDB
Linux Kernel up to 6.12.73 wg_cpumask_choose_online rx_queue infinite loop (WID-SEC-2026-2077)
vuldb·2026-06-29·CVSS 7.5
CVE-2026-52945 [HIGH] Linux Kernel up to 6.12.73 wg_cpumask_choose_online rx_queue infinite loop (WID-SEC-2026-2077)
A vulnerability described as critical has been identified in Linux Kernel up to 6.12.73. This impacts the function wg_cpumask_choose_online. Executing a manipulation of the argument rx_queue can lead to infinite loop.
The identification of this vulnerability is CVE-2026-52945. The attack may be launched remotely. There is no exploit available.
Upgrading the affected component is recommended.
GHSA
In the Linux kernel, the following vulnerability has been resolved: Revert "wireguard: device: enable threaded NAPI" This reverts commit 933466fc50a8e4eb167acbd0d8ec96a078462e9c which is commit db9a
ghsa_unreviewed·2026-06-24
CVE-2026-52945 In the Linux kernel, the following vulnerability has been resolved: Revert "wireguard: device: enable threaded NAPI" This reverts commit 933466fc50a8e4eb167acbd0d8ec96a078462e9c which is commit db9a
In the Linux kernel, the following vulnerability has been resolved:
Revert "wireguard: device: enable threaded NAPI"
This reverts commit 933466fc50a8e4eb167acbd0d8ec96a078462e9c which is
commit db9ae3b6b43c79b1ba87eea849fd65efa05b4b2e upstream.
We have had three independent production user reports in combination
with Cilium utilizing WireGuard as encryption underneath that k8s Pod
E/W traffic to certain peer nodes fully stalled. The situation appears
as follows:
- Occurs very rarely but at random times under heavy networking load.
- Once the issue triggers the decryption side stops working completely
for that WireGuard peer, other peers keep working fine. The stall
happens also for newly initiated connections towards that particular
WireGuard peer.
- Only the decryption side is affecte
Red Hat
CVE-2026-52945: A flaw was found in the Linux kernel's WireGuard component
vendor_redhat·2026-06-24·CVSS 7.0
CVE-2026-52945 [MEDIUM] CWE-367 CVE-2026-52945: A flaw was found in the Linux kernel's WireGuard component
A flaw was found in the Linux kernel's WireGuard component. Under heavy network load, particularly when used with Cilium, the threaded NAPI (New API) implementation can cause the decryption side for a WireGuard peer to stop processing traffic. This leads to a complete stall of network communication for that peer, resulting in a Denial of Service (DoS) condition where data cannot be received.
Package: kernel (Red Hat Enterprise Linux 10) - Affected
Package: kernel (Red Hat Enterprise Linux 6) - Not affected
Package: kernel (Red Hat Enterprise Linux 7) - Not affected
Package: kernel-rt (Red Hat Enterprise Linux 7) - Not affected
Package: kernel (Red Hat Enterprise Linux 8) - Not affected
Package: kernel-rt (Red Hat Enterprise Linux 8) - Not affected
Package: kernel (Red Hat Enterprise
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
2026-06-24
Published