<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-30T03:09:19.420202+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2024-46681</id>
    <title>CVE-2024-46681 — pktgen: use cpus_read_lock() in pg_net_init()</title>
    <updated>2026-09-30T03:09:20.109775+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>pktgen: use cpus_read_lock() in pg_net_init()</p>
<p>I have seen the WARN_ON(smp_processor_id() != cpu) firing
in pktgen_thread_worker() during tests.</p>
<p>We must use cpus_read_lock()/cpus_read_unlock()
around the for_each_online_cpu(cpu) loop.</p>
<p>While we are at it use WARN_ON_ONCE() to avoid a possible syslog flood.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2024-46681"/>
  </entry>
</feed>
