<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Fri, 16 Oct 2026 22:02:55 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-35839 — netfilter: bridge: replace physindev with physinif in nf_bridge_info</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2024-35839</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;netfilter: bridge: replace physindev with physinif in nf_bridge_info&lt;/p&gt;
&lt;p&gt;An skb can be added to a neigh-&amp;gt;arp_queue while waiting for an arp
reply. Where original skb&amp;#39;s skb-&amp;gt;dev can be different to neigh&amp;#39;s
neigh-&amp;gt;dev. For instance in case of bridging dnated skb from one veth to
another, the skb would be added to a neigh-&amp;gt;arp_queue of the bridge.&lt;/p&gt;
&lt;p&gt;As skb-&amp;gt;dev can be reset back to nf_bridge-&amp;gt;physindev and used, and as
there is no explicit mechanism that prevents this physindev from been
freed under us (for instance neigh_flush_dev doesn&amp;#39;t cleanup skbs from
different device&amp;#39;s neigh queue) we can crash on e.g. this stack:&lt;/p&gt;
&lt;p&gt;arp_process
  neigh_update
    skb = __skb_dequeue(&amp;amp;neigh-&amp;gt;arp_queue)
      neigh_resolve_output(..., skb)
        ...
          br_nf_dev_xmit
            br_nf_pre_routing_finish_bridge_slow
              skb-&amp;gt;dev = nf_bridge-&amp;gt;physindev
              br_handle_frame_finish&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s use plain ifindex instead of net_device link. To peek into the
original net_device we will use dev_get_by_index_rcu(). Thus either we
get device and are safe to use it or we don&amp;#39;t get it and drop skb.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;netfilter: bridge: replace physindev with physinif in nf_bridge_info&lt;/p&gt;
&lt;p&gt;An skb can be added to a neigh-&amp;gt;arp_queue while waiting for an arp
reply. Where original skb&amp;#39;s skb-&amp;gt;dev can be different to neigh&amp;#39;s
neigh-&amp;gt;dev. For instance in case of bridging dnated skb from one veth to
another, the skb would be added to a neigh-&amp;gt;arp_queue of the bridge.&lt;/p&gt;
&lt;p&gt;As skb-&amp;gt;dev can be reset back to nf_bridge-&amp;gt;physindev and used, and as
there is no explicit mechanism that prevents this physindev from been
freed under us (for instance neigh_flush_dev doesn&amp;#39;t cleanup skbs from
different device&amp;#39;s neigh queue) we can crash on e.g. this stack:&lt;/p&gt;
&lt;p&gt;arp_process
  neigh_update
    skb = __skb_dequeue(&amp;amp;neigh-&amp;gt;arp_queue)
      neigh_resolve_output(..., skb)
        ...
          br_nf_dev_xmit
            br_nf_pre_routing_finish_bridge_slow
              skb-&amp;gt;dev = nf_bridge-&amp;gt;physindev
              br_handle_frame_finish&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s use plain ifindex instead of net_device link. To peek into the
original net_device we will use dev_get_by_index_rcu(). Thus either we
get device and are safe to use it or we don&amp;#39;t get it and drop skb.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2024-35839</guid>
    </item>
    <item>
      <title>USN-6818-1 — linux, linux-gcp, linux-gcp-6.5, linux-lowlatency, linux-lowlatency-hwe-6.5, linux-raspi vulnerabilities</title>
      <link>https://cve.radiocsirt.org/vuln/usn-6818-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:22.04:LTS: linux-gcp-6.5, Ubuntu:22.04:LTS: linux-lowlatency-hwe-6.5&lt;/p&gt;
&lt;p&gt;Alon Zahavi discovered that the NVMe-oF/TCP subsystem in the Linux kernel
did not properly validate H2C PDU data, leading to a null pointer
dereference vulnerability. A remote attacker could use this to cause a
denial of service (system crash). (CVE-2023-6356, CVE-2023-6535,
CVE-2023-6536)&lt;/p&gt;
&lt;p&gt;It was discovered that the Intel Data Streaming and Intel Analytics
Accelerator drivers in the Linux kernel allowed direct access to the
devices for unprivileged users and virtual machines. A local attacker could
use this to cause a denial of service. (CVE-2024-21823)&lt;/p&gt;
&lt;p&gt;Chenyuan Yang discovered that the RDS Protocol implementation in the Linux
kernel contained an out-of-bounds read vulnerability. An attacker could use
this to possibly cause a denial of service (system crash). (CVE-2024-23849)&lt;/p&gt;
&lt;p&gt;It was discovered that a race condition existed in the Bluetooth subsystem
in the Linux kernel, leading to a null pointer dereference vulnerability. A
privileged local attacker could use this to possibly cause a denial of
service (system crash). (CVE-2024-24860)&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - ARM64 architecture;
  - PowerPC architecture;
  - RISC-V architecture;
  - S390 architecture;
  - Core kernel;
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - ACPI drivers;
  - Android drivers;
  - Drivers core;
  - Power management…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:22.04:LTS: linux-gcp-6.5, Ubuntu:22.04:LTS: linux-lowlatency-hwe-6.5&lt;/p&gt;
&lt;p&gt;Alon Zahavi discovered that the NVMe-oF/TCP subsystem in the Linux kernel
did not properly validate H2C PDU data, leading to a null pointer
dereference vulnerability. A remote attacker could use this to cause a
denial of service (system crash). (CVE-2023-6356, CVE-2023-6535,
CVE-2023-6536)&lt;/p&gt;
&lt;p&gt;It was discovered that the Intel Data Streaming and Intel Analytics
Accelerator drivers in the Linux kernel allowed direct access to the
devices for unprivileged users and virtual machines. A local attacker could
use this to cause a denial of service. (CVE-2024-21823)&lt;/p&gt;
&lt;p&gt;Chenyuan Yang discovered that the RDS Protocol implementation in the Linux
kernel contained an out-of-bounds read vulnerability. An attacker could use
this to possibly cause a denial of service (system crash). (CVE-2024-23849)&lt;/p&gt;
&lt;p&gt;It was discovered that a race condition existed in the Bluetooth subsystem
in the Linux kernel, leading to a null pointer dereference vulnerability. A
privileged local attacker could use this to possibly cause a denial of
service (system crash). (CVE-2024-24860)&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - ARM64 architecture;
  - PowerPC architecture;
  - RISC-V architecture;
  - S390 architecture;
  - Core kernel;
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - ACPI drivers;
  - Android drivers;
  - Drivers core;
  - Power management…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/usn-6818-1</guid>
    </item>
  </channel>
</rss>
