<?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>Tue, 17 Nov 2026 10:11:01 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-99127</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-99127</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-99127</guid>
    </item>
    <item>
      <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>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1473</link>
      <description>certfr-2026-avi-1473</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-1473</guid>
    </item>
    <item>
      <title>EUVD-2026-396185</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-396185</link>
      <description>EUVD-2026-396185</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-396185</guid>
    </item>
    <item>
      <title>fkie_cve-2026-99127</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-99127</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;page_pool: keep frag_offset aligned for odd-sized requests&lt;/p&gt;
&lt;p&gt;page_pool_alloc_frag_netmem() rounds the requested fragment size with&lt;/p&gt;
&lt;p&gt;size = ALIGN(size, dma_get_cache_alignment());&lt;/p&gt;
&lt;p&gt;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-&amp;gt;frag_offset advances by the raw,
unrounded size.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;The per-cpu system_page_pool used by generic XDP hits this.
skb_pp_cow_data() allocates its fragments with the raw packet length:&lt;/p&gt;
&lt;p&gt;size = min_t(u32, len, PAGE_SIZE);
	truesize = size;
	page = page_pool_dev_alloc(pool, &amp;amp;page_off, &amp;amp;truesize);&lt;/p&gt;
&lt;p&gt;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-&amp;gt;head, and skb_shinfo(skb) ==
skb-&amp;gt;head + skb-&amp;gt;end is misaligned with it.&lt;/p&gt;
&lt;p&gt;skb_shinfo()-&amp;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…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;page_pool: keep frag_offset aligned for odd-sized requests&lt;/p&gt;
&lt;p&gt;page_pool_alloc_frag_netmem() rounds the requested fragment size with&lt;/p&gt;
&lt;p&gt;size = ALIGN(size, dma_get_cache_alignment());&lt;/p&gt;
&lt;p&gt;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-&amp;gt;frag_offset advances by the raw,
unrounded size.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;The per-cpu system_page_pool used by generic XDP hits this.
skb_pp_cow_data() allocates its fragments with the raw packet length:&lt;/p&gt;
&lt;p&gt;size = min_t(u32, len, PAGE_SIZE);
	truesize = size;
	page = page_pool_dev_alloc(pool, &amp;amp;page_off, &amp;amp;truesize);&lt;/p&gt;
&lt;p&gt;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-&amp;gt;head, and skb_shinfo(skb) ==
skb-&amp;gt;head + skb-&amp;gt;end is misaligned with it.&lt;/p&gt;
&lt;p&gt;skb_shinfo()-&amp;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…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-99127</guid>
    </item>
    <item>
      <title>GHSA-4j2x-r727-jfq6</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-4j2x-r727-jfq6</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;page_pool: keep frag_offset aligned for odd-sized requests&lt;/p&gt;
&lt;p&gt;page_pool_alloc_frag_netmem() rounds the requested fragment size with&lt;/p&gt;
&lt;p&gt;size = ALIGN(size, dma_get_cache_alignment());&lt;/p&gt;
&lt;p&gt;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-&amp;gt;frag_offset advances by the raw,
unrounded size.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;The per-cpu system_page_pool used by generic XDP hits this.
skb_pp_cow_data() allocates its fragments with the raw packet length:&lt;/p&gt;
&lt;p&gt;size = min_t(u32, len, PAGE_SIZE);
	truesize = size;
	page = page_pool_dev_alloc(pool, &amp;amp;page_off, &amp;amp;truesize);&lt;/p&gt;
&lt;p&gt;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-&amp;gt;head, and skb_shinfo(skb) ==
skb-&amp;gt;head + skb-&amp;gt;end is misaligned with it.&lt;/p&gt;
&lt;p&gt;skb_shinfo()-&amp;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…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;page_pool: keep frag_offset aligned for odd-sized requests&lt;/p&gt;
&lt;p&gt;page_pool_alloc_frag_netmem() rounds the requested fragment size with&lt;/p&gt;
&lt;p&gt;size = ALIGN(size, dma_get_cache_alignment());&lt;/p&gt;
&lt;p&gt;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-&amp;gt;frag_offset advances by the raw,
unrounded size.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;The per-cpu system_page_pool used by generic XDP hits this.
skb_pp_cow_data() allocates its fragments with the raw packet length:&lt;/p&gt;
&lt;p&gt;size = min_t(u32, len, PAGE_SIZE);
	truesize = size;
	page = page_pool_dev_alloc(pool, &amp;amp;page_off, &amp;amp;truesize);&lt;/p&gt;
&lt;p&gt;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-&amp;gt;head, and skb_shinfo(skb) ==
skb-&amp;gt;head + skb-&amp;gt;end is misaligned with it.&lt;/p&gt;
&lt;p&gt;skb_shinfo()-&amp;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…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-4j2x-r727-jfq6</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-99127 — page_pool: keep frag_offset aligned for odd-sized requests</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-99127</link>
      <description>msrc_CVE-2026-99127</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-99127</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-99127</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-99127</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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&lt;/p&gt;
&lt;p&gt;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-&amp;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;amp;page_off, &amp;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-&amp;gt;head, and skb_shinfo(skb) == skb-&amp;gt;head + skb-&amp;gt;end is misaligned with it. skb_shinfo()-&amp;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…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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&lt;/p&gt;
&lt;p&gt;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-&amp;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;amp;page_off, &amp;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-&amp;gt;head, and skb_shinfo(skb) == skb-&amp;gt;head + skb-&amp;gt;end is misaligned with it. skb_shinfo()-&amp;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…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-99127</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4224 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4224</link>
      <description>&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4224</guid>
    </item>
  </channel>
</rss>
