Към съдържанието
Търсене

CVE-2026-52945: Linux, състезание за ресурс

7.5

CVSS 3.1

Няма данни

Вероятност да бъде експлоатирана в следващите 30 дни (EPSS)

Няма потвърждение

Атакува се

Няма данни

Време до експлоатация

Атакува се по мрежата, без особени условия, без вход и без действие от потребителя.

CVE радар: още уязвимости от този вид

  • Експлоатация: няма данни за експлоатация
  • Атаката може да се автоматизира

Описание

Оригинално описание

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 swi

Засегнати продукти

  • Linux Linux: 18e65229a328304a7ef59899a30fd34ad73ed56b преди cfdb22762f903d95c36ab91e9fe6167f22fa9f6d; fb978675ccfd4a93549e49624127d8332cc61cbf преди 42bc3f45425b607a5ca7b7aaaab661b54407c8f8; 8c9e9cd398777fd60ba202211da1110614cb5bc5 преди 168ee1549fa24fff2ab924a2ca7b1d85f30e062d; 933466fc50a8e4eb167acbd0d8ec96a078462e9c преди e94b369ff82f9bc84f090f271bd78f41c9f6ab2f; aba544ff9ec522e120b1b3d8b32efa4e6d16d4d7; 6.15.3 преди 6.16
  • Linux Linux: 5.15.186 преди 5.15.201; 6.1.142 преди 6.1.164; 6.6.94 преди 6.6.127; 6.12.34 преди 6.12.74

Вид слабост

История

  • 24 юни 2026 Публикувано

Други уязвимости в Linux Linux

Първоизточници

CVE-2026-52945: Linux, състезание за ресурс | freedomonline.bg