<?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://vulnerability.circl.lu</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>Sun, 11 Oct 2026 05:55:10 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-58019 — nvkm/gsp: correctly advance the read pointer of GSP message queue</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-58019</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;nvkm/gsp: correctly advance the read pointer of GSP message queue&lt;/p&gt;
&lt;p&gt;A GSP event message consists three parts: message header, RPC header,
message body. GSP calculates the number of pages to write from the
total size of a GSP message. This behavior can be observed from the
movement of the write pointer.&lt;/p&gt;
&lt;p&gt;However, nvkm takes only the size of RPC header and message body as
the message size when advancing the read pointer. When handling a
two-page GSP message in the non rollback case, It wrongly takes the
message body of the previous message as the message header of the next
message. As the &amp;#34;message length&amp;#34; tends to be zero, in the calculation of
size needs to be copied (0 - size of (message header)), the size needs to
be copied will be &amp;#34;0xffffffxx&amp;#34;. It also triggers a kernel panic due to a
NULL pointer error.&lt;/p&gt;
&lt;p&gt;[  547.614102] msg: 00000f90: ff ff ff ff ff ff ff ff 40 d7 18 fb 8b 00 00 00  ........@.......
[  547.622533] msg: 00000fa0: 00 00 00 00 ff ff ff ff ff ff ff ff 00 00 00 00  ................
[  547.630965] msg: 00000fb0: ff ff ff ff ff ff ff ff 00 00 00 00 ff ff ff ff  ................
[  547.639397] msg: 00000fc0: ff ff ff ff 00 00 00 00 ff ff ff ff ff ff ff ff  ................
[  547.647832] nvkm 0000:c1:00.0: gsp: peek msg rpc fn:0 len:0x0/0xffffffffffffffe0
[  547.655225] nvkm 0000:c1:00.0: gsp: get msg rpc fn:0 len:0x0/0xffffffffffffffe0
[  547.662532] BUG: kernel NULL pointer dereference, address:…&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;nvkm/gsp: correctly advance the read pointer of GSP message queue&lt;/p&gt;
&lt;p&gt;A GSP event message consists three parts: message header, RPC header,
message body. GSP calculates the number of pages to write from the
total size of a GSP message. This behavior can be observed from the
movement of the write pointer.&lt;/p&gt;
&lt;p&gt;However, nvkm takes only the size of RPC header and message body as
the message size when advancing the read pointer. When handling a
two-page GSP message in the non rollback case, It wrongly takes the
message body of the previous message as the message header of the next
message. As the &amp;#34;message length&amp;#34; tends to be zero, in the calculation of
size needs to be copied (0 - size of (message header)), the size needs to
be copied will be &amp;#34;0xffffffxx&amp;#34;. It also triggers a kernel panic due to a
NULL pointer error.&lt;/p&gt;
&lt;p&gt;[  547.614102] msg: 00000f90: ff ff ff ff ff ff ff ff 40 d7 18 fb 8b 00 00 00  ........@.......
[  547.622533] msg: 00000fa0: 00 00 00 00 ff ff ff ff ff ff ff ff 00 00 00 00  ................
[  547.630965] msg: 00000fb0: ff ff ff ff ff ff ff ff 00 00 00 00 ff ff ff ff  ................
[  547.639397] msg: 00000fc0: ff ff ff ff 00 00 00 00 ff ff ff ff ff ff ff ff  ................
[  547.647832] nvkm 0000:c1:00.0: gsp: peek msg rpc fn:0 len:0x0/0xffffffffffffffe0
[  547.655225] nvkm 0000:c1:00.0: gsp: get msg rpc fn:0 len:0x0/0xffffffffffffffe0
[  547.662532] BUG: kernel NULL pointer dereference, address:…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-58019</guid>
    </item>
    <item>
      <title>USN-7521-1 — linux, linux-azure, linux-azure-6.11, linux-gcp, linux-gcp-6.11, linux-hwe-6.11, linux-oem-6.11, linux-raspi, linux-rea…</title>
      <link>https://vulnerability.circl.lu/vuln/usn-7521-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-azure-6.11, Ubuntu:24.04:LTS: linux-gcp-6.11, Ubuntu:24.04:LTS: linux-hwe-6.11, Ubuntu:24.04:LTS: linux-oem-6.11&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;
  - x86 architecture;
  - Block layer subsystem;
  - Serial ATA and Parallel ATA drivers;
  - Drivers core;
  - Network block device driver;
  - Bluetooth drivers;
  - Character device driver;
  - TPM device driver;
  - Clock framework and drivers;
  - Hardware crypto device drivers;
  - FireWire subsystem;
  - EFI core;
  - Qualcomm firmware drivers;
  - GPIO subsystem;
  - GPU drivers;
  - HID subsystem;
  - I2C subsystem;
  - I3C subsystem;
  - InfiniBand drivers;
  - Input Device (Mouse) drivers;
  - IOMMU subsystem;
  - Multiple devices driver;
  - Media drivers;
  - NVIDIA Tegra memory controller driver;
  - Fastrpc Driver;
  - Network drivers;
  - Operating Performance Points (OPP) driver;
  - PCI subsystem;
  - x86 platform drivers;
  - PPS (Pulse Per Second) driver;
  - PTP clock framework;
  - Remote Processor subsystem;
  - Real Time Clock drivers;
  - S/390 drivers;
  - SCSI subsystem;
  - QCOM SoC drivers;
  - SPI subsystem;
  - Media staging drivers;
  - Trusted Execution Environment drivers;
  - TTY drivers;
  - UFS subsystem;
  - USB Device Class drivers;
  - USB core drivers;
  - USB Gadget drivers;
  - USB Host Controller drivers;
  - Framebuffer layer;
  - File systems infrastructure;
  - BTRFS file system;
  - Ceph distributed fi…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-azure-6.11, Ubuntu:24.04:LTS: linux-gcp-6.11, Ubuntu:24.04:LTS: linux-hwe-6.11, Ubuntu:24.04:LTS: linux-oem-6.11&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;
  - x86 architecture;
  - Block layer subsystem;
  - Serial ATA and Parallel ATA drivers;
  - Drivers core;
  - Network block device driver;
  - Bluetooth drivers;
  - Character device driver;
  - TPM device driver;
  - Clock framework and drivers;
  - Hardware crypto device drivers;
  - FireWire subsystem;
  - EFI core;
  - Qualcomm firmware drivers;
  - GPIO subsystem;
  - GPU drivers;
  - HID subsystem;
  - I2C subsystem;
  - I3C subsystem;
  - InfiniBand drivers;
  - Input Device (Mouse) drivers;
  - IOMMU subsystem;
  - Multiple devices driver;
  - Media drivers;
  - NVIDIA Tegra memory controller driver;
  - Fastrpc Driver;
  - Network drivers;
  - Operating Performance Points (OPP) driver;
  - PCI subsystem;
  - x86 platform drivers;
  - PPS (Pulse Per Second) driver;
  - PTP clock framework;
  - Remote Processor subsystem;
  - Real Time Clock drivers;
  - S/390 drivers;
  - SCSI subsystem;
  - QCOM SoC drivers;
  - SPI subsystem;
  - Media staging drivers;
  - Trusted Execution Environment drivers;
  - TTY drivers;
  - UFS subsystem;
  - USB Device Class drivers;
  - USB core drivers;
  - USB Gadget drivers;
  - USB Host Controller drivers;
  - Framebuffer layer;
  - File systems infrastructure;
  - BTRFS file system;
  - Ceph distributed fi…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/usn-7521-1</guid>
    </item>
  </channel>
</rss>
