<?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:34:15 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-47659 — smack: tcp: ipv4, fix incorrect labeling</title>
      <link>https://db.gcve.eu/vuln/cve-2024-47659</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;smack: tcp: ipv4, fix incorrect labeling&lt;/p&gt;
&lt;p&gt;Currently, Smack mirrors the label of incoming tcp/ipv4 connections:
when a label &amp;#39;foo&amp;#39; connects to a label &amp;#39;bar&amp;#39; with tcp/ipv4,
&amp;#39;foo&amp;#39; always gets &amp;#39;foo&amp;#39; in returned ipv4 packets. So,
1) returned packets are incorrectly labeled (&amp;#39;foo&amp;#39; instead of &amp;#39;bar&amp;#39;)
2) &amp;#39;bar&amp;#39; can write to &amp;#39;foo&amp;#39; without being authorized to write.&lt;/p&gt;
&lt;p&gt;Here is a scenario how to see this:&lt;/p&gt;
&lt;p&gt;* Take two machines, let&amp;#39;s call them C and S,
   with active Smack in the default state
   (no settings, no rules, no labeled hosts, only builtin labels)&lt;/p&gt;
&lt;p&gt;* At S, add Smack rule &amp;#39;foo bar w&amp;#39;
   (labels &amp;#39;foo&amp;#39; and &amp;#39;bar&amp;#39; are instantiated at S at this moment)&lt;/p&gt;
&lt;p&gt;* At S, at label &amp;#39;bar&amp;#39;, launch a program
   that listens for incoming tcp/ipv4 connections&lt;/p&gt;
&lt;p&gt;* From C, at label &amp;#39;foo&amp;#39;, connect to the listener at S.
   (label &amp;#39;foo&amp;#39; is instantiated at C at this moment)
   Connection succeedes and works.&lt;/p&gt;
&lt;p&gt;* Send some data in both directions.
* Collect network traffic of this connection.&lt;/p&gt;
&lt;p&gt;All packets in both directions are labeled with the CIPSO
of the label &amp;#39;foo&amp;#39;. Hence, label &amp;#39;bar&amp;#39; writes to &amp;#39;foo&amp;#39; without
being authorized, and even without ever being known at C.&lt;/p&gt;
&lt;p&gt;If anybody cares: exactly the same happens with DCCP.&lt;/p&gt;
&lt;p&gt;This behavior 1st manifested in release 2.6.29.4 (see Fixes below)
and it looks unintentional. At least, no explanation was provided.&lt;/p&gt;
&lt;p&gt;I changed returned packes label into the &amp;#39;bar&amp;#39;,
to bring it into line with the Smack doc…&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;smack: tcp: ipv4, fix incorrect labeling&lt;/p&gt;
&lt;p&gt;Currently, Smack mirrors the label of incoming tcp/ipv4 connections:
when a label &amp;#39;foo&amp;#39; connects to a label &amp;#39;bar&amp;#39; with tcp/ipv4,
&amp;#39;foo&amp;#39; always gets &amp;#39;foo&amp;#39; in returned ipv4 packets. So,
1) returned packets are incorrectly labeled (&amp;#39;foo&amp;#39; instead of &amp;#39;bar&amp;#39;)
2) &amp;#39;bar&amp;#39; can write to &amp;#39;foo&amp;#39; without being authorized to write.&lt;/p&gt;
&lt;p&gt;Here is a scenario how to see this:&lt;/p&gt;
&lt;p&gt;* Take two machines, let&amp;#39;s call them C and S,
   with active Smack in the default state
   (no settings, no rules, no labeled hosts, only builtin labels)&lt;/p&gt;
&lt;p&gt;* At S, add Smack rule &amp;#39;foo bar w&amp;#39;
   (labels &amp;#39;foo&amp;#39; and &amp;#39;bar&amp;#39; are instantiated at S at this moment)&lt;/p&gt;
&lt;p&gt;* At S, at label &amp;#39;bar&amp;#39;, launch a program
   that listens for incoming tcp/ipv4 connections&lt;/p&gt;
&lt;p&gt;* From C, at label &amp;#39;foo&amp;#39;, connect to the listener at S.
   (label &amp;#39;foo&amp;#39; is instantiated at C at this moment)
   Connection succeedes and works.&lt;/p&gt;
&lt;p&gt;* Send some data in both directions.
* Collect network traffic of this connection.&lt;/p&gt;
&lt;p&gt;All packets in both directions are labeled with the CIPSO
of the label &amp;#39;foo&amp;#39;. Hence, label &amp;#39;bar&amp;#39; writes to &amp;#39;foo&amp;#39; without
being authorized, and even without ever being known at C.&lt;/p&gt;
&lt;p&gt;If anybody cares: exactly the same happens with DCCP.&lt;/p&gt;
&lt;p&gt;This behavior 1st manifested in release 2.6.29.4 (see Fixes below)
and it looks unintentional. At least, no explanation was provided.&lt;/p&gt;
&lt;p&gt;I changed returned packes label into the &amp;#39;bar&amp;#39;,
to bring it into line with the Smack doc…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2024-47659</guid>
    </item>
    <item>
      <title>USN-7088-1 — linux, linux-gcp, linux-gcp-5.4, linux-gkeop, linux-hwe-5.4, linux-ibm, linux-ibm-5.4 vulnerabilities</title>
      <link>https://db.gcve.eu/vuln/usn-7088-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:18.04:LTS: linux-gcp-5.4, Ubuntu:Pro:18.04:LTS: linux-hwe-5.4, Ubuntu:Pro:18.04:LTS: linux-ibm-5.4, Ubuntu:20.04:LTS: linux, Ubuntu:20.04:LTS: linux-gcp, Ubuntu:20.04:LTS: linux-gkeop, Ubuntu:20.04:LTS: linux-ibm&lt;/p&gt;
&lt;p&gt;Ziming Zhang discovered that the VMware Virtual GPU DRM driver in the Linux
kernel contained an integer overflow vulnerability. A local attacker could
use this to cause a denial of service (system crash). (CVE-2022-36402)&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;
  - PowerPC architecture;
  - User-Mode Linux (UML);
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Android drivers;
  - Serial ATA and Parallel ATA drivers;
  - ATM drivers;
  - Drivers core;
  - CPU frequency scaling framework;
  - Device frequency scaling framework;
  - GPU drivers;
  - HID subsystem;
  - Hardware monitoring drivers;
  - InfiniBand drivers;
  - Input Device core drivers;
  - IOMMU subsystem;
  - IRQ chip drivers;
  - ISDN/mISDN subsystem;
  - LED subsystem;
  - Multiple devices driver;
  - Media drivers;
  - EEPROM drivers;
  - VMware VMCI Driver;
  - MMC subsystem;
  - Network drivers;
  - Near Field Communication (NFC) drivers;
  - NVME drivers;
  - Device tree and open firmware driver;
  - Parport drivers;
  - PCI subsystem;
  - Pin controllers subsystem;
  - Remote Processor subsystem;
  - S/390 drivers;
  - SCSI drivers;
  - QCOM SoC drivers;
  - Direct Digital Synthesis drivers;
  - TTY drivers;
  - Userspace I/O drivers;
  - DesignWare USB3 driver;
  - USB subsystem;
  - BTRFS file system;
  - File sy…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:18.04:LTS: linux-gcp-5.4, Ubuntu:Pro:18.04:LTS: linux-hwe-5.4, Ubuntu:Pro:18.04:LTS: linux-ibm-5.4, Ubuntu:20.04:LTS: linux, Ubuntu:20.04:LTS: linux-gcp, Ubuntu:20.04:LTS: linux-gkeop, Ubuntu:20.04:LTS: linux-ibm&lt;/p&gt;
&lt;p&gt;Ziming Zhang discovered that the VMware Virtual GPU DRM driver in the Linux
kernel contained an integer overflow vulnerability. A local attacker could
use this to cause a denial of service (system crash). (CVE-2022-36402)&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;
  - PowerPC architecture;
  - User-Mode Linux (UML);
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Android drivers;
  - Serial ATA and Parallel ATA drivers;
  - ATM drivers;
  - Drivers core;
  - CPU frequency scaling framework;
  - Device frequency scaling framework;
  - GPU drivers;
  - HID subsystem;
  - Hardware monitoring drivers;
  - InfiniBand drivers;
  - Input Device core drivers;
  - IOMMU subsystem;
  - IRQ chip drivers;
  - ISDN/mISDN subsystem;
  - LED subsystem;
  - Multiple devices driver;
  - Media drivers;
  - EEPROM drivers;
  - VMware VMCI Driver;
  - MMC subsystem;
  - Network drivers;
  - Near Field Communication (NFC) drivers;
  - NVME drivers;
  - Device tree and open firmware driver;
  - Parport drivers;
  - PCI subsystem;
  - Pin controllers subsystem;
  - Remote Processor subsystem;
  - S/390 drivers;
  - SCSI drivers;
  - QCOM SoC drivers;
  - Direct Digital Synthesis drivers;
  - TTY drivers;
  - Userspace I/O drivers;
  - DesignWare USB3 driver;
  - USB subsystem;
  - BTRFS file system;
  - File sy…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/usn-7088-1</guid>
    </item>
  </channel>
</rss>
