CVE-2024-46681: Linux kernel · pktgen: use cpus_read_lock() in pg_net_init()
Affects Linux kernelSource GCVE Database
Not known to be exploited.
Data as of 30 Oct 2026, 13:34 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
Thin evidence
One scorer or noneExploitation evidence
Disclosed: evidence found.
CVE published 13 Sep 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
Description
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.
References
- git.kernel.org/stable/c/1b4fe364b561b952dd7beeba7f7616f9a419b83a (opens in a new tab)
- git.kernel.org/stable/c/7eed5b3115ce9e057bf64c3f6be9ea72f8298e4e (opens in a new tab)
- git.kernel.org/stable/c/5f5f7366dda8ae870e8305d6e7b3c0c2686cd2cf (opens in a new tab)
- git.kernel.org/stable/c/979b581e4c69257acab1af415ddad6b2d78a2fa5 (opens in a new tab)