<?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://cve.radiocsirt.org</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, 03 Oct 2026 05:05:27 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-64590</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-64590</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://cve.radiocsirt.org/vuln/bell-cve-2026-64590</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1031 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Certaines d'entre elles permettent à…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1031</link>
      <description>certfr-2026-avi-1031</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-1031</guid>
    </item>
    <item>
      <title>EUVD-2026-357829</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-357829</link>
      <description>EUVD-2026-357829</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-357829</guid>
    </item>
    <item>
      <title>fkie_cve-2026-64590</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-64590</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;dma-buf/udmabuf: skip redundant cpu sync to fix cacheline EEXIST warning&lt;/p&gt;
&lt;p&gt;When CONFIG_DMA_API_DEBUG_SG is enabled, importing a udmabuf into a DRM
driver (e.g. amdgpu for video playback in GNOME Videos / Showtime)
triggers a spurious warning:&lt;/p&gt;
&lt;p&gt;DMA-API: amdgpu 0000:03:00.0: cacheline tracking EEXIST, \
      overlapping mappings aren&amp;#39;t supported
  WARNING: kernel/dma/debug.c:619 at add_dma_entry+0x473/0x5f0&lt;/p&gt;
&lt;p&gt;The call chain is:&lt;/p&gt;
&lt;p&gt;amdgpu_cs_ioctl
   -&amp;gt; amdgpu_ttm_backend_bind
    -&amp;gt; dma_buf_map_attachment
     -&amp;gt; [udmabuf] map_udmabuf -&amp;gt; get_sg_table
      -&amp;gt; dma_map_sgtable(dev, sg, direction, 0)  // attrs=0
       -&amp;gt; debug_dma_map_sg -&amp;gt; add_dma_entry -&amp;gt; EEXIST&lt;/p&gt;
&lt;p&gt;This happens because udmabuf builds a per-page scatter-gather list via
sg_set_folio().  When begin_cpu_udmabuf() has already created an sg
table mapped for the misc device, and an importer such as amdgpu maps
the same pages for its own device via map_udmabuf(), the DMA debug
infrastructure sees two active mappings whose physical addresses share
cacheline boundaries and warns about the overlap.&lt;/p&gt;
&lt;p&gt;The DMA_ATTR_SKIP_CPU_SYNC flag suppresses this check in
add_dma_entry() because it signals that no CPU cache maintenance is
performed at map/unmap time, making the cacheline overlap harmless.&lt;/p&gt;
&lt;p&gt;All other major dma-buf exporters already pass this flag:
  - drm_gem_map_dma_buf() passes DMA_ATTR_SKIP_CPU_SYNC
  - amdgpu_dma_buf_map() passes DMA_ATTR_SKIP_CPU_SYN…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;dma-buf/udmabuf: skip redundant cpu sync to fix cacheline EEXIST warning&lt;/p&gt;
&lt;p&gt;When CONFIG_DMA_API_DEBUG_SG is enabled, importing a udmabuf into a DRM
driver (e.g. amdgpu for video playback in GNOME Videos / Showtime)
triggers a spurious warning:&lt;/p&gt;
&lt;p&gt;DMA-API: amdgpu 0000:03:00.0: cacheline tracking EEXIST, \
      overlapping mappings aren&amp;#39;t supported
  WARNING: kernel/dma/debug.c:619 at add_dma_entry+0x473/0x5f0&lt;/p&gt;
&lt;p&gt;The call chain is:&lt;/p&gt;
&lt;p&gt;amdgpu_cs_ioctl
   -&amp;gt; amdgpu_ttm_backend_bind
    -&amp;gt; dma_buf_map_attachment
     -&amp;gt; [udmabuf] map_udmabuf -&amp;gt; get_sg_table
      -&amp;gt; dma_map_sgtable(dev, sg, direction, 0)  // attrs=0
       -&amp;gt; debug_dma_map_sg -&amp;gt; add_dma_entry -&amp;gt; EEXIST&lt;/p&gt;
&lt;p&gt;This happens because udmabuf builds a per-page scatter-gather list via
sg_set_folio().  When begin_cpu_udmabuf() has already created an sg
table mapped for the misc device, and an importer such as amdgpu maps
the same pages for its own device via map_udmabuf(), the DMA debug
infrastructure sees two active mappings whose physical addresses share
cacheline boundaries and warns about the overlap.&lt;/p&gt;
&lt;p&gt;The DMA_ATTR_SKIP_CPU_SYNC flag suppresses this check in
add_dma_entry() because it signals that no CPU cache maintenance is
performed at map/unmap time, making the cacheline overlap harmless.&lt;/p&gt;
&lt;p&gt;All other major dma-buf exporters already pass this flag:
  - drm_gem_map_dma_buf() passes DMA_ATTR_SKIP_CPU_SYNC
  - amdgpu_dma_buf_map() passes DMA_ATTR_SKIP_CPU_SYN…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-64590</guid>
    </item>
    <item>
      <title>GHSA-j99r-j84h-cmw8</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-j99r-j84h-cmw8</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;dma-buf/udmabuf: skip redundant cpu sync to fix cacheline EEXIST warning&lt;/p&gt;
&lt;p&gt;When CONFIG_DMA_API_DEBUG_SG is enabled, importing a udmabuf into a DRM
driver (e.g. amdgpu for video playback in GNOME Videos / Showtime)
triggers a spurious warning:&lt;/p&gt;
&lt;p&gt;DMA-API: amdgpu 0000:03:00.0: cacheline tracking EEXIST, \
      overlapping mappings aren&amp;#39;t supported
  WARNING: kernel/dma/debug.c:619 at add_dma_entry+0x473/0x5f0&lt;/p&gt;
&lt;p&gt;The call chain is:&lt;/p&gt;
&lt;p&gt;amdgpu_cs_ioctl
   -&amp;gt; amdgpu_ttm_backend_bind
    -&amp;gt; dma_buf_map_attachment
     -&amp;gt; [udmabuf] map_udmabuf -&amp;gt; get_sg_table
      -&amp;gt; dma_map_sgtable(dev, sg, direction, 0)  // attrs=0
       -&amp;gt; debug_dma_map_sg -&amp;gt; add_dma_entry -&amp;gt; EEXIST&lt;/p&gt;
&lt;p&gt;This happens because udmabuf builds a per-page scatter-gather list via
sg_set_folio().  When begin_cpu_udmabuf() has already created an sg
table mapped for the misc device, and an importer such as amdgpu maps
the same pages for its own device via map_udmabuf(), the DMA debug
infrastructure sees two active mappings whose physical addresses share
cacheline boundaries and warns about the overlap.&lt;/p&gt;
&lt;p&gt;The DMA_ATTR_SKIP_CPU_SYNC flag suppresses this check in
add_dma_entry() because it signals that no CPU cache maintenance is
performed at map/unmap time, making the cacheline overlap harmless.&lt;/p&gt;
&lt;p&gt;All other major dma-buf exporters already pass this flag:
  - drm_gem_map_dma_buf() passes DMA_ATTR_SKIP_CPU_SYNC
  - amdgpu_dma_buf_map() passes DMA_ATTR_SKIP_CPU_SYN…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;dma-buf/udmabuf: skip redundant cpu sync to fix cacheline EEXIST warning&lt;/p&gt;
&lt;p&gt;When CONFIG_DMA_API_DEBUG_SG is enabled, importing a udmabuf into a DRM
driver (e.g. amdgpu for video playback in GNOME Videos / Showtime)
triggers a spurious warning:&lt;/p&gt;
&lt;p&gt;DMA-API: amdgpu 0000:03:00.0: cacheline tracking EEXIST, \
      overlapping mappings aren&amp;#39;t supported
  WARNING: kernel/dma/debug.c:619 at add_dma_entry+0x473/0x5f0&lt;/p&gt;
&lt;p&gt;The call chain is:&lt;/p&gt;
&lt;p&gt;amdgpu_cs_ioctl
   -&amp;gt; amdgpu_ttm_backend_bind
    -&amp;gt; dma_buf_map_attachment
     -&amp;gt; [udmabuf] map_udmabuf -&amp;gt; get_sg_table
      -&amp;gt; dma_map_sgtable(dev, sg, direction, 0)  // attrs=0
       -&amp;gt; debug_dma_map_sg -&amp;gt; add_dma_entry -&amp;gt; EEXIST&lt;/p&gt;
&lt;p&gt;This happens because udmabuf builds a per-page scatter-gather list via
sg_set_folio().  When begin_cpu_udmabuf() has already created an sg
table mapped for the misc device, and an importer such as amdgpu maps
the same pages for its own device via map_udmabuf(), the DMA debug
infrastructure sees two active mappings whose physical addresses share
cacheline boundaries and warns about the overlap.&lt;/p&gt;
&lt;p&gt;The DMA_ATTR_SKIP_CPU_SYNC flag suppresses this check in
add_dma_entry() because it signals that no CPU cache maintenance is
performed at map/unmap time, making the cacheline overlap harmless.&lt;/p&gt;
&lt;p&gt;All other major dma-buf exporters already pass this flag:
  - drm_gem_map_dma_buf() passes DMA_ATTR_SKIP_CPU_SYNC
  - amdgpu_dma_buf_map() passes DMA_ATTR_SKIP_CPU_SYN…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-j99r-j84h-cmw8</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-64590 — dma-buf/udmabuf: skip redundant cpu sync to fix cacheline EEXIST warning</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-64590</link>
      <description>msrc_CVE-2026-64590</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-64590</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:11476-1 — kernel-devel-7.1.7-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:11476-1</link>
      <description>&lt;p&gt;kernel-devel-7.1.7-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel-devel-7.1.7-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2026:11476-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-64590</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-64590</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 195 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: dma-buf/udmabuf: skip redundant cpu sync to fix cacheline EEXIST warning When CONFIG_DMA_API_DEBUG_SG is enabled, importing a udmabuf into a DRM driver (e.g. amdgpu for video playback in GNOME Videos / Showtime) triggers a spurious warning:   DMA-API: amdgpu 0000:03:00.0: cacheline tracking EEXIST, \       overlapping mappings aren&amp;#39;t supported   WARNING: kernel/dma/debug.c:619 at add_dma_entry+0x473/0x5f0 The call chain is:   amdgpu_cs_ioctl    -&amp;gt; amdgpu_ttm_backend_bind     -&amp;gt; dma_buf_map_attachment      -&amp;gt; [udmabuf] map_udmabuf -&amp;gt; get_sg_table       -&amp;gt; dma_map_sgtable(dev, sg, direction, 0)  // attrs=0        -&amp;gt; debug_dma_map_sg -&amp;gt; add_dma_entry -&amp;gt; EEXIST This happens because udmabuf builds a per-page scatter-gather list via sg_set_folio().  When begin_cpu_udmabuf() has already created an sg table mapped for the misc device, and an importer such as amdgpu maps the same pages for its own device via map_udmabuf(), the DMA debug infrastructure sees two active mappings whose physical addresses share cacheline boundaries and warns about the overlap. The DMA_ATTR_SKIP_CPU_SYNC flag suppresses this check in add_dma_entry() because it signals that no CPU cache maintenance is performed at map/unmap time, making the cacheline overlap harmless. All other major dma-buf exporters already pass this flag:   - drm_gem_map_dma_buf() passes DMA_ATTR_SKIP_CPU_SYNC   - amdgpu_dma_buf_map() passes DMA_ATTR_SKIP_CPU_SYNC The CP…&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 195 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: dma-buf/udmabuf: skip redundant cpu sync to fix cacheline EEXIST warning When CONFIG_DMA_API_DEBUG_SG is enabled, importing a udmabuf into a DRM driver (e.g. amdgpu for video playback in GNOME Videos / Showtime) triggers a spurious warning:   DMA-API: amdgpu 0000:03:00.0: cacheline tracking EEXIST, \       overlapping mappings aren&amp;#39;t supported   WARNING: kernel/dma/debug.c:619 at add_dma_entry+0x473/0x5f0 The call chain is:   amdgpu_cs_ioctl    -&amp;gt; amdgpu_ttm_backend_bind     -&amp;gt; dma_buf_map_attachment      -&amp;gt; [udmabuf] map_udmabuf -&amp;gt; get_sg_table       -&amp;gt; dma_map_sgtable(dev, sg, direction, 0)  // attrs=0        -&amp;gt; debug_dma_map_sg -&amp;gt; add_dma_entry -&amp;gt; EEXIST This happens because udmabuf builds a per-page scatter-gather list via sg_set_folio().  When begin_cpu_udmabuf() has already created an sg table mapped for the misc device, and an importer such as amdgpu maps the same pages for its own device via map_udmabuf(), the DMA debug infrastructure sees two active mappings whose physical addresses share cacheline boundaries and warns about the overlap. The DMA_ATTR_SKIP_CPU_SYNC flag suppresses this check in add_dma_entry() because it signals that no CPU cache maintenance is performed at map/unmap time, making the cacheline overlap harmless. All other major dma-buf exporters already pass this flag:   - drm_gem_map_dma_buf() passes DMA_ATTR_SKIP_CPU_SYNC   - amdgpu_dma_buf_map() passes DMA_ATTR_SKIP_CPU_SYNC The CP…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-64590</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2680 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2680</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, darunter möglicherweise das Auslösen eines Denial-of-Service-Zustands, die Umgehung von Sicherheitsmaßnahmen oder das Verursachen von Speicherbeschädigungen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, darunter möglicherweise das Auslösen eines Denial-of-Service-Zustands, die Umgehung von Sicherheitsmaßnahmen oder das Verursachen von Speicherbeschädigungen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2680</guid>
    </item>
  </channel>
</rss>
