<?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 12:36:56 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-72470</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-72470</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-72470</guid>
    </item>
    <item>
      <title>EUVD-2026-354114</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-354114</link>
      <description>EUVD-2026-354114</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-354114</guid>
    </item>
    <item>
      <title>fkie_cve-2026-72470</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-72470</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;fs/ntfs3: resize log-&amp;gt;one_page_buf when adopting on-disk page size&lt;/p&gt;
&lt;p&gt;log_replay() allocates log-&amp;gt;one_page_buf using the page size that was
chosen from the host PAGE_SIZE:&lt;/p&gt;
&lt;p&gt;log-&amp;gt;one_page_buf = kmalloc(log-&amp;gt;page_size, GFP_NOFS);&lt;/p&gt;
&lt;p&gt;Later, when a restart area is found, the log page size recorded on disk
is adopted:&lt;/p&gt;
&lt;p&gt;t32 = le32_to_cpu(log-&amp;gt;rst_info.r_page-&amp;gt;sys_page_size);
	if (log-&amp;gt;page_size != t32) {
		log-&amp;gt;l_size = log-&amp;gt;orig_file_size;
		log-&amp;gt;page_size = norm_file_page(t32, &amp;amp;log-&amp;gt;l_size,
						t32 == DefaultLogPageSize);
	}&lt;/p&gt;
&lt;p&gt;If the on-disk page size is larger than the size used for the initial
allocation, log-&amp;gt;page_size grows but one_page_buf is left at its
original, smaller size. A subsequent unaligned read_log_page() then
reads log-&amp;gt;page_size bytes into the undersized scratch buffer:&lt;/p&gt;
&lt;p&gt;page_buf = page_off ? log-&amp;gt;one_page_buf : *buffer;
	err = ntfs_read_run_nb_ra(ni-&amp;gt;mi.sbi, &amp;amp;ni-&amp;gt;file.run, page_vbo, page_buf,
				  log-&amp;gt;page_size, NULL, &amp;amp;log-&amp;gt;read_ahead);&lt;/p&gt;
&lt;p&gt;overflowing the allocation. This is reachable when mounting a dirty
NTFS volume whose log was formatted with a page size larger than the
buffer initially allocated on the mounting host (for example a 64K-log
volume mounted on a host that allocated a 4K scratch buffer).&lt;/p&gt;
&lt;p&gt;Grow one_page_buf when the adopted on-disk page size exceeds the size
used for the initial allocation. On krealloc() failure the original
buffer is left intact and freed by the existing erro…&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: resize log-&amp;gt;one_page_buf when adopting on-disk page size&lt;/p&gt;
&lt;p&gt;log_replay() allocates log-&amp;gt;one_page_buf using the page size that was
chosen from the host PAGE_SIZE:&lt;/p&gt;
&lt;p&gt;log-&amp;gt;one_page_buf = kmalloc(log-&amp;gt;page_size, GFP_NOFS);&lt;/p&gt;
&lt;p&gt;Later, when a restart area is found, the log page size recorded on disk
is adopted:&lt;/p&gt;
&lt;p&gt;t32 = le32_to_cpu(log-&amp;gt;rst_info.r_page-&amp;gt;sys_page_size);
	if (log-&amp;gt;page_size != t32) {
		log-&amp;gt;l_size = log-&amp;gt;orig_file_size;
		log-&amp;gt;page_size = norm_file_page(t32, &amp;amp;log-&amp;gt;l_size,
						t32 == DefaultLogPageSize);
	}&lt;/p&gt;
&lt;p&gt;If the on-disk page size is larger than the size used for the initial
allocation, log-&amp;gt;page_size grows but one_page_buf is left at its
original, smaller size. A subsequent unaligned read_log_page() then
reads log-&amp;gt;page_size bytes into the undersized scratch buffer:&lt;/p&gt;
&lt;p&gt;page_buf = page_off ? log-&amp;gt;one_page_buf : *buffer;
	err = ntfs_read_run_nb_ra(ni-&amp;gt;mi.sbi, &amp;amp;ni-&amp;gt;file.run, page_vbo, page_buf,
				  log-&amp;gt;page_size, NULL, &amp;amp;log-&amp;gt;read_ahead);&lt;/p&gt;
&lt;p&gt;overflowing the allocation. This is reachable when mounting a dirty
NTFS volume whose log was formatted with a page size larger than the
buffer initially allocated on the mounting host (for example a 64K-log
volume mounted on a host that allocated a 4K scratch buffer).&lt;/p&gt;
&lt;p&gt;Grow one_page_buf when the adopted on-disk page size exceeds the size
used for the initial allocation. On krealloc() failure the original
buffer is left intact and freed by the existing erro…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-72470</guid>
    </item>
    <item>
      <title>GHSA-mxhq-w28g-hr4q</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-mxhq-w28g-hr4q</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;fs/ntfs3: resize log-&amp;gt;one_page_buf when adopting on-disk page size&lt;/p&gt;
&lt;p&gt;log_replay() allocates log-&amp;gt;one_page_buf using the page size that was
chosen from the host PAGE_SIZE:&lt;/p&gt;
&lt;p&gt;log-&amp;gt;one_page_buf = kmalloc(log-&amp;gt;page_size, GFP_NOFS);&lt;/p&gt;
&lt;p&gt;Later, when a restart area is found, the log page size recorded on disk
is adopted:&lt;/p&gt;
&lt;p&gt;t32 = le32_to_cpu(log-&amp;gt;rst_info.r_page-&amp;gt;sys_page_size);
	if (log-&amp;gt;page_size != t32) {
		log-&amp;gt;l_size = log-&amp;gt;orig_file_size;
		log-&amp;gt;page_size = norm_file_page(t32, &amp;amp;log-&amp;gt;l_size,
						t32 == DefaultLogPageSize);
	}&lt;/p&gt;
&lt;p&gt;If the on-disk page size is larger than the size used for the initial
allocation, log-&amp;gt;page_size grows but one_page_buf is left at its
original, smaller size. A subsequent unaligned read_log_page() then
reads log-&amp;gt;page_size bytes into the undersized scratch buffer:&lt;/p&gt;
&lt;p&gt;page_buf = page_off ? log-&amp;gt;one_page_buf : *buffer;
	err = ntfs_read_run_nb_ra(ni-&amp;gt;mi.sbi, &amp;amp;ni-&amp;gt;file.run, page_vbo, page_buf,
				  log-&amp;gt;page_size, NULL, &amp;amp;log-&amp;gt;read_ahead);&lt;/p&gt;
&lt;p&gt;overflowing the allocation. This is reachable when mounting a dirty
NTFS volume whose log was formatted with a page size larger than the
buffer initially allocated on the mounting host (for example a 64K-log
volume mounted on a host that allocated a 4K scratch buffer).&lt;/p&gt;
&lt;p&gt;Grow one_page_buf when the adopted on-disk page size exceeds the size
used for the initial allocation. On krealloc() failure the original
buffer is left intact and freed by the existing erro…&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: resize log-&amp;gt;one_page_buf when adopting on-disk page size&lt;/p&gt;
&lt;p&gt;log_replay() allocates log-&amp;gt;one_page_buf using the page size that was
chosen from the host PAGE_SIZE:&lt;/p&gt;
&lt;p&gt;log-&amp;gt;one_page_buf = kmalloc(log-&amp;gt;page_size, GFP_NOFS);&lt;/p&gt;
&lt;p&gt;Later, when a restart area is found, the log page size recorded on disk
is adopted:&lt;/p&gt;
&lt;p&gt;t32 = le32_to_cpu(log-&amp;gt;rst_info.r_page-&amp;gt;sys_page_size);
	if (log-&amp;gt;page_size != t32) {
		log-&amp;gt;l_size = log-&amp;gt;orig_file_size;
		log-&amp;gt;page_size = norm_file_page(t32, &amp;amp;log-&amp;gt;l_size,
						t32 == DefaultLogPageSize);
	}&lt;/p&gt;
&lt;p&gt;If the on-disk page size is larger than the size used for the initial
allocation, log-&amp;gt;page_size grows but one_page_buf is left at its
original, smaller size. A subsequent unaligned read_log_page() then
reads log-&amp;gt;page_size bytes into the undersized scratch buffer:&lt;/p&gt;
&lt;p&gt;page_buf = page_off ? log-&amp;gt;one_page_buf : *buffer;
	err = ntfs_read_run_nb_ra(ni-&amp;gt;mi.sbi, &amp;amp;ni-&amp;gt;file.run, page_vbo, page_buf,
				  log-&amp;gt;page_size, NULL, &amp;amp;log-&amp;gt;read_ahead);&lt;/p&gt;
&lt;p&gt;overflowing the allocation. This is reachable when mounting a dirty
NTFS volume whose log was formatted with a page size larger than the
buffer initially allocated on the mounting host (for example a 64K-log
volume mounted on a host that allocated a 4K scratch buffer).&lt;/p&gt;
&lt;p&gt;Grow one_page_buf when the adopted on-disk page size exceeds the size
used for the initial allocation. On krealloc() failure the original
buffer is left intact and freed by the existing erro…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-mxhq-w28g-hr4q</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-72470</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-72470</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: resize log-&amp;gt;one_page_buf when adopting on-disk page size log_replay() allocates log-&amp;gt;one_page_buf using the page size that was chosen from the host PAGE_SIZE: 	log-&amp;gt;one_page_buf = kmalloc(log-&amp;gt;page_size, GFP_NOFS); Later, when a restart area is found, the log page size recorded on disk is adopted: 	t32 = le32_to_cpu(log-&amp;gt;rst_info.r_page-&amp;gt;sys_page_size); 	if (log-&amp;gt;page_size != t32) { 		log-&amp;gt;l_size = log-&amp;gt;orig_file_size; 		log-&amp;gt;page_size = norm_file_page(t32, &amp;amp;log-&amp;gt;l_size, 						t32 == DefaultLogPageSize); 	} If the on-disk page size is larger than the size used for the initial allocation, log-&amp;gt;page_size grows but one_page_buf is left at its original, smaller size. A subsequent unaligned read_log_page() then reads log-&amp;gt;page_size bytes into the undersized scratch buffer: 	page_buf = page_off ? log-&amp;gt;one_page_buf : *buffer; 	err = ntfs_read_run_nb_ra(ni-&amp;gt;mi.sbi, &amp;amp;ni-&amp;gt;file.run, page_vbo, page_buf, 				  log-&amp;gt;page_size, NULL, &amp;amp;log-&amp;gt;read_ahead); overflowing the allocation. This is reachable when mounting a dirty NTFS volume whose log was formatted with a page size larger than the buffer initially allocated on the mounting host (for example a 64K-log volume mounted on a host that allocated a 4K scratch buffer). Grow one_page_buf when the adopted on-disk page size exceeds the size used for the initial allocation. On krealloc() failure the original buffer is left intact and freed by the existing error path.&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: resize log-&amp;gt;one_page_buf when adopting on-disk page size log_replay() allocates log-&amp;gt;one_page_buf using the page size that was chosen from the host PAGE_SIZE: 	log-&amp;gt;one_page_buf = kmalloc(log-&amp;gt;page_size, GFP_NOFS); Later, when a restart area is found, the log page size recorded on disk is adopted: 	t32 = le32_to_cpu(log-&amp;gt;rst_info.r_page-&amp;gt;sys_page_size); 	if (log-&amp;gt;page_size != t32) { 		log-&amp;gt;l_size = log-&amp;gt;orig_file_size; 		log-&amp;gt;page_size = norm_file_page(t32, &amp;amp;log-&amp;gt;l_size, 						t32 == DefaultLogPageSize); 	} If the on-disk page size is larger than the size used for the initial allocation, log-&amp;gt;page_size grows but one_page_buf is left at its original, smaller size. A subsequent unaligned read_log_page() then reads log-&amp;gt;page_size bytes into the undersized scratch buffer: 	page_buf = page_off ? log-&amp;gt;one_page_buf : *buffer; 	err = ntfs_read_run_nb_ra(ni-&amp;gt;mi.sbi, &amp;amp;ni-&amp;gt;file.run, page_vbo, page_buf, 				  log-&amp;gt;page_size, NULL, &amp;amp;log-&amp;gt;read_ahead); overflowing the allocation. This is reachable when mounting a dirty NTFS volume whose log was formatted with a page size larger than the buffer initially allocated on the mounting host (for example a 64K-log volume mounted on a host that allocated a 4K scratch buffer). Grow one_page_buf when the adopted on-disk page size exceeds the size used for the initial allocation. On krealloc() failure the original buffer is left intact and freed by the existing error path.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-72470</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>
