<?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>Tue, 17 Nov 2026 10:37:40 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-99059</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-99059</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-99059</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1537 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1537</link>
      <description>certfr-2026-avi-1537</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-1537</guid>
    </item>
    <item>
      <title>EUVD-2026-396153</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-396153</link>
      <description>EUVD-2026-396153</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-396153</guid>
    </item>
    <item>
      <title>fkie_cve-2026-99059</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-99059</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;wireguard: noise: reject response consumption after intermediate initiation&lt;/p&gt;
&lt;p&gt;Two threads begin processing the identical response message, received
twice. The first thread, A, runs. While it&amp;#39;s running, the second one,
B, gets partway through, and during that slow calculation, or even while
blocking on down_write(), A completes and then also a handshake
initiation that&amp;#39;s already been queued up runs in thread C, which itself
takes that same down_write(). The handshake initiation creation
succeeds, and sets the state back to waiting-for-response, and calls
up_write(), at which point thread B resumes, because either its finished
its calculations or was finally allowed to acquire down_write(). Thread
B then copies the state back to the peer, and begins a new session,
using that state, which is the same session as the one made in thread A.&lt;/p&gt;
&lt;p&gt;Thread A			Thread B			Thread C&lt;/p&gt;
&lt;p&gt;down_read()
 sA = handshake-&amp;gt;state
 memcpy(cA, handshake-&amp;gt;crypto)
up_read()
if (sA != 1)
 goto fail
slow_crypto(cA)
				down_read()
				 sB = handshake-&amp;gt;state
				 memcpy(cB, handshake-&amp;gt;crypto)
				up_read()
				if (sB != 1)
				 goto fail
				slow_crypto(cB)
down_write()
 if (sA != handshake-&amp;gt;state)
  goto fail
 memcpy(handshake-&amp;gt;crypto, cA)
 handshake-&amp;gt;state = 2
up_write()
down_write()
 if (handshake-&amp;gt;state != 2)
  goto fail
 derive_session(handshake-&amp;gt;crypto)
up_write()
								down_write()
								 slow_crypto(handshake-&amp;gt;crypto)
								 hands…&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;wireguard: noise: reject response consumption after intermediate initiation&lt;/p&gt;
&lt;p&gt;Two threads begin processing the identical response message, received
twice. The first thread, A, runs. While it&amp;#39;s running, the second one,
B, gets partway through, and during that slow calculation, or even while
blocking on down_write(), A completes and then also a handshake
initiation that&amp;#39;s already been queued up runs in thread C, which itself
takes that same down_write(). The handshake initiation creation
succeeds, and sets the state back to waiting-for-response, and calls
up_write(), at which point thread B resumes, because either its finished
its calculations or was finally allowed to acquire down_write(). Thread
B then copies the state back to the peer, and begins a new session,
using that state, which is the same session as the one made in thread A.&lt;/p&gt;
&lt;p&gt;Thread A			Thread B			Thread C&lt;/p&gt;
&lt;p&gt;down_read()
 sA = handshake-&amp;gt;state
 memcpy(cA, handshake-&amp;gt;crypto)
up_read()
if (sA != 1)
 goto fail
slow_crypto(cA)
				down_read()
				 sB = handshake-&amp;gt;state
				 memcpy(cB, handshake-&amp;gt;crypto)
				up_read()
				if (sB != 1)
				 goto fail
				slow_crypto(cB)
down_write()
 if (sA != handshake-&amp;gt;state)
  goto fail
 memcpy(handshake-&amp;gt;crypto, cA)
 handshake-&amp;gt;state = 2
up_write()
down_write()
 if (handshake-&amp;gt;state != 2)
  goto fail
 derive_session(handshake-&amp;gt;crypto)
up_write()
								down_write()
								 slow_crypto(handshake-&amp;gt;crypto)
								 hands…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-99059</guid>
    </item>
    <item>
      <title>GHSA-c2jq-9mfv-9wqh</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-c2jq-9mfv-9wqh</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;wireguard: noise: reject response consumption after intermediate initiation&lt;/p&gt;
&lt;p&gt;Two threads begin processing the identical response message, received
twice. The first thread, A, runs. While it&amp;#39;s running, the second one,
B, gets partway through, and during that slow calculation, or even while
blocking on down_write(), A completes and then also a handshake
initiation that&amp;#39;s already been queued up runs in thread C, which itself
takes that same down_write(). The handshake initiation creation
succeeds, and sets the state back to waiting-for-response, and calls
up_write(), at which point thread B resumes, because either its finished
its calculations or was finally allowed to acquire down_write(). Thread
B then copies the state back to the peer, and begins a new session,
using that state, which is the same session as the one made in thread A.&lt;/p&gt;
&lt;p&gt;Thread A			Thread B			Thread C&lt;/p&gt;
&lt;p&gt;down_read()
 sA = handshake-&amp;gt;state
 memcpy(cA, handshake-&amp;gt;crypto)
up_read()
if (sA != 1)
 goto fail
slow_crypto(cA)
				down_read()
				 sB = handshake-&amp;gt;state
				 memcpy(cB, handshake-&amp;gt;crypto)
				up_read()
				if (sB != 1)
				 goto fail
				slow_crypto(cB)
down_write()
 if (sA != handshake-&amp;gt;state)
  goto fail
 memcpy(handshake-&amp;gt;crypto, cA)
 handshake-&amp;gt;state = 2
up_write()
down_write()
 if (handshake-&amp;gt;state != 2)
  goto fail
 derive_session(handshake-&amp;gt;crypto)
up_write()
								down_write()
								 slow_crypto(handshake-&amp;gt;crypto)
								 hands…&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;wireguard: noise: reject response consumption after intermediate initiation&lt;/p&gt;
&lt;p&gt;Two threads begin processing the identical response message, received
twice. The first thread, A, runs. While it&amp;#39;s running, the second one,
B, gets partway through, and during that slow calculation, or even while
blocking on down_write(), A completes and then also a handshake
initiation that&amp;#39;s already been queued up runs in thread C, which itself
takes that same down_write(). The handshake initiation creation
succeeds, and sets the state back to waiting-for-response, and calls
up_write(), at which point thread B resumes, because either its finished
its calculations or was finally allowed to acquire down_write(). Thread
B then copies the state back to the peer, and begins a new session,
using that state, which is the same session as the one made in thread A.&lt;/p&gt;
&lt;p&gt;Thread A			Thread B			Thread C&lt;/p&gt;
&lt;p&gt;down_read()
 sA = handshake-&amp;gt;state
 memcpy(cA, handshake-&amp;gt;crypto)
up_read()
if (sA != 1)
 goto fail
slow_crypto(cA)
				down_read()
				 sB = handshake-&amp;gt;state
				 memcpy(cB, handshake-&amp;gt;crypto)
				up_read()
				if (sB != 1)
				 goto fail
				slow_crypto(cB)
down_write()
 if (sA != handshake-&amp;gt;state)
  goto fail
 memcpy(handshake-&amp;gt;crypto, cA)
 handshake-&amp;gt;state = 2
up_write()
down_write()
 if (handshake-&amp;gt;state != 2)
  goto fail
 derive_session(handshake-&amp;gt;crypto)
up_write()
								down_write()
								 slow_crypto(handshake-&amp;gt;crypto)
								 hands…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-c2jq-9mfv-9wqh</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-99059 — wireguard: noise: reject response consumption after intermediate initiation</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-99059</link>
      <description>msrc_CVE-2026-99059</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-99059</guid>
    </item>
    <item>
      <title>OESA-2026-4810 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2026-4810</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP4: 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;wifi: brcmsmac: Fix dma_free_coherent() size&lt;/p&gt;
&lt;p&gt;dma_alloc_consistent() may change the size to align it. The new size is
saved in alloced.&lt;/p&gt;
&lt;p&gt;Change the free size to match the allocation size.(CVE-2026-31661)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/amd/display: Validate GPIO pin LUT table size before iterating&lt;/p&gt;
&lt;p&gt;[Why&amp;amp;amp;How]
The GPIO pin table parsers in get_gpio_i2c_info() and
bios_parser_get_gpio_pin_info() derive an element count from the VBIOS
table_header.structuresize field, then iterate over gpio_pin[] entries.
However, GET_IMAGE() only validates that the table header itself fits
within the BIOS image. If the VBIOS reports a structuresize larger than
the actual mapped data, the loop reads past the end of the BIOS image,
causing an out-of-bounds read.&lt;/p&gt;
&lt;p&gt;Fix this by calling bios_get_image() to validate that the full claimed
structuresize is accessible within the BIOS image before entering the
loop in both functions.&lt;/p&gt;
&lt;p&gt;(cherry picked from commit ba5e95b43b773ae1bf1f66ee6b31eb774e65afe3)(CVE-2026-64097)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;usbip: vudc: fix NULL deref in vep_dequeue()&lt;/p&gt;
&lt;p&gt;vep_alloc_request() wasn&amp;amp;apos;t initializing vrequest-&amp;amp;gt;udc, so cancellations
on the FunctionFS AIO path were arriving in vep_dequeue without a valid
UDC reference.&lt;/p&gt;
&lt;p&gt;Since vrequest-&amp;amp;gt;udc…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP4: 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;wifi: brcmsmac: Fix dma_free_coherent() size&lt;/p&gt;
&lt;p&gt;dma_alloc_consistent() may change the size to align it. The new size is
saved in alloced.&lt;/p&gt;
&lt;p&gt;Change the free size to match the allocation size.(CVE-2026-31661)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/amd/display: Validate GPIO pin LUT table size before iterating&lt;/p&gt;
&lt;p&gt;[Why&amp;amp;amp;How]
The GPIO pin table parsers in get_gpio_i2c_info() and
bios_parser_get_gpio_pin_info() derive an element count from the VBIOS
table_header.structuresize field, then iterate over gpio_pin[] entries.
However, GET_IMAGE() only validates that the table header itself fits
within the BIOS image. If the VBIOS reports a structuresize larger than
the actual mapped data, the loop reads past the end of the BIOS image,
causing an out-of-bounds read.&lt;/p&gt;
&lt;p&gt;Fix this by calling bios_get_image() to validate that the full claimed
structuresize is accessible within the BIOS image before entering the
loop in both functions.&lt;/p&gt;
&lt;p&gt;(cherry picked from commit ba5e95b43b773ae1bf1f66ee6b31eb774e65afe3)(CVE-2026-64097)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;usbip: vudc: fix NULL deref in vep_dequeue()&lt;/p&gt;
&lt;p&gt;vep_alloc_request() wasn&amp;amp;apos;t initializing vrequest-&amp;amp;gt;udc, so cancellations
on the FunctionFS AIO path were arriving in vep_dequeue without a valid
UDC reference.&lt;/p&gt;
&lt;p&gt;Since vrequest-&amp;amp;gt;udc…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2026-4810</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-99059</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-99059</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 203 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: wireguard: noise: reject response consumption after intermediate initiation Two threads begin processing the identical response message, received twice. The first thread, A, runs. While it&amp;#39;s running, the second one, B, gets partway through, and during that slow calculation, or even while blocking on down_write(), A completes and then also a handshake initiation that&amp;#39;s already been queued up runs in thread C, which itself takes that same down_write(). The handshake initiation creation succeeds, and sets the state back to waiting-for-response, and calls up_write(), at which point thread B resumes, because either its finished its calculations or was finally allowed to acquire down_write(). Thread B then copies the state back to the peer, and begins a new session, using that state, which is the same session as the one made in thread A. Thread A			Thread B			Thread C down_read()  sA = handshake-&amp;gt;state  memcpy(cA, handshake-&amp;gt;crypto) up_read() if (sA != 1)  goto fail slow_crypto(cA) 				down_read() 				 sB = handshake-&amp;gt;state 				 memcpy(cB, handshake-&amp;gt;crypto) 				up_read() 				if (sB != 1) 				 goto fail 				slow_crypto(cB) down_write()  if (sA != handshake-&amp;gt;state)   goto fail  memcpy(handshake-&amp;gt;crypto, cA)  handshake-&amp;gt;state = 2 up_write() down_write()  if (handshake-&amp;gt;state != 2)   goto fail  derive_session(handshake-&amp;gt;crypto) up_write() 								down_write() 								 slow_crypto(handshake-&amp;gt;crypto) 								 handshake…&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 203 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: wireguard: noise: reject response consumption after intermediate initiation Two threads begin processing the identical response message, received twice. The first thread, A, runs. While it&amp;#39;s running, the second one, B, gets partway through, and during that slow calculation, or even while blocking on down_write(), A completes and then also a handshake initiation that&amp;#39;s already been queued up runs in thread C, which itself takes that same down_write(). The handshake initiation creation succeeds, and sets the state back to waiting-for-response, and calls up_write(), at which point thread B resumes, because either its finished its calculations or was finally allowed to acquire down_write(). Thread B then copies the state back to the peer, and begins a new session, using that state, which is the same session as the one made in thread A. Thread A			Thread B			Thread C down_read()  sA = handshake-&amp;gt;state  memcpy(cA, handshake-&amp;gt;crypto) up_read() if (sA != 1)  goto fail slow_crypto(cA) 				down_read() 				 sB = handshake-&amp;gt;state 				 memcpy(cB, handshake-&amp;gt;crypto) 				up_read() 				if (sB != 1) 				 goto fail 				slow_crypto(cB) down_write()  if (sA != handshake-&amp;gt;state)   goto fail  memcpy(handshake-&amp;gt;crypto, cA)  handshake-&amp;gt;state = 2 up_write() down_write()  if (handshake-&amp;gt;state != 2)   goto fail  derive_session(handshake-&amp;gt;crypto) up_write() 								down_write() 								 slow_crypto(handshake-&amp;gt;crypto) 								 handshake…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-99059</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4152 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4152</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen.&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, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4152</guid>
    </item>
  </channel>
</rss>
