<?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://127.0.0.1:10001</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>Sat, 21 Nov 2026 07:06:31 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-43226</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-43226</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://127.0.0.1:10001/vuln/bell-cve-2026-43226</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0696 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Certaines d'entre elles permettent à…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2026-avi-0696</link>
      <description>certfr-2026-avi-0696</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-0696</guid>
    </item>
    <item>
      <title>OESA-2026-3155 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2026-3155</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.03-LTS-SP4: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;iio: accel: bmc150: Fix irq assumption regression&lt;/p&gt;
&lt;p&gt;The code in bmc150-accel-core.c unconditionally calls
bmc150_accel_set_interrupt() in the iio_buffer_setup_ops,
such as on the runtime PM resume path giving a kernel
splat like this if the device has no interrupts:&lt;/p&gt;
&lt;p&gt;Unable to handle kernel NULL pointer dereference at virtual
  address 00000001 when read&lt;/p&gt;
&lt;p&gt;PC is at bmc150_accel_set_interrupt+0x98/0x194
LR is at __pm_runtime_resume+0x5c/0x64
(...)
Call trace:
bmc150_accel_set_interrupt from bmc150_accel_buffer_postenable+0x40/0x108
bmc150_accel_buffer_postenable from __iio_update_buffers+0xbe0/0xcbc
__iio_update_buffers from enable_store+0x84/0xc8
enable_store from kernfs_fop_write_iter+0x154/0x1b4&lt;/p&gt;
&lt;p&gt;This bug seems to have been in the driver since the beginning,
but it only manifests recently, I do not know why.&lt;/p&gt;
&lt;p&gt;Store the IRQ number in the state struct, as this is a common
pattern in other drivers, then use this to determine if we have
IRQ support or not.(CVE-2025-68330)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;iio: adc: at91-sama5d2_adc: Fix potential use-after-free in sama5d2_adc driver&lt;/p&gt;
&lt;p&gt;at91_adc_interrupt can call at91_adc_touch_data_handler function
to start the work by schedule_work(&amp;amp;amp;st-&amp;amp;gt;touch_st.workq).&lt;/p&gt;
&lt;p&gt;If we remove the module which will call at91_adc_remove to
make cleanup, it will free indio_d…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.03-LTS-SP4: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;iio: accel: bmc150: Fix irq assumption regression&lt;/p&gt;
&lt;p&gt;The code in bmc150-accel-core.c unconditionally calls
bmc150_accel_set_interrupt() in the iio_buffer_setup_ops,
such as on the runtime PM resume path giving a kernel
splat like this if the device has no interrupts:&lt;/p&gt;
&lt;p&gt;Unable to handle kernel NULL pointer dereference at virtual
  address 00000001 when read&lt;/p&gt;
&lt;p&gt;PC is at bmc150_accel_set_interrupt+0x98/0x194
LR is at __pm_runtime_resume+0x5c/0x64
(...)
Call trace:
bmc150_accel_set_interrupt from bmc150_accel_buffer_postenable+0x40/0x108
bmc150_accel_buffer_postenable from __iio_update_buffers+0xbe0/0xcbc
__iio_update_buffers from enable_store+0x84/0xc8
enable_store from kernfs_fop_write_iter+0x154/0x1b4&lt;/p&gt;
&lt;p&gt;This bug seems to have been in the driver since the beginning,
but it only manifests recently, I do not know why.&lt;/p&gt;
&lt;p&gt;Store the IRQ number in the state struct, as this is a common
pattern in other drivers, then use this to determine if we have
IRQ support or not.(CVE-2025-68330)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;iio: adc: at91-sama5d2_adc: Fix potential use-after-free in sama5d2_adc driver&lt;/p&gt;
&lt;p&gt;at91_adc_interrupt can call at91_adc_touch_data_handler function
to start the work by schedule_work(&amp;amp;amp;st-&amp;amp;gt;touch_st.workq).&lt;/p&gt;
&lt;p&gt;If we remove the module which will call at91_adc_remove to
make cleanup, it will free indio_d…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2026-3155</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-43226</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-43226</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 225 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net/rds: No shortcut out of RDS_CONN_ERROR RDS connections carry a state &amp;#34;rds_conn_path::cp_state&amp;#34; and transitions from one state to another and are conditional upon an expected state: &amp;#34;rds_conn_path_transition.&amp;#34; There is one exception to this conditionality, which is &amp;#34;RDS_CONN_ERROR&amp;#34; that can be enforced by &amp;#34;rds_conn_path_drop&amp;#34; regardless of what state the condition is currently in. But as soon as a connection enters state &amp;#34;RDS_CONN_ERROR&amp;#34;, the connection handling code expects it to go through the shutdown-path. The RDS/TCP multipath changes added a shortcut out of &amp;#34;RDS_CONN_ERROR&amp;#34; straight back to &amp;#34;RDS_CONN_CONNECTING&amp;#34; via &amp;#34;rds_tcp_accept_one_path&amp;#34; (e.g. after &amp;#34;rds_tcp_state_change&amp;#34;). A subsequent &amp;#34;rds_tcp_reset_callbacks&amp;#34; can then transition the state to &amp;#34;RDS_CONN_RESETTING&amp;#34; with a shutdown-worker queued. That&amp;#39;ll trip up &amp;#34;rds_conn_init_shutdown&amp;#34;, which was never adjusted to handle &amp;#34;RDS_CONN_RESETTING&amp;#34; and subsequently drops the connection with the dreaded &amp;#34;DR_INV_CONN_STATE&amp;#34;, which leaves &amp;#34;RDS_SHUTDOWN_WORK_QUEUED&amp;#34; on forever. So we do two things here: a) Don&amp;#39;t shortcut &amp;#34;RDS_CONN_ERROR&amp;#34;, but take the longer    path through the shutdown code. b) Add &amp;#34;RDS_CONN_RESETTING&amp;#34; to the expected states in   &amp;#34;rds_conn_init_shutdown&amp;#34; so that we won&amp;#39;t error out   and get stuck, if we ever hit weird state transitions   like this again.&amp;#34;&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 225 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net/rds: No shortcut out of RDS_CONN_ERROR RDS connections carry a state &amp;#34;rds_conn_path::cp_state&amp;#34; and transitions from one state to another and are conditional upon an expected state: &amp;#34;rds_conn_path_transition.&amp;#34; There is one exception to this conditionality, which is &amp;#34;RDS_CONN_ERROR&amp;#34; that can be enforced by &amp;#34;rds_conn_path_drop&amp;#34; regardless of what state the condition is currently in. But as soon as a connection enters state &amp;#34;RDS_CONN_ERROR&amp;#34;, the connection handling code expects it to go through the shutdown-path. The RDS/TCP multipath changes added a shortcut out of &amp;#34;RDS_CONN_ERROR&amp;#34; straight back to &amp;#34;RDS_CONN_CONNECTING&amp;#34; via &amp;#34;rds_tcp_accept_one_path&amp;#34; (e.g. after &amp;#34;rds_tcp_state_change&amp;#34;). A subsequent &amp;#34;rds_tcp_reset_callbacks&amp;#34; can then transition the state to &amp;#34;RDS_CONN_RESETTING&amp;#34; with a shutdown-worker queued. That&amp;#39;ll trip up &amp;#34;rds_conn_init_shutdown&amp;#34;, which was never adjusted to handle &amp;#34;RDS_CONN_RESETTING&amp;#34; and subsequently drops the connection with the dreaded &amp;#34;DR_INV_CONN_STATE&amp;#34;, which leaves &amp;#34;RDS_SHUTDOWN_WORK_QUEUED&amp;#34; on forever. So we do two things here: a) Don&amp;#39;t shortcut &amp;#34;RDS_CONN_ERROR&amp;#34;, but take the longer    path through the shutdown code. b) Add &amp;#34;RDS_CONN_RESETTING&amp;#34; to the expected states in   &amp;#34;rds_conn_init_shutdown&amp;#34; so that we won&amp;#39;t error out   and get stuck, if we ever hit weird state transitions   like this again.&amp;#34;&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-43226</guid>
    </item>
  </channel>
</rss>
