<?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 19:52:31 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-50005 — mac802154: Fix potential RCU dereference issue in mac802154_scan_worker</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-50005</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;mac802154: Fix potential RCU dereference issue in mac802154_scan_worker&lt;/p&gt;
&lt;p&gt;In the `mac802154_scan_worker` function, the `scan_req-&amp;gt;type` field was
accessed after the RCU read-side critical section was unlocked. According
to RCU usage rules, this is illegal and can lead to unpredictable
behavior, such as accessing memory that has been updated or causing
use-after-free issues.&lt;/p&gt;
&lt;p&gt;This possible bug was identified using a static analysis tool developed
by myself, specifically designed to detect RCU-related issues.&lt;/p&gt;
&lt;p&gt;To address this, the `scan_req-&amp;gt;type` value is now stored in a local
variable `scan_req_type` while still within the RCU read-side critical
section. The `scan_req_type` is then used after the RCU lock is released,
ensuring that the type value is safely accessed without violating RCU
rules.&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;mac802154: Fix potential RCU dereference issue in mac802154_scan_worker&lt;/p&gt;
&lt;p&gt;In the `mac802154_scan_worker` function, the `scan_req-&amp;gt;type` field was
accessed after the RCU read-side critical section was unlocked. According
to RCU usage rules, this is illegal and can lead to unpredictable
behavior, such as accessing memory that has been updated or causing
use-after-free issues.&lt;/p&gt;
&lt;p&gt;This possible bug was identified using a static analysis tool developed
by myself, specifically designed to detect RCU-related issues.&lt;/p&gt;
&lt;p&gt;To address this, the `scan_req-&amp;gt;type` value is now stored in a local
variable `scan_req_type` while still within the RCU read-side critical
section. The `scan_req_type` is then used after the RCU lock is released,
ensuring that the type value is safely accessed without violating RCU
rules.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-50005</guid>
    </item>
  </channel>
</rss>
