<?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 11:32:07 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-10239</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-10239</link>
      <description>bdu:2025-10239</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-10239</guid>
    </item>
    <item>
      <title>BELL-CVE-2023-52935</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2023-52935</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2023-52935</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0307 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2025-avi-0307</link>
      <description>certfr-2025-avi-0307</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0307</guid>
    </item>
    <item>
      <title>EUVD-2026-345106</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-345106</link>
      <description>EUVD-2026-345106</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-345106</guid>
    </item>
    <item>
      <title>fkie_cve-2023-52935</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-52935</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mm/khugepaged: fix -&amp;gt;anon_vma race&lt;/p&gt;
&lt;p&gt;If an -&amp;gt;anon_vma is attached to the VMA, collapse_and_free_pmd() requires
it to be locked.&lt;/p&gt;
&lt;p&gt;Page table traversal is allowed under any one of the mmap lock, the
anon_vma lock (if the VMA is associated with an anon_vma), and the
mapping lock (if the VMA is associated with a mapping); and so to be
able to remove page tables, we must hold all three of them. 
retract_page_tables() bails out if an -&amp;gt;anon_vma is attached, but does
this check before holding the mmap lock (as the comment above the check
explains).&lt;/p&gt;
&lt;p&gt;If we racily merged an existing -&amp;gt;anon_vma (shared with a child
process) from a neighboring VMA, subsequent rmap traversals on pages
belonging to the child will be able to see the page tables that we are
concurrently removing while assuming that nothing else can access them.&lt;/p&gt;
&lt;p&gt;Repeat the -&amp;gt;anon_vma check once we hold the mmap lock to ensure that
there really is no concurrent page table access.&lt;/p&gt;
&lt;p&gt;Hitting this bug causes a lockdep warning in collapse_and_free_pmd(),
in the line &amp;#34;lockdep_assert_held_write(&amp;amp;vma-&amp;gt;anon_vma-&amp;gt;root-&amp;gt;rwsem)&amp;#34;. 
It can also lead to use-after-free access.&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;mm/khugepaged: fix -&amp;gt;anon_vma race&lt;/p&gt;
&lt;p&gt;If an -&amp;gt;anon_vma is attached to the VMA, collapse_and_free_pmd() requires
it to be locked.&lt;/p&gt;
&lt;p&gt;Page table traversal is allowed under any one of the mmap lock, the
anon_vma lock (if the VMA is associated with an anon_vma), and the
mapping lock (if the VMA is associated with a mapping); and so to be
able to remove page tables, we must hold all three of them. 
retract_page_tables() bails out if an -&amp;gt;anon_vma is attached, but does
this check before holding the mmap lock (as the comment above the check
explains).&lt;/p&gt;
&lt;p&gt;If we racily merged an existing -&amp;gt;anon_vma (shared with a child
process) from a neighboring VMA, subsequent rmap traversals on pages
belonging to the child will be able to see the page tables that we are
concurrently removing while assuming that nothing else can access them.&lt;/p&gt;
&lt;p&gt;Repeat the -&amp;gt;anon_vma check once we hold the mmap lock to ensure that
there really is no concurrent page table access.&lt;/p&gt;
&lt;p&gt;Hitting this bug causes a lockdep warning in collapse_and_free_pmd(),
in the line &amp;#34;lockdep_assert_held_write(&amp;amp;vma-&amp;gt;anon_vma-&amp;gt;root-&amp;gt;rwsem)&amp;#34;. 
It can also lead to use-after-free access.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-52935</guid>
    </item>
    <item>
      <title>GHSA-whcm-px77-62x7</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-whcm-px77-62x7</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mm/khugepaged: fix -&amp;gt;anon_vma race&lt;/p&gt;
&lt;p&gt;If an -&amp;gt;anon_vma is attached to the VMA, collapse_and_free_pmd() requires
it to be locked.&lt;/p&gt;
&lt;p&gt;Page table traversal is allowed under any one of the mmap lock, the
anon_vma lock (if the VMA is associated with an anon_vma), and the
mapping lock (if the VMA is associated with a mapping); and so to be
able to remove page tables, we must hold all three of them. 
retract_page_tables() bails out if an -&amp;gt;anon_vma is attached, but does
this check before holding the mmap lock (as the comment above the check
explains).&lt;/p&gt;
&lt;p&gt;If we racily merged an existing -&amp;gt;anon_vma (shared with a child
process) from a neighboring VMA, subsequent rmap traversals on pages
belonging to the child will be able to see the page tables that we are
concurrently removing while assuming that nothing else can access them.&lt;/p&gt;
&lt;p&gt;Repeat the -&amp;gt;anon_vma check once we hold the mmap lock to ensure that
there really is no concurrent page table access.&lt;/p&gt;
&lt;p&gt;Hitting this bug causes a lockdep warning in collapse_and_free_pmd(),
in the line &amp;#34;lockdep_assert_held_write(&amp;amp;vma-&amp;gt;anon_vma-&amp;gt;root-&amp;gt;rwsem)&amp;#34;. 
It can also lead to use-after-free access.&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;mm/khugepaged: fix -&amp;gt;anon_vma race&lt;/p&gt;
&lt;p&gt;If an -&amp;gt;anon_vma is attached to the VMA, collapse_and_free_pmd() requires
it to be locked.&lt;/p&gt;
&lt;p&gt;Page table traversal is allowed under any one of the mmap lock, the
anon_vma lock (if the VMA is associated with an anon_vma), and the
mapping lock (if the VMA is associated with a mapping); and so to be
able to remove page tables, we must hold all three of them. 
retract_page_tables() bails out if an -&amp;gt;anon_vma is attached, but does
this check before holding the mmap lock (as the comment above the check
explains).&lt;/p&gt;
&lt;p&gt;If we racily merged an existing -&amp;gt;anon_vma (shared with a child
process) from a neighboring VMA, subsequent rmap traversals on pages
belonging to the child will be able to see the page tables that we are
concurrently removing while assuming that nothing else can access them.&lt;/p&gt;
&lt;p&gt;Repeat the -&amp;gt;anon_vma check once we hold the mmap lock to ensure that
there really is no concurrent page table access.&lt;/p&gt;
&lt;p&gt;Hitting this bug causes a lockdep warning in collapse_and_free_pmd(),
in the line &amp;#34;lockdep_assert_held_write(&amp;amp;vma-&amp;gt;anon_vma-&amp;gt;root-&amp;gt;rwsem)&amp;#34;. 
It can also lead to use-after-free access.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-whcm-px77-62x7</guid>
    </item>
    <item>
      <title>msrc_CVE-2023-52935 — mm/khugepaged: fix -&gt;anon_vma race</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2023-52935</link>
      <description>msrc_CVE-2023-52935</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2023-52935</guid>
    </item>
    <item>
      <title>OESA-2025-1448 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2025-1448</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP3: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mm/khugepaged: fix -&amp;amp;gt;anon_vma race&lt;/p&gt;
&lt;p&gt;If an -&amp;amp;gt;anon_vma is attached to the VMA, collapse_and_free_pmd() requires
it to be locked.&lt;/p&gt;
&lt;p&gt;Page table traversal is allowed under any one of the mmap lock, the
anon_vma lock (if the VMA is associated with an anon_vma), and the
mapping lock (if the VMA is associated with a mapping); and so to be
able to remove page tables, we must hold all three of them. 
retract_page_tables() bails out if an -&amp;amp;gt;anon_vma is attached, but does
this check before holding the mmap lock (as the comment above the check
explains).&lt;/p&gt;
&lt;p&gt;If we racily merged an existing -&amp;amp;gt;anon_vma (shared with a child
process) from a neighboring VMA, subsequent rmap traversals on pages
belonging to the child will be able to see the page tables that we are
concurrently removing while assuming that nothing else can access them.&lt;/p&gt;
&lt;p&gt;Repeat the -&amp;amp;gt;anon_vma check once we hold the mmap lock to ensure that
there really is no concurrent page table access.&lt;/p&gt;
&lt;p&gt;Hitting this bug causes a lockdep warning in collapse_and_free_pmd(),
in the line &amp;amp;quot;lockdep_assert_held_write(&amp;amp;amp;vma-&amp;amp;gt;anon_vma-&amp;amp;gt;root-&amp;amp;gt;rwsem)&amp;amp;quot;. 
It can also lead to use-after-free access.(CVE-2023-52935)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bnxt: Do not read past the end of test names&lt;/p&gt;
&lt;p&gt;Test names were being concatenated based on a offset beyo…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP3: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mm/khugepaged: fix -&amp;amp;gt;anon_vma race&lt;/p&gt;
&lt;p&gt;If an -&amp;amp;gt;anon_vma is attached to the VMA, collapse_and_free_pmd() requires
it to be locked.&lt;/p&gt;
&lt;p&gt;Page table traversal is allowed under any one of the mmap lock, the
anon_vma lock (if the VMA is associated with an anon_vma), and the
mapping lock (if the VMA is associated with a mapping); and so to be
able to remove page tables, we must hold all three of them. 
retract_page_tables() bails out if an -&amp;amp;gt;anon_vma is attached, but does
this check before holding the mmap lock (as the comment above the check
explains).&lt;/p&gt;
&lt;p&gt;If we racily merged an existing -&amp;amp;gt;anon_vma (shared with a child
process) from a neighboring VMA, subsequent rmap traversals on pages
belonging to the child will be able to see the page tables that we are
concurrently removing while assuming that nothing else can access them.&lt;/p&gt;
&lt;p&gt;Repeat the -&amp;amp;gt;anon_vma check once we hold the mmap lock to ensure that
there really is no concurrent page table access.&lt;/p&gt;
&lt;p&gt;Hitting this bug causes a lockdep warning in collapse_and_free_pmd(),
in the line &amp;amp;quot;lockdep_assert_held_write(&amp;amp;amp;vma-&amp;amp;gt;anon_vma-&amp;amp;gt;root-&amp;amp;gt;rwsem)&amp;amp;quot;. 
It can also lead to use-after-free access.(CVE-2023-52935)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bnxt: Do not read past the end of test names&lt;/p&gt;
&lt;p&gt;Test names were being concatenated based on a offset beyo…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2025-1448</guid>
    </item>
    <item>
      <title>RHSA-2024:9315 — Red Hat Security Advisory: kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2024:9315</link>
      <description>&lt;p&gt;kernel: use after free in i2c kernel: bluetooth: BR/EDR Bluetooth Impersonation Attacks (BIAS) kernel: hwmon: (lm90) Prevent integer overflow/underflow in hysteresis calculations kernel: asix: fix uninit-value in asix_mdio_read() kernel: tty: tty_buffer: Fix the softlockup issue in flush_to_ldisc kernel: hwmon: (w83793) Fix NULL pointer dereference by removing unnecessary structure field kernel: hwmon: (w83791d) Fix NULL pointer dereference by removing unnecessary structure field kernel: powerpc/64s: fix program check interrupt emergency stack path kernel: powerpc/64s: Fix unrecoverable MCE calling async handler from NMI kernel: lib/generic-radix-tree.c: Don&amp;#39;t overflow in peek() kernel: powerpc/smp: do not decrement idle task preempt count in CPU offline kernel: can: isotp: isotp_sendmsg(): add result check for wait_event_interruptible() kernel: usbnet: sanity check for maxpacket kernel: nvmem: Fix shift-out-of-bound (UBSAN) with byte size cells kernel: aio: fix use-after-free due to missing POLLFREE handling kernel: powerpc/pseries: Fix potential memleak in papr_get_attr() kernel: of: fdt: fix off-by-one error in unflatten_dt_nodes() kernel: thermal/int340x_thermal: handle data_vault when the value is ZERO_SIZE_PTR kernel: vt_ioctl: fix array_index_nospec in vt_setactivate kernel: bpf: Fix crash due to out of bounds access into reg2btf_ids. kernel: lz4: fix LZ4_decompress_safe_partial read out of bound kernel: x86/mce: Work around an erratum on fast string copy instructions…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: use after free in i2c kernel: bluetooth: BR/EDR Bluetooth Impersonation Attacks (BIAS) kernel: hwmon: (lm90) Prevent integer overflow/underflow in hysteresis calculations kernel: asix: fix uninit-value in asix_mdio_read() kernel: tty: tty_buffer: Fix the softlockup issue in flush_to_ldisc kernel: hwmon: (w83793) Fix NULL pointer dereference by removing unnecessary structure field kernel: hwmon: (w83791d) Fix NULL pointer dereference by removing unnecessary structure field kernel: powerpc/64s: fix program check interrupt emergency stack path kernel: powerpc/64s: Fix unrecoverable MCE calling async handler from NMI kernel: lib/generic-radix-tree.c: Don&amp;#39;t overflow in peek() kernel: powerpc/smp: do not decrement idle task preempt count in CPU offline kernel: can: isotp: isotp_sendmsg(): add result check for wait_event_interruptible() kernel: usbnet: sanity check for maxpacket kernel: nvmem: Fix shift-out-of-bound (UBSAN) with byte size cells kernel: aio: fix use-after-free due to missing POLLFREE handling kernel: powerpc/pseries: Fix potential memleak in papr_get_attr() kernel: of: fdt: fix off-by-one error in unflatten_dt_nodes() kernel: thermal/int340x_thermal: handle data_vault when the value is ZERO_SIZE_PTR kernel: vt_ioctl: fix array_index_nospec in vt_setactivate kernel: bpf: Fix crash due to out of bounds access into reg2btf_ids. kernel: lz4: fix LZ4_decompress_safe_partial read out of bound kernel: x86/mce: Work around an erratum on fast string copy instructions…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2024:9315</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:1176-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:1176-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2025:1176-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2023-52935</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-52935</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 154 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: mm/khugepaged: fix -&amp;gt;anon_vma race If an -&amp;gt;anon_vma is attached to the VMA, collapse_and_free_pmd() requires it to be locked. Page table traversal is allowed under any one of the mmap lock, the anon_vma lock (if the VMA is associated with an anon_vma), and the mapping lock (if the VMA is associated with a mapping); and so to be able to remove page tables, we must hold all three of them. retract_page_tables() bails out if an -&amp;gt;anon_vma is attached, but does this check before holding the mmap lock (as the comment above the check explains). If we racily merged an existing -&amp;gt;anon_vma (shared with a child process) from a neighboring VMA, subsequent rmap traversals on pages belonging to the child will be able to see the page tables that we are concurrently removing while assuming that nothing else can access them. Repeat the -&amp;gt;anon_vma check once we hold the mmap lock to ensure that there really is no concurrent page table access. Hitting this bug causes a lockdep warning in collapse_and_free_pmd(), in the line &amp;#34;lockdep_assert_held_write(&amp;amp;vma-&amp;gt;anon_vma-&amp;gt;root-&amp;gt;rwsem)&amp;#34;. It can also lead to use-after-free access.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 154 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: mm/khugepaged: fix -&amp;gt;anon_vma race If an -&amp;gt;anon_vma is attached to the VMA, collapse_and_free_pmd() requires it to be locked. Page table traversal is allowed under any one of the mmap lock, the anon_vma lock (if the VMA is associated with an anon_vma), and the mapping lock (if the VMA is associated with a mapping); and so to be able to remove page tables, we must hold all three of them. retract_page_tables() bails out if an -&amp;gt;anon_vma is attached, but does this check before holding the mmap lock (as the comment above the check explains). If we racily merged an existing -&amp;gt;anon_vma (shared with a child process) from a neighboring VMA, subsequent rmap traversals on pages belonging to the child will be able to see the page tables that we are concurrently removing while assuming that nothing else can access them. Repeat the -&amp;gt;anon_vma check once we hold the mmap lock to ensure that there really is no concurrent page table access. Hitting this bug causes a lockdep warning in collapse_and_free_pmd(), in the line &amp;#34;lockdep_assert_held_write(&amp;amp;vma-&amp;gt;anon_vma-&amp;gt;root-&amp;gt;rwsem)&amp;#34;. It can also lead to use-after-free access.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-52935</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-0649 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0649</link>
      <description>&lt;p&gt;Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht spezifizierte Effekte zu erzielen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht spezifizierte Effekte zu erzielen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0649</guid>
    </item>
  </channel>
</rss>
