<?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>Fri, 16 Oct 2026 08:50:45 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-26627 — scsi: core: Move scsi_host_busy() out of host lock for waking up EH handler</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2024-26627</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;scsi: core: Move scsi_host_busy() out of host lock for waking up EH handler&lt;/p&gt;
&lt;p&gt;Inside scsi_eh_wakeup(), scsi_host_busy() is called &amp;amp; checked with host
lock every time for deciding if error handler kthread needs to be waken up.&lt;/p&gt;
&lt;p&gt;This can be too heavy in case of recovery, such as:&lt;/p&gt;
&lt;p&gt;- N hardware queues&lt;/p&gt;
&lt;p&gt;- queue depth is M for each hardware queue&lt;/p&gt;
&lt;p&gt;- each scsi_host_busy() iterates over (N * M) tag/requests&lt;/p&gt;
&lt;p&gt;If recovery is triggered in case that all requests are in-flight, each
scsi_eh_wakeup() is strictly serialized, when scsi_eh_wakeup() is called
for the last in-flight request, scsi_host_busy() has been run for (N * M -
1) times, and request has been iterated for (N*M - 1) * (N * M) times.&lt;/p&gt;
&lt;p&gt;If both N and M are big enough, hard lockup can be triggered on acquiring
host lock, and it is observed on mpi3mr(128 hw queues, queue depth 8169).&lt;/p&gt;
&lt;p&gt;Fix the issue by calling scsi_host_busy() outside the host lock. We don&amp;#39;t
need the host lock for getting busy count because host the lock never
covers that.&lt;/p&gt;
&lt;p&gt;[mkp: Drop unnecessary &amp;#39;busy&amp;#39; variables pointed out by Bart]&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;scsi: core: Move scsi_host_busy() out of host lock for waking up EH handler&lt;/p&gt;
&lt;p&gt;Inside scsi_eh_wakeup(), scsi_host_busy() is called &amp;amp; checked with host
lock every time for deciding if error handler kthread needs to be waken up.&lt;/p&gt;
&lt;p&gt;This can be too heavy in case of recovery, such as:&lt;/p&gt;
&lt;p&gt;- N hardware queues&lt;/p&gt;
&lt;p&gt;- queue depth is M for each hardware queue&lt;/p&gt;
&lt;p&gt;- each scsi_host_busy() iterates over (N * M) tag/requests&lt;/p&gt;
&lt;p&gt;If recovery is triggered in case that all requests are in-flight, each
scsi_eh_wakeup() is strictly serialized, when scsi_eh_wakeup() is called
for the last in-flight request, scsi_host_busy() has been run for (N * M -
1) times, and request has been iterated for (N*M - 1) * (N * M) times.&lt;/p&gt;
&lt;p&gt;If both N and M are big enough, hard lockup can be triggered on acquiring
host lock, and it is observed on mpi3mr(128 hw queues, queue depth 8169).&lt;/p&gt;
&lt;p&gt;Fix the issue by calling scsi_host_busy() outside the host lock. We don&amp;#39;t
need the host lock for getting busy count because host the lock never
covers that.&lt;/p&gt;
&lt;p&gt;[mkp: Drop unnecessary &amp;#39;busy&amp;#39; variables pointed out by Bart]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2024-26627</guid>
    </item>
    <item>
      <title>USN-6688-1 — linux-oem-6.1 vulnerabilities</title>
      <link>https://cve.radiocsirt.org/vuln/usn-6688-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:22.04:LTS: linux-oem-6.1&lt;/p&gt;
&lt;p&gt;Pratyush Yadav discovered that the Xen network backend implementation in
the Linux kernel did not properly handle zero length data request, leading
to a null pointer dereference vulnerability. An attacker in a guest VM
could possibly use this to cause a denial of service (host domain crash).
(CVE-2023-46838)&lt;/p&gt;
&lt;p&gt;It was discovered that the Habana&amp;#39;s AI Processors driver in the Linux
kernel did not properly initialize certain data structures before passing
them to user space. A local attacker could use this to expose sensitive
information (kernel memory). (CVE-2023-50431)&lt;/p&gt;
&lt;p&gt;Murray McAllister discovered that the VMware Virtual GPU DRM driver in the
Linux kernel did not properly handle memory objects when storing surfaces,
leading to a use-after-free vulnerability. A local attacker in a guest VM
could use this to cause a denial of service (system crash) or possibly
execute arbitrary code. (CVE-2023-5633)&lt;/p&gt;
&lt;p&gt;It was discovered that the CIFS network file system implementation in the
Linux kernel did not properly validate certain SMB messages, leading to an
out-of-bounds read vulnerability. An attacker could use this to cause a
denial of service (system crash) or possibly expose sensitive information.
(CVE-2023-6610)&lt;/p&gt;
&lt;p&gt;It was discovered that the VirtIO subsystem in the Linux kernel did not
properly initialize memory in some situations. A local attacker could use
this to possibly expose sensitive information (kernel memory).
(CVE-2024-0340)&lt;/p&gt;
&lt;p&gt;Lonial Con discovered that the netfilter subsystem…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:22.04:LTS: linux-oem-6.1&lt;/p&gt;
&lt;p&gt;Pratyush Yadav discovered that the Xen network backend implementation in
the Linux kernel did not properly handle zero length data request, leading
to a null pointer dereference vulnerability. An attacker in a guest VM
could possibly use this to cause a denial of service (host domain crash).
(CVE-2023-46838)&lt;/p&gt;
&lt;p&gt;It was discovered that the Habana&amp;#39;s AI Processors driver in the Linux
kernel did not properly initialize certain data structures before passing
them to user space. A local attacker could use this to expose sensitive
information (kernel memory). (CVE-2023-50431)&lt;/p&gt;
&lt;p&gt;Murray McAllister discovered that the VMware Virtual GPU DRM driver in the
Linux kernel did not properly handle memory objects when storing surfaces,
leading to a use-after-free vulnerability. A local attacker in a guest VM
could use this to cause a denial of service (system crash) or possibly
execute arbitrary code. (CVE-2023-5633)&lt;/p&gt;
&lt;p&gt;It was discovered that the CIFS network file system implementation in the
Linux kernel did not properly validate certain SMB messages, leading to an
out-of-bounds read vulnerability. An attacker could use this to cause a
denial of service (system crash) or possibly expose sensitive information.
(CVE-2023-6610)&lt;/p&gt;
&lt;p&gt;It was discovered that the VirtIO subsystem in the Linux kernel did not
properly initialize memory in some situations. A local attacker could use
this to possibly expose sensitive information (kernel memory).
(CVE-2024-0340)&lt;/p&gt;
&lt;p&gt;Lonial Con discovered that the netfilter subsystem…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/usn-6688-1</guid>
    </item>
  </channel>
</rss>
