<?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 08:23:53 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-98949</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-98949</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-2026-98949</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1470 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2026-avi-1470</link>
      <description>certfr-2026-avi-1470</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-1470</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-98949</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-98949</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 164 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drm/imagination: Fix reference and vm_bo handling in remap() When a map overlaps part of an existing mapping, pvr_vm_gpuva_remap() splits the mapping into prev/next parts covering what the request did not take, instead of creating something new. It gets two things wrong. - A GEM reference is taken for each part but it&amp;#39;s never needed and never   dropped, so it leaks one reference per split (remap-next-in-2m in   tests/imagination/pvr_vm_map.c):     CRITICAL: 33558528 bytes of shmem still held after close - The parts still belong to the original object being split, but   pvr_vm_gpuva_remap() links them to ctx-&amp;gt;gpuvm_bo, the new object&amp;#39;s   vm_bo:     prev_va --obj--&amp;gt; BO_A          BO_B &amp;lt;--obj-- vm_bo (ctx-&amp;gt;gpuvm_bo)             \___________link___________/  (mismatch: BO_A != BO_B)   drm_gpuva_link() catches the mismatch:     WARNING: drivers/gpu/drm/drm_gpuvm.c:2108 at drm_gpuva_link+0x2ec/0x310       drm_WARN_ON(obj != vm_bo-&amp;gt;obj)     Call trace:      drm_gpuva_link      pvr_vm_gpuva_remap      __drm_gpuvm_sm_map      pvr_vm_map      pvr_ioctl_vm_map   Link them to op-&amp;gt;remap.unmap-&amp;gt;va-&amp;gt;vm_bo instead. The locking of the GPUVA lists of the other objects touched by a split is not addressed here; it is handled by switching the GPUVM to immediate mode.&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 164 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drm/imagination: Fix reference and vm_bo handling in remap() When a map overlaps part of an existing mapping, pvr_vm_gpuva_remap() splits the mapping into prev/next parts covering what the request did not take, instead of creating something new. It gets two things wrong. - A GEM reference is taken for each part but it&amp;#39;s never needed and never   dropped, so it leaks one reference per split (remap-next-in-2m in   tests/imagination/pvr_vm_map.c):     CRITICAL: 33558528 bytes of shmem still held after close - The parts still belong to the original object being split, but   pvr_vm_gpuva_remap() links them to ctx-&amp;gt;gpuvm_bo, the new object&amp;#39;s   vm_bo:     prev_va --obj--&amp;gt; BO_A          BO_B &amp;lt;--obj-- vm_bo (ctx-&amp;gt;gpuvm_bo)             \___________link___________/  (mismatch: BO_A != BO_B)   drm_gpuva_link() catches the mismatch:     WARNING: drivers/gpu/drm/drm_gpuvm.c:2108 at drm_gpuva_link+0x2ec/0x310       drm_WARN_ON(obj != vm_bo-&amp;gt;obj)     Call trace:      drm_gpuva_link      pvr_vm_gpuva_remap      __drm_gpuvm_sm_map      pvr_vm_map      pvr_ioctl_vm_map   Link them to op-&amp;gt;remap.unmap-&amp;gt;va-&amp;gt;vm_bo instead. The locking of the GPUVA lists of the other objects touched by a split is not addressed here; it is handled by switching the GPUVM to immediate mode.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-98949</guid>
    </item>
  </channel>
</rss>
