<?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:53:32 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-43276 — net: mana: Fix double destroy_workqueue on service rescan PCI path</title>
      <link>https://db.gcve.eu/vuln/cve-2026-43276</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: mana: Fix double destroy_workqueue on service rescan PCI path&lt;/p&gt;
&lt;p&gt;While testing corner cases in the driver, a use-after-free crash
was found on the service rescan PCI path.&lt;/p&gt;
&lt;p&gt;When mana_serv_reset() calls mana_gd_suspend(), mana_gd_cleanup()
destroys gc-&amp;gt;service_wq. If the subsequent mana_gd_resume() fails
with -ETIMEDOUT or -EPROTO, the code falls through to
mana_serv_rescan() which triggers pci_stop_and_remove_bus_device().
This invokes the PCI .remove callback (mana_gd_remove), which calls
mana_gd_cleanup() a second time, attempting to destroy the already-
freed workqueue. Fix this by NULL-checking gc-&amp;gt;service_wq in
mana_gd_cleanup() and setting it to NULL after destruction.&lt;/p&gt;
&lt;p&gt;Call stack of issue for reference:
[Sat Feb 21 18:53:48 2026] Call Trace:
[Sat Feb 21 18:53:48 2026]  &amp;lt;TASK&amp;gt;
[Sat Feb 21 18:53:48 2026]  mana_gd_cleanup+0x33/0x70 [mana]
[Sat Feb 21 18:53:48 2026]  mana_gd_remove+0x3a/0xc0 [mana]
[Sat Feb 21 18:53:48 2026]  pci_device_remove+0x41/0xb0
[Sat Feb 21 18:53:48 2026]  device_remove+0x46/0x70
[Sat Feb 21 18:53:48 2026]  device_release_driver_internal+0x1e3/0x250
[Sat Feb 21 18:53:48 2026]  device_release_driver+0x12/0x20
[Sat Feb 21 18:53:48 2026]  pci_stop_bus_device+0x6a/0x90
[Sat Feb 21 18:53:48 2026]  pci_stop_and_remove_bus_device+0x13/0x30
[Sat Feb 21 18:53:48 2026]  mana_do_service+0x180/0x290 [mana]
[Sat Feb 21 18:53:48 2026]  mana_serv_func+0x24/0x50 [mana]
[Sat Feb 21 18:53:48 20…&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: mana: Fix double destroy_workqueue on service rescan PCI path&lt;/p&gt;
&lt;p&gt;While testing corner cases in the driver, a use-after-free crash
was found on the service rescan PCI path.&lt;/p&gt;
&lt;p&gt;When mana_serv_reset() calls mana_gd_suspend(), mana_gd_cleanup()
destroys gc-&amp;gt;service_wq. If the subsequent mana_gd_resume() fails
with -ETIMEDOUT or -EPROTO, the code falls through to
mana_serv_rescan() which triggers pci_stop_and_remove_bus_device().
This invokes the PCI .remove callback (mana_gd_remove), which calls
mana_gd_cleanup() a second time, attempting to destroy the already-
freed workqueue. Fix this by NULL-checking gc-&amp;gt;service_wq in
mana_gd_cleanup() and setting it to NULL after destruction.&lt;/p&gt;
&lt;p&gt;Call stack of issue for reference:
[Sat Feb 21 18:53:48 2026] Call Trace:
[Sat Feb 21 18:53:48 2026]  &amp;lt;TASK&amp;gt;
[Sat Feb 21 18:53:48 2026]  mana_gd_cleanup+0x33/0x70 [mana]
[Sat Feb 21 18:53:48 2026]  mana_gd_remove+0x3a/0xc0 [mana]
[Sat Feb 21 18:53:48 2026]  pci_device_remove+0x41/0xb0
[Sat Feb 21 18:53:48 2026]  device_remove+0x46/0x70
[Sat Feb 21 18:53:48 2026]  device_release_driver_internal+0x1e3/0x250
[Sat Feb 21 18:53:48 2026]  device_release_driver+0x12/0x20
[Sat Feb 21 18:53:48 2026]  pci_stop_bus_device+0x6a/0x90
[Sat Feb 21 18:53:48 2026]  pci_stop_and_remove_bus_device+0x13/0x30
[Sat Feb 21 18:53:48 2026]  mana_do_service+0x180/0x290 [mana]
[Sat Feb 21 18:53:48 2026]  mana_serv_func+0x24/0x50 [mana]
[Sat Feb 21 18:53:48 20…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-43276</guid>
    </item>
    <item>
      <title>USN-8310-1 — linux-azure, linux-azure-6.17 vulnerabilities</title>
      <link>https://db.gcve.eu/vuln/usn-8310-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-azure-6.17, Ubuntu:25.10: linux-azure&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;
  - Microsoft Azure Network Adapter (MANA) 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-23454, CVE-2026-31419, CVE-2026-31504,
CVE-2026-31533, CVE-2026-43033, CVE-2026-43077, CVE-2026-43078,
CVE-2026-43276)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-azure-6.17, Ubuntu:25.10: linux-azure&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;
  - Microsoft Azure Network Adapter (MANA) 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-23454, CVE-2026-31419, CVE-2026-31504,
CVE-2026-31533, CVE-2026-43033, CVE-2026-43077, CVE-2026-43078,
CVE-2026-43276)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/usn-8310-1</guid>
    </item>
  </channel>
</rss>
