<?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://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-15T07:20:44.383303+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" 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://cve.radiocsirt.org/vuln/cve-2025-21682</id>
    <title>CVE-2025-21682 — eth: bnxt: always recalculate features after XDP clearing, fix null-deref</title>
    <updated>2026-10-15T07:20:44.591662+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux, Siemens SIMATIC S7-1500 CPU 1518-4 PN/DP MFP, Siemens SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP, Siemens SIPLUS S7-1500 CPU 1518-4 PN/DP MFP</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>eth: bnxt: always recalculate features after XDP clearing, fix null-deref</p>
<p>Recalculate features when XDP is detached.</p>
<p>Before:
  # ip li set dev eth0 xdp obj xdp_dummy.bpf.o sec xdp
  # ip li set dev eth0 xdp off
  # ethtool -k eth0 | grep gro
  rx-gro-hw: off [requested on]</p>
<p>After:
  # ip li set dev eth0 xdp obj xdp_dummy.bpf.o sec xdp
  # ip li set dev eth0 xdp off
  # ethtool -k eth0 | grep gro
  rx-gro-hw: on</p>
<p>The fact that HW-GRO doesn't get re-enabled automatically is just
a minor annoyance. The real issue is that the features will randomly
come back during another reconfiguration which just happens to invoke
netdev_update_features(). The driver doesn't handle reconfiguring
two things at a time very robustly.</p>
<p>Starting with commit 98ba1d931f61 ("bnxt_en: Fix RSS logic in
__bnxt_reserve_rings()") we only reconfigure the RSS hash table
if the "effective" number of Rx rings has changed. If HW-GRO is
enabled "effective" number of rings is 2x what user sees.
So if we are in the bad state, with HW-GRO re-enablement "pending"
after XDP off, and we lower the rings by / 2 - the HW-GRO rings
doing 2x and the ethtool -L doing / 2 may cancel each other out,
and the:</p>
<p>if (old_rx_rings != bp-&gt;hw_resc.resv_rx_rings &amp;&amp;</p>
<p>condition in __bnxt_reserve_rings() will be false.
The RSS map won't get updated, and we'll crash with:</p>
<p>BUG: kernel NULL pointer dereference, address: 0000000000000168
  RIP: 0010:__bnxt_hwrm_vni…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2025-21682"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/usn-7445-1</id>
    <title>USN-7445-1 — linux, linux-aws, linux-gcp, linux-hwe-6.11, linux-lowlatency, linux-lowlatency-hwe-6.11, linux-oem-6.11, linux-oracle,…</title>
    <updated>2026-10-15T07:20:44.591764+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:24.04:LTS: linux-hwe-6.11, Ubuntu:24.04:LTS: linux-lowlatency-hwe-6.11, Ubuntu:24.04:LTS: linux-oem-6.11</p>
<p>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:
  - GPIO subsystem;
  - GPU drivers;
  - IRQ chip drivers;
  - Network drivers;
  - Mellanox network drivers;
  - x86 platform drivers;
  - i.MX PM domains;
  - SCSI subsystem;
  - USB Serial drivers;
  - AFS file system;
  - GFS2 file system;
  - File systems infrastructure;
  - Proc file system;
  - SMB network file system;
  - Timer subsystem;
  - Kernel CPU control infrastructure;
  - Memory management;
  - Networking core;
  - Ethtool driver;
  - IEEE 802.15.4 subsystem;
  - Open vSwitch;
  - Network traffic control;
  - VMware vSockets driver;
(CVE-2025-21685, CVE-2025-21684, CVE-2025-21756, CVE-2025-21670,
CVE-2024-57949, CVE-2025-21677, CVE-2025-21680, CVE-2025-21703,
CVE-2024-57952, CVE-2025-21674, CVE-2025-21701, CVE-2025-21691,
CVE-2025-21689, CVE-2025-21668, CVE-2025-21665, CVE-2025-21683,
CVE-2025-21675, CVE-2025-21672, CVE-2024-57948, CVE-2025-21669,
CVE-2025-21673, CVE-2025-21692, CVE-2025-21699, CVE-2025-21702,
CVE-2025-21682, CVE-2025-21690, CVE-2025-21681, CVE-2025-21695,
CVE-2025-21696, CVE-2025-21700, CVE-2025-21678, CVE-2025-21676,
CVE-2024-57950, CVE-2025-21666, CVE-2025-21694, CVE-2025-21693,
CVE-2025-21993, CVE-2024-57951, CVE-2025-21697, CVE-2025-21667)</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/usn-7445-1"/>
  </entry>
</feed>
