<?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>Thu, 19 Nov 2026 19:35:33 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-43492</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-43492</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-43492</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0862 — 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-0862</link>
      <description>certfr-2026-avi-0862</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-0862</guid>
    </item>
    <item>
      <title>OESA-2026-2493 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2026-2493</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: 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;scsi: target: Fix recursive locking in __configfs_open_file()&lt;/p&gt;
&lt;p&gt;In flush_write_buffer, &amp;amp;amp;p-&amp;amp;gt;frag_sem is acquired and then the loaded store
function is called, which, here, is target_core_item_dbroot_store().  This
function called filp_open(), following which these functions were called
(in reverse order), according to the call trace:&lt;/p&gt;
&lt;p&gt;down_read
  __configfs_open_file
  do_dentry_open
  vfs_open
  do_open
  path_openat
  do_filp_open
  file_open_name
  filp_open
  target_core_item_dbroot_store
  flush_write_buffer
  configfs_write_iter&lt;/p&gt;
&lt;p&gt;target_core_item_dbroot_store() tries to validate the new file path by
trying to open the file path provided to it; however, in this case, the bug
report shows:&lt;/p&gt;
&lt;p&gt;db_root: not a directory: /sys/kernel/config/target/dbroot&lt;/p&gt;
&lt;p&gt;indicating that the same configfs file was tried to be opened, on which it
is currently working on. Thus, it is trying to acquire frag_sem semaphore
of the same file of which it already holds the semaphore obtained in
flush_write_buffer(), leading to acquiring the semaphore in a nested manner
and a possibility of recursive locking.&lt;/p&gt;
&lt;p&gt;Fix this by modifying target_core_item_dbroot_store() to use kern_path()
instead of filp_open() to avoid opening the file using filesystem-specific
function __configfs_open_file(), and further modifying it to make this fix
compatible.(CVE-2026-23292)…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: 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;scsi: target: Fix recursive locking in __configfs_open_file()&lt;/p&gt;
&lt;p&gt;In flush_write_buffer, &amp;amp;amp;p-&amp;amp;gt;frag_sem is acquired and then the loaded store
function is called, which, here, is target_core_item_dbroot_store().  This
function called filp_open(), following which these functions were called
(in reverse order), according to the call trace:&lt;/p&gt;
&lt;p&gt;down_read
  __configfs_open_file
  do_dentry_open
  vfs_open
  do_open
  path_openat
  do_filp_open
  file_open_name
  filp_open
  target_core_item_dbroot_store
  flush_write_buffer
  configfs_write_iter&lt;/p&gt;
&lt;p&gt;target_core_item_dbroot_store() tries to validate the new file path by
trying to open the file path provided to it; however, in this case, the bug
report shows:&lt;/p&gt;
&lt;p&gt;db_root: not a directory: /sys/kernel/config/target/dbroot&lt;/p&gt;
&lt;p&gt;indicating that the same configfs file was tried to be opened, on which it
is currently working on. Thus, it is trying to acquire frag_sem semaphore
of the same file of which it already holds the semaphore obtained in
flush_write_buffer(), leading to acquiring the semaphore in a nested manner
and a possibility of recursive locking.&lt;/p&gt;
&lt;p&gt;Fix this by modifying target_core_item_dbroot_store() to use kern_path()
instead of filp_open() to avoid opening the file using filesystem-specific
function __configfs_open_file(), and further modifying it to make this fix
compatible.(CVE-2026-23292)…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2026-2493</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-43492</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-43492</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, 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 and 254 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: lib/crypto: mpi: Fix integer underflow in mpi_read_raw_from_sgl() Yiming reports an integer underflow in mpi_read_raw_from_sgl() when subtracting &amp;#34;lzeros&amp;#34; from the unsigned &amp;#34;nbytes&amp;#34;. For this to happen, the scatterlist &amp;#34;sgl&amp;#34; needs to occupy more bytes than the &amp;#34;nbytes&amp;#34; parameter and the first &amp;#34;nbytes + 1&amp;#34; bytes of the scatterlist must be zero.  Under these conditions, the while loop iterating over the scatterlist will count more zeroes than &amp;#34;nbytes&amp;#34;, subtract the number of zeroes from &amp;#34;nbytes&amp;#34; and cause the underflow. When commit 2d4d1eea540b (&amp;#34;lib/mpi: Add mpi sgl helpers&amp;#34;) originally introduced the bug, it couldn&amp;#39;t be triggered because all callers of mpi_read_raw_from_sgl() passed a scatterlist whose length was equal to &amp;#34;nbytes&amp;#34;. However since commit 63ba4d67594a (&amp;#34;KEYS: asymmetric: Use new crypto interface without scatterlists&amp;#34;), the underflow can now actually be triggered.  When invoking a KEYCTL_PKEY_ENCRYPT system call with a larger &amp;#34;out_len&amp;#34; than &amp;#34;in_len&amp;#34; and filling the &amp;#34;in&amp;#34; buffer with zeroes, crypto_akcipher_sync_prep() will create an all-zero scatterlist used for both the &amp;#34;src&amp;#34; and &amp;#34;dst&amp;#34; member of struct akcipher_request and thereby fulfil the conditions to trigger the bug:   sys_keyctl()     keyctl_pkey_e_d_s()       asymmetric_key_eds_op()         software_key_eds_op()           crypto_akcipher_sync_encrypt()             crypto_akcipher_sync_prep()               crypto_akcipher_encrypt()…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, 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 and 254 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: lib/crypto: mpi: Fix integer underflow in mpi_read_raw_from_sgl() Yiming reports an integer underflow in mpi_read_raw_from_sgl() when subtracting &amp;#34;lzeros&amp;#34; from the unsigned &amp;#34;nbytes&amp;#34;. For this to happen, the scatterlist &amp;#34;sgl&amp;#34; needs to occupy more bytes than the &amp;#34;nbytes&amp;#34; parameter and the first &amp;#34;nbytes + 1&amp;#34; bytes of the scatterlist must be zero.  Under these conditions, the while loop iterating over the scatterlist will count more zeroes than &amp;#34;nbytes&amp;#34;, subtract the number of zeroes from &amp;#34;nbytes&amp;#34; and cause the underflow. When commit 2d4d1eea540b (&amp;#34;lib/mpi: Add mpi sgl helpers&amp;#34;) originally introduced the bug, it couldn&amp;#39;t be triggered because all callers of mpi_read_raw_from_sgl() passed a scatterlist whose length was equal to &amp;#34;nbytes&amp;#34;. However since commit 63ba4d67594a (&amp;#34;KEYS: asymmetric: Use new crypto interface without scatterlists&amp;#34;), the underflow can now actually be triggered.  When invoking a KEYCTL_PKEY_ENCRYPT system call with a larger &amp;#34;out_len&amp;#34; than &amp;#34;in_len&amp;#34; and filling the &amp;#34;in&amp;#34; buffer with zeroes, crypto_akcipher_sync_prep() will create an all-zero scatterlist used for both the &amp;#34;src&amp;#34; and &amp;#34;dst&amp;#34; member of struct akcipher_request and thereby fulfil the conditions to trigger the bug:   sys_keyctl()     keyctl_pkey_e_d_s()       asymmetric_key_eds_op()         software_key_eds_op()           crypto_akcipher_sync_encrypt()             crypto_akcipher_sync_prep()               crypto_akcipher_encrypt()…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-43492</guid>
    </item>
  </channel>
</rss>
