<?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://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-17T10:17:48.056495+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" 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://cve.radiocsirt.org/vuln/bell-cve-2026-99127</id>
    <title>BELL-CVE-2026-99127</title>
    <updated>2026-11-17T10:17:48.068915+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://cve.radiocsirt.org/vuln/bell-cve-2026-99127"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1473</id>
    <title>certfr-2026-avi-1473 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Elles permettent à un attaquant de provo…</title>
    <updated>2026-11-17T10:17:48.068982+00:00</updated>
    <content>certfr-2026-avi-1473</content>
    <link href="https://cve.radiocsirt.org/vuln/certfr-2026-avi-1473"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-396185</id>
    <title>EUVD-2026-396185</title>
    <updated>2026-11-17T10:17:48.069012+00:00</updated>
    <content>EUVD-2026-396185</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-396185"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-99127</id>
    <title>fkie_cve-2026-99127</title>
    <updated>2026-11-17T10:17:48.069034+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>page_pool: keep frag_offset aligned for odd-sized requests</p>
<p>page_pool_alloc_frag_netmem() rounds the requested fragment size with</p>
<p>size = ALIGN(size, dma_get_cache_alignment());</p>
<p>dma_get_cache_alignment() returns 1 unless the architecture defines
ARCH_DMA_MINALIGN, which DMA-coherent architectures such as x86 do not.
There the ALIGN() is a no-op and pool-&gt;frag_offset advances by the raw,
unrounded size.</p>
<p>A single caller asking for an odd size then leaves frag_offset misaligned
for every fragment carved out of that page afterwards.  The pool is shared,
so the damage is not confined to the caller that caused it.</p>
<p>The per-cpu system_page_pool used by generic XDP hits this.
skb_pp_cow_data() allocates its fragments with the raw packet length:</p>
<p>size = min_t(u32, len, PAGE_SIZE);
	truesize = size;
	page = page_pool_dev_alloc(pool, &amp;page_off, &amp;truesize);</p>
<p>leaving frag_offset odd for whatever is carved out of that page next.  Its
own head allocation is already aligned -- SKB_HEAD_ALIGN(size) plus the
XDP_PACKET_HEADROOM its callers pass -- so it is a later user of the shared
pool that pays: page_pool_dev_alloc_va() returns a misaligned buffer,
napi_build_skb() installs it as skb-&gt;head, and skb_shinfo(skb) ==
skb-&gt;head + skb-&gt;end is misaligned with it.</p>
<p>skb_shinfo()-&gt;dataref is a 4-byte atomic_t at offset 0x20, so the
atomic_inc() in __skb_clone() straddles a cache line.  On x86 with split
lock detection -- fatal…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-99127"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-4j2x-r727-jfq6</id>
    <title>GHSA-4j2x-r727-jfq6</title>
    <updated>2026-11-17T10:17:48.069119+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>page_pool: keep frag_offset aligned for odd-sized requests</p>
<p>page_pool_alloc_frag_netmem() rounds the requested fragment size with</p>
<p>size = ALIGN(size, dma_get_cache_alignment());</p>
<p>dma_get_cache_alignment() returns 1 unless the architecture defines
ARCH_DMA_MINALIGN, which DMA-coherent architectures such as x86 do not.
There the ALIGN() is a no-op and pool-&gt;frag_offset advances by the raw,
unrounded size.</p>
<p>A single caller asking for an odd size then leaves frag_offset misaligned
for every fragment carved out of that page afterwards.  The pool is shared,
so the damage is not confined to the caller that caused it.</p>
<p>The per-cpu system_page_pool used by generic XDP hits this.
skb_pp_cow_data() allocates its fragments with the raw packet length:</p>
<p>size = min_t(u32, len, PAGE_SIZE);
	truesize = size;
	page = page_pool_dev_alloc(pool, &amp;page_off, &amp;truesize);</p>
<p>leaving frag_offset odd for whatever is carved out of that page next.  Its
own head allocation is already aligned -- SKB_HEAD_ALIGN(size) plus the
XDP_PACKET_HEADROOM its callers pass -- so it is a later user of the shared
pool that pays: page_pool_dev_alloc_va() returns a misaligned buffer,
napi_build_skb() installs it as skb-&gt;head, and skb_shinfo(skb) ==
skb-&gt;head + skb-&gt;end is misaligned with it.</p>
<p>skb_shinfo()-&gt;dataref is a 4-byte atomic_t at offset 0x20, so the
atomic_inc() in __skb_clone() straddles a cache line.  On x86 with split
lock detection -- fatal…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-4j2x-r727-jfq6"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/msrc_cve-2026-99127</id>
    <title>msrc_CVE-2026-99127 — page_pool: keep frag_offset aligned for odd-sized requests</title>
    <updated>2026-11-17T10:17:48.069203+00:00</updated>
    <content>msrc_CVE-2026-99127</content>
    <link href="https://cve.radiocsirt.org/vuln/msrc_cve-2026-99127"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-99127</id>
    <title>UBUNTU-CVE-2026-99127</title>
    <updated>2026-11-17T10:17:48.069232+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:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 195 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: page_pool: keep frag_offset aligned for odd-sized requests page_pool_alloc_frag_netmem() rounds the requested fragment size with 	size = ALIGN(size, dma_get_cache_alignment()); dma_get_cache_alignment() returns 1 unless the architecture defines ARCH_DMA_MINALIGN, which DMA-coherent architectures such as x86 do not. There the ALIGN() is a no-op and pool-&gt;frag_offset advances by the raw, unrounded size. A single caller asking for an odd size then leaves frag_offset misaligned for every fragment carved out of that page afterwards.  The pool is shared, so the damage is not confined to the caller that caused it. The per-cpu system_page_pool used by generic XDP hits this. skb_pp_cow_data() allocates its fragments with the raw packet length: 	size = min_t(u32, len, PAGE_SIZE); 	truesize = size; 	page = page_pool_dev_alloc(pool, &amp;page_off, &amp;truesize); leaving frag_offset odd for whatever is carved out of that page next.  Its own head allocation is already aligned -- SKB_HEAD_ALIGN(size) plus the XDP_PACKET_HEADROOM its callers pass -- so it is a later user of the shared pool that pays: page_pool_dev_alloc_va() returns a misaligned buffer, napi_build_skb() installs it as skb-&gt;head, and skb_shinfo(skb) == skb-&gt;head + skb-&gt;end is misaligned with it. skb_shinfo()-&gt;dataref is a 4-byte atomic_t at offset 0x20, so the atomic_inc() in __skb_clone() straddles a cache line.  On x86 with split lock detection -- fatal for kerne…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-99127"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4224</id>
    <title>WID-SEC-W-2026-4224 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
    <updated>2026-11-17T10:17:48.069631+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 einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4224"/>
  </entry>
</feed>
