<?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>Mon, 28 Sep 2026 10:27:21 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-98160</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-98160</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;staging: rtl8723bs: fix mismatched free of HalData in rtw_sdio_if1_init()&lt;/p&gt;
&lt;p&gt;padapter-&amp;gt;HalData is allocated via vzalloc(), but incorrectly freed
using kfree() in the rtw_sdio_if1_init() error path. Using kfree() to
release this vmalloc-backed buffer can lead to memory corruption.&lt;/p&gt;
&lt;p&gt;Use rtw_hal_data_deinit() to pair the free correctly and free
HalData with vfree().&lt;/p&gt;
&lt;p&gt;The bug was first flagged by an experimental static analysis tool we
are developing for kernel memory-management bugs. Manual inspection
confirms that the issue is still present in current mainline.&lt;/p&gt;
&lt;p&gt;An x86_64 allyesconfig build showed no new warnings. As we do not have
suitable RTL8723BS SDIO hardware to test with, no runtime testing was
able to be performed.&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;staging: rtl8723bs: fix mismatched free of HalData in rtw_sdio_if1_init()&lt;/p&gt;
&lt;p&gt;padapter-&amp;gt;HalData is allocated via vzalloc(), but incorrectly freed
using kfree() in the rtw_sdio_if1_init() error path. Using kfree() to
release this vmalloc-backed buffer can lead to memory corruption.&lt;/p&gt;
&lt;p&gt;Use rtw_hal_data_deinit() to pair the free correctly and free
HalData with vfree().&lt;/p&gt;
&lt;p&gt;The bug was first flagged by an experimental static analysis tool we
are developing for kernel memory-management bugs. Manual inspection
confirms that the issue is still present in current mainline.&lt;/p&gt;
&lt;p&gt;An x86_64 allyesconfig build showed no new warnings. As we do not have
suitable RTL8723BS SDIO hardware to test with, no runtime testing was
able to be performed.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-98160</guid>
    </item>
    <item>
      <title>GHSA-4hh4-86px-498m</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-4hh4-86px-498m</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;staging: rtl8723bs: fix mismatched free of HalData in rtw_sdio_if1_init()&lt;/p&gt;
&lt;p&gt;padapter-&amp;gt;HalData is allocated via vzalloc(), but incorrectly freed
using kfree() in the rtw_sdio_if1_init() error path. Using kfree() to
release this vmalloc-backed buffer can lead to memory corruption.&lt;/p&gt;
&lt;p&gt;Use rtw_hal_data_deinit() to pair the free correctly and free
HalData with vfree().&lt;/p&gt;
&lt;p&gt;The bug was first flagged by an experimental static analysis tool we
are developing for kernel memory-management bugs. Manual inspection
confirms that the issue is still present in current mainline.&lt;/p&gt;
&lt;p&gt;An x86_64 allyesconfig build showed no new warnings. As we do not have
suitable RTL8723BS SDIO hardware to test with, no runtime testing was
able to be performed.&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;staging: rtl8723bs: fix mismatched free of HalData in rtw_sdio_if1_init()&lt;/p&gt;
&lt;p&gt;padapter-&amp;gt;HalData is allocated via vzalloc(), but incorrectly freed
using kfree() in the rtw_sdio_if1_init() error path. Using kfree() to
release this vmalloc-backed buffer can lead to memory corruption.&lt;/p&gt;
&lt;p&gt;Use rtw_hal_data_deinit() to pair the free correctly and free
HalData with vfree().&lt;/p&gt;
&lt;p&gt;The bug was first flagged by an experimental static analysis tool we
are developing for kernel memory-management bugs. Manual inspection
confirms that the issue is still present in current mainline.&lt;/p&gt;
&lt;p&gt;An x86_64 allyesconfig build showed no new warnings. As we do not have
suitable RTL8723BS SDIO hardware to test with, no runtime testing was
able to be performed.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-4hh4-86px-498m</guid>
    </item>
  </channel>
</rss>
