<?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://cve.radiocsirt.org</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, 07 Oct 2026 11:45:54 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-42232 — libceph: fix race between delayed_work() and ceph_monc_stop()</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2024-42232</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;libceph: fix race between delayed_work() and ceph_monc_stop()&lt;/p&gt;
&lt;p&gt;The way the delayed work is handled in ceph_monc_stop() is prone to
races with mon_fault() and possibly also finish_hunting().  Both of
these can requeue the delayed work which wouldn&amp;#39;t be canceled by any of
the following code in case that happens after cancel_delayed_work_sync()
runs -- __close_session() doesn&amp;#39;t mess with the delayed work in order
to avoid interfering with the hunting interval logic.  This part was
missed in commit b5d91704f53e (&amp;#34;libceph: behave in mon_fault() if
cur_mon &amp;lt; 0&amp;#34;) and use-after-free can still ensue on monc and objects
that hang off of it, with monc-&amp;gt;auth and monc-&amp;gt;monmap being
particularly susceptible to quickly being reused.&lt;/p&gt;
&lt;p&gt;To fix this:&lt;/p&gt;
&lt;p&gt;- clear monc-&amp;gt;cur_mon and monc-&amp;gt;hunting as part of closing the session
  in ceph_monc_stop()
- bail from delayed_work() if monc-&amp;gt;cur_mon is cleared, similar to how
  it&amp;#39;s done in mon_fault() and finish_hunting() (based on monc-&amp;gt;hunting)
- call cancel_delayed_work_sync() after the session is closed&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;libceph: fix race between delayed_work() and ceph_monc_stop()&lt;/p&gt;
&lt;p&gt;The way the delayed work is handled in ceph_monc_stop() is prone to
races with mon_fault() and possibly also finish_hunting().  Both of
these can requeue the delayed work which wouldn&amp;#39;t be canceled by any of
the following code in case that happens after cancel_delayed_work_sync()
runs -- __close_session() doesn&amp;#39;t mess with the delayed work in order
to avoid interfering with the hunting interval logic.  This part was
missed in commit b5d91704f53e (&amp;#34;libceph: behave in mon_fault() if
cur_mon &amp;lt; 0&amp;#34;) and use-after-free can still ensue on monc and objects
that hang off of it, with monc-&amp;gt;auth and monc-&amp;gt;monmap being
particularly susceptible to quickly being reused.&lt;/p&gt;
&lt;p&gt;To fix this:&lt;/p&gt;
&lt;p&gt;- clear monc-&amp;gt;cur_mon and monc-&amp;gt;hunting as part of closing the session
  in ceph_monc_stop()
- bail from delayed_work() if monc-&amp;gt;cur_mon is cleared, similar to how
  it&amp;#39;s done in mon_fault() and finish_hunting() (based on monc-&amp;gt;hunting)
- call cancel_delayed_work_sync() after the session is closed&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2024-42232</guid>
    </item>
  </channel>
</rss>
