<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-28T20:40:16.522924+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/CERTFR-2026-AVI-0108</id>
    <title>CERTFR-2026-AVI-0108 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
    <updated>2026-09-28T20:40:20.089087+00:00</updated>
    <content>CERTFR-2026-AVI-0108</content>
    <link href="https://vulnerability.circl.lu/vuln/CERTFR-2026-AVI-0108"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/fkie_cve-2022-50744</id>
    <title>fkie_cve-2022-50744</title>
    <updated>2026-09-28T20:40:20.089247+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>scsi: lpfc: Fix hard lockup when reading the rx_monitor from debugfs</p>
<p>During I/O and simultaneous cat of /sys/kernel/debug/lpfc/fnX/rx_monitor, a
hard lockup similar to the call trace below may occur.</p>
<p>The spin_lock_bh in lpfc_rx_monitor_report is not protecting from timer
interrupts as expected, so change the strength of the spin lock to _irq.</p>
<p>Kernel panic - not syncing: Hard LOCKUP
CPU: 3 PID: 110402 Comm: cat Kdump: loaded</p>
<p>exception RIP: native_queued_spin_lock_slowpath+91</p>
<p>[IRQ stack]
 native_queued_spin_lock_slowpath at ffffffffb814e30b
 _raw_spin_lock at ffffffffb89a667a
 lpfc_rx_monitor_record at ffffffffc0a73a36 [lpfc]
 lpfc_cmf_timer at ffffffffc0abbc67 [lpfc]
 __hrtimer_run_queues at ffffffffb8184250
 hrtimer_interrupt at ffffffffb8184ab0
 smp_apic_timer_interrupt at ffffffffb8a026ba
 apic_timer_interrupt at ffffffffb8a01c4f
[End of IRQ stack]</p>
<p>apic_timer_interrupt at ffffffffb8a01c4f
 lpfc_rx_monitor_report at ffffffffc0a73c80 [lpfc]
 lpfc_rx_monitor_read at ffffffffc0addde1 [lpfc]
 full_proxy_read at ffffffffb83e7fc3
 vfs_read at ffffffffb833fe71
 ksys_read at ffffffffb83402af
 do_syscall_64 at ffffffffb800430b
 entry_SYSCALL_64_after_hwframe at ffffffffb8a000ad</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/fkie_cve-2022-50744"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-jwx3-cmq4-vhrg</id>
    <title>GHSA-jwx3-cmq4-vhrg</title>
    <updated>2026-09-28T20:40:20.089428+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>scsi: lpfc: Fix hard lockup when reading the rx_monitor from debugfs</p>
<p>During I/O and simultaneous cat of /sys/kernel/debug/lpfc/fnX/rx_monitor, a
hard lockup similar to the call trace below may occur.</p>
<p>The spin_lock_bh in lpfc_rx_monitor_report is not protecting from timer
interrupts as expected, so change the strength of the spin lock to _irq.</p>
<p>Kernel panic - not syncing: Hard LOCKUP
CPU: 3 PID: 110402 Comm: cat Kdump: loaded</p>
<p>exception RIP: native_queued_spin_lock_slowpath+91</p>
<p>[IRQ stack]
 native_queued_spin_lock_slowpath at ffffffffb814e30b
 _raw_spin_lock at ffffffffb89a667a
 lpfc_rx_monitor_record at ffffffffc0a73a36 [lpfc]
 lpfc_cmf_timer at ffffffffc0abbc67 [lpfc]
 __hrtimer_run_queues at ffffffffb8184250
 hrtimer_interrupt at ffffffffb8184ab0
 smp_apic_timer_interrupt at ffffffffb8a026ba
 apic_timer_interrupt at ffffffffb8a01c4f
[End of IRQ stack]</p>
<p>apic_timer_interrupt at ffffffffb8a01c4f
 lpfc_rx_monitor_report at ffffffffc0a73c80 [lpfc]
 lpfc_rx_monitor_read at ffffffffc0addde1 [lpfc]
 full_proxy_read at ffffffffb83e7fc3
 vfs_read at ffffffffb833fe71
 ksys_read at ffffffffb83402af
 do_syscall_64 at ffffffffb800430b
 entry_SYSCALL_64_after_hwframe at ffffffffb8a000ad</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-jwx3-cmq4-vhrg"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/rhsa-2023:2458</id>
    <title>RHSA-2023:2458 — security update for kernel</title>
    <updated>2026-09-28T20:40:20.089494+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>security update for kernel</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/rhsa-2023:2458"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/suse-su-2026:0263-1</id>
    <title>SUSE-SU-2026:0263-1 — Security update for the Linux Kernel</title>
    <updated>2026-09-28T20:40:20.090088+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Security update for the Linux Kernel</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/suse-su-2026:0263-1"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ubuntu-cve-2022-50744</id>
    <title>UBUNTU-CVE-2022-50744</title>
    <updated>2026-09-28T20:40:20.090588+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 159 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Fix hard lockup when reading the rx_monitor from debugfs During I/O and simultaneous cat of /sys/kernel/debug/lpfc/fnX/rx_monitor, a hard lockup similar to the call trace below may occur. The spin_lock_bh in lpfc_rx_monitor_report is not protecting from timer interrupts as expected, so change the strength of the spin lock to _irq. Kernel panic - not syncing: Hard LOCKUP CPU: 3 PID: 110402 Comm: cat Kdump: loaded exception RIP: native_queued_spin_lock_slowpath+91 [IRQ stack]  native_queued_spin_lock_slowpath at ffffffffb814e30b  _raw_spin_lock at ffffffffb89a667a  lpfc_rx_monitor_record at ffffffffc0a73a36 [lpfc]  lpfc_cmf_timer at ffffffffc0abbc67 [lpfc]  __hrtimer_run_queues at ffffffffb8184250  hrtimer_interrupt at ffffffffb8184ab0  smp_apic_timer_interrupt at ffffffffb8a026ba  apic_timer_interrupt at ffffffffb8a01c4f [End of IRQ stack]  apic_timer_interrupt at ffffffffb8a01c4f  lpfc_rx_monitor_report at ffffffffc0a73c80 [lpfc]  lpfc_rx_monitor_read at ffffffffc0addde1 [lpfc]  full_proxy_read at ffffffffb83e7fc3  vfs_read at ffffffffb833fe71  ksys_read at ffffffffb83402af  do_syscall_64 at ffffffffb800430b  entry_SYSCALL_64_after_hwframe at ffffffffb8a000ad</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ubuntu-cve-2022-50744"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/wid-sec-w-2025-2929</id>
    <title>WID-SEC-W-2025-2929 — Linux Kernel: Mehrere Schwachstellen</title>
    <updated>2026-09-28T20:40:20.091083+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Ein Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/wid-sec-w-2025-2929"/>
  </entry>
</feed>
