<?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 21:31:32 +0000</lastBuildDate>
    <item>
      <title>bdu:2024-07587</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2024-07587</link>
      <description>bdu:2024-07587</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2024-07587</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0779 — 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://cve.radiocsirt.org/vuln/certfr-2024-avi-0779</link>
      <description>certfr-2024-avi-0779</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-0779</guid>
    </item>
    <item>
      <title>EUVD-2026-344604</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-344604</link>
      <description>EUVD-2026-344604</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-344604</guid>
    </item>
    <item>
      <title>fkie_cve-2022-48871</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-48871</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;tty: serial: qcom-geni-serial: fix slab-out-of-bounds on RX FIFO buffer&lt;/p&gt;
&lt;p&gt;Driver&amp;#39;s probe allocates memory for RX FIFO (port-&amp;gt;rx_fifo) based on
default RX FIFO depth, e.g. 16.  Later during serial startup the
qcom_geni_serial_port_setup() updates the RX FIFO depth
(port-&amp;gt;rx_fifo_depth) to match real device capabilities, e.g. to 32.&lt;/p&gt;
&lt;p&gt;The RX UART handle code will read &amp;#34;port-&amp;gt;rx_fifo_depth&amp;#34; number of words
into &amp;#34;port-&amp;gt;rx_fifo&amp;#34; buffer, thus exceeding the bounds.  This can be
observed in certain configurations with Qualcomm Bluetooth HCI UART
device and KASAN:&lt;/p&gt;
&lt;p&gt;Bluetooth: hci0: QCA Product ID   :0x00000010
  Bluetooth: hci0: QCA SOC Version  :0x400a0200
  Bluetooth: hci0: QCA ROM Version  :0x00000200
  Bluetooth: hci0: QCA Patch Version:0x00000d2b
  Bluetooth: hci0: QCA controller version 0x02000200
  Bluetooth: hci0: QCA Downloading qca/htbtfw20.tlv
  bluetooth hci0: Direct firmware load for qca/htbtfw20.tlv failed with error -2
  Bluetooth: hci0: QCA Failed to request file: qca/htbtfw20.tlv (-2)
  Bluetooth: hci0: QCA Failed to download patch (-2)
  ==================================================================
  BUG: KASAN: slab-out-of-bounds in handle_rx_uart+0xa8/0x18c
  Write of size 4 at addr ffff279347d578c0 by task swapper/0/0&lt;/p&gt;
&lt;p&gt;CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.1.0-rt5-00350-gb2450b7e00be-dirty #26
  Hardware name: Qualcomm Technologies, Inc. Robotics RB5 (DT)
  Call trace:
   dump_backt…&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;tty: serial: qcom-geni-serial: fix slab-out-of-bounds on RX FIFO buffer&lt;/p&gt;
&lt;p&gt;Driver&amp;#39;s probe allocates memory for RX FIFO (port-&amp;gt;rx_fifo) based on
default RX FIFO depth, e.g. 16.  Later during serial startup the
qcom_geni_serial_port_setup() updates the RX FIFO depth
(port-&amp;gt;rx_fifo_depth) to match real device capabilities, e.g. to 32.&lt;/p&gt;
&lt;p&gt;The RX UART handle code will read &amp;#34;port-&amp;gt;rx_fifo_depth&amp;#34; number of words
into &amp;#34;port-&amp;gt;rx_fifo&amp;#34; buffer, thus exceeding the bounds.  This can be
observed in certain configurations with Qualcomm Bluetooth HCI UART
device and KASAN:&lt;/p&gt;
&lt;p&gt;Bluetooth: hci0: QCA Product ID   :0x00000010
  Bluetooth: hci0: QCA SOC Version  :0x400a0200
  Bluetooth: hci0: QCA ROM Version  :0x00000200
  Bluetooth: hci0: QCA Patch Version:0x00000d2b
  Bluetooth: hci0: QCA controller version 0x02000200
  Bluetooth: hci0: QCA Downloading qca/htbtfw20.tlv
  bluetooth hci0: Direct firmware load for qca/htbtfw20.tlv failed with error -2
  Bluetooth: hci0: QCA Failed to request file: qca/htbtfw20.tlv (-2)
  Bluetooth: hci0: QCA Failed to download patch (-2)
  ==================================================================
  BUG: KASAN: slab-out-of-bounds in handle_rx_uart+0xa8/0x18c
  Write of size 4 at addr ffff279347d578c0 by task swapper/0/0&lt;/p&gt;
&lt;p&gt;CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.1.0-rt5-00350-gb2450b7e00be-dirty #26
  Hardware name: Qualcomm Technologies, Inc. Robotics RB5 (DT)
  Call trace:
   dump_backt…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-48871</guid>
    </item>
    <item>
      <title>GHSA-hq8p-jq83-pjp2</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-hq8p-jq83-pjp2</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;tty: serial: qcom-geni-serial: fix slab-out-of-bounds on RX FIFO buffer&lt;/p&gt;
&lt;p&gt;Driver&amp;#39;s probe allocates memory for RX FIFO (port-&amp;gt;rx_fifo) based on
default RX FIFO depth, e.g. 16.  Later during serial startup the
qcom_geni_serial_port_setup() updates the RX FIFO depth
(port-&amp;gt;rx_fifo_depth) to match real device capabilities, e.g. to 32.&lt;/p&gt;
&lt;p&gt;The RX UART handle code will read &amp;#34;port-&amp;gt;rx_fifo_depth&amp;#34; number of words
into &amp;#34;port-&amp;gt;rx_fifo&amp;#34; buffer, thus exceeding the bounds.  This can be
observed in certain configurations with Qualcomm Bluetooth HCI UART
device and KASAN:&lt;/p&gt;
&lt;p&gt;Bluetooth: hci0: QCA Product ID   :0x00000010
  Bluetooth: hci0: QCA SOC Version  :0x400a0200
  Bluetooth: hci0: QCA ROM Version  :0x00000200
  Bluetooth: hci0: QCA Patch Version:0x00000d2b
  Bluetooth: hci0: QCA controller version 0x02000200
  Bluetooth: hci0: QCA Downloading qca/htbtfw20.tlv
  bluetooth hci0: Direct firmware load for qca/htbtfw20.tlv failed with error -2
  Bluetooth: hci0: QCA Failed to request file: qca/htbtfw20.tlv (-2)
  Bluetooth: hci0: QCA Failed to download patch (-2)
  ==================================================================
  BUG: KASAN: slab-out-of-bounds in handle_rx_uart+0xa8/0x18c
  Write of size 4 at addr ffff279347d578c0 by task swapper/0/0&lt;/p&gt;
&lt;p&gt;CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.1.0-rt5-00350-gb2450b7e00be-dirty #26
  Hardware name: Qualcomm Technologies, Inc. Robotics RB5 (DT)
  Call trace:
   dump_backt…&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;tty: serial: qcom-geni-serial: fix slab-out-of-bounds on RX FIFO buffer&lt;/p&gt;
&lt;p&gt;Driver&amp;#39;s probe allocates memory for RX FIFO (port-&amp;gt;rx_fifo) based on
default RX FIFO depth, e.g. 16.  Later during serial startup the
qcom_geni_serial_port_setup() updates the RX FIFO depth
(port-&amp;gt;rx_fifo_depth) to match real device capabilities, e.g. to 32.&lt;/p&gt;
&lt;p&gt;The RX UART handle code will read &amp;#34;port-&amp;gt;rx_fifo_depth&amp;#34; number of words
into &amp;#34;port-&amp;gt;rx_fifo&amp;#34; buffer, thus exceeding the bounds.  This can be
observed in certain configurations with Qualcomm Bluetooth HCI UART
device and KASAN:&lt;/p&gt;
&lt;p&gt;Bluetooth: hci0: QCA Product ID   :0x00000010
  Bluetooth: hci0: QCA SOC Version  :0x400a0200
  Bluetooth: hci0: QCA ROM Version  :0x00000200
  Bluetooth: hci0: QCA Patch Version:0x00000d2b
  Bluetooth: hci0: QCA controller version 0x02000200
  Bluetooth: hci0: QCA Downloading qca/htbtfw20.tlv
  bluetooth hci0: Direct firmware load for qca/htbtfw20.tlv failed with error -2
  Bluetooth: hci0: QCA Failed to request file: qca/htbtfw20.tlv (-2)
  Bluetooth: hci0: QCA Failed to download patch (-2)
  ==================================================================
  BUG: KASAN: slab-out-of-bounds in handle_rx_uart+0xa8/0x18c
  Write of size 4 at addr ffff279347d578c0 by task swapper/0/0&lt;/p&gt;
&lt;p&gt;CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.1.0-rt5-00350-gb2450b7e00be-dirty #26
  Hardware name: Qualcomm Technologies, Inc. Robotics RB5 (DT)
  Call trace:
   dump_backt…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-hq8p-jq83-pjp2</guid>
    </item>
    <item>
      <title>OESA-2024-2106 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2024-2106</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP1: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
ibmvnic: don&amp;amp;apos;t release napi in __ibmvnic_open()&#13;
&#13;
If __ibmvnic_open() encounters an error such as when setting link state,
it calls release_resources() which frees the napi structures needlessly.
Instead, have __ibmvnic_open() only clean up the work it did so far (i.e.
disable napi and irqs) and leave the rest to the callers.&#13;
&#13;
If caller of __ibmvnic_open() is ibmvnic_open(), it should release the
resources immediately. If the caller is do_reset() or do_hard_reset(),
they will release the resources on the next reset.&#13;
&#13;
This fixes following crash that occurred when running the drmgr command
several times to add/remove a vnic interface:&#13;
&#13;
	[102056] ibmvnic 30000003 env3: Disabling rx_scrq[6] irq
	[102056] ibmvnic 30000003 env3: Disabling rx_scrq[7] irq
	[102056] ibmvnic 30000003 env3: Replenished 8 pools
	Kernel attempted to read user page (10) - exploit attempt? (uid: 0)
	BUG: Kernel NULL pointer dereference on read at 0x00000010
	Faulting instruction address: 0xc000000000a3c840
	Oops: Kernel access of bad area, sig: 11 [#1]
	LE PAGE_SIZE=64K MMU=Radix SMP NR_CPUS=2048 NUMA pSeries
	...
	CPU: 9 PID: 102056 Comm: kworker/9:2 Kdump: loaded Not tainted 5.16.0-rc5-autotest-g6441998e2e37 #1
	Workqueue: events_long __ibmvnic_reset [ibmvnic]
	NIP:  c000000000a3c840 LR: c0080000029b5378 CTR: c000000000a3c820
	REGS: c0000000548e37e…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP1: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
ibmvnic: don&amp;amp;apos;t release napi in __ibmvnic_open()&#13;
&#13;
If __ibmvnic_open() encounters an error such as when setting link state,
it calls release_resources() which frees the napi structures needlessly.
Instead, have __ibmvnic_open() only clean up the work it did so far (i.e.
disable napi and irqs) and leave the rest to the callers.&#13;
&#13;
If caller of __ibmvnic_open() is ibmvnic_open(), it should release the
resources immediately. If the caller is do_reset() or do_hard_reset(),
they will release the resources on the next reset.&#13;
&#13;
This fixes following crash that occurred when running the drmgr command
several times to add/remove a vnic interface:&#13;
&#13;
	[102056] ibmvnic 30000003 env3: Disabling rx_scrq[6] irq
	[102056] ibmvnic 30000003 env3: Disabling rx_scrq[7] irq
	[102056] ibmvnic 30000003 env3: Replenished 8 pools
	Kernel attempted to read user page (10) - exploit attempt? (uid: 0)
	BUG: Kernel NULL pointer dereference on read at 0x00000010
	Faulting instruction address: 0xc000000000a3c840
	Oops: Kernel access of bad area, sig: 11 [#1]
	LE PAGE_SIZE=64K MMU=Radix SMP NR_CPUS=2048 NUMA pSeries
	...
	CPU: 9 PID: 102056 Comm: kworker/9:2 Kdump: loaded Not tainted 5.16.0-rc5-autotest-g6441998e2e37 #1
	Workqueue: events_long __ibmvnic_reset [ibmvnic]
	NIP:  c000000000a3c840 LR: c0080000029b5378 CTR: c000000000a3c820
	REGS: c0000000548e37e…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2024-2106</guid>
    </item>
    <item>
      <title>SUSE-SU-2024:3190-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2024:3190-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-2024:3190-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-48871</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-48871</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 91 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: tty: serial: qcom-geni-serial: fix slab-out-of-bounds on RX FIFO buffer Driver&amp;#39;s probe allocates memory for RX FIFO (port-&amp;gt;rx_fifo) based on default RX FIFO depth, e.g. 16.  Later during serial startup the qcom_geni_serial_port_setup() updates the RX FIFO depth (port-&amp;gt;rx_fifo_depth) to match real device capabilities, e.g. to 32. The RX UART handle code will read &amp;#34;port-&amp;gt;rx_fifo_depth&amp;#34; number of words into &amp;#34;port-&amp;gt;rx_fifo&amp;#34; buffer, thus exceeding the bounds.  This can be observed in certain configurations with Qualcomm Bluetooth HCI UART device and KASAN:   Bluetooth: hci0: QCA Product ID   :0x00000010   Bluetooth: hci0: QCA SOC Version  :0x400a0200   Bluetooth: hci0: QCA ROM Version  :0x00000200   Bluetooth: hci0: QCA Patch Version:0x00000d2b   Bluetooth: hci0: QCA controller version 0x02000200   Bluetooth: hci0: QCA Downloading qca/htbtfw20.tlv   bluetooth hci0: Direct firmware load for qca/htbtfw20.tlv failed with error -2   Bluetooth: hci0: QCA Failed to request file: qca/htbtfw20.tlv (-2)   Bluetooth: hci0: QCA Failed to download patch (-2)   ==================================================================   BUG: KASAN: slab-out-of-bounds in handle_rx_uart+0xa8/0x18c   Write of size 4 at addr ffff279347d578c0 by task swapper/0/0   CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.1.0-rt5-00350-gb2450b7e00be-dirty #26   Hardware name: Qualcomm Technologies, Inc. Robotics RB5 (DT)   Call trace:    dump_backtrace.…&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 91 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: tty: serial: qcom-geni-serial: fix slab-out-of-bounds on RX FIFO buffer Driver&amp;#39;s probe allocates memory for RX FIFO (port-&amp;gt;rx_fifo) based on default RX FIFO depth, e.g. 16.  Later during serial startup the qcom_geni_serial_port_setup() updates the RX FIFO depth (port-&amp;gt;rx_fifo_depth) to match real device capabilities, e.g. to 32. The RX UART handle code will read &amp;#34;port-&amp;gt;rx_fifo_depth&amp;#34; number of words into &amp;#34;port-&amp;gt;rx_fifo&amp;#34; buffer, thus exceeding the bounds.  This can be observed in certain configurations with Qualcomm Bluetooth HCI UART device and KASAN:   Bluetooth: hci0: QCA Product ID   :0x00000010   Bluetooth: hci0: QCA SOC Version  :0x400a0200   Bluetooth: hci0: QCA ROM Version  :0x00000200   Bluetooth: hci0: QCA Patch Version:0x00000d2b   Bluetooth: hci0: QCA controller version 0x02000200   Bluetooth: hci0: QCA Downloading qca/htbtfw20.tlv   bluetooth hci0: Direct firmware load for qca/htbtfw20.tlv failed with error -2   Bluetooth: hci0: QCA Failed to request file: qca/htbtfw20.tlv (-2)   Bluetooth: hci0: QCA Failed to download patch (-2)   ==================================================================   BUG: KASAN: slab-out-of-bounds in handle_rx_uart+0xa8/0x18c   Write of size 4 at addr ffff279347d578c0 by task swapper/0/0   CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.1.0-rt5-00350-gb2450b7e00be-dirty #26   Hardware name: Qualcomm Technologies, Inc. Robotics RB5 (DT)   Call trace:    dump_backtrace.…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-48871</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-1888 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1888</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen oder einen unspezifischen Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen oder einen unspezifischen Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1888</guid>
    </item>
  </channel>
</rss>
