<?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:01:36.345227+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-44964</id>
    <title>CVE-2024-44964 — idpf: fix memory leaks and crashes while performing a soft reset</title>
    <updated>2026-11-19T17:01:36.396272+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>idpf: fix memory leaks and crashes while performing a soft reset</p>
<p>The second tagged commit introduced a UAF, as it removed restoring
q_vector-&gt;vport pointers after reinitializating the structures.
This is due to that all queue allocation functions are performed here
with the new temporary vport structure and those functions rewrite
the backpointers to the vport. Then, this new struct is freed and
the pointers start leading to nowhere.</p>
<p>But generally speaking, the current logic is very fragile. It claims
to be more reliable when the system is low on memory, but in fact, it
consumes two times more memory as at the moment of running this
function, there are two vports allocated with their queues and vectors.
Moreover, it claims to prevent the driver from running into "bad state",
but in fact, any error during the rebuild leaves the old vport in the
partially allocated state.
Finally, if the interface is down when the function is called, it always
allocates a new queue set, but when the user decides to enable the
interface later on, vport_open() allocates them once again, IOW there's
a clear memory leak here.</p>
<p>Just don't allocate a new queue set when performing a reset, that solves
crashes and memory leaks. Readd the old queue number and reopen the
interface on rollback - that solves limbo states when the device is left
disabled and/or without HW queues enabled.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2024-44964"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/usn-7511-1</id>
    <title>USN-7511-1 — linux-gcp vulnerabilities</title>
    <updated>2026-11-19T17:01:36.396384+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:22.04:LTS: linux-gcp</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;
  - x86 architecture;
  - Block layer subsystem;
  - Network block device driver;
  - Bus devices;
  - Character device driver;
  - TPM device driver;
  - Clock framework and drivers;
  - GPIO subsystem;
  - GPU drivers;
  - HID subsystem;
  - I2C subsystem;
  - InfiniBand drivers;
  - Media drivers;
  - NVIDIA Tegra memory controller driver;
  - Network drivers;
  - PCI subsystem;
  - PPS (Pulse Per Second) driver;
  - PTP clock framework;
  - RapidIO drivers;
  - Real Time Clock drivers;
  - SLIMbus drivers;
  - QCOM SoC drivers;
  - Trusted Execution Environment drivers;
  - TTY drivers;
  - USB DSL drivers;
  - USB Device Class drivers;
  - USB core drivers;
  - USB Gadget drivers;
  - USB Host Controller drivers;
  - Renesas USBHS Controller drivers;
  - ACRN Hypervisor Service Module driver;
  - File systems infrastructure;
  - BTRFS file system;
  - F2FS file system;
  - Network file system (NFS) server daemon;
  - NILFS2 file system;
  - Overlay file system;
  - SMB network file system;
  - UBI file system;
  - KVM subsystem;
  - L3 Master device support module;
  - Process Accounting mechanism;
  - Padata parallel execution mechanism;
  - printk logging mechanism;
  - Scheduler infrastructure;
  - Timer subsystem;
  - Tracing infrastructure…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/usn-7511-1"/>
  </entry>
</feed>
