<?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-04T17:31:12.030052+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/bdu:2025-04086</id>
    <title>bdu:2025-04086</title>
    <updated>2026-10-04T17:31:12.149053+00:00</updated>
    <content>bdu:2025-04086</content>
    <link href="https://cve.radiocsirt.org/vuln/bdu:2025-04086"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/bell-cve-2025-21921</id>
    <title>BELL-CVE-2025-21921</title>
    <updated>2026-10-04T17:31:12.149089+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p><strong>Affected:</strong> Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/bell-cve-2025-21921"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/certfr-2025-avi-1057</id>
    <title>certfr-2025-avi-1057 — De multiples vulnérabilités ont été découvertes dans les produits VMware. Elles permettent à un attaquant de provoquer…</title>
    <updated>2026-10-04T17:31:12.149120+00:00</updated>
    <content>certfr-2025-avi-1057</content>
    <link href="https://cve.radiocsirt.org/vuln/certfr-2025-avi-1057"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-314098</id>
    <title>EUVD-2026-314098</title>
    <updated>2026-10-04T17:31:12.149138+00:00</updated>
    <content>EUVD-2026-314098</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-314098"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2025-21921</id>
    <title>fkie_cve-2025-21921</title>
    <updated>2026-10-04T17:31:12.149150+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>net: ethtool: netlink: Allow NULL nlattrs when getting a phy_device</p>
<p>ethnl_req_get_phydev() is used to lookup a phy_device, in the case an
ethtool netlink command targets a specific phydev within a netdev's
topology.</p>
<p>It takes as a parameter a const struct nlattr *header that's used for
error handling :</p>
<p>if (!phydev) {
               NL_SET_ERR_MSG_ATTR(extack, header,
                                   "no phy matching phyindex");
               return ERR_PTR(-ENODEV);
       }</p>
<p>In the notify path after a -&gt;set operation however, there's no request
attributes available.</p>
<p>The typical callsite for the above function looks like:</p>
<p>phydev = ethnl_req_get_phydev(req_base, tb[ETHTOOL_A_XXX_HEADER],
				      info-&gt;extack);</p>
<p>So, when tb is NULL (such as in the ethnl notify path), we have a nice
crash.</p>
<p>It turns out that there's only the PLCA command that is in that case, as
the other phydev-specific commands don't have a notification.</p>
<p>This commit fixes the crash by passing the cmd index and the nlattr
array separately, allowing NULL-checking it directly inside the helper.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2025-21921"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-qc6x-3767-556f</id>
    <title>GHSA-qc6x-3767-556f</title>
    <updated>2026-10-04T17:31:12.149191+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>net: ethtool: netlink: Allow NULL nlattrs when getting a phy_device</p>
<p>ethnl_req_get_phydev() is used to lookup a phy_device, in the case an
ethtool netlink command targets a specific phydev within a netdev's
topology.</p>
<p>It takes as a parameter a const struct nlattr *header that's used for
error handling :</p>
<p>if (!phydev) {
               NL_SET_ERR_MSG_ATTR(extack, header,
                                   "no phy matching phyindex");
               return ERR_PTR(-ENODEV);
       }</p>
<p>In the notify path after a -&gt;set operation however, there's no request
attributes available.</p>
<p>The typical callsite for the above function looks like:</p>
<p>phydev = ethnl_req_get_phydev(req_base, tb[ETHTOOL_A_XXX_HEADER],
				      info-&gt;extack);</p>
<p>So, when tb is NULL (such as in the ethnl notify path), we have a nice
crash.</p>
<p>It turns out that there's only the PLCA command that is in that case, as
the other phydev-specific commands don't have a notification.</p>
<p>This commit fixes the crash by passing the cmd index and the nlattr
array separately, allowing NULL-checking it directly inside the helper.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-qc6x-3767-556f"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-21921</id>
    <title>UBUNTU-CVE-2025-21921</title>
    <updated>2026-10-04T17:31:12.149221+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 70 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: net: ethtool: netlink: Allow NULL nlattrs when getting a phy_device ethnl_req_get_phydev() is used to lookup a phy_device, in the case an ethtool netlink command targets a specific phydev within a netdev's topology. It takes as a parameter a const struct nlattr *header that's used for error handling :        if (!phydev) {                NL_SET_ERR_MSG_ATTR(extack, header,                                    "no phy matching phyindex");                return ERR_PTR(-ENODEV);        } In the notify path after a -&gt;set operation however, there's no request attributes available. The typical callsite for the above function looks like: 	phydev = ethnl_req_get_phydev(req_base, tb[ETHTOOL_A_XXX_HEADER], 				      info-&gt;extack); So, when tb is NULL (such as in the ethnl notify path), we have a nice crash. It turns out that there's only the PLCA command that is in that case, as the other phydev-specific commands don't have a notification. This commit fixes the crash by passing the cmd index and the nlattr array separately, allowing NULL-checking it directly inside the helper.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-21921"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0683</id>
    <title>WID-SEC-W-2025-0683 — Linux Kernel: Mehrere Schwachstellen</title>
    <updated>2026-10-04T17:31:12.149345+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial-of-Service auszulösen und um nicht näher spezifizierte Auswirkungen zu erzielen.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0683"/>
  </entry>
</feed>
