<?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:42:36 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-52486 — drm: Don't unref the same fb many times by mistake due to deadlock handling</title>
      <link>https://db.gcve.eu/vuln/cve-2023-52486</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;drm: Don&amp;#39;t unref the same fb many times by mistake due to deadlock handling&lt;/p&gt;
&lt;p&gt;If we get a deadlock after the fb lookup in drm_mode_page_flip_ioctl()
we proceed to unref the fb and then retry the whole thing from the top.
But we forget to reset the fb pointer back to NULL, and so if we then
get another error during the retry, before the fb lookup, we proceed
the unref the same fb again without having gotten another reference.
The end result is that the fb will (eventually) end up being freed
while it&amp;#39;s still in use.&lt;/p&gt;
&lt;p&gt;Reset fb to NULL once we&amp;#39;ve unreffed it to avoid doing it again
until we&amp;#39;ve done another fb lookup.&lt;/p&gt;
&lt;p&gt;This turned out to be pretty easy to hit on a DG2 when doing async
flips (and CONFIG_DEBUG_WW_MUTEX_SLOWPATH=y). The first symptom I
saw that drm_closefb() simply got stuck in a busy loop while walking
the framebuffer list. Fortunately I was able to convince it to oops
instead, and from there it was easier to track down the culprit.&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;drm: Don&amp;#39;t unref the same fb many times by mistake due to deadlock handling&lt;/p&gt;
&lt;p&gt;If we get a deadlock after the fb lookup in drm_mode_page_flip_ioctl()
we proceed to unref the fb and then retry the whole thing from the top.
But we forget to reset the fb pointer back to NULL, and so if we then
get another error during the retry, before the fb lookup, we proceed
the unref the same fb again without having gotten another reference.
The end result is that the fb will (eventually) end up being freed
while it&amp;#39;s still in use.&lt;/p&gt;
&lt;p&gt;Reset fb to NULL once we&amp;#39;ve unreffed it to avoid doing it again
until we&amp;#39;ve done another fb lookup.&lt;/p&gt;
&lt;p&gt;This turned out to be pretty easy to hit on a DG2 when doing async
flips (and CONFIG_DEBUG_WW_MUTEX_SLOWPATH=y). The first symptom I
saw that drm_closefb() simply got stuck in a busy loop while walking
the framebuffer list. Fortunately I was able to convince it to oops
instead, and from there it was easier to track down the culprit.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2023-52486</guid>
    </item>
    <item>
      <title>USN-6766-1 — linux, linux-azure, linux-azure-5.15, linux-azure-fde, linux-azure-fde-5.15, linux-gcp, linux-gcp-5.15, linux-gke, linu…</title>
      <link>https://db.gcve.eu/vuln/usn-6766-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:20.04:LTS: linux-azure-5.15, Ubuntu:20.04:LTS: linux-azure-fde-5.15, Ubuntu:20.04:LTS: linux-gcp-5.15, Ubuntu:20.04:LTS: linux-gkeop-5.15, Ubuntu:20.04:LTS: linux-ibm-5.15, Ubuntu:20.04:LTS: linux-lowlatency-hwe-5.15, Ubuntu:20.04:LTS: linux-oracle-5.15, Ubuntu:22.04:LTS: linux, Ubuntu:22.04:LTS: linux-azure, Ubuntu:22.04:LTS: linux-azure-fde and 8 more&lt;/p&gt;
&lt;p&gt;It was discovered that the Open vSwitch implementation in the Linux kernel
could overflow its stack during recursive action operations under certain
conditions. A local attacker could use this to cause a denial of service
(system crash). (CVE-2024-1151)&lt;/p&gt;
&lt;p&gt;Sander Wiebing, Alvise de Faveri Tron, Herbert Bos, and Cristiano Giuffrida
discovered that the Linux kernel mitigations for the initial Branch History
Injection vulnerability (CVE-2022-0001) were insufficient for Intel
processors. A local attacker could potentially use this to expose sensitive
information. (CVE-2024-2201)&lt;/p&gt;
&lt;p&gt;Chenyuan Yang discovered that the RDS Protocol implementation in the Linux
kernel contained an out-of-bounds read vulnerability. An attacker could use
this to possibly cause a denial of service (system crash). (CVE-2024-23849)&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:
  - PowerPC architecture;
  - S390 architecture;
  - Core kernel;
  - Block layer subsystem;
  - Android drivers;
  - Power management core;
  - Bus devices;
  - Hardware random number generator core;
  - Cryptographic API;
  - Device frequency;
  - DMA engine subsystem;
  - ARM SCMI message protocol;
  - GPU drivers;
  - HID subsystem;
  - Hardware monitoring drivers;
  - I2C subsystem;
  - IIO ADC drivers;
  - IIO subsystem;
  - IIO Magnetometer sensors drivers;
  - InfiniBand drivers;
  - Media drivers…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:20.04:LTS: linux-azure-5.15, Ubuntu:20.04:LTS: linux-azure-fde-5.15, Ubuntu:20.04:LTS: linux-gcp-5.15, Ubuntu:20.04:LTS: linux-gkeop-5.15, Ubuntu:20.04:LTS: linux-ibm-5.15, Ubuntu:20.04:LTS: linux-lowlatency-hwe-5.15, Ubuntu:20.04:LTS: linux-oracle-5.15, Ubuntu:22.04:LTS: linux, Ubuntu:22.04:LTS: linux-azure, Ubuntu:22.04:LTS: linux-azure-fde and 8 more&lt;/p&gt;
&lt;p&gt;It was discovered that the Open vSwitch implementation in the Linux kernel
could overflow its stack during recursive action operations under certain
conditions. A local attacker could use this to cause a denial of service
(system crash). (CVE-2024-1151)&lt;/p&gt;
&lt;p&gt;Sander Wiebing, Alvise de Faveri Tron, Herbert Bos, and Cristiano Giuffrida
discovered that the Linux kernel mitigations for the initial Branch History
Injection vulnerability (CVE-2022-0001) were insufficient for Intel
processors. A local attacker could potentially use this to expose sensitive
information. (CVE-2024-2201)&lt;/p&gt;
&lt;p&gt;Chenyuan Yang discovered that the RDS Protocol implementation in the Linux
kernel contained an out-of-bounds read vulnerability. An attacker could use
this to possibly cause a denial of service (system crash). (CVE-2024-23849)&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:
  - PowerPC architecture;
  - S390 architecture;
  - Core kernel;
  - Block layer subsystem;
  - Android drivers;
  - Power management core;
  - Bus devices;
  - Hardware random number generator core;
  - Cryptographic API;
  - Device frequency;
  - DMA engine subsystem;
  - ARM SCMI message protocol;
  - GPU drivers;
  - HID subsystem;
  - Hardware monitoring drivers;
  - I2C subsystem;
  - IIO ADC drivers;
  - IIO subsystem;
  - IIO Magnetometer sensors drivers;
  - InfiniBand drivers;
  - Media drivers…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/usn-6766-1</guid>
    </item>
  </channel>
</rss>
