<?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>Sun, 04 Oct 2026 10:18:12 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-03010</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-03010</link>
      <description>bdu:2025-03010</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-03010</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-41083</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-41083</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2024-41083</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0957 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2024-avi-0957</link>
      <description>certfr-2024-avi-0957</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-0957</guid>
    </item>
    <item>
      <title>EUVD-2026-313009</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-313009</link>
      <description>EUVD-2026-313009</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-313009</guid>
    </item>
    <item>
      <title>fkie_cve-2024-41083</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-41083</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;netfs: Fix netfs_page_mkwrite() to check folio-&amp;gt;mapping is valid&lt;/p&gt;
&lt;p&gt;Fix netfs_page_mkwrite() to check that folio-&amp;gt;mapping is valid once it has
taken the folio lock (as filemap_page_mkwrite() does).  Without this,
generic/247 occasionally oopses with something like the following:&lt;/p&gt;
&lt;p&gt;BUG: kernel NULL pointer dereference, address: 0000000000000000
    #PF: supervisor read access in kernel mode
    #PF: error_code(0x0000) - not-present page&lt;/p&gt;
&lt;p&gt;RIP: 0010:trace_event_raw_event_netfs_folio+0x61/0xc0
    ...
    Call Trace:
     &amp;lt;TASK&amp;gt;
     ? __die_body+0x1a/0x60
     ? page_fault_oops+0x6e/0xa0
     ? exc_page_fault+0xc2/0xe0
     ? asm_exc_page_fault+0x22/0x30
     ? trace_event_raw_event_netfs_folio+0x61/0xc0
     trace_netfs_folio+0x39/0x40
     netfs_page_mkwrite+0x14c/0x1d0
     do_page_mkwrite+0x50/0x90
     do_pte_missing+0x184/0x200
     __handle_mm_fault+0x42d/0x500
     handle_mm_fault+0x121/0x1f0
     do_user_addr_fault+0x23e/0x3c0
     exc_page_fault+0xc2/0xe0
     asm_exc_page_fault+0x22/0x30&lt;/p&gt;
&lt;p&gt;This is due to the invalidate_inode_pages2_range() issued at the end of the
DIO write interfering with the mmap&amp;#39;d writes.&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;netfs: Fix netfs_page_mkwrite() to check folio-&amp;gt;mapping is valid&lt;/p&gt;
&lt;p&gt;Fix netfs_page_mkwrite() to check that folio-&amp;gt;mapping is valid once it has
taken the folio lock (as filemap_page_mkwrite() does).  Without this,
generic/247 occasionally oopses with something like the following:&lt;/p&gt;
&lt;p&gt;BUG: kernel NULL pointer dereference, address: 0000000000000000
    #PF: supervisor read access in kernel mode
    #PF: error_code(0x0000) - not-present page&lt;/p&gt;
&lt;p&gt;RIP: 0010:trace_event_raw_event_netfs_folio+0x61/0xc0
    ...
    Call Trace:
     &amp;lt;TASK&amp;gt;
     ? __die_body+0x1a/0x60
     ? page_fault_oops+0x6e/0xa0
     ? exc_page_fault+0xc2/0xe0
     ? asm_exc_page_fault+0x22/0x30
     ? trace_event_raw_event_netfs_folio+0x61/0xc0
     trace_netfs_folio+0x39/0x40
     netfs_page_mkwrite+0x14c/0x1d0
     do_page_mkwrite+0x50/0x90
     do_pte_missing+0x184/0x200
     __handle_mm_fault+0x42d/0x500
     handle_mm_fault+0x121/0x1f0
     do_user_addr_fault+0x23e/0x3c0
     exc_page_fault+0xc2/0xe0
     asm_exc_page_fault+0x22/0x30&lt;/p&gt;
&lt;p&gt;This is due to the invalidate_inode_pages2_range() issued at the end of the
DIO write interfering with the mmap&amp;#39;d writes.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-41083</guid>
    </item>
    <item>
      <title>GHSA-xj6g-c6gv-vmjp</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-xj6g-c6gv-vmjp</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;netfs: Fix netfs_page_mkwrite() to check folio-&amp;gt;mapping is valid&lt;/p&gt;
&lt;p&gt;Fix netfs_page_mkwrite() to check that folio-&amp;gt;mapping is valid once it has
taken the folio lock (as filemap_page_mkwrite() does).  Without this,
generic/247 occasionally oopses with something like the following:&lt;/p&gt;
&lt;p&gt;BUG: kernel NULL pointer dereference, address: 0000000000000000
    #PF: supervisor read access in kernel mode
    #PF: error_code(0x0000) - not-present page&lt;/p&gt;
&lt;p&gt;RIP: 0010:trace_event_raw_event_netfs_folio+0x61/0xc0
    ...
    Call Trace:
     &amp;lt;TASK&amp;gt;
     ? __die_body+0x1a/0x60
     ? page_fault_oops+0x6e/0xa0
     ? exc_page_fault+0xc2/0xe0
     ? asm_exc_page_fault+0x22/0x30
     ? trace_event_raw_event_netfs_folio+0x61/0xc0
     trace_netfs_folio+0x39/0x40
     netfs_page_mkwrite+0x14c/0x1d0
     do_page_mkwrite+0x50/0x90
     do_pte_missing+0x184/0x200
     __handle_mm_fault+0x42d/0x500
     handle_mm_fault+0x121/0x1f0
     do_user_addr_fault+0x23e/0x3c0
     exc_page_fault+0xc2/0xe0
     asm_exc_page_fault+0x22/0x30&lt;/p&gt;
&lt;p&gt;This is due to the invalidate_inode_pages2_range() issued at the end of the
DIO write interfering with the mmap&amp;#39;d writes.&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;netfs: Fix netfs_page_mkwrite() to check folio-&amp;gt;mapping is valid&lt;/p&gt;
&lt;p&gt;Fix netfs_page_mkwrite() to check that folio-&amp;gt;mapping is valid once it has
taken the folio lock (as filemap_page_mkwrite() does).  Without this,
generic/247 occasionally oopses with something like the following:&lt;/p&gt;
&lt;p&gt;BUG: kernel NULL pointer dereference, address: 0000000000000000
    #PF: supervisor read access in kernel mode
    #PF: error_code(0x0000) - not-present page&lt;/p&gt;
&lt;p&gt;RIP: 0010:trace_event_raw_event_netfs_folio+0x61/0xc0
    ...
    Call Trace:
     &amp;lt;TASK&amp;gt;
     ? __die_body+0x1a/0x60
     ? page_fault_oops+0x6e/0xa0
     ? exc_page_fault+0xc2/0xe0
     ? asm_exc_page_fault+0x22/0x30
     ? trace_event_raw_event_netfs_folio+0x61/0xc0
     trace_netfs_folio+0x39/0x40
     netfs_page_mkwrite+0x14c/0x1d0
     do_page_mkwrite+0x50/0x90
     do_pte_missing+0x184/0x200
     __handle_mm_fault+0x42d/0x500
     handle_mm_fault+0x121/0x1f0
     do_user_addr_fault+0x23e/0x3c0
     exc_page_fault+0xc2/0xe0
     asm_exc_page_fault+0x22/0x30&lt;/p&gt;
&lt;p&gt;This is due to the invalidate_inode_pages2_range() issued at the end of the
DIO write interfering with the mmap&amp;#39;d writes.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-xj6g-c6gv-vmjp</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-41083</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-41083</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 88 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: netfs: Fix netfs_page_mkwrite() to check folio-&amp;gt;mapping is valid Fix netfs_page_mkwrite() to check that folio-&amp;gt;mapping is valid once it has taken the folio lock (as filemap_page_mkwrite() does).  Without this, generic/247 occasionally oopses with something like the following:     BUG: kernel NULL pointer dereference, address: 0000000000000000     #PF: supervisor read access in kernel mode     #PF: error_code(0x0000) - not-present page     RIP: 0010:trace_event_raw_event_netfs_folio+0x61/0xc0     ...     Call Trace:      &amp;lt;TASK&amp;gt;      ? __die_body+0x1a/0x60      ? page_fault_oops+0x6e/0xa0      ? exc_page_fault+0xc2/0xe0      ? asm_exc_page_fault+0x22/0x30      ? trace_event_raw_event_netfs_folio+0x61/0xc0      trace_netfs_folio+0x39/0x40      netfs_page_mkwrite+0x14c/0x1d0      do_page_mkwrite+0x50/0x90      do_pte_missing+0x184/0x200      __handle_mm_fault+0x42d/0x500      handle_mm_fault+0x121/0x1f0      do_user_addr_fault+0x23e/0x3c0      exc_page_fault+0xc2/0xe0      asm_exc_page_fault+0x22/0x30 This is due to the invalidate_inode_pages2_range() issued at the end of the DIO write interfering with the mmap&amp;#39;d writes.&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 88 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: netfs: Fix netfs_page_mkwrite() to check folio-&amp;gt;mapping is valid Fix netfs_page_mkwrite() to check that folio-&amp;gt;mapping is valid once it has taken the folio lock (as filemap_page_mkwrite() does).  Without this, generic/247 occasionally oopses with something like the following:     BUG: kernel NULL pointer dereference, address: 0000000000000000     #PF: supervisor read access in kernel mode     #PF: error_code(0x0000) - not-present page     RIP: 0010:trace_event_raw_event_netfs_folio+0x61/0xc0     ...     Call Trace:      &amp;lt;TASK&amp;gt;      ? __die_body+0x1a/0x60      ? page_fault_oops+0x6e/0xa0      ? exc_page_fault+0xc2/0xe0      ? asm_exc_page_fault+0x22/0x30      ? trace_event_raw_event_netfs_folio+0x61/0xc0      trace_netfs_folio+0x39/0x40      netfs_page_mkwrite+0x14c/0x1d0      do_page_mkwrite+0x50/0x90      do_pte_missing+0x184/0x200      __handle_mm_fault+0x42d/0x500      handle_mm_fault+0x121/0x1f0      do_user_addr_fault+0x23e/0x3c0      exc_page_fault+0xc2/0xe0      asm_exc_page_fault+0x22/0x30 This is due to the invalidate_inode_pages2_range() issued at the end of the DIO write interfering with the mmap&amp;#39;d writes.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-41083</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-1722 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1722</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.&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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1722</guid>
    </item>
  </channel>
</rss>
