<?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>Tue, 17 Nov 2026 10:33:20 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-99081</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-99081</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-99081</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1537 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1537</link>
      <description>certfr-2026-avi-1537</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-1537</guid>
    </item>
    <item>
      <title>EUVD-2026-396163</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-396163</link>
      <description>EUVD-2026-396163</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-396163</guid>
    </item>
    <item>
      <title>fkie_cve-2026-99081</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-99081</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bnxt_en: fix DMA mapping length for padded small packets&lt;/p&gt;
&lt;p&gt;Stefan Fleischmann reported Intel IOMMU DMA Read faults on BCM57412
NetXtreme-E NICs when transmitting packets on VLAN/macvlan interfaces:&lt;/p&gt;
&lt;p&gt;DMAR: [DMA Read NO_PASID] Request device [18:00.0] fault addr 0xfc499000
        [fault reason 0x06] PTE Read access is not set
  bnxt_en 0000:18:00.0 eno1np0: Abandoning msg {0xb4 0x41a} len: 0 due to firmware status: 0x2000001
  ...
  NETDEV WATCHDOG: eno1np0 (bnxt_en): transmit queue 0 timed out&lt;/p&gt;
&lt;p&gt;The fault address (0xfc499000) is on an exact 4KB page boundary,
pointing to a DMA read buffer overrun.&lt;/p&gt;
&lt;p&gt;In bnxt_start_xmit(), packets smaller than BNXT_MIN_PKT_SIZE (52 bytes),
such as 42-byte untagged ARP frames, are padded:&lt;/p&gt;
&lt;p&gt;if (length &amp;lt; BNXT_MIN_PKT_SIZE) {
        pad = BNXT_MIN_PKT_SIZE - length;
        if (skb_pad(skb, pad))
            goto tx_kick_pending;
        length = BNXT_MIN_PKT_SIZE;
    }&lt;/p&gt;
&lt;p&gt;mapping = dma_map_single(&amp;amp;pdev-&amp;gt;dev, skb-&amp;gt;data, len, DMA_TO_DEVICE);
    ...
    dma_unmap_len_set(tx_buf, len, len);&lt;/p&gt;
&lt;p&gt;However, &amp;#39;len&amp;#39; was initialized earlier to skb_headlen(skb) (e.g. 42 bytes)
and is left unadjusted after padding. Consequently, dma_map_single() and
dma_unmap_len_set() map and track only 42 bytes.&lt;/p&gt;
&lt;p&gt;Later, the hardware TX buffer descriptor is programmed with the padded length:&lt;/p&gt;
&lt;p&gt;txbd-&amp;gt;tx_bd_len_flags_type =
        cpu_to_le32(((len + pad) &amp;lt;&amp;lt; TX_BD_LEN_SHIFT) | flags |…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bnxt_en: fix DMA mapping length for padded small packets&lt;/p&gt;
&lt;p&gt;Stefan Fleischmann reported Intel IOMMU DMA Read faults on BCM57412
NetXtreme-E NICs when transmitting packets on VLAN/macvlan interfaces:&lt;/p&gt;
&lt;p&gt;DMAR: [DMA Read NO_PASID] Request device [18:00.0] fault addr 0xfc499000
        [fault reason 0x06] PTE Read access is not set
  bnxt_en 0000:18:00.0 eno1np0: Abandoning msg {0xb4 0x41a} len: 0 due to firmware status: 0x2000001
  ...
  NETDEV WATCHDOG: eno1np0 (bnxt_en): transmit queue 0 timed out&lt;/p&gt;
&lt;p&gt;The fault address (0xfc499000) is on an exact 4KB page boundary,
pointing to a DMA read buffer overrun.&lt;/p&gt;
&lt;p&gt;In bnxt_start_xmit(), packets smaller than BNXT_MIN_PKT_SIZE (52 bytes),
such as 42-byte untagged ARP frames, are padded:&lt;/p&gt;
&lt;p&gt;if (length &amp;lt; BNXT_MIN_PKT_SIZE) {
        pad = BNXT_MIN_PKT_SIZE - length;
        if (skb_pad(skb, pad))
            goto tx_kick_pending;
        length = BNXT_MIN_PKT_SIZE;
    }&lt;/p&gt;
&lt;p&gt;mapping = dma_map_single(&amp;amp;pdev-&amp;gt;dev, skb-&amp;gt;data, len, DMA_TO_DEVICE);
    ...
    dma_unmap_len_set(tx_buf, len, len);&lt;/p&gt;
&lt;p&gt;However, &amp;#39;len&amp;#39; was initialized earlier to skb_headlen(skb) (e.g. 42 bytes)
and is left unadjusted after padding. Consequently, dma_map_single() and
dma_unmap_len_set() map and track only 42 bytes.&lt;/p&gt;
&lt;p&gt;Later, the hardware TX buffer descriptor is programmed with the padded length:&lt;/p&gt;
&lt;p&gt;txbd-&amp;gt;tx_bd_len_flags_type =
        cpu_to_le32(((len + pad) &amp;lt;&amp;lt; TX_BD_LEN_SHIFT) | flags |…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-99081</guid>
    </item>
    <item>
      <title>GHSA-9368-hxmw-4c4j</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-9368-hxmw-4c4j</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bnxt_en: fix DMA mapping length for padded small packets&lt;/p&gt;
&lt;p&gt;Stefan Fleischmann reported Intel IOMMU DMA Read faults on BCM57412
NetXtreme-E NICs when transmitting packets on VLAN/macvlan interfaces:&lt;/p&gt;
&lt;p&gt;DMAR: [DMA Read NO_PASID] Request device [18:00.0] fault addr 0xfc499000
        [fault reason 0x06] PTE Read access is not set
  bnxt_en 0000:18:00.0 eno1np0: Abandoning msg {0xb4 0x41a} len: 0 due to firmware status: 0x2000001
  ...
  NETDEV WATCHDOG: eno1np0 (bnxt_en): transmit queue 0 timed out&lt;/p&gt;
&lt;p&gt;The fault address (0xfc499000) is on an exact 4KB page boundary,
pointing to a DMA read buffer overrun.&lt;/p&gt;
&lt;p&gt;In bnxt_start_xmit(), packets smaller than BNXT_MIN_PKT_SIZE (52 bytes),
such as 42-byte untagged ARP frames, are padded:&lt;/p&gt;
&lt;p&gt;if (length &amp;lt; BNXT_MIN_PKT_SIZE) {
        pad = BNXT_MIN_PKT_SIZE - length;
        if (skb_pad(skb, pad))
            goto tx_kick_pending;
        length = BNXT_MIN_PKT_SIZE;
    }&lt;/p&gt;
&lt;p&gt;mapping = dma_map_single(&amp;amp;pdev-&amp;gt;dev, skb-&amp;gt;data, len, DMA_TO_DEVICE);
    ...
    dma_unmap_len_set(tx_buf, len, len);&lt;/p&gt;
&lt;p&gt;However, &amp;#39;len&amp;#39; was initialized earlier to skb_headlen(skb) (e.g. 42 bytes)
and is left unadjusted after padding. Consequently, dma_map_single() and
dma_unmap_len_set() map and track only 42 bytes.&lt;/p&gt;
&lt;p&gt;Later, the hardware TX buffer descriptor is programmed with the padded length:&lt;/p&gt;
&lt;p&gt;txbd-&amp;gt;tx_bd_len_flags_type =
        cpu_to_le32(((len + pad) &amp;lt;&amp;lt; TX_BD_LEN_SHIFT) | flags |…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bnxt_en: fix DMA mapping length for padded small packets&lt;/p&gt;
&lt;p&gt;Stefan Fleischmann reported Intel IOMMU DMA Read faults on BCM57412
NetXtreme-E NICs when transmitting packets on VLAN/macvlan interfaces:&lt;/p&gt;
&lt;p&gt;DMAR: [DMA Read NO_PASID] Request device [18:00.0] fault addr 0xfc499000
        [fault reason 0x06] PTE Read access is not set
  bnxt_en 0000:18:00.0 eno1np0: Abandoning msg {0xb4 0x41a} len: 0 due to firmware status: 0x2000001
  ...
  NETDEV WATCHDOG: eno1np0 (bnxt_en): transmit queue 0 timed out&lt;/p&gt;
&lt;p&gt;The fault address (0xfc499000) is on an exact 4KB page boundary,
pointing to a DMA read buffer overrun.&lt;/p&gt;
&lt;p&gt;In bnxt_start_xmit(), packets smaller than BNXT_MIN_PKT_SIZE (52 bytes),
such as 42-byte untagged ARP frames, are padded:&lt;/p&gt;
&lt;p&gt;if (length &amp;lt; BNXT_MIN_PKT_SIZE) {
        pad = BNXT_MIN_PKT_SIZE - length;
        if (skb_pad(skb, pad))
            goto tx_kick_pending;
        length = BNXT_MIN_PKT_SIZE;
    }&lt;/p&gt;
&lt;p&gt;mapping = dma_map_single(&amp;amp;pdev-&amp;gt;dev, skb-&amp;gt;data, len, DMA_TO_DEVICE);
    ...
    dma_unmap_len_set(tx_buf, len, len);&lt;/p&gt;
&lt;p&gt;However, &amp;#39;len&amp;#39; was initialized earlier to skb_headlen(skb) (e.g. 42 bytes)
and is left unadjusted after padding. Consequently, dma_map_single() and
dma_unmap_len_set() map and track only 42 bytes.&lt;/p&gt;
&lt;p&gt;Later, the hardware TX buffer descriptor is programmed with the padded length:&lt;/p&gt;
&lt;p&gt;txbd-&amp;gt;tx_bd_len_flags_type =
        cpu_to_le32(((len + pad) &amp;lt;&amp;lt; TX_BD_LEN_SHIFT) | flags |…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-9368-hxmw-4c4j</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-99081 — bnxt_en: fix DMA mapping length for padded small packets</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-99081</link>
      <description>msrc_CVE-2026-99081</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-99081</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-99081</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-99081</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:16.04:LTS: linux-hwe-edge and 256 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: bnxt_en: fix DMA mapping length for padded small packets Stefan Fleischmann reported Intel IOMMU DMA Read faults on BCM57412 NetXtreme-E NICs when transmitting packets on VLAN/macvlan interfaces:   DMAR: [DMA Read NO_PASID] Request device [18:00.0] fault addr 0xfc499000         [fault reason 0x06] PTE Read access is not set   bnxt_en 0000:18:00.0 eno1np0: Abandoning msg {0xb4 0x41a} len: 0 due to firmware status: 0x2000001   ...   NETDEV WATCHDOG: eno1np0 (bnxt_en): transmit queue 0 timed out The fault address (0xfc499000) is on an exact 4KB page boundary, pointing to a DMA read buffer overrun. In bnxt_start_xmit(), packets smaller than BNXT_MIN_PKT_SIZE (52 bytes), such as 42-byte untagged ARP frames, are padded:     if (length &amp;lt; BNXT_MIN_PKT_SIZE) {         pad = BNXT_MIN_PKT_SIZE - length;         if (skb_pad(skb, pad))             goto tx_kick_pending;         length = BNXT_MIN_PKT_SIZE;     }     mapping = dma_map_single(&amp;amp;pdev-&amp;gt;dev, skb-&amp;gt;data, len, DMA_TO_DEVICE);     ...     dma_unmap_len_set(tx_buf, len, len); However, &amp;#39;len&amp;#39; was initialized earlier to skb_headlen(skb) (e.g. 42 bytes) and is left unadjusted after padding. Consequently, dma_map_single() and dma_unmap_len_set() map and track only 42 bytes. Later, the hardware TX buffer descriptor is programmed with the padded length:     txbd-&amp;gt;tx_bd_len_flags_type =         cpu_to_le32(((len + pad) &amp;lt;&amp;lt; TX_BD_LEN_SHIFT) | flags |                     TX_BD_…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:16.04:LTS: linux-hwe-edge and 256 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: bnxt_en: fix DMA mapping length for padded small packets Stefan Fleischmann reported Intel IOMMU DMA Read faults on BCM57412 NetXtreme-E NICs when transmitting packets on VLAN/macvlan interfaces:   DMAR: [DMA Read NO_PASID] Request device [18:00.0] fault addr 0xfc499000         [fault reason 0x06] PTE Read access is not set   bnxt_en 0000:18:00.0 eno1np0: Abandoning msg {0xb4 0x41a} len: 0 due to firmware status: 0x2000001   ...   NETDEV WATCHDOG: eno1np0 (bnxt_en): transmit queue 0 timed out The fault address (0xfc499000) is on an exact 4KB page boundary, pointing to a DMA read buffer overrun. In bnxt_start_xmit(), packets smaller than BNXT_MIN_PKT_SIZE (52 bytes), such as 42-byte untagged ARP frames, are padded:     if (length &amp;lt; BNXT_MIN_PKT_SIZE) {         pad = BNXT_MIN_PKT_SIZE - length;         if (skb_pad(skb, pad))             goto tx_kick_pending;         length = BNXT_MIN_PKT_SIZE;     }     mapping = dma_map_single(&amp;amp;pdev-&amp;gt;dev, skb-&amp;gt;data, len, DMA_TO_DEVICE);     ...     dma_unmap_len_set(tx_buf, len, len); However, &amp;#39;len&amp;#39; was initialized earlier to skb_headlen(skb) (e.g. 42 bytes) and is left unadjusted after padding. Consequently, dma_map_single() and dma_unmap_len_set() map and track only 42 bytes. Later, the hardware TX buffer descriptor is programmed with the padded length:     txbd-&amp;gt;tx_bd_len_flags_type =         cpu_to_le32(((len + pad) &amp;lt;&amp;lt; TX_BD_LEN_SHIFT) | flags |                     TX_BD_…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-99081</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4152 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4152</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4152</guid>
    </item>
  </channel>
</rss>
