<?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://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-19T17:34:09.238391+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" 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://db.gcve.eu/vuln/cve-2024-47659</id>
    <title>CVE-2024-47659 — smack: tcp: ipv4, fix incorrect labeling</title>
    <updated>2026-11-19T17:34:09.433274+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>smack: tcp: ipv4, fix incorrect labeling</p>
<p>Currently, Smack mirrors the label of incoming tcp/ipv4 connections:
when a label 'foo' connects to a label 'bar' with tcp/ipv4,
'foo' always gets 'foo' in returned ipv4 packets. So,
1) returned packets are incorrectly labeled ('foo' instead of 'bar')
2) 'bar' can write to 'foo' without being authorized to write.</p>
<p>Here is a scenario how to see this:</p>
<p>* Take two machines, let's call them C and S,
   with active Smack in the default state
   (no settings, no rules, no labeled hosts, only builtin labels)</p>
<p>* At S, add Smack rule 'foo bar w'
   (labels 'foo' and 'bar' are instantiated at S at this moment)</p>
<p>* At S, at label 'bar', launch a program
   that listens for incoming tcp/ipv4 connections</p>
<p>* From C, at label 'foo', connect to the listener at S.
   (label 'foo' is instantiated at C at this moment)
   Connection succeedes and works.</p>
<p>* Send some data in both directions.
* Collect network traffic of this connection.</p>
<p>All packets in both directions are labeled with the CIPSO
of the label 'foo'. Hence, label 'bar' writes to 'foo' without
being authorized, and even without ever being known at C.</p>
<p>If anybody cares: exactly the same happens with DCCP.</p>
<p>This behavior 1st manifested in release 2.6.29.4 (see Fixes below)
and it looks unintentional. At least, no explanation was provided.</p>
<p>I changed returned packes label into the 'bar',
to bring it into line with the Smack doc…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2024-47659"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/usn-7088-1</id>
    <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>
    <updated>2026-11-19T17:34:09.433381+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> 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</p>
<p>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)</p>
<p>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…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/usn-7088-1"/>
  </entry>
</feed>
