<?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>Tue, 29 Sep 2026 11:29:04 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-53529 — wifi: rtw88: Fix memory leak in rtw88_usb</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2023-53529</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: rtw88: Fix memory leak in rtw88_usb&lt;/p&gt;
&lt;p&gt;Kmemleak shows the following leak arising from routine in the usb
probe routine:&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff895cb29bba00 (size 512):
  comm &amp;#34;(udev-worker)&amp;#34;, pid 534, jiffies 4294903932 (age 102751.088s)
  hex dump (first 32 bytes):
    77 30 30 30 00 00 00 00 02 2f 2d 2b 30 00 00 00  w000...../-+0...
    02 00 2a 28 00 00 00 00 ff 55 ff ff ff 00 00 00  ..*(.....U......
  backtrace:
    [&amp;lt;ffffffff9265fa36&amp;gt;] kmalloc_trace+0x26/0x90
    [&amp;lt;ffffffffc17eec41&amp;gt;] rtw_usb_probe+0x2f1/0x680 [rtw_usb]
    [&amp;lt;ffffffffc03e19fd&amp;gt;] usb_probe_interface+0xdd/0x2e0 [usbcore]
    [&amp;lt;ffffffff92b4f2fe&amp;gt;] really_probe+0x18e/0x3d0
    [&amp;lt;ffffffff92b4f5b8&amp;gt;] __driver_probe_device+0x78/0x160
    [&amp;lt;ffffffff92b4f6bf&amp;gt;] driver_probe_device+0x1f/0x90
    [&amp;lt;ffffffff92b4f8df&amp;gt;] __driver_attach+0xbf/0x1b0
    [&amp;lt;ffffffff92b4d350&amp;gt;] bus_for_each_dev+0x70/0xc0
    [&amp;lt;ffffffff92b4e51e&amp;gt;] bus_add_driver+0x10e/0x210
    [&amp;lt;ffffffff92b50935&amp;gt;] driver_register+0x55/0xf0
    [&amp;lt;ffffffffc03e0708&amp;gt;] usb_register_driver+0x88/0x140 [usbcore]
    [&amp;lt;ffffffff92401153&amp;gt;] do_one_initcall+0x43/0x210
    [&amp;lt;ffffffff9254f42a&amp;gt;] do_init_module+0x4a/0x200
    [&amp;lt;ffffffff92551d1c&amp;gt;] __do_sys_finit_module+0xac/0x120
    [&amp;lt;ffffffff92ee6626&amp;gt;] do_syscall_64+0x56/0x80
    [&amp;lt;ffffffff9300006a&amp;gt;] entry_SYSCALL_64_after_hwframe+0x46/0xb0&lt;/p&gt;
&lt;p&gt;The leak was verified to be real by unloading the driver, which resulted
in a dangling pointer to the allocation.…&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: rtw88: Fix memory leak in rtw88_usb&lt;/p&gt;
&lt;p&gt;Kmemleak shows the following leak arising from routine in the usb
probe routine:&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff895cb29bba00 (size 512):
  comm &amp;#34;(udev-worker)&amp;#34;, pid 534, jiffies 4294903932 (age 102751.088s)
  hex dump (first 32 bytes):
    77 30 30 30 00 00 00 00 02 2f 2d 2b 30 00 00 00  w000...../-+0...
    02 00 2a 28 00 00 00 00 ff 55 ff ff ff 00 00 00  ..*(.....U......
  backtrace:
    [&amp;lt;ffffffff9265fa36&amp;gt;] kmalloc_trace+0x26/0x90
    [&amp;lt;ffffffffc17eec41&amp;gt;] rtw_usb_probe+0x2f1/0x680 [rtw_usb]
    [&amp;lt;ffffffffc03e19fd&amp;gt;] usb_probe_interface+0xdd/0x2e0 [usbcore]
    [&amp;lt;ffffffff92b4f2fe&amp;gt;] really_probe+0x18e/0x3d0
    [&amp;lt;ffffffff92b4f5b8&amp;gt;] __driver_probe_device+0x78/0x160
    [&amp;lt;ffffffff92b4f6bf&amp;gt;] driver_probe_device+0x1f/0x90
    [&amp;lt;ffffffff92b4f8df&amp;gt;] __driver_attach+0xbf/0x1b0
    [&amp;lt;ffffffff92b4d350&amp;gt;] bus_for_each_dev+0x70/0xc0
    [&amp;lt;ffffffff92b4e51e&amp;gt;] bus_add_driver+0x10e/0x210
    [&amp;lt;ffffffff92b50935&amp;gt;] driver_register+0x55/0xf0
    [&amp;lt;ffffffffc03e0708&amp;gt;] usb_register_driver+0x88/0x140 [usbcore]
    [&amp;lt;ffffffff92401153&amp;gt;] do_one_initcall+0x43/0x210
    [&amp;lt;ffffffff9254f42a&amp;gt;] do_init_module+0x4a/0x200
    [&amp;lt;ffffffff92551d1c&amp;gt;] __do_sys_finit_module+0xac/0x120
    [&amp;lt;ffffffff92ee6626&amp;gt;] do_syscall_64+0x56/0x80
    [&amp;lt;ffffffff9300006a&amp;gt;] entry_SYSCALL_64_after_hwframe+0x46/0xb0&lt;/p&gt;
&lt;p&gt;The leak was verified to be real by unloading the driver, which resulted
in a dangling pointer to the allocation.…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2023-53529</guid>
    </item>
  </channel>
</rss>
