<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
  <title>CVE Daily – Fairphone</title>
  <link>https://cvedaily.com/pages/tags/fairphone.html</link>
  <atom:link href="https://cvedaily.com/feed-tags/fairphone.xml" rel="self" type="application/rss+xml"/>
  <description>CVE Daily – Fairphone</description>
  <language>en</language>
  <lastBuildDate>Wed, 03 Jun 2026 21:27:05 +0000</lastBuildDate>
  <item>
    <title>[Medium] CVE-2025-39923 – In the Linux kernel, the following vulnerability has been resolved:

dmaengine: ...</title>
    <link>https://nvd.nist.gov/vuln/detail/CVE-2025-39923</link>
    <guid isPermaLink="true">https://nvd.nist.gov/vuln/detail/CVE-2025-39923</guid>
    <pubDate>Wed, 01 Oct 2025 08:15:35 +0000</pubDate>
    <description>
<![CDATA[
  <p><strong><span class="badge risk medium">Medium</span> CVE-2025-39923</strong></p>
  <p>In the Linux kernel, the following vulnerability has been resolved:  dmaengine: qcom: bam_dma: Fix DT error handling for num-channels/ees  When we don't have a clock specified in the device tree, we have no way to ensure the BAM is on. This is often the case for remotely-controlled or remotely-powered BAM instances. In this case, we need to read num-channels from the DT to have all the necessary…</p>
  <p><strong>CVSS:</strong> 5.5 · <strong>CWE:</strong> N/A</p>
  <p><a href="https://nvd.nist.gov/vuln/detail/CVE-2025-39923">View on NVD</a></p>
]]>
    </description>
  </item>
</channel>
</rss>
