In the Linux kernel, the following vulnerability has been resolved: pktgen: use cpus_read_lock() in pg_net_init() I have seen the WARN_ON(smp_processor_id() != cpu) firing in pktgen_thread_worker() during tests. We must use cpus_read_lock()/cpus_read_unlock() around the for_each_online_cpu(cpu) loop. While we are at it use WARN_ON_ONCE() to avoid a possible syslog flood.
Fix
Patch, vendor advisory and mitigation references on NVD 2
- https://git.kernel.org/stable/c/5f5f7366dda8ae870e8305d6e7b3c0c2686cd2cf Patch
- https://git.kernel.org/stable/c/979b581e4c69257acab1af415ddad6b2d78a2fa5 Patch
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 4
- Cpes+6 CPE criteria (now 6)NVD modified 2026-10-21 13:17
- StatusPublished → ModifiedNVD modified 2026-10-21 13:17
- CVSS5.5 (v3.1, CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H)NVD modified 2026-10-21 13:17
- First seenunscored · linuxNVD modified 2026-10-21 12:35
Affected (CPE criteria) 6
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*cpe:2.3:o:linux:linux_kernel:6.11:rc1:*:*:*:*:*:*cpe:2.3:o:linux:linux_kernel:6.11:rc2:*:*:*:*:*:*cpe:2.3:o:linux:linux_kernel:6.11:rc3:*:*:*:*:*:*cpe:2.3:o:linux:linux_kernel:6.11:rc4:*:*:*:*:*:*cpe:2.3:o:linux:linux_kernel:6.11:rc5:*:*:*:*:*:*