<?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 02:50:46 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2024-26674</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-26674</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/bell-cve-2024-26674</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0526 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent une élé…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2024-avi-0526</link>
      <description>certfr-2024-avi-0526</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2024-avi-0526</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-26674</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-26674</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 66 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: x86/lib: Revert to _ASM_EXTABLE_UA() for {get,put}_user() fixups During memory error injection test on kernels &amp;gt;= v6.4, the kernel panics like below. However, this issue couldn&amp;#39;t be reproduced on kernels &amp;lt;= v6.3.   mce: [Hardware Error]: CPU 296: Machine Check Exception: f Bank 1: bd80000000100134   mce: [Hardware Error]: RIP 10:&amp;lt;ffffffff821b9776&amp;gt; {__get_user_nocheck_4+0x6/0x20}   mce: [Hardware Error]: TSC 411a93533ed ADDR 346a8730040 MISC 86   mce: [Hardware Error]: PROCESSOR 0:a06d0 TIME 1706000767 SOCKET 1 APIC 211 microcode 80001490   mce: [Hardware Error]: Run the above through &amp;#39;mcelog --ascii&amp;#39;   mce: [Hardware Error]: Machine check: Data load in unrecoverable area of kernel   Kernel panic - not syncing: Fatal local machine check The MCA code can recover from an in-kernel #MC if the fixup type is EX_TYPE_UACCESS, explicitly indicating that the kernel is attempting to access userspace memory. However, if the fixup type is EX_TYPE_DEFAULT the only thing that is raised for an in-kernel #MC is a panic. ex_handler_uaccess() would warn if users gave a non-canonical addresses (with bit 63 clear) to {get, put}_user(), which was unexpected. Therefore, commit   b19b74bc99b1 (&amp;#34;x86/mm: Rework address range check in get_user() and put_user()&amp;#34;) replaced _ASM_EXTABLE_UA() with _ASM_EXTABLE() for {get, put}_user() fixups. However, the new fixup type EX_TYPE_DEFAULT results in a panic. Commit   6014bc27561f (&amp;#34;x86-64: m…&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 66 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: x86/lib: Revert to _ASM_EXTABLE_UA() for {get,put}_user() fixups During memory error injection test on kernels &amp;gt;= v6.4, the kernel panics like below. However, this issue couldn&amp;#39;t be reproduced on kernels &amp;lt;= v6.3.   mce: [Hardware Error]: CPU 296: Machine Check Exception: f Bank 1: bd80000000100134   mce: [Hardware Error]: RIP 10:&amp;lt;ffffffff821b9776&amp;gt; {__get_user_nocheck_4+0x6/0x20}   mce: [Hardware Error]: TSC 411a93533ed ADDR 346a8730040 MISC 86   mce: [Hardware Error]: PROCESSOR 0:a06d0 TIME 1706000767 SOCKET 1 APIC 211 microcode 80001490   mce: [Hardware Error]: Run the above through &amp;#39;mcelog --ascii&amp;#39;   mce: [Hardware Error]: Machine check: Data load in unrecoverable area of kernel   Kernel panic - not syncing: Fatal local machine check The MCA code can recover from an in-kernel #MC if the fixup type is EX_TYPE_UACCESS, explicitly indicating that the kernel is attempting to access userspace memory. However, if the fixup type is EX_TYPE_DEFAULT the only thing that is raised for an in-kernel #MC is a panic. ex_handler_uaccess() would warn if users gave a non-canonical addresses (with bit 63 clear) to {get, put}_user(), which was unexpected. Therefore, commit   b19b74bc99b1 (&amp;#34;x86/mm: Rework address range check in get_user() and put_user()&amp;#34;) replaced _ASM_EXTABLE_UA() with _ASM_EXTABLE() for {get, put}_user() fixups. However, the new fixup type EX_TYPE_DEFAULT results in a panic. Commit   6014bc27561f (&amp;#34;x86-64: m…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-26674</guid>
    </item>
  </channel>
</rss>
