<?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:12:34 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-80704 — drm/amd/display: use proper context for logging</title>
      <link>https://db.gcve.eu/vuln/cve-2026-80704</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/amd/display: use proper context for logging&lt;/p&gt;
&lt;p&gt;The same as the rest of the code, get_ss_info_from_atombios() uses
calc_pll_cs-&amp;gt;ctx-&amp;gt;logger for logging. But calc_pll_cs-&amp;gt;ctx is
initialized only later in calc_pll_max_vco_construct(). Therefore, any
output using DC_LOG_SYNC() leads to a NULL pointer deference in
get_ss_info_from_atombios().&lt;/p&gt;
&lt;p&gt;According to Sashiko, the very same problem exists in
dce112_get_pix_clk_dividers() and dcn3_get_pix_clk_dividers() too.&lt;/p&gt;
&lt;p&gt;To avoid accessing the NULL context, use clk_src-&amp;gt;base.ctx-&amp;gt;logger
everywhere. That context in base is initialized earlier in
dce110_clk_src_construct() and dce112_clk_src_construct(). Before
get_ss_info_from_atombios() or Sashiko&amp;#39;s get_pix_clk_dividers functions
above are actually called. This is done by redefining DC_LOGGER to
CTX-&amp;gt;logger.&lt;/p&gt;
&lt;p&gt;Before:
dce110_clk_src_construct() did:
 -&amp;gt; sets clk_src-&amp;gt;base.ctx = ctx;
 -&amp;gt; ss_info_from_atombios_create()
   -&amp;gt; get_ss_info_from_atombios()   &amp;lt;- uses calc_pll_cs-&amp;gt;ctx  # BOOM
 -&amp;gt; calc_pll_max_vco_construct()    &amp;lt;- sets calc_pll_cs-&amp;gt;ctx&lt;/p&gt;
&lt;p&gt;After:
dce110_clk_src_construct() does:
 -&amp;gt; sets clk_src-&amp;gt;base.ctx = ctx;
 -&amp;gt; ss_info_from_atombios_create()
   -&amp;gt; get_ss_info_from_atombios()   &amp;lt;- uses clk_src-&amp;gt;base.ctx&lt;/p&gt;
&lt;p&gt;(cherry picked from commit 6f16fcbb0c46a87e3d9685407e906573d60104b0)&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/amd/display: use proper context for logging&lt;/p&gt;
&lt;p&gt;The same as the rest of the code, get_ss_info_from_atombios() uses
calc_pll_cs-&amp;gt;ctx-&amp;gt;logger for logging. But calc_pll_cs-&amp;gt;ctx is
initialized only later in calc_pll_max_vco_construct(). Therefore, any
output using DC_LOG_SYNC() leads to a NULL pointer deference in
get_ss_info_from_atombios().&lt;/p&gt;
&lt;p&gt;According to Sashiko, the very same problem exists in
dce112_get_pix_clk_dividers() and dcn3_get_pix_clk_dividers() too.&lt;/p&gt;
&lt;p&gt;To avoid accessing the NULL context, use clk_src-&amp;gt;base.ctx-&amp;gt;logger
everywhere. That context in base is initialized earlier in
dce110_clk_src_construct() and dce112_clk_src_construct(). Before
get_ss_info_from_atombios() or Sashiko&amp;#39;s get_pix_clk_dividers functions
above are actually called. This is done by redefining DC_LOGGER to
CTX-&amp;gt;logger.&lt;/p&gt;
&lt;p&gt;Before:
dce110_clk_src_construct() did:
 -&amp;gt; sets clk_src-&amp;gt;base.ctx = ctx;
 -&amp;gt; ss_info_from_atombios_create()
   -&amp;gt; get_ss_info_from_atombios()   &amp;lt;- uses calc_pll_cs-&amp;gt;ctx  # BOOM
 -&amp;gt; calc_pll_max_vco_construct()    &amp;lt;- sets calc_pll_cs-&amp;gt;ctx&lt;/p&gt;
&lt;p&gt;After:
dce110_clk_src_construct() does:
 -&amp;gt; sets clk_src-&amp;gt;base.ctx = ctx;
 -&amp;gt; ss_info_from_atombios_create()
   -&amp;gt; get_ss_info_from_atombios()   &amp;lt;- uses clk_src-&amp;gt;base.ctx&lt;/p&gt;
&lt;p&gt;(cherry picked from commit 6f16fcbb0c46a87e3d9685407e906573d60104b0)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-80704</guid>
    </item>
    <item>
      <title>USN-8959-1 — linux, linux-aws, linux-gcp, linux-hwe-7.0, linux-ibm, linux-oracle vulnerabilities</title>
      <link>https://db.gcve.eu/vuln/usn-8959-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-hwe-7.0, Ubuntu:26.04:LTS: linux, Ubuntu:26.04:LTS: linux-aws, Ubuntu:26.04:LTS: linux-gcp, Ubuntu:26.04:LTS: linux-ibm, Ubuntu:26.04:LTS: linux-oracle&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:
  - USB Gadget drivers;
  - Memory management;
  - Multiple devices driver;
  - ARM64 architecture;
  - EROFS file system;
  - Networking core;
  - eXpress Data Path;
  - ARM32 architecture;
  - M68K architecture;
  - MIPS architecture;
  - OpenRISC architecture;
  - PA-RISC architecture;
  - PowerPC architecture;
  - RISC-V architecture;
  - S390 architecture;
  - User-Mode Linux (UML);
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Compute Acceleration Framework;
  - Intel NPU Driver;
  - Speakup Console Speech Driver;
  - ACPI drivers;
  - Serial ATA and Parallel ATA drivers;
  - Auxiliary display drivers;
  - Drivers core;
  - Micron PCIe SSD driver;
  - Null block device driver;
  - Ublk userspace block driver;
  - Compressed RAM block device driver;
  - Bluetooth drivers;
  - Bus devices;
  - AMD CDX bus driver;
  - Hardware random number generator core;
  - Character device driver;
  - TPM device driver;
  - Clock framework and drivers;
  - Clocksource drivers;
  - CPU frequency scaling framework;
  - CPU idle management framework;
  - Hardware crypto device drivers;
  - CXL (Compute Express Link) drivers;
  - DAX dirext access to differentiated memory framework;
  - DIBS (Direct Internal Buffer Sharing) drivers;
  - Buffer Sharing and Synchronization framework;…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-hwe-7.0, Ubuntu:26.04:LTS: linux, Ubuntu:26.04:LTS: linux-aws, Ubuntu:26.04:LTS: linux-gcp, Ubuntu:26.04:LTS: linux-ibm, Ubuntu:26.04:LTS: linux-oracle&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:
  - USB Gadget drivers;
  - Memory management;
  - Multiple devices driver;
  - ARM64 architecture;
  - EROFS file system;
  - Networking core;
  - eXpress Data Path;
  - ARM32 architecture;
  - M68K architecture;
  - MIPS architecture;
  - OpenRISC architecture;
  - PA-RISC architecture;
  - PowerPC architecture;
  - RISC-V architecture;
  - S390 architecture;
  - User-Mode Linux (UML);
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Compute Acceleration Framework;
  - Intel NPU Driver;
  - Speakup Console Speech Driver;
  - ACPI drivers;
  - Serial ATA and Parallel ATA drivers;
  - Auxiliary display drivers;
  - Drivers core;
  - Micron PCIe SSD driver;
  - Null block device driver;
  - Ublk userspace block driver;
  - Compressed RAM block device driver;
  - Bluetooth drivers;
  - Bus devices;
  - AMD CDX bus driver;
  - Hardware random number generator core;
  - Character device driver;
  - TPM device driver;
  - Clock framework and drivers;
  - Clocksource drivers;
  - CPU frequency scaling framework;
  - CPU idle management framework;
  - Hardware crypto device drivers;
  - CXL (Compute Express Link) drivers;
  - DAX dirext access to differentiated memory framework;
  - DIBS (Direct Internal Buffer Sharing) drivers;
  - Buffer Sharing and Synchronization framework;…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/usn-8959-1</guid>
    </item>
  </channel>
</rss>
