<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://127.0.0.1:10001/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-21T10:57:41.285310+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://127.0.0.1:10001" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://127.0.0.1:10001/vuln/bell-cve-2025-68198</id>
    <title>BELL-CVE-2025-68198</title>
    <updated>2026-11-21T10:57:41.290343+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p><strong>Affected:</strong> Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p>
      </div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/bell-cve-2025-68198"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/certfr-2026-avi-0128</id>
    <title>certfr-2026-avi-0128 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
    <updated>2026-11-21T10:57:41.290386+00:00</updated>
    <content>certfr-2026-avi-0128</content>
    <link href="https://127.0.0.1:10001/vuln/certfr-2026-avi-0128"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/oesa-2026-2675</id>
    <title>OESA-2026-2675 — kernel security update</title>
    <updated>2026-11-21T10:57:41.290398+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> openEuler:24.03-LTS-SP1: kernel</p>
<p>The Linux Kernel, the operating system core itself.

Security Fix(es):</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>drm/i915/gt: Fix timeline left held on VMA alloc error</p>
<p>The following error has been reported sporadically by CI when a test
unbinds the i915 driver on a ring submission platform:</p>
<p>&amp;lt;4&amp;gt; [239.330153] ------------[ cut here ]------------
&amp;lt;4&amp;gt; [239.330166] i915 0000:00:02.0: [drm] drm_WARN_ON(dev_priv-&amp;gt;mm.shrink_count)
&amp;lt;4&amp;gt; [239.330196] WARNING: CPU: 1 PID: 18570 at drivers/gpu/drm/i915/i915_gem.c:1309 i915_gem_cleanup_early+0x13e/0x150 [i915]
...
&amp;lt;4&amp;gt; [239.330640] RIP: 0010:i915_gem_cleanup_early+0x13e/0x150 [i915]
...
&amp;lt;4&amp;gt; [239.330942] Call Trace:
&amp;lt;4&amp;gt; [239.330944]  &amp;lt;TASK&amp;gt;
&amp;lt;4&amp;gt; [239.330949]  i915_driver_late_release+0x2b/0xa0 [i915]
&amp;lt;4&amp;gt; [239.331202]  i915_driver_release+0x86/0xa0 [i915]
&amp;lt;4&amp;gt; [239.331482]  devm_drm_dev_init_release+0x61/0x90
&amp;lt;4&amp;gt; [239.331494]  devm_action_release+0x15/0x30
&amp;lt;4&amp;gt; [239.331504]  release_nodes+0x3d/0x120
&amp;lt;4&amp;gt; [239.331517]  devres_release_all+0x96/0xd0
&amp;lt;4&amp;gt; [239.331533]  device_unbind_cleanup+0x12/0x80
&amp;lt;4&amp;gt; [239.331543]  device_release_driver_internal+0x23a/0x280
&amp;lt;4&amp;gt; [239.331550]  ? bus_find_device+0xa5/0xe0
&amp;lt;4&amp;gt; [239.331563]  device_driver_detach+0x14/0x20
...
&amp;lt;4&amp;gt; [357.719679] ---[ end trace 0000000000000000 ]---</p>
<p>If the test also unloads the i915 module then that&amp;apos;s followed with:</p>
<p>&amp;lt;3&amp;gt; [357.787478] ===…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/oesa-2026-2675"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-68198</id>
    <title>UBUNTU-CVE-2025-68198</title>
    <updated>2026-11-21T10:57:41.290584+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> 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 137 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: crash: fix crashkernel resource shrink When crashkernel is configured with a high reservation, shrinking its value below the low crashkernel reservation causes two issues: 1. Invalid crashkernel resource objects 2. Kernel crash if crashkernel shrinking is done twice For example, with crashkernel=200M,high, the kernel reserves 200MB of high memory and some default low memory (say 256MB).  The reservation appears as: cat /proc/iomem | grep -i crash af000000-beffffff : Crash kernel 433000000-43f7fffff : Crash kernel If crashkernel is then shrunk to 50MB (echo 52428800 &gt; /sys/kernel/kexec_crash_size), /proc/iomem still shows 256MB reserved: af000000-beffffff : Crash kernel Instead, it should show 50MB: af000000-b21fffff : Crash kernel Further shrinking crashkernel to 40MB causes a kernel crash with the following trace (x86): BUG: kernel NULL pointer dereference, address: 0000000000000038 PGD 0 P4D 0 Oops: 0000 [#1] PREEMPT SMP NOPTI &lt;snip...&gt; Call Trace: &lt;TASK&gt; ? __die_body.cold+0x19/0x27 ? page_fault_oops+0x15a/0x2f0 ? search_module_extables+0x19/0x60 ? search_bpf_extables+0x5f/0x80 ? exc_page_fault+0x7e/0x180 ? asm_exc_page_fault+0x26/0x30 ? __release_resource+0xd/0xb0 release_resource+0x26/0x40 __crash_shrink_memory+0xe5/0x110 crash_shrink_memory+0x12a/0x190 kexec_crash_size_store+0x41/0x80 kernfs_fop_write_iter+0x141/0x1f0 vfs_write+0x294/0x460 ksys_write+0x6d/0xf0 &lt;snip...&gt; This happens because __crash_shri…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/ubuntu-cve-2025-68198"/>
  </entry>
</feed>
