<?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>Thu, 08 Oct 2026 19:18:24 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-38300 — crypto: sun8i-ce-cipher - fix error handling in sun8i_ce_cipher_prepare()</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2025-38300</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;crypto: sun8i-ce-cipher - fix error handling in sun8i_ce_cipher_prepare()&lt;/p&gt;
&lt;p&gt;Fix two DMA cleanup issues on the error path in sun8i_ce_cipher_prepare():&lt;/p&gt;
&lt;p&gt;1] If dma_map_sg() fails for areq-&amp;gt;dst, the device driver would try to free
   DMA memory it has not allocated in the first place. To fix this, on the
   &amp;#34;theend_sgs&amp;#34; error path, call dma unmap only if the corresponding dma
   map was successful.&lt;/p&gt;
&lt;p&gt;2] If the dma_map_single() call for the IV fails, the device driver would
   try to free an invalid DMA memory address on the &amp;#34;theend_iv&amp;#34; path:
   ------------[ cut here ]------------
   DMA-API: sun8i-ce 1904000.crypto: device driver tries to free an invalid DMA memory address
   WARNING: CPU: 2 PID: 69 at kernel/dma/debug.c:968 check_unmap+0x123c/0x1b90
   Modules linked in: skcipher_example(O+)
   CPU: 2 UID: 0 PID: 69 Comm: 1904000.crypto- Tainted: G           O        6.15.0-rc3+ #24 PREEMPT
   Tainted: [O]=OOT_MODULE
   Hardware name: OrangePi Zero2 (DT)
   pc : check_unmap+0x123c/0x1b90
   lr : check_unmap+0x123c/0x1b90
   ...
   Call trace:
    check_unmap+0x123c/0x1b90 (P)
    debug_dma_unmap_page+0xac/0xc0
    dma_unmap_page_attrs+0x1f4/0x5fc
    sun8i_ce_cipher_do_one+0x1bd4/0x1f40
    crypto_pump_work+0x334/0x6e0
    kthread_worker_fn+0x21c/0x438
    kthread+0x374/0x664
    ret_from_fork+0x10/0x20
   ---[ end trace 0000000000000000 ]---&lt;/p&gt;
&lt;p&gt;To fix this, check for !dma_mapping_error() before calling
dma_unma…&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;crypto: sun8i-ce-cipher - fix error handling in sun8i_ce_cipher_prepare()&lt;/p&gt;
&lt;p&gt;Fix two DMA cleanup issues on the error path in sun8i_ce_cipher_prepare():&lt;/p&gt;
&lt;p&gt;1] If dma_map_sg() fails for areq-&amp;gt;dst, the device driver would try to free
   DMA memory it has not allocated in the first place. To fix this, on the
   &amp;#34;theend_sgs&amp;#34; error path, call dma unmap only if the corresponding dma
   map was successful.&lt;/p&gt;
&lt;p&gt;2] If the dma_map_single() call for the IV fails, the device driver would
   try to free an invalid DMA memory address on the &amp;#34;theend_iv&amp;#34; path:
   ------------[ cut here ]------------
   DMA-API: sun8i-ce 1904000.crypto: device driver tries to free an invalid DMA memory address
   WARNING: CPU: 2 PID: 69 at kernel/dma/debug.c:968 check_unmap+0x123c/0x1b90
   Modules linked in: skcipher_example(O+)
   CPU: 2 UID: 0 PID: 69 Comm: 1904000.crypto- Tainted: G           O        6.15.0-rc3+ #24 PREEMPT
   Tainted: [O]=OOT_MODULE
   Hardware name: OrangePi Zero2 (DT)
   pc : check_unmap+0x123c/0x1b90
   lr : check_unmap+0x123c/0x1b90
   ...
   Call trace:
    check_unmap+0x123c/0x1b90 (P)
    debug_dma_unmap_page+0xac/0xc0
    dma_unmap_page_attrs+0x1f4/0x5fc
    sun8i_ce_cipher_do_one+0x1bd4/0x1f40
    crypto_pump_work+0x334/0x6e0
    kthread_worker_fn+0x21c/0x438
    kthread+0x374/0x664
    ret_from_fork+0x10/0x20
   ---[ end trace 0000000000000000 ]---&lt;/p&gt;
&lt;p&gt;To fix this, check for !dma_mapping_error() before calling
dma_unma…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2025-38300</guid>
    </item>
  </channel>
</rss>
