<?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://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-19T17:42:37.875022+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" 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://db.gcve.eu/vuln/cve-2026-46325</id>
    <title>CVE-2026-46325 — RDMA/rxe: Fix iova-to-va conversion for MR page sizes != PAGE_SIZE</title>
    <updated>2026-11-19T17:42:37.884300+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>RDMA/rxe: Fix iova-to-va conversion for MR page sizes != PAGE_SIZE</p>
<p>The current implementation incorrectly handles memory regions (MRs) with
page sizes different from the system PAGE_SIZE. The core issue is that
rxe_set_page() is called with mr-&gt;page_size step increments, but the
page_list stores individual struct page pointers, each representing
PAGE_SIZE of memory.</p>
<p>ib_sg_to_page() has ensured that when i&gt;=1 either
a) SG[i-1].dma_end and SG[i].dma_addr are contiguous
or
b) SG[i-1].dma_end and SG[i].dma_addr are mr-&gt;page_size aligned.</p>
<p>This leads to incorrect iova-to-va conversion in scenarios:</p>
<p>1) page_size &lt; PAGE_SIZE (e.g., MR: 4K, system: 64K):
   ibmr-&gt;iova = 0x181800
   sg[0]: dma_addr=0x181800, len=0x800
   sg[1]: dma_addr=0x173000, len=0x1000</p>
<p>Access iova = 0x181800 + 0x810 = 0x182010
   Expected VA: 0x173010 (second SG, offset 0x10)
   Before fix:
     - index = (0x182010 &gt;&gt; 12) - (0x181800 &gt;&gt; 12) = 1
     - page_offset = 0x182010 &amp; 0xFFF = 0x10
     - xarray[1] stores system page base 0x170000
     - Resulting VA: 0x170000 + 0x10 = 0x170010 (wrong)</p>
<p>2) page_size &gt; PAGE_SIZE (e.g., MR: 64K, system: 4K):
   ibmr-&gt;iova = 0x18f800
   sg[0]: dma_addr=0x18f800, len=0x800
   sg[1]: dma_addr=0x170000, len=0x1000</p>
<p>Access iova = 0x18f800 + 0x810 = 0x190010
   Expected VA: 0x170010 (second SG, offset 0x10)
   Before fix:
     - index = (0x190010 &gt;&gt; 16) - (0x18f800 &gt;&gt; 16) = 1
     - page_offset = 0x190…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2026-46325"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/usn-8490-1</id>
    <title>USN-8490-1 — linux, linux-aws, linux-aws-6.17, linux-gcp, linux-gcp-6.17, linux-oracle, linux-oracle-6.17 vulnerabilities</title>
    <updated>2026-11-19T17:42:37.884414+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:24.04:LTS: linux-aws-6.17, Ubuntu:24.04:LTS: linux-gcp-6.17, Ubuntu:24.04:LTS: linux-oracle-6.17, Ubuntu:25.10: linux, Ubuntu:25.10: linux-aws, Ubuntu:25.10: linux-gcp, Ubuntu:25.10: linux-oracle</p>
<p>Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - ARM64 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - DMA engine subsystem;
  - InfiniBand drivers;
  - STMicroelectronics network drivers;
  - Network drivers;
  - NVME drivers;
  - SCSI subsystem;
  - USB over IP driver;
  - File systems infrastructure;
  - Ext4 file system;
  - Network file system (NFS) server daemon;
  - SMB network file system;
  - Kernel thread helper (kthread);
  - IPv6 networking;
  - Tracing infrastructure;
  - Kernel exit() syscall;
  - Scatterlist API;
  - B.A.T.M.A.N. meshing protocol;
  - Ethernet bridge;
  - Ceph Core library;
  - IPv4 networking;
  - Multipath TCP;
  - Netfilter;
  - RxRPC session sockets;
  - SMC sockets;
  - X.25 network layer;
(CVE-2026-22984, CVE-2026-23272, CVE-2026-23278, CVE-2026-23392,
CVE-2026-23427, CVE-2026-23428, CVE-2026-23450, CVE-2026-23455,
CVE-2026-31402, CVE-2026-31418, CVE-2026-31436, CVE-2026-31448,
CVE-2026-31478, CVE-2026-31607, CVE-2026-31635, CVE-2026-31637,
CVE-2026-31649, CVE-2026-31657, CVE-2026-31659, CVE-2026-31668,
CVE-2026-31669, CVE-2026-31682, CVE-2026-31685, CVE-2026-31718,
CVE-2026-43011, CVE-2026-43037, CVE-2026-43038, CVE-2026-43071,
CVE-2026-43083, CVE-2026-43114, CVE-2026-43117, CVE-2026-43125,
CVE-2026-43186, CVE-2026-43197, CVE-2026-43304, CVE-2026-43341,
CVE-2026-43376, CVE-2026-43378,…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/usn-8490-1"/>
  </entry>
</feed>
