<?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://cve.radiocsirt.org</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, 04 Oct 2026 11:55:03 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-80678</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-80678</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-80678</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1163 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Certaines d'entre elles permettent à…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1163</link>
      <description>certfr-2026-avi-1163</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-1163</guid>
    </item>
    <item>
      <title>EUVD-2026-361567</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-361567</link>
      <description>EUVD-2026-361567</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-361567</guid>
    </item>
    <item>
      <title>fkie_cve-2026-80678</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-80678</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;i2c: imx: Fix slave registration race and error handling&lt;/p&gt;
&lt;p&gt;In i2c_imx_reg_slave(), the slave pointer was assigned before
pm_runtime_resume_and_get().  If pm_runtime_resume_and_get() failed,
the error path returned without clearing i2c_imx-&amp;gt;slave, leaving it
non-NULL and causing all subsequent registration attempts to fail
with -EBUSY.&lt;/p&gt;
&lt;p&gt;Additionally, because this driver uses a shared IRQ, the interrupt
handler i2c_imx_isr() can execute concurrently and, after acquiring
slave_lock, dereference i2c_imx-&amp;gt;slave.  The previous fix attempt
added a lockless i2c_imx-&amp;gt;slave = NULL on the error path, but that
could race with the ISR under the lock and still cause a NULL pointer
dereference.&lt;/p&gt;
&lt;p&gt;Fix both issues by deferring the assignment of i2c_imx-&amp;gt;slave and
i2c_imx-&amp;gt;last_slave_event to after a successful resume, and by
performing the assignment inside the slave_lock critical section.
This guarantees that the slave pointer is never left stale on the
error path and is always valid when observed by the interrupt handler.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;i2c: imx: Fix slave registration race and error handling&lt;/p&gt;
&lt;p&gt;In i2c_imx_reg_slave(), the slave pointer was assigned before
pm_runtime_resume_and_get().  If pm_runtime_resume_and_get() failed,
the error path returned without clearing i2c_imx-&amp;gt;slave, leaving it
non-NULL and causing all subsequent registration attempts to fail
with -EBUSY.&lt;/p&gt;
&lt;p&gt;Additionally, because this driver uses a shared IRQ, the interrupt
handler i2c_imx_isr() can execute concurrently and, after acquiring
slave_lock, dereference i2c_imx-&amp;gt;slave.  The previous fix attempt
added a lockless i2c_imx-&amp;gt;slave = NULL on the error path, but that
could race with the ISR under the lock and still cause a NULL pointer
dereference.&lt;/p&gt;
&lt;p&gt;Fix both issues by deferring the assignment of i2c_imx-&amp;gt;slave and
i2c_imx-&amp;gt;last_slave_event to after a successful resume, and by
performing the assignment inside the slave_lock critical section.
This guarantees that the slave pointer is never left stale on the
error path and is always valid when observed by the interrupt handler.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-80678</guid>
    </item>
    <item>
      <title>GHSA-gjgg-c5pr-g266</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-gjgg-c5pr-g266</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;i2c: imx: Fix slave registration race and error handling&lt;/p&gt;
&lt;p&gt;In i2c_imx_reg_slave(), the slave pointer was assigned before
pm_runtime_resume_and_get().  If pm_runtime_resume_and_get() failed,
the error path returned without clearing i2c_imx-&amp;gt;slave, leaving it
non-NULL and causing all subsequent registration attempts to fail
with -EBUSY.&lt;/p&gt;
&lt;p&gt;Additionally, because this driver uses a shared IRQ, the interrupt
handler i2c_imx_isr() can execute concurrently and, after acquiring
slave_lock, dereference i2c_imx-&amp;gt;slave.  The previous fix attempt
added a lockless i2c_imx-&amp;gt;slave = NULL on the error path, but that
could race with the ISR under the lock and still cause a NULL pointer
dereference.&lt;/p&gt;
&lt;p&gt;Fix both issues by deferring the assignment of i2c_imx-&amp;gt;slave and
i2c_imx-&amp;gt;last_slave_event to after a successful resume, and by
performing the assignment inside the slave_lock critical section.
This guarantees that the slave pointer is never left stale on the
error path and is always valid when observed by the interrupt handler.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;i2c: imx: Fix slave registration race and error handling&lt;/p&gt;
&lt;p&gt;In i2c_imx_reg_slave(), the slave pointer was assigned before
pm_runtime_resume_and_get().  If pm_runtime_resume_and_get() failed,
the error path returned without clearing i2c_imx-&amp;gt;slave, leaving it
non-NULL and causing all subsequent registration attempts to fail
with -EBUSY.&lt;/p&gt;
&lt;p&gt;Additionally, because this driver uses a shared IRQ, the interrupt
handler i2c_imx_isr() can execute concurrently and, after acquiring
slave_lock, dereference i2c_imx-&amp;gt;slave.  The previous fix attempt
added a lockless i2c_imx-&amp;gt;slave = NULL on the error path, but that
could race with the ISR under the lock and still cause a NULL pointer
dereference.&lt;/p&gt;
&lt;p&gt;Fix both issues by deferring the assignment of i2c_imx-&amp;gt;slave and
i2c_imx-&amp;gt;last_slave_event to after a successful resume, and by
performing the assignment inside the slave_lock critical section.
This guarantees that the slave pointer is never left stale on the
error path and is always valid when observed by the interrupt handler.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-gjgg-c5pr-g266</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-80678 — i2c: imx: Fix slave registration race and error handling</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-80678</link>
      <description>msrc_CVE-2026-80678</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-80678</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-80678</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-80678</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 193 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: i2c: imx: Fix slave registration race and error handling In i2c_imx_reg_slave(), the slave pointer was assigned before pm_runtime_resume_and_get().  If pm_runtime_resume_and_get() failed, the error path returned without clearing i2c_imx-&amp;gt;slave, leaving it non-NULL and causing all subsequent registration attempts to fail with -EBUSY. Additionally, because this driver uses a shared IRQ, the interrupt handler i2c_imx_isr() can execute concurrently and, after acquiring slave_lock, dereference i2c_imx-&amp;gt;slave.  The previous fix attempt added a lockless i2c_imx-&amp;gt;slave = NULL on the error path, but that could race with the ISR under the lock and still cause a NULL pointer dereference. Fix both issues by deferring the assignment of i2c_imx-&amp;gt;slave and i2c_imx-&amp;gt;last_slave_event to after a successful resume, and by performing the assignment inside the slave_lock critical section. This guarantees that the slave pointer is never left stale on the error path and is always valid when observed by the interrupt handler.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 193 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: i2c: imx: Fix slave registration race and error handling In i2c_imx_reg_slave(), the slave pointer was assigned before pm_runtime_resume_and_get().  If pm_runtime_resume_and_get() failed, the error path returned without clearing i2c_imx-&amp;gt;slave, leaving it non-NULL and causing all subsequent registration attempts to fail with -EBUSY. Additionally, because this driver uses a shared IRQ, the interrupt handler i2c_imx_isr() can execute concurrently and, after acquiring slave_lock, dereference i2c_imx-&amp;gt;slave.  The previous fix attempt added a lockless i2c_imx-&amp;gt;slave = NULL on the error path, but that could race with the ISR under the lock and still cause a NULL pointer dereference. Fix both issues by deferring the assignment of i2c_imx-&amp;gt;slave and i2c_imx-&amp;gt;last_slave_event to after a successful resume, and by performing the assignment inside the slave_lock critical section. This guarantees that the slave pointer is never left stale on the error path and is always valid when observed by the interrupt handler.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-80678</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-3075 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3075</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, darunter möglicherweise Speicherbeschädigungen, die Offenlegung oder Manipulation von Daten sowie Denial-of-Service-Zustände.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, darunter möglicherweise Speicherbeschädigungen, die Offenlegung oder Manipulation von Daten sowie Denial-of-Service-Zustände.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3075</guid>
    </item>
  </channel>
</rss>
