<?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:32:46 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-71152 — net: dsa: properly keep track of conduit reference</title>
      <link>https://db.gcve.eu/vuln/cve-2025-71152</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;net: dsa: properly keep track of conduit reference&lt;/p&gt;
&lt;p&gt;Problem description
-------------------&lt;/p&gt;
&lt;p&gt;DSA has a mumbo-jumbo of reference handling of the conduit net device
and its kobject which, sadly, is just wrong and doesn&amp;#39;t make sense.&lt;/p&gt;
&lt;p&gt;There are two distinct problems.&lt;/p&gt;
&lt;p&gt;1. The OF path, which uses of_find_net_device_by_node(), never releases
   the elevated refcount on the conduit&amp;#39;s kobject. Nominally, the OF and
   non-OF paths should result in objects having identical reference
   counts taken, and it is already suspicious that
   dsa_dev_to_net_device() has a put_device() call which is missing in
   dsa_port_parse_of(), but we can actually even verify that an issue
   exists. With CONFIG_DEBUG_KOBJECT_RELEASE=y, if we run this command
   &amp;#34;before&amp;#34; and &amp;#34;after&amp;#34; applying this patch:&lt;/p&gt;
&lt;p&gt;(unbind the conduit driver for net device eno2)
echo 0000:00:00.2 &amp;gt; /sys/bus/pci/drivers/fsl_enetc/unbind&lt;/p&gt;
&lt;p&gt;we see these lines in the output diff which appear only with the patch
applied:&lt;/p&gt;
&lt;p&gt;kobject: &amp;#39;eno2&amp;#39; (ffff002009a3a6b8): kobject_release, parent 0000000000000000 (delayed 1000)
kobject: &amp;#39;109&amp;#39; (ffff0020099d59a0): kobject_release, parent 0000000000000000 (delayed 1000)&lt;/p&gt;
&lt;p&gt;2. After we find the conduit interface one way (OF) or another (non-OF),
   it can get unregistered at any time, and DSA remains with a long-lived,
   but in this case stale, cpu_dp-&amp;gt;conduit pointer. Holding the net
   device&amp;#39;s underlying kobject isn&amp;#39;t actually of much…&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;net: dsa: properly keep track of conduit reference&lt;/p&gt;
&lt;p&gt;Problem description
-------------------&lt;/p&gt;
&lt;p&gt;DSA has a mumbo-jumbo of reference handling of the conduit net device
and its kobject which, sadly, is just wrong and doesn&amp;#39;t make sense.&lt;/p&gt;
&lt;p&gt;There are two distinct problems.&lt;/p&gt;
&lt;p&gt;1. The OF path, which uses of_find_net_device_by_node(), never releases
   the elevated refcount on the conduit&amp;#39;s kobject. Nominally, the OF and
   non-OF paths should result in objects having identical reference
   counts taken, and it is already suspicious that
   dsa_dev_to_net_device() has a put_device() call which is missing in
   dsa_port_parse_of(), but we can actually even verify that an issue
   exists. With CONFIG_DEBUG_KOBJECT_RELEASE=y, if we run this command
   &amp;#34;before&amp;#34; and &amp;#34;after&amp;#34; applying this patch:&lt;/p&gt;
&lt;p&gt;(unbind the conduit driver for net device eno2)
echo 0000:00:00.2 &amp;gt; /sys/bus/pci/drivers/fsl_enetc/unbind&lt;/p&gt;
&lt;p&gt;we see these lines in the output diff which appear only with the patch
applied:&lt;/p&gt;
&lt;p&gt;kobject: &amp;#39;eno2&amp;#39; (ffff002009a3a6b8): kobject_release, parent 0000000000000000 (delayed 1000)
kobject: &amp;#39;109&amp;#39; (ffff0020099d59a0): kobject_release, parent 0000000000000000 (delayed 1000)&lt;/p&gt;
&lt;p&gt;2. After we find the conduit interface one way (OF) or another (non-OF),
   it can get unregistered at any time, and DSA remains with a long-lived,
   but in this case stale, cpu_dp-&amp;gt;conduit pointer. Holding the net
   device&amp;#39;s underlying kobject isn&amp;#39;t actually of much…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2025-71152</guid>
    </item>
    <item>
      <title>USN-8277-1 — linux, linux-aws, linux-hwe-6.17, linux-oem-6.17, linux-oracle, linux-raspi, linux-realtime, linux-realtime-6.17 vulner…</title>
      <link>https://db.gcve.eu/vuln/usn-8277-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-hwe-6.17, Ubuntu:24.04:LTS: linux-oem-6.17, Ubuntu:Pro:Realtime:24.04:LTS: linux-realtime-6.17, Ubuntu:25.10: linux, Ubuntu:25.10: linux-aws, Ubuntu:25.10: linux-oracle, Ubuntu:25.10: linux-raspi, Ubuntu:25.10: linux-realtime&lt;/p&gt;
&lt;p&gt;It was discovered that the Linux kernel algif_aead module did not properly
handle in-place cryptographic operations. This flaw is known as Copy Fail.
A local attacker could use this to escalate privileges, or possibly escape
a container. (CVE-2026-31431)&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:
  - S390 architecture;
  - Cryptographic API;
  - GPU drivers;
  - Ethernet bonding driver;
  - Network file system (NFS) server daemon;
  - Distributed Switch Architecture;
  - Netfilter;
  - Control group (cgroup);
  - Kernel kexec() syscall;
  - Memory management;
  - MAC80211 subsystem;
  - Multipath TCP;
  - Packet sockets;
  - TLS protocol;
  - Unix domain sockets;
(CVE-2025-71088, CVE-2025-71090, CVE-2025-71127, CVE-2025-71134,
CVE-2025-71139, CVE-2025-71141, CVE-2025-71142, CVE-2025-71144,
CVE-2025-71152, CVE-2025-71155, CVE-2026-23274, CVE-2026-23351,
CVE-2026-23394, CVE-2026-31419, CVE-2026-31504, CVE-2026-31533,
CVE-2026-43033, CVE-2026-43077, CVE-2026-43078)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-hwe-6.17, Ubuntu:24.04:LTS: linux-oem-6.17, Ubuntu:Pro:Realtime:24.04:LTS: linux-realtime-6.17, Ubuntu:25.10: linux, Ubuntu:25.10: linux-aws, Ubuntu:25.10: linux-oracle, Ubuntu:25.10: linux-raspi, Ubuntu:25.10: linux-realtime&lt;/p&gt;
&lt;p&gt;It was discovered that the Linux kernel algif_aead module did not properly
handle in-place cryptographic operations. This flaw is known as Copy Fail.
A local attacker could use this to escalate privileges, or possibly escape
a container. (CVE-2026-31431)&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:
  - S390 architecture;
  - Cryptographic API;
  - GPU drivers;
  - Ethernet bonding driver;
  - Network file system (NFS) server daemon;
  - Distributed Switch Architecture;
  - Netfilter;
  - Control group (cgroup);
  - Kernel kexec() syscall;
  - Memory management;
  - MAC80211 subsystem;
  - Multipath TCP;
  - Packet sockets;
  - TLS protocol;
  - Unix domain sockets;
(CVE-2025-71088, CVE-2025-71090, CVE-2025-71127, CVE-2025-71134,
CVE-2025-71139, CVE-2025-71141, CVE-2025-71142, CVE-2025-71144,
CVE-2025-71152, CVE-2025-71155, CVE-2026-23274, CVE-2026-23351,
CVE-2026-23394, CVE-2026-31419, CVE-2026-31504, CVE-2026-31533,
CVE-2026-43033, CVE-2026-43077, CVE-2026-43078)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/usn-8277-1</guid>
    </item>
  </channel>
</rss>
