<?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>Wed, 30 Sep 2026 01:15:09 +0000</lastBuildDate>
    <item>
      <title>RUSTSEC-2025-0142 — Segmentation fault and invalid memory read in `mnl::cb_run`</title>
      <link>https://vulnerability.circl.lu/vuln/rustsec-2025-0142</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: mnl&lt;/p&gt;
&lt;p&gt;The function `mnl::cb_run` is marked as safe but exhibits unsound behavior when processing malformed Netlink message buffers.&lt;/p&gt;
&lt;p&gt;Passing a crafted byte slice to `mnl::cb_run` can trigger memory violations. The function does not sufficiently validate the input buffer structure before processing, leading to out-of-bounds reads.&lt;/p&gt;
&lt;p&gt;This vulnerability allows an attacker to cause a Denial of Service (segmentation fault) or potentially read unmapped memory by providing a malformed Netlink message.&lt;/p&gt;
&lt;p&gt;The underlying issue is a bug in `libmnl` where during validation `nlh-&amp;gt;nlmsg_len` is cast to an `int` and becomes negative if `nlmsg_len` is greater than `INT_MAX`. This causes the validation to succeed even if the buffer is too small for the message. This has been fixed in `libmnl` but still affects version 1.0.5.&lt;/p&gt;
&lt;p&gt;The issue in `mnl` was fixed in commit `cd51bdc` by checking the validity of netlink messages passed to `mnl::cb_run`.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: mnl&lt;/p&gt;
&lt;p&gt;The function `mnl::cb_run` is marked as safe but exhibits unsound behavior when processing malformed Netlink message buffers.&lt;/p&gt;
&lt;p&gt;Passing a crafted byte slice to `mnl::cb_run` can trigger memory violations. The function does not sufficiently validate the input buffer structure before processing, leading to out-of-bounds reads.&lt;/p&gt;
&lt;p&gt;This vulnerability allows an attacker to cause a Denial of Service (segmentation fault) or potentially read unmapped memory by providing a malformed Netlink message.&lt;/p&gt;
&lt;p&gt;The underlying issue is a bug in `libmnl` where during validation `nlh-&amp;gt;nlmsg_len` is cast to an `int` and becomes negative if `nlmsg_len` is greater than `INT_MAX`. This causes the validation to succeed even if the buffer is too small for the message. This has been fixed in `libmnl` but still affects version 1.0.5.&lt;/p&gt;
&lt;p&gt;The issue in `mnl` was fixed in commit `cd51bdc` by checking the validity of netlink messages passed to `mnl::cb_run`.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/rustsec-2025-0142</guid>
    </item>
  </channel>
</rss>
