<?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>Sat, 03 Oct 2026 14:02:37 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-72197</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-72197</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-72197</guid>
    </item>
    <item>
      <title>EUVD-2026-353972</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-353972</link>
      <description>EUVD-2026-353972</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-353972</guid>
    </item>
    <item>
      <title>fkie_cve-2026-72197</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-72197</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;fs/ntfs3: bound DeleteIndexEntryAllocation memmove length&lt;/p&gt;
&lt;p&gt;In do_action()&amp;#39;s DeleteIndexEntryAllocation case, e-&amp;gt;size comes
from an on-disk INDEX_BUFFER entry.  When e-&amp;gt;size makes
e + e-&amp;gt;size point past hdr + hdr-&amp;gt;used,
PtrOffset(e1, Add2Ptr(hdr, used)) returns a negative ptrdiff_t
that is silently cast to a quasi-infinite size_t when passed
to memmove().  The memmove then walks past the destination
buffer.&lt;/p&gt;
&lt;p&gt;The sibling DeleteIndexEntryRoot case at fslog.c:3540-3543
already carries the corresponding guard:&lt;/p&gt;
&lt;p&gt;if (PtrOffset(e1, Add2Ptr(hdr, used)) &amp;lt; esize ||
	    Add2Ptr(e, esize) &amp;gt; Add2Ptr(lrh, rec_len) ||
	    used + esize &amp;gt; le32_to_cpu(hdr-&amp;gt;total)) {
		goto dirty_vol;
	}&lt;/p&gt;
&lt;p&gt;Apply the same shape to the allocation-path case.  Also reject
esize == 0: memmove(e, e, ...) is a no-op and leaves
hdr-&amp;gt;used unchanged, hiding a malformed entry from the
existing check_index_header() walk.&lt;/p&gt;
&lt;p&gt;Reproduced under UML+KASAN on mainline 8d90b09e6741 by
mounting a crafted NTFS image: the unguarded memmove takes a
length of 0xffffffffffffff00 and the kernel oopses in
memmove+0x81/0x1a0 on the do_action+0x36a2 frame.&lt;/p&gt;
&lt;p&gt;[almaz.alexandrovich@paragon-software.com: clang-formatted the changes]&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;fs/ntfs3: bound DeleteIndexEntryAllocation memmove length&lt;/p&gt;
&lt;p&gt;In do_action()&amp;#39;s DeleteIndexEntryAllocation case, e-&amp;gt;size comes
from an on-disk INDEX_BUFFER entry.  When e-&amp;gt;size makes
e + e-&amp;gt;size point past hdr + hdr-&amp;gt;used,
PtrOffset(e1, Add2Ptr(hdr, used)) returns a negative ptrdiff_t
that is silently cast to a quasi-infinite size_t when passed
to memmove().  The memmove then walks past the destination
buffer.&lt;/p&gt;
&lt;p&gt;The sibling DeleteIndexEntryRoot case at fslog.c:3540-3543
already carries the corresponding guard:&lt;/p&gt;
&lt;p&gt;if (PtrOffset(e1, Add2Ptr(hdr, used)) &amp;lt; esize ||
	    Add2Ptr(e, esize) &amp;gt; Add2Ptr(lrh, rec_len) ||
	    used + esize &amp;gt; le32_to_cpu(hdr-&amp;gt;total)) {
		goto dirty_vol;
	}&lt;/p&gt;
&lt;p&gt;Apply the same shape to the allocation-path case.  Also reject
esize == 0: memmove(e, e, ...) is a no-op and leaves
hdr-&amp;gt;used unchanged, hiding a malformed entry from the
existing check_index_header() walk.&lt;/p&gt;
&lt;p&gt;Reproduced under UML+KASAN on mainline 8d90b09e6741 by
mounting a crafted NTFS image: the unguarded memmove takes a
length of 0xffffffffffffff00 and the kernel oopses in
memmove+0x81/0x1a0 on the do_action+0x36a2 frame.&lt;/p&gt;
&lt;p&gt;[almaz.alexandrovich@paragon-software.com: clang-formatted the changes]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-72197</guid>
    </item>
    <item>
      <title>GHSA-j9fv-qm2v-gr26</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-j9fv-qm2v-gr26</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;fs/ntfs3: bound DeleteIndexEntryAllocation memmove length&lt;/p&gt;
&lt;p&gt;In do_action()&amp;#39;s DeleteIndexEntryAllocation case, e-&amp;gt;size comes
from an on-disk INDEX_BUFFER entry.  When e-&amp;gt;size makes
e + e-&amp;gt;size point past hdr + hdr-&amp;gt;used,
PtrOffset(e1, Add2Ptr(hdr, used)) returns a negative ptrdiff_t
that is silently cast to a quasi-infinite size_t when passed
to memmove().  The memmove then walks past the destination
buffer.&lt;/p&gt;
&lt;p&gt;The sibling DeleteIndexEntryRoot case at fslog.c:3540-3543
already carries the corresponding guard:&lt;/p&gt;
&lt;p&gt;if (PtrOffset(e1, Add2Ptr(hdr, used)) &amp;lt; esize ||
	    Add2Ptr(e, esize) &amp;gt; Add2Ptr(lrh, rec_len) ||
	    used + esize &amp;gt; le32_to_cpu(hdr-&amp;gt;total)) {
		goto dirty_vol;
	}&lt;/p&gt;
&lt;p&gt;Apply the same shape to the allocation-path case.  Also reject
esize == 0: memmove(e, e, ...) is a no-op and leaves
hdr-&amp;gt;used unchanged, hiding a malformed entry from the
existing check_index_header() walk.&lt;/p&gt;
&lt;p&gt;Reproduced under UML+KASAN on mainline 8d90b09e6741 by
mounting a crafted NTFS image: the unguarded memmove takes a
length of 0xffffffffffffff00 and the kernel oopses in
memmove+0x81/0x1a0 on the do_action+0x36a2 frame.&lt;/p&gt;
&lt;p&gt;[almaz.alexandrovich@paragon-software.com: clang-formatted the changes]&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;fs/ntfs3: bound DeleteIndexEntryAllocation memmove length&lt;/p&gt;
&lt;p&gt;In do_action()&amp;#39;s DeleteIndexEntryAllocation case, e-&amp;gt;size comes
from an on-disk INDEX_BUFFER entry.  When e-&amp;gt;size makes
e + e-&amp;gt;size point past hdr + hdr-&amp;gt;used,
PtrOffset(e1, Add2Ptr(hdr, used)) returns a negative ptrdiff_t
that is silently cast to a quasi-infinite size_t when passed
to memmove().  The memmove then walks past the destination
buffer.&lt;/p&gt;
&lt;p&gt;The sibling DeleteIndexEntryRoot case at fslog.c:3540-3543
already carries the corresponding guard:&lt;/p&gt;
&lt;p&gt;if (PtrOffset(e1, Add2Ptr(hdr, used)) &amp;lt; esize ||
	    Add2Ptr(e, esize) &amp;gt; Add2Ptr(lrh, rec_len) ||
	    used + esize &amp;gt; le32_to_cpu(hdr-&amp;gt;total)) {
		goto dirty_vol;
	}&lt;/p&gt;
&lt;p&gt;Apply the same shape to the allocation-path case.  Also reject
esize == 0: memmove(e, e, ...) is a no-op and leaves
hdr-&amp;gt;used unchanged, hiding a malformed entry from the
existing check_index_header() walk.&lt;/p&gt;
&lt;p&gt;Reproduced under UML+KASAN on mainline 8d90b09e6741 by
mounting a crafted NTFS image: the unguarded memmove takes a
length of 0xffffffffffffff00 and the kernel oopses in
memmove+0x81/0x1a0 on the do_action+0x36a2 frame.&lt;/p&gt;
&lt;p&gt;[almaz.alexandrovich@paragon-software.com: clang-formatted the changes]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-j9fv-qm2v-gr26</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-72197</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-72197</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 193 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: bound DeleteIndexEntryAllocation memmove length In do_action()&amp;#39;s DeleteIndexEntryAllocation case, e-&amp;gt;size comes from an on-disk INDEX_BUFFER entry.  When e-&amp;gt;size makes e + e-&amp;gt;size point past hdr + hdr-&amp;gt;used, PtrOffset(e1, Add2Ptr(hdr, used)) returns a negative ptrdiff_t that is silently cast to a quasi-infinite size_t when passed to memmove().  The memmove then walks past the destination buffer. The sibling DeleteIndexEntryRoot case at fslog.c:3540-3543 already carries the corresponding guard: 	if (PtrOffset(e1, Add2Ptr(hdr, used)) &amp;lt; esize || 	    Add2Ptr(e, esize) &amp;gt; Add2Ptr(lrh, rec_len) || 	    used + esize &amp;gt; le32_to_cpu(hdr-&amp;gt;total)) { 		goto dirty_vol; 	} Apply the same shape to the allocation-path case.  Also reject esize == 0: memmove(e, e, ...) is a no-op and leaves hdr-&amp;gt;used unchanged, hiding a malformed entry from the existing check_index_header() walk. Reproduced under UML+KASAN on mainline 8d90b09e6741 by mounting a crafted NTFS image: the unguarded memmove takes a length of 0xffffffffffffff00 and the kernel oopses in memmove+0x81/0x1a0 on the do_action+0x36a2 frame. [almaz.alexandrovich@paragon-software.com: clang-formatted the changes]&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 193 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: bound DeleteIndexEntryAllocation memmove length In do_action()&amp;#39;s DeleteIndexEntryAllocation case, e-&amp;gt;size comes from an on-disk INDEX_BUFFER entry.  When e-&amp;gt;size makes e + e-&amp;gt;size point past hdr + hdr-&amp;gt;used, PtrOffset(e1, Add2Ptr(hdr, used)) returns a negative ptrdiff_t that is silently cast to a quasi-infinite size_t when passed to memmove().  The memmove then walks past the destination buffer. The sibling DeleteIndexEntryRoot case at fslog.c:3540-3543 already carries the corresponding guard: 	if (PtrOffset(e1, Add2Ptr(hdr, used)) &amp;lt; esize || 	    Add2Ptr(e, esize) &amp;gt; Add2Ptr(lrh, rec_len) || 	    used + esize &amp;gt; le32_to_cpu(hdr-&amp;gt;total)) { 		goto dirty_vol; 	} Apply the same shape to the allocation-path case.  Also reject esize == 0: memmove(e, e, ...) is a no-op and leaves hdr-&amp;gt;used unchanged, hiding a malformed entry from the existing check_index_header() walk. Reproduced under UML+KASAN on mainline 8d90b09e6741 by mounting a crafted NTFS image: the unguarded memmove takes a length of 0xffffffffffffff00 and the kernel oopses in memmove+0x81/0x1a0 on the do_action+0x36a2 frame. [almaz.alexandrovich@paragon-software.com: clang-formatted the changes]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-72197</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2852 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2852</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um root Rechte zu erlangen, um einen Denial of Service herbeizuführen oder einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um root Rechte zu erlangen, um einen Denial of Service herbeizuführen oder einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2852</guid>
    </item>
  </channel>
</rss>
