<?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://db.gcve.eu</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>Thu, 19 Nov 2026 18:23:38 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-38042 — dmaengine: ti: k3-udma-glue: Drop skip_fdq argument from k3_udma_glue_reset_rx_chn</title>
      <link>https://db.gcve.eu/vuln/cve-2025-38042</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;dmaengine: ti: k3-udma-glue: Drop skip_fdq argument from k3_udma_glue_reset_rx_chn&lt;/p&gt;
&lt;p&gt;The user of k3_udma_glue_reset_rx_chn() e.g. ti_am65_cpsw_nuss can
run on multiple platforms having different DMA architectures.
On some platforms there can be one FDQ for all flows in the RX channel
while for others there is a separate FDQ for each flow in the RX channel.&lt;/p&gt;
&lt;p&gt;So far we have been relying on the skip_fdq argument of
k3_udma_glue_reset_rx_chn().&lt;/p&gt;
&lt;p&gt;Instead of relying on the user to provide this information, infer it
based on DMA architecture during k3_udma_glue_request_rx_chn() and save it
in an internal flag &amp;#39;single_fdq&amp;#39;. Use that flag at
k3_udma_glue_reset_rx_chn() to deicide if the FDQ needs
to be cleared for every flow or just for flow 0.&lt;/p&gt;
&lt;p&gt;Fixes the below issue on ti_am65_cpsw_nuss driver on AM62-SK.&lt;/p&gt;
&lt;p&gt;&amp;gt; ip link set eth1 down
&amp;gt; ip link set eth0 down
&amp;gt; ethtool -L eth0 rx 8
&amp;gt; ip link set eth0 up
&amp;gt; modprobe -r ti_am65_cpsw_nuss&lt;/p&gt;
&lt;p&gt;[  103.045726] ------------[ cut here ]------------
[  103.050505] k3_knav_desc_pool size 512000 != avail 64000
[  103.050703] WARNING: CPU: 1 PID: 450 at drivers/net/ethernet/ti/k3-cppi-desc-pool.c:33 k3_cppi_desc_pool_destroy+0xa0/0xa8 [k3_cppi_desc_pool]
[  103.068810] Modules linked in: ti_am65_cpsw_nuss(-) k3_cppi_desc_pool snd_soc_hdmi_codec crct10dif_ce snd_soc_simple_card snd_soc_simple_card_utils display_connector rtc_ti_k3 k3_j72xx_bandgap tidss drm_client_lib snd_soc_davinci_mcas…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;dmaengine: ti: k3-udma-glue: Drop skip_fdq argument from k3_udma_glue_reset_rx_chn&lt;/p&gt;
&lt;p&gt;The user of k3_udma_glue_reset_rx_chn() e.g. ti_am65_cpsw_nuss can
run on multiple platforms having different DMA architectures.
On some platforms there can be one FDQ for all flows in the RX channel
while for others there is a separate FDQ for each flow in the RX channel.&lt;/p&gt;
&lt;p&gt;So far we have been relying on the skip_fdq argument of
k3_udma_glue_reset_rx_chn().&lt;/p&gt;
&lt;p&gt;Instead of relying on the user to provide this information, infer it
based on DMA architecture during k3_udma_glue_request_rx_chn() and save it
in an internal flag &amp;#39;single_fdq&amp;#39;. Use that flag at
k3_udma_glue_reset_rx_chn() to deicide if the FDQ needs
to be cleared for every flow or just for flow 0.&lt;/p&gt;
&lt;p&gt;Fixes the below issue on ti_am65_cpsw_nuss driver on AM62-SK.&lt;/p&gt;
&lt;p&gt;&amp;gt; ip link set eth1 down
&amp;gt; ip link set eth0 down
&amp;gt; ethtool -L eth0 rx 8
&amp;gt; ip link set eth0 up
&amp;gt; modprobe -r ti_am65_cpsw_nuss&lt;/p&gt;
&lt;p&gt;[  103.045726] ------------[ cut here ]------------
[  103.050505] k3_knav_desc_pool size 512000 != avail 64000
[  103.050703] WARNING: CPU: 1 PID: 450 at drivers/net/ethernet/ti/k3-cppi-desc-pool.c:33 k3_cppi_desc_pool_destroy+0xa0/0xa8 [k3_cppi_desc_pool]
[  103.068810] Modules linked in: ti_am65_cpsw_nuss(-) k3_cppi_desc_pool snd_soc_hdmi_codec crct10dif_ce snd_soc_simple_card snd_soc_simple_card_utils display_connector rtc_ti_k3 k3_j72xx_bandgap tidss drm_client_lib snd_soc_davinci_mcas…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2025-38042</guid>
    </item>
    <item>
      <title>USN-7769-1 — linux, linux-aws, linux-gcp, linux-gcp-6.14, linux-oracle, linux-realtime vulnerabilities</title>
      <link>https://db.gcve.eu/vuln/usn-7769-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-gcp-6.14&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - ARM64 architecture;
  - PowerPC architecture;
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - ACPI drivers;
  - Android drivers;
  - Bluetooth drivers;
  - Bus devices;
  - Clock framework and drivers;
  - CPU frequency scaling framework;
  - Hardware crypto device drivers;
  - DMA engine subsystem;
  - EDAC drivers;
  - Arm Firmware Framework for ARMv8-A(FFA);
  - FPGA Framework;
  - GPIO subsystem;
  - GPU drivers;
  - HID subsystem;
  - Hardware monitoring drivers;
  - HW tracing;
  - InfiniBand drivers;
  - IOMMU subsystem;
  - Multiple devices driver;
  - Media drivers;
  - VMware VMCI Driver;
  - MTD block device drivers;
  - Network drivers;
  - Mellanox network drivers;
  - STMicroelectronics network drivers;
  - NVDIMM (Non-Volatile Memory Device) drivers;
  - NVME drivers;
  - NVMEM (Non Volatile Memory) drivers;
  - PCI subsystem;
  - Amlogic Meson DDR PMU;
  - NI-700 PMU driver;
  - PHY drivers;
  - Pin controllers subsystem;
  - x86 platform drivers;
  - PTP clock framework;
  - SCSI subsystem;
  - ASPEED SoC drivers;
  - SPI subsystem;
  - TCM subsystem;
  - Thunderbolt and USB4 drivers;
  - TTY drivers;
  - UFS subsystem;
  - USB core drivers;
  - USB Gadget drivers;
  - Renesas USBHS Controller drivers;
  - USB Type-C Port Controller Manager driver;…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-gcp-6.14&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - ARM64 architecture;
  - PowerPC architecture;
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - ACPI drivers;
  - Android drivers;
  - Bluetooth drivers;
  - Bus devices;
  - Clock framework and drivers;
  - CPU frequency scaling framework;
  - Hardware crypto device drivers;
  - DMA engine subsystem;
  - EDAC drivers;
  - Arm Firmware Framework for ARMv8-A(FFA);
  - FPGA Framework;
  - GPIO subsystem;
  - GPU drivers;
  - HID subsystem;
  - Hardware monitoring drivers;
  - HW tracing;
  - InfiniBand drivers;
  - IOMMU subsystem;
  - Multiple devices driver;
  - Media drivers;
  - VMware VMCI Driver;
  - MTD block device drivers;
  - Network drivers;
  - Mellanox network drivers;
  - STMicroelectronics network drivers;
  - NVDIMM (Non-Volatile Memory Device) drivers;
  - NVME drivers;
  - NVMEM (Non Volatile Memory) drivers;
  - PCI subsystem;
  - Amlogic Meson DDR PMU;
  - NI-700 PMU driver;
  - PHY drivers;
  - Pin controllers subsystem;
  - x86 platform drivers;
  - PTP clock framework;
  - SCSI subsystem;
  - ASPEED SoC drivers;
  - SPI subsystem;
  - TCM subsystem;
  - Thunderbolt and USB4 drivers;
  - TTY drivers;
  - UFS subsystem;
  - USB core drivers;
  - USB Gadget drivers;
  - Renesas USBHS Controller drivers;
  - USB Type-C Port Controller Manager driver;…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/usn-7769-1</guid>
    </item>
  </channel>
</rss>
