<?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 15:39:38 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-12450</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-12450</link>
      <description>bdu:2026-12450</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-12450</guid>
    </item>
    <item>
      <title>BELL-CVE-2026-23227</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-23227</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-23227</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0316 — De multiples vulnérabilités ont été découvertes dans les produits VMware. Elles permettent à un attaquant de provoquer…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0316</link>
      <description>certfr-2026-avi-0316</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0316</guid>
    </item>
    <item>
      <title>EUVD-2026-347617</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-347617</link>
      <description>EUVD-2026-347617</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-347617</guid>
    </item>
    <item>
      <title>fkie_cve-2026-23227</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-23227</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/exynos: vidi: use ctx-&amp;gt;lock to protect struct vidi_context member variables related to memory alloc/free&lt;/p&gt;
&lt;p&gt;Exynos Virtual Display driver performs memory alloc/free operations
without lock protection, which easily causes concurrency problem.&lt;/p&gt;
&lt;p&gt;For example, use-after-free can occur in race scenario like this:
```
	CPU0				CPU1				CPU2
	----				----				----
  vidi_connection_ioctl()
    if (vidi-&amp;gt;connection) // true
      drm_edid = drm_edid_alloc(); // alloc drm_edid
      ...
      ctx-&amp;gt;raw_edid = drm_edid;
      ...
								drm_mode_getconnector()
								  drm_helper_probe_single_connector_modes()
								    vidi_get_modes()
								      if (ctx-&amp;gt;raw_edid) // true
								        drm_edid_dup(ctx-&amp;gt;raw_edid);
								          if (!drm_edid) // false
								          ...
				vidi_connection_ioctl()
				  if (vidi-&amp;gt;connection) // false
				    drm_edid_free(ctx-&amp;gt;raw_edid); // free drm_edid
				    ...
								          drm_edid_alloc(drm_edid-&amp;gt;edid)
								            kmemdup(edid); // UAF!!
								            ...
```&lt;/p&gt;
&lt;p&gt;To prevent these vulns, at least in vidi_context, member variables related
to memory alloc/free should be protected with ctx-&amp;gt;lock.&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;drm/exynos: vidi: use ctx-&amp;gt;lock to protect struct vidi_context member variables related to memory alloc/free&lt;/p&gt;
&lt;p&gt;Exynos Virtual Display driver performs memory alloc/free operations
without lock protection, which easily causes concurrency problem.&lt;/p&gt;
&lt;p&gt;For example, use-after-free can occur in race scenario like this:
```
	CPU0				CPU1				CPU2
	----				----				----
  vidi_connection_ioctl()
    if (vidi-&amp;gt;connection) // true
      drm_edid = drm_edid_alloc(); // alloc drm_edid
      ...
      ctx-&amp;gt;raw_edid = drm_edid;
      ...
								drm_mode_getconnector()
								  drm_helper_probe_single_connector_modes()
								    vidi_get_modes()
								      if (ctx-&amp;gt;raw_edid) // true
								        drm_edid_dup(ctx-&amp;gt;raw_edid);
								          if (!drm_edid) // false
								          ...
				vidi_connection_ioctl()
				  if (vidi-&amp;gt;connection) // false
				    drm_edid_free(ctx-&amp;gt;raw_edid); // free drm_edid
				    ...
								          drm_edid_alloc(drm_edid-&amp;gt;edid)
								            kmemdup(edid); // UAF!!
								            ...
```&lt;/p&gt;
&lt;p&gt;To prevent these vulns, at least in vidi_context, member variables related
to memory alloc/free should be protected with ctx-&amp;gt;lock.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-23227</guid>
    </item>
    <item>
      <title>GHSA-g3vh-wfh4-fp76</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-g3vh-wfh4-fp76</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/exynos: vidi: use ctx-&amp;gt;lock to protect struct vidi_context member variables related to memory alloc/free&lt;/p&gt;
&lt;p&gt;Exynos Virtual Display driver performs memory alloc/free operations
without lock protection, which easily causes concurrency problem.&lt;/p&gt;
&lt;p&gt;For example, use-after-free can occur in race scenario like this:
```
	CPU0				CPU1				CPU2
	----				----				----
  vidi_connection_ioctl()
    if (vidi-&amp;gt;connection) // true
      drm_edid = drm_edid_alloc(); // alloc drm_edid
      ...
      ctx-&amp;gt;raw_edid = drm_edid;
      ...
								drm_mode_getconnector()
								  drm_helper_probe_single_connector_modes()
								    vidi_get_modes()
								      if (ctx-&amp;gt;raw_edid) // true
								        drm_edid_dup(ctx-&amp;gt;raw_edid);
								          if (!drm_edid) // false
								          ...
				vidi_connection_ioctl()
				  if (vidi-&amp;gt;connection) // false
				    drm_edid_free(ctx-&amp;gt;raw_edid); // free drm_edid
				    ...
								          drm_edid_alloc(drm_edid-&amp;gt;edid)
								            kmemdup(edid); // UAF!!
								            ...
```&lt;/p&gt;
&lt;p&gt;To prevent these vulns, at least in vidi_context, member variables related
to memory alloc/free should be protected with ctx-&amp;gt;lock.&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;drm/exynos: vidi: use ctx-&amp;gt;lock to protect struct vidi_context member variables related to memory alloc/free&lt;/p&gt;
&lt;p&gt;Exynos Virtual Display driver performs memory alloc/free operations
without lock protection, which easily causes concurrency problem.&lt;/p&gt;
&lt;p&gt;For example, use-after-free can occur in race scenario like this:
```
	CPU0				CPU1				CPU2
	----				----				----
  vidi_connection_ioctl()
    if (vidi-&amp;gt;connection) // true
      drm_edid = drm_edid_alloc(); // alloc drm_edid
      ...
      ctx-&amp;gt;raw_edid = drm_edid;
      ...
								drm_mode_getconnector()
								  drm_helper_probe_single_connector_modes()
								    vidi_get_modes()
								      if (ctx-&amp;gt;raw_edid) // true
								        drm_edid_dup(ctx-&amp;gt;raw_edid);
								          if (!drm_edid) // false
								          ...
				vidi_connection_ioctl()
				  if (vidi-&amp;gt;connection) // false
				    drm_edid_free(ctx-&amp;gt;raw_edid); // free drm_edid
				    ...
								          drm_edid_alloc(drm_edid-&amp;gt;edid)
								            kmemdup(edid); // UAF!!
								            ...
```&lt;/p&gt;
&lt;p&gt;To prevent these vulns, at least in vidi_context, member variables related
to memory alloc/free should be protected with ctx-&amp;gt;lock.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-g3vh-wfh4-fp76</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-23227 — drm/exynos: vidi: use ctx-&gt;lock to protect struct vidi_context member variables related to memory alloc/free</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-23227</link>
      <description>msrc_CVE-2026-23227</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-23227</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:10387-1 — kernel-devel-6.19.8-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:10387-1</link>
      <description>&lt;p&gt;kernel-devel-6.19.8-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel-devel-6.19.8-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2026:10387-1</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:23066-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2026:23066-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2026:23066-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-23227</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-23227</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, 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 and 232 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drm/exynos: vidi: use ctx-&amp;gt;lock to protect struct vidi_context member variables related to memory alloc/free Exynos Virtual Display driver performs memory alloc/free operations without lock protection, which easily causes concurrency problem. For example, use-after-free can occur in race scenario like this: ``` 	CPU0				CPU1				CPU2 	----				----				----   vidi_connection_ioctl()     if (vidi-&amp;gt;connection) // true       drm_edid = drm_edid_alloc(); // alloc drm_edid       ...       ctx-&amp;gt;raw_edid = drm_edid;       ... 								drm_mode_getconnector() 								  drm_helper_probe_single_connector_modes() 								    vidi_get_modes() 								      if (ctx-&amp;gt;raw_edid) // true 								        drm_edid_dup(ctx-&amp;gt;raw_edid); 								          if (!drm_edid) // false 								          ... 				vidi_connection_ioctl() 				  if (vidi-&amp;gt;connection) // false 				    drm_edid_free(ctx-&amp;gt;raw_edid); // free drm_edid 				    ... 								          drm_edid_alloc(drm_edid-&amp;gt;edid) 								            kmemdup(edid); // UAF!! 								            ... ``` To prevent these vulns, at least in vidi_context, member variables related to memory alloc/free should be protected with ctx-&amp;gt;lock.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, 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 and 232 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drm/exynos: vidi: use ctx-&amp;gt;lock to protect struct vidi_context member variables related to memory alloc/free Exynos Virtual Display driver performs memory alloc/free operations without lock protection, which easily causes concurrency problem. For example, use-after-free can occur in race scenario like this: ``` 	CPU0				CPU1				CPU2 	----				----				----   vidi_connection_ioctl()     if (vidi-&amp;gt;connection) // true       drm_edid = drm_edid_alloc(); // alloc drm_edid       ...       ctx-&amp;gt;raw_edid = drm_edid;       ... 								drm_mode_getconnector() 								  drm_helper_probe_single_connector_modes() 								    vidi_get_modes() 								      if (ctx-&amp;gt;raw_edid) // true 								        drm_edid_dup(ctx-&amp;gt;raw_edid); 								          if (!drm_edid) // false 								          ... 				vidi_connection_ioctl() 				  if (vidi-&amp;gt;connection) // false 				    drm_edid_free(ctx-&amp;gt;raw_edid); // free drm_edid 				    ... 								          drm_edid_alloc(drm_edid-&amp;gt;edid) 								            kmemdup(edid); // UAF!! 								            ... ``` To prevent these vulns, at least in vidi_context, member variables related to memory alloc/free should be protected with ctx-&amp;gt;lock.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-23227</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-0462 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0462</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0462</guid>
    </item>
  </channel>
</rss>
