<?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://vulnerability.circl.lu</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>Sun, 04 Oct 2026 05:53:32 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-53315 — wifi: ath11k: Fix SKB corruption in REO destination ring</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2023-53315</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;wifi: ath11k: Fix SKB corruption in REO destination ring&lt;/p&gt;
&lt;p&gt;While running traffics for a long time, randomly an RX descriptor
filled with value &amp;#34;0&amp;#34; from REO destination ring is received.
This descriptor which is invalid causes the wrong SKB (SKB stored in
the IDR lookup with buffer id &amp;#34;0&amp;#34;) to be fetched which in turn
causes SKB memory corruption issue and the same leads to crash
after some time.&lt;/p&gt;
&lt;p&gt;Changed the start id for idr allocation to &amp;#34;1&amp;#34; and the buffer id &amp;#34;0&amp;#34;
is reserved for error validation. Introduced Sanity check to validate
the descriptor, before processing the SKB.&lt;/p&gt;
&lt;p&gt;Crash Signature :&lt;/p&gt;
&lt;p&gt;Unable to handle kernel paging request at virtual address 3f004900
PC points to &amp;#34;b15_dma_inv_range+0x30/0x50&amp;#34;
LR points to &amp;#34;dma_cache_maint_page+0x8c/0x128&amp;#34;.
The Backtrace obtained is as follows:
[&amp;lt;8031716c&amp;gt;] (b15_dma_inv_range) from [&amp;lt;80313a4c&amp;gt;] (dma_cache_maint_page+0x8c/0x128)
[&amp;lt;80313a4c&amp;gt;] (dma_cache_maint_page) from [&amp;lt;80313b90&amp;gt;] (__dma_page_dev_to_cpu+0x28/0xcc)
[&amp;lt;80313b90&amp;gt;] (__dma_page_dev_to_cpu) from [&amp;lt;7fb5dd68&amp;gt;] (ath11k_dp_process_rx+0x1e8/0x4a4 [ath11k])
[&amp;lt;7fb5dd68&amp;gt;] (ath11k_dp_process_rx [ath11k]) from [&amp;lt;7fb53c20&amp;gt;] (ath11k_dp_service_srng+0xb0/0x2ac [ath11k])
[&amp;lt;7fb53c20&amp;gt;] (ath11k_dp_service_srng [ath11k]) from [&amp;lt;7f67bba4&amp;gt;] (ath11k_pci_ext_grp_napi_poll+0x1c/0x78 [ath11k_pci])
[&amp;lt;7f67bba4&amp;gt;] (ath11k_pci_ext_grp_napi_poll [ath11k_pci]) from [&amp;lt;807d5cf4&amp;gt;] (__napi_poll+0x28/0xb8)
[&amp;lt;807d5cf4&amp;gt;] (__napi_poll) from [&amp;lt;80…&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;wifi: ath11k: Fix SKB corruption in REO destination ring&lt;/p&gt;
&lt;p&gt;While running traffics for a long time, randomly an RX descriptor
filled with value &amp;#34;0&amp;#34; from REO destination ring is received.
This descriptor which is invalid causes the wrong SKB (SKB stored in
the IDR lookup with buffer id &amp;#34;0&amp;#34;) to be fetched which in turn
causes SKB memory corruption issue and the same leads to crash
after some time.&lt;/p&gt;
&lt;p&gt;Changed the start id for idr allocation to &amp;#34;1&amp;#34; and the buffer id &amp;#34;0&amp;#34;
is reserved for error validation. Introduced Sanity check to validate
the descriptor, before processing the SKB.&lt;/p&gt;
&lt;p&gt;Crash Signature :&lt;/p&gt;
&lt;p&gt;Unable to handle kernel paging request at virtual address 3f004900
PC points to &amp;#34;b15_dma_inv_range+0x30/0x50&amp;#34;
LR points to &amp;#34;dma_cache_maint_page+0x8c/0x128&amp;#34;.
The Backtrace obtained is as follows:
[&amp;lt;8031716c&amp;gt;] (b15_dma_inv_range) from [&amp;lt;80313a4c&amp;gt;] (dma_cache_maint_page+0x8c/0x128)
[&amp;lt;80313a4c&amp;gt;] (dma_cache_maint_page) from [&amp;lt;80313b90&amp;gt;] (__dma_page_dev_to_cpu+0x28/0xcc)
[&amp;lt;80313b90&amp;gt;] (__dma_page_dev_to_cpu) from [&amp;lt;7fb5dd68&amp;gt;] (ath11k_dp_process_rx+0x1e8/0x4a4 [ath11k])
[&amp;lt;7fb5dd68&amp;gt;] (ath11k_dp_process_rx [ath11k]) from [&amp;lt;7fb53c20&amp;gt;] (ath11k_dp_service_srng+0xb0/0x2ac [ath11k])
[&amp;lt;7fb53c20&amp;gt;] (ath11k_dp_service_srng [ath11k]) from [&amp;lt;7f67bba4&amp;gt;] (ath11k_pci_ext_grp_napi_poll+0x1c/0x78 [ath11k_pci])
[&amp;lt;7f67bba4&amp;gt;] (ath11k_pci_ext_grp_napi_poll [ath11k_pci]) from [&amp;lt;807d5cf4&amp;gt;] (__napi_poll+0x28/0xb8)
[&amp;lt;807d5cf4&amp;gt;] (__napi_poll) from [&amp;lt;80…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2023-53315</guid>
    </item>
  </channel>
</rss>
