<?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-28T09:04:26.828300+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/bell-cve-2026-89481</id>
    <title>BELL-CVE-2026-89481</title>
    <updated>2026-09-28T09:04:27.009209+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/bell-cve-2026-89481"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/fkie_cve-2026-89481</id>
    <title>fkie_cve-2026-89481</title>
    <updated>2026-09-28T09:04:27.009370+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>nvme-tcp: fix host memory disclosure on R2T for a read command</p>
<p>nvme_tcp_handle_r2t() does not check the direction of the request the
R2T refers to. A malicious controller can send an R2T for a READ and
the host will answer it: nvme_tcp_setup_h2c_data_pdu() builds the
H2CData header and nvme_tcp_try_send_data() sends the request's data
buffer. That buffer is the READ destination, so its contents go to the
controller.</p>
<p>The command then completes normally and nothing is logged.</p>
<p>Against a test controller that answers every READ with an R2T, a 4096
byte buffered read returned all 4096 bytes, split over two R2Ts. The
pages contained stale kernel data, including an array of struct page
pointers.</p>
<p>Reject an R2T for a request that is not a write.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/fkie_cve-2026-89481"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-fmg2-x8fr-fw62</id>
    <title>GHSA-fmg2-x8fr-fw62</title>
    <updated>2026-09-28T09:04:27.009473+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>nvme-tcp: fix host memory disclosure on R2T for a read command</p>
<p>nvme_tcp_handle_r2t() does not check the direction of the request the
R2T refers to. A malicious controller can send an R2T for a READ and
the host will answer it: nvme_tcp_setup_h2c_data_pdu() builds the
H2CData header and nvme_tcp_try_send_data() sends the request's data
buffer. That buffer is the READ destination, so its contents go to the
controller.</p>
<p>The command then completes normally and nothing is logged.</p>
<p>Against a test controller that answers every READ with an R2T, a 4096
byte buffered read returned all 4096 bytes, split over two R2Ts. The
pages contained stale kernel data, including an array of struct page
pointers.</p>
<p>Reject an R2T for a request that is not a write.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-fmg2-x8fr-fw62"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/msrc_cve-2026-89481</id>
    <title>msrc_CVE-2026-89481 — nvme-tcp: fix host memory disclosure on R2T for a read command</title>
    <updated>2026-09-28T09:04:27.009524+00:00</updated>
    <content>msrc_CVE-2026-89481</content>
    <link href="https://vulnerability.circl.lu/vuln/msrc_cve-2026-89481"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/opensuse-su-2026:11880-1</id>
    <title>openSUSE-SU-2026:11880-1 — kernel-devel-7.2.7-1.1 on GA media</title>
    <updated>2026-09-28T09:04:27.009570+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>kernel-devel-7.2.7-1.1 on GA media</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/opensuse-su-2026:11880-1"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/rhsa-2026:71602</id>
    <title>RHSA-2026:71602 — Red Hat Security Advisory: kernel security, bug fix, and enhancement update</title>
    <updated>2026-09-28T09:04:27.011056+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>kernel: fbcon: Set fb_display[i]-&gt;mode to NULL when the mode is released kernel: libceph: fix potential use-after-free in have_mon_and_osd_map() kernel: libceph: make decode_pool() more resilient against corrupted osdmaps kernel: libceph: prevent potential out-of-bounds reads in handle_auth_done() kernel: libceph: replace overzealous BUG_ON in osdmap_apply_incremental() kernel: Linux kernel: Denial of Service in libceph OSD client due to unreset sparse-read state kernel: drm/amdgpu/vcn4: Prevent OOB reads when parsing dec msg kernel: drm/amdgpu/vcn4: Prevent OOB reads when parsing IB kernel: drm/amdgpu/vcn3: Prevent OOB reads when parsing dec msg kernel: drm/amdgpu/userq: fix access to stale wptr mapping kernel: af_unix: Drop all SCM attributes for SOCKMAP kernel: accel/ivpu: Add buffer overflow check in MS get_info_ioctl kernel: drm/xe/eustall: Fix drm_dev_put called before stream disable in close kernel: drm/virtio: use uninterruptible resv lock for plane updates kernel: drm/amdgpu/vce: fix integer overflow in image size kernel: pppoe: reload header pointer after dev_hard_header() kernel: drm/amdkfd: fix 32-bit overflow in CWSR total size calculation kernel: drm/xe: Hold a dma-buf reference for imported BOs kernel: drm/xe/rtp: Add RING_FORCE_TO_NONPRIV_DENY to OA whitelists kernel: drm/amdgpu: Fix context pstate override handling kernel: ipvs: do not propagate one-packet flag to synced conns kernel: nvme-tcp: fix host memory disclosure on R2T for a read command</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/rhsa-2026:71602"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/rlsa-2026:71602</id>
    <title>RLSA-2026:71602 — Important: kernel security, bug fix, and enhancement update</title>
    <updated>2026-09-28T09:04:27.011154+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Rocky Linux:10: kernel</p>
<p>The kernel packages contain the Linux kernel, the core of any Linux operating system.</p>
<p>Security Fix(es):</p>
<p>* kernel: fbcon: Set fb_display[i]-&gt;mode to NULL when the mode is released (CVE-2025-40323)</p>
<p>* kernel: libceph: fix potential use-after-free in have_mon_and_osd_map() (CVE-2025-68285)</p>
<p>* kernel: libceph: make decode_pool() more resilient against corrupted osdmaps (CVE-2025-71116)</p>
<p>* kernel: libceph: prevent potential out-of-bounds reads in handle_auth_done() (CVE-2026-22984)</p>
<p>* kernel: libceph: replace overzealous BUG_ON in osdmap_apply_incremental() (CVE-2026-22990)</p>
<p>* kernel: Linux kernel: Denial of Service in libceph OSD client due to unreset sparse-read state (CVE-2026-23136)</p>
<p>* kernel: drm/amdgpu/vcn3: Prevent OOB reads when parsing dec msg (CVE-2026-46230)</p>
<p>* kernel: drm/amdgpu/vcn4: Prevent OOB reads when parsing IB (CVE-2026-46204)</p>
<p>* kernel: drm/amdgpu/vcn4: Prevent OOB reads when parsing dec msg (CVE-2026-46199)</p>
<p>* kernel: drm/amdgpu/userq: fix access to stale wptr mapping (CVE-2026-46311)</p>
<p>* kernel: af_unix: Drop all SCM attributes for SOCKMAP (CVE-2026-53005)</p>
<p>* kernel: accel/ivpu: Add buffer overflow check in MS get_info_ioctl (CVE-2026-53203)</p>
<p>* kernel: drm/xe/eustall: Fix drm_dev_put called before stream disable in close (CVE-2026-53290)</p>
<p>* kernel: drm/virtio: use uninterruptible resv lock for plane updates (CVE-2026-64098)</p>
<p>* kernel: Linux kernel: PPPoE memory corruption via stale pointer (CVE-2026-68121)</p>
<p>* kernel: drm/amdgpu/vce: fix integer overflow in…</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/rlsa-2026:71602"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-89481</id>
    <title>UBUNTU-CVE-2026-89481</title>
    <updated>2026-09-28T09:04:27.011261+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 219 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: nvme-tcp: fix host memory disclosure on R2T for a read command nvme_tcp_handle_r2t() does not check the direction of the request the R2T refers to. A malicious controller can send an R2T for a READ and the host will answer it: nvme_tcp_setup_h2c_data_pdu() builds the H2CData header and nvme_tcp_try_send_data() sends the request's data buffer. That buffer is the READ destination, so its contents go to the controller. The command then completes normally and nothing is logged. Against a test controller that answers every READ with an R2T, a 4096 byte buffered read returned all 4096 bytes, split over two R2Ts. The pages contained stale kernel data, including an array of struct page pointers. Reject an R2T for a request that is not a write.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-89481"/>
  </entry>
</feed>
