<?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://db.gcve.eu</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>Thu, 19 Nov 2026 17:05:56 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-40251 — devlink: rate: Unset parent pointer in devl_rate_nodes_destroy</title>
      <link>https://db.gcve.eu/vuln/cve-2025-40251</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Siemens RUGGEDCOM RST2428P&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;devlink: rate: Unset parent pointer in devl_rate_nodes_destroy&lt;/p&gt;
&lt;p&gt;The function devl_rate_nodes_destroy is documented to &amp;#34;Unset parent for
all rate objects&amp;#34;. However, it was only calling the driver-specific
`rate_leaf_parent_set` or `rate_node_parent_set` ops and decrementing
the parent&amp;#39;s refcount, without actually setting the
`devlink_rate-&amp;gt;parent` pointer to NULL.&lt;/p&gt;
&lt;p&gt;This leaves a dangling pointer in the `devlink_rate` struct, which cause
refcount error in netdevsim[1] and mlx5[2]. In addition, this is
inconsistent with the behavior of `devlink_nl_rate_parent_node_set`,
where the parent pointer is correctly cleared.&lt;/p&gt;
&lt;p&gt;This patch fixes the issue by explicitly setting `devlink_rate-&amp;gt;parent`
to NULL after notifying the driver, thus fulfilling the function&amp;#39;s
documented behavior for all rate objects.&lt;/p&gt;
&lt;p&gt;[1]
repro steps:
echo 1 &amp;gt; /sys/bus/netdevsim/new_device
devlink dev eswitch set netdevsim/netdevsim1 mode switchdev
echo 1 &amp;gt; /sys/bus/netdevsim/devices/netdevsim1/sriov_numvfs
devlink port function rate add netdevsim/netdevsim1/test_node
devlink port function rate set netdevsim/netdevsim1/128 parent test_node
echo 1 &amp;gt; /sys/bus/netdevsim/del_device&lt;/p&gt;
&lt;p&gt;dmesg:
refcount_t: decrement hit 0; leaking memory.
WARNING: CPU: 8 PID: 1530 at lib/refcount.c:31 refcount_warn_saturate+0x42/0xe0
CPU: 8 UID: 0 PID: 1530 Comm: bash Not tainted 6.18.0-rc4+ #1 NONE
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.0-0-gd2395…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Siemens RUGGEDCOM RST2428P&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;devlink: rate: Unset parent pointer in devl_rate_nodes_destroy&lt;/p&gt;
&lt;p&gt;The function devl_rate_nodes_destroy is documented to &amp;#34;Unset parent for
all rate objects&amp;#34;. However, it was only calling the driver-specific
`rate_leaf_parent_set` or `rate_node_parent_set` ops and decrementing
the parent&amp;#39;s refcount, without actually setting the
`devlink_rate-&amp;gt;parent` pointer to NULL.&lt;/p&gt;
&lt;p&gt;This leaves a dangling pointer in the `devlink_rate` struct, which cause
refcount error in netdevsim[1] and mlx5[2]. In addition, this is
inconsistent with the behavior of `devlink_nl_rate_parent_node_set`,
where the parent pointer is correctly cleared.&lt;/p&gt;
&lt;p&gt;This patch fixes the issue by explicitly setting `devlink_rate-&amp;gt;parent`
to NULL after notifying the driver, thus fulfilling the function&amp;#39;s
documented behavior for all rate objects.&lt;/p&gt;
&lt;p&gt;[1]
repro steps:
echo 1 &amp;gt; /sys/bus/netdevsim/new_device
devlink dev eswitch set netdevsim/netdevsim1 mode switchdev
echo 1 &amp;gt; /sys/bus/netdevsim/devices/netdevsim1/sriov_numvfs
devlink port function rate add netdevsim/netdevsim1/test_node
devlink port function rate set netdevsim/netdevsim1/128 parent test_node
echo 1 &amp;gt; /sys/bus/netdevsim/del_device&lt;/p&gt;
&lt;p&gt;dmesg:
refcount_t: decrement hit 0; leaking memory.
WARNING: CPU: 8 PID: 1530 at lib/refcount.c:31 refcount_warn_saturate+0x42/0xe0
CPU: 8 UID: 0 PID: 1530 Comm: bash Not tainted 6.18.0-rc4+ #1 NONE
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.0-0-gd2395…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2025-40251</guid>
    </item>
    <item>
      <title>USN-8094-1 — linux, linux-aws, linux-aws-6.17, linux-gcp, linux-hwe-6.17, linux-oracle, linux-oracle-6.17 vulnerabilities</title>
      <link>https://db.gcve.eu/vuln/usn-8094-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-aws-6.17, Ubuntu:24.04:LTS: linux-hwe-6.17, Ubuntu:24.04:LTS: linux-oracle-6.17, Ubuntu:25.10: linux, Ubuntu:25.10: linux-aws, Ubuntu:25.10: linux-gcp, Ubuntu:25.10: linux-oracle&lt;/p&gt;
&lt;p&gt;Qualys discovered that several vulnerabilities existed in the AppArmor
Linux kernel Security Module (LSM). An unprivileged local attacker could
use these issues to load, replace, and remove arbitrary AppArmor profiles
causing denial of service, exposure of sensitive information (kernel
memory), local privilege escalation, or possibly escape a container.
(LP: #2143853)&lt;/p&gt;
&lt;p&gt;It was discovered that some AMD Zen 5 processors supporting RDSEED
instruction did not properly handle entropy, potentially resulting in the
consumption of insufficiently random values. A local attacker could
possibly use this issue to influence the values returned by the RDSEED
instruction causing loss of confidentiality and integrity. (CVE-2025-62626)&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;
  - S390 architecture;
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Compute Acceleration Framework;
  - ATM drivers;
  - Network block device driver;
  - Bluetooth drivers;
  - Data acquisition framework and drivers;
  - Hardware crypto device drivers;
  - Device frequency scaling framework;
  - Intel Stratix 10 firmware drivers;
  - GPIO subsystem;
  - GPU drivers;
  - Microsoft Hyper-V drivers;
  - CoreSight HW tracing drivers;
  - IIO subsystem;
  - InfiniBand drivers;
  - Input Device core drivers;
  - Input Device (Tablet) d…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-aws-6.17, Ubuntu:24.04:LTS: linux-hwe-6.17, Ubuntu:24.04:LTS: linux-oracle-6.17, Ubuntu:25.10: linux, Ubuntu:25.10: linux-aws, Ubuntu:25.10: linux-gcp, Ubuntu:25.10: linux-oracle&lt;/p&gt;
&lt;p&gt;Qualys discovered that several vulnerabilities existed in the AppArmor
Linux kernel Security Module (LSM). An unprivileged local attacker could
use these issues to load, replace, and remove arbitrary AppArmor profiles
causing denial of service, exposure of sensitive information (kernel
memory), local privilege escalation, or possibly escape a container.
(LP: #2143853)&lt;/p&gt;
&lt;p&gt;It was discovered that some AMD Zen 5 processors supporting RDSEED
instruction did not properly handle entropy, potentially resulting in the
consumption of insufficiently random values. A local attacker could
possibly use this issue to influence the values returned by the RDSEED
instruction causing loss of confidentiality and integrity. (CVE-2025-62626)&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;
  - S390 architecture;
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Compute Acceleration Framework;
  - ATM drivers;
  - Network block device driver;
  - Bluetooth drivers;
  - Data acquisition framework and drivers;
  - Hardware crypto device drivers;
  - Device frequency scaling framework;
  - Intel Stratix 10 firmware drivers;
  - GPIO subsystem;
  - GPU drivers;
  - Microsoft Hyper-V drivers;
  - CoreSight HW tracing drivers;
  - IIO subsystem;
  - InfiniBand drivers;
  - Input Device core drivers;
  - Input Device (Tablet) d…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/usn-8094-1</guid>
    </item>
  </channel>
</rss>
