<?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:18:50 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2025-38696</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2025-38696</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-2025-38696</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0825 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Elles permettent à un attaquant de provo…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2025-avi-0825</link>
      <description>certfr-2025-avi-0825</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2025-avi-0825</guid>
    </item>
    <item>
      <title>OESA-2025-2695 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2025-2695</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS-SP1: 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;misc: pci_endpoint_test: Avoid issue of interrupts remaining after request_irq error&lt;/p&gt;
&lt;p&gt;After devm_request_irq() fails with error in pci_endpoint_test_request_irq(),
the pci_endpoint_test_free_irq_vectors() is called assuming that all IRQs
have been released.&lt;/p&gt;
&lt;p&gt;However, some requested IRQs remain unreleased, so there are still
/proc/irq/* entries remaining, and this results in WARN() with the
following message:&lt;/p&gt;
&lt;p&gt;remove_proc_entry: removing non-empty directory &amp;amp;apos;irq/30&amp;amp;apos;, leaking at least &amp;amp;apos;pci-endpoint-test.0&amp;amp;apos;
  WARNING: CPU: 0 PID: 202 at fs/proc/generic.c:719 remove_proc_entry +0x190/0x19c&lt;/p&gt;
&lt;p&gt;To solve this issue, set the number of remaining IRQs to test-&amp;amp;gt;num_irqs,
and release IRQs in advance by calling pci_endpoint_test_release_irq().&lt;/p&gt;
&lt;p&gt;[kwilczynski: commit log](CVE-2025-23140)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/amdgpu: csa unmap use uninterruptible lock&lt;/p&gt;
&lt;p&gt;After process exit to unmap csa and free GPU vm, if signal is accepted
and then waiting to take vm lock is interrupted and return, it causes
memory leaking and below warning backtrace.&lt;/p&gt;
&lt;p&gt;Change to use uninterruptible wait lock fix the issue.&lt;/p&gt;
&lt;p&gt;WARNING: CPU: 69 PID: 167800 at amd/amdgpu/amdgpu_kms.c:1525
 amdgpu_driver_postclose_kms+0x294/0x2a0 [amdgpu]
 Call Trace:
  &amp;amp;lt;TASK&amp;amp;gt;
  drm_file_free.part.0+0x1da/0x230 [drm]
  drm_clo…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS-SP1: 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;misc: pci_endpoint_test: Avoid issue of interrupts remaining after request_irq error&lt;/p&gt;
&lt;p&gt;After devm_request_irq() fails with error in pci_endpoint_test_request_irq(),
the pci_endpoint_test_free_irq_vectors() is called assuming that all IRQs
have been released.&lt;/p&gt;
&lt;p&gt;However, some requested IRQs remain unreleased, so there are still
/proc/irq/* entries remaining, and this results in WARN() with the
following message:&lt;/p&gt;
&lt;p&gt;remove_proc_entry: removing non-empty directory &amp;amp;apos;irq/30&amp;amp;apos;, leaking at least &amp;amp;apos;pci-endpoint-test.0&amp;amp;apos;
  WARNING: CPU: 0 PID: 202 at fs/proc/generic.c:719 remove_proc_entry +0x190/0x19c&lt;/p&gt;
&lt;p&gt;To solve this issue, set the number of remaining IRQs to test-&amp;amp;gt;num_irqs,
and release IRQs in advance by calling pci_endpoint_test_release_irq().&lt;/p&gt;
&lt;p&gt;[kwilczynski: commit log](CVE-2025-23140)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/amdgpu: csa unmap use uninterruptible lock&lt;/p&gt;
&lt;p&gt;After process exit to unmap csa and free GPU vm, if signal is accepted
and then waiting to take vm lock is interrupted and return, it causes
memory leaking and below warning backtrace.&lt;/p&gt;
&lt;p&gt;Change to use uninterruptible wait lock fix the issue.&lt;/p&gt;
&lt;p&gt;WARNING: CPU: 69 PID: 167800 at amd/amdgpu/amdgpu_kms.c:1525
 amdgpu_driver_postclose_kms+0x294/0x2a0 [amdgpu]
 Call Trace:
  &amp;amp;lt;TASK&amp;amp;gt;
  drm_file_free.part.0+0x1da/0x230 [drm]
  drm_clo…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2025-2695</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-38696</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-38696</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 205 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: MIPS: Don&amp;#39;t crash in stack_top() for tasks without ABI or vDSO Not all tasks have an ABI associated or vDSO mapped, for example kthreads never do. If such a task ever ends up calling stack_top(), it will derefence the NULL ABI pointer and crash. This can for example happen when using kunit:     mips_stack_top+0x28/0xc0     arch_pick_mmap_layout+0x190/0x220     kunit_vm_mmap_init+0xf8/0x138     __kunit_add_resource+0x40/0xa8     kunit_vm_mmap+0x88/0xd8     usercopy_test_init+0xb8/0x240     kunit_try_run_case+0x5c/0x1a8     kunit_generic_run_threadfn_adapter+0x28/0x50     kthread+0x118/0x240     ret_from_kernel_thread+0x14/0x1c Only dereference the ABI point if it is set. The GIC page is also included as it is specific to the vDSO. Also move the randomization adjustment into the same conditional.&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 205 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: MIPS: Don&amp;#39;t crash in stack_top() for tasks without ABI or vDSO Not all tasks have an ABI associated or vDSO mapped, for example kthreads never do. If such a task ever ends up calling stack_top(), it will derefence the NULL ABI pointer and crash. This can for example happen when using kunit:     mips_stack_top+0x28/0xc0     arch_pick_mmap_layout+0x190/0x220     kunit_vm_mmap_init+0xf8/0x138     __kunit_add_resource+0x40/0xa8     kunit_vm_mmap+0x88/0xd8     usercopy_test_init+0xb8/0x240     kunit_try_run_case+0x5c/0x1a8     kunit_generic_run_threadfn_adapter+0x28/0x50     kthread+0x118/0x240     ret_from_kernel_thread+0x14/0x1c Only dereference the ABI point if it is set. The GIC page is also included as it is specific to the vDSO. Also move the randomization adjustment into the same conditional.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2025-38696</guid>
    </item>
  </channel>
</rss>
