<?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 02:34:58 +0000</lastBuildDate>
    <item>
      <title>bdu:2017-02405</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2017-02405</link>
      <description>bdu:2017-02405</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2017-02405</guid>
    </item>
    <item>
      <title>certfr-2017-avi-324 — Une vulnérabilité a été découverte dans le noyau Linux de RedHat . Elle
permet à un attaquant de provoquer une élévatio…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2017-avi-324</link>
      <description>certfr-2017-avi-324</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2017-avi-324</guid>
    </item>
    <item>
      <title>cnvd-2017-29914</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2017-29914</link>
      <description>cnvd-2017-29914</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2017-29914</guid>
    </item>
    <item>
      <title>EUVD-2026-256306</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-256306</link>
      <description>EUVD-2026-256306</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-256306</guid>
    </item>
    <item>
      <title>fkie_cve-2017-1000253</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2017-1000253</link>
      <description>&lt;p&gt;Linux distributions that have not patched their long-term kernels with https://git.kernel.org/linus/a87938b2e246b81b4fb713edb371a9fa3c5c3c86 (committed on April 14, 2015). This kernel vulnerability was fixed in April 2015 by commit a87938b2e246b81b4fb713edb371a9fa3c5c3c86 (backported to Linux 3.10.77 in May 2015), but it was not recognized as a security threat. With CONFIG_ARCH_BINFMT_ELF_RANDOMIZE_PIE enabled, and a normal top-down address allocation strategy, load_elf_binary() will attempt to map a PIE binary into an address range immediately below mm-&amp;gt;mmap_base. Unfortunately, load_elf_ binary() does not take account of the need to allocate sufficient space for the entire binary which means that, while the first PT_LOAD segment is mapped below mm-&amp;gt;mmap_base, the subsequent PT_LOAD segment(s) end up being mapped above mm-&amp;gt;mmap_base into the are that is supposed to be the &amp;#34;gap&amp;#34; between the stack and the binary.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Linux distributions that have not patched their long-term kernels with https://git.kernel.org/linus/a87938b2e246b81b4fb713edb371a9fa3c5c3c86 (committed on April 14, 2015). This kernel vulnerability was fixed in April 2015 by commit a87938b2e246b81b4fb713edb371a9fa3c5c3c86 (backported to Linux 3.10.77 in May 2015), but it was not recognized as a security threat. With CONFIG_ARCH_BINFMT_ELF_RANDOMIZE_PIE enabled, and a normal top-down address allocation strategy, load_elf_binary() will attempt to map a PIE binary into an address range immediately below mm-&amp;gt;mmap_base. Unfortunately, load_elf_ binary() does not take account of the need to allocate sufficient space for the entire binary which means that, while the first PT_LOAD segment is mapped below mm-&amp;gt;mmap_base, the subsequent PT_LOAD segment(s) end up being mapped above mm-&amp;gt;mmap_base into the are that is supposed to be the &amp;#34;gap&amp;#34; between the stack and the binary.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2017-1000253</guid>
    </item>
    <item>
      <title>GHSA-rm92-8pw8-34fm</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-rm92-8pw8-34fm</link>
      <description>&lt;p&gt;Linux distributions that have not patched their long-term kernels with https://git.kernel.org/linus/a87938b2e246b81b4fb713edb371a9fa3c5c3c86 (committed on April 14, 2015). This kernel vulnerability was fixed in April 2015 by commit a87938b2e246b81b4fb713edb371a9fa3c5c3c86 (backported to Linux 3.10.77 in May 2015), but it was not recognized as a security threat. With CONFIG_ARCH_BINFMT_ELF_RANDOMIZE_PIE enabled, and a normal top-down address allocation strategy, load_elf_binary() will attempt to map a PIE binary into an address range immediately below mm-&amp;gt;mmap_base. Unfortunately, load_elf_ binary() does not take account of the need to allocate sufficient space for the entire binary which means that, while the first PT_LOAD segment is mapped below mm-&amp;gt;mmap_base, the subsequent PT_LOAD segment(s) end up being mapped above mm-&amp;gt;mmap_base into the are that is supposed to be the &amp;#34;gap&amp;#34; between the stack and the binary.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Linux distributions that have not patched their long-term kernels with https://git.kernel.org/linus/a87938b2e246b81b4fb713edb371a9fa3c5c3c86 (committed on April 14, 2015). This kernel vulnerability was fixed in April 2015 by commit a87938b2e246b81b4fb713edb371a9fa3c5c3c86 (backported to Linux 3.10.77 in May 2015), but it was not recognized as a security threat. With CONFIG_ARCH_BINFMT_ELF_RANDOMIZE_PIE enabled, and a normal top-down address allocation strategy, load_elf_binary() will attempt to map a PIE binary into an address range immediately below mm-&amp;gt;mmap_base. Unfortunately, load_elf_ binary() does not take account of the need to allocate sufficient space for the entire binary which means that, while the first PT_LOAD segment is mapped below mm-&amp;gt;mmap_base, the subsequent PT_LOAD segment(s) end up being mapped above mm-&amp;gt;mmap_base into the are that is supposed to be the &amp;#34;gap&amp;#34; between the stack and the binary.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-rm92-8pw8-34fm</guid>
    </item>
    <item>
      <title>gsd-2017-1000253</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2017-1000253</link>
      <description>gsd-2017-1000253</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2017-1000253</guid>
    </item>
    <item>
      <title>RHSA-2017:1842 — Red Hat Security Advisory: kernel security, bug fix, and enhancement update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2017:1842</link>
      <description>&lt;p&gt;Kernel: fs: VFS denial of service Kernel: fs: umount denial of service kernel: ext4 filesystem page fault race condition with fallocate call. kernel: crypto: GPF in lrw_crypt caused by null-deref kernel: Overflowing kernel mount table using shared bind mount kernel: Stack corruption while reading /proc/keys when gcc stack protector is enabled kernel: Setting a POSIX ACL via setxattr doesn&amp;#39;t clear the setgid bit kernel: a BUG() statement can be hit in net/ipv4/tcp_input.c kernel: Use after free in SCSI generic device interface Kernel: kvm: nVMX: uncaught software exceptions in L1 guest leads to DoS kernel: security: The built-in keyrings for security tokens can be joined as a session and then modified by the root user kernel: Memory leaks in xfs_attr_list.c error paths kernel: netlink: double-free in netlink_dump kernel: Use after free in SCSI generic device interface (CVE-2016-9576 regression) kernel: Kernel crash by spawning mcrypt(alg) with incompatible algorithm kernel: l2tp: Race condition in the L2TPv3 IP encapsulation feature kernel: race condition between direct and memory-mapped I/O in fs/xfs/xfs_aops.c Kernel: kvm: use after free in complete_emulated_mmio Kernel: kvm: page reference leakage in handle_vmon kernel: Null pointer dereference in search_keyring kernel: ping socket / AF_LLC connect() sin_family race kernel: S_ISGD is not cleared when setting posix ACLs in tmpfs (CVE-2016-7097 incomplete fix) kernel: ipv4: Invalid IP options could cause skb-&amp;gt;dst drop kernel…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Kernel: fs: VFS denial of service Kernel: fs: umount denial of service kernel: ext4 filesystem page fault race condition with fallocate call. kernel: crypto: GPF in lrw_crypt caused by null-deref kernel: Overflowing kernel mount table using shared bind mount kernel: Stack corruption while reading /proc/keys when gcc stack protector is enabled kernel: Setting a POSIX ACL via setxattr doesn&amp;#39;t clear the setgid bit kernel: a BUG() statement can be hit in net/ipv4/tcp_input.c kernel: Use after free in SCSI generic device interface Kernel: kvm: nVMX: uncaught software exceptions in L1 guest leads to DoS kernel: security: The built-in keyrings for security tokens can be joined as a session and then modified by the root user kernel: Memory leaks in xfs_attr_list.c error paths kernel: netlink: double-free in netlink_dump kernel: Use after free in SCSI generic device interface (CVE-2016-9576 regression) kernel: Kernel crash by spawning mcrypt(alg) with incompatible algorithm kernel: l2tp: Race condition in the L2TPv3 IP encapsulation feature kernel: race condition between direct and memory-mapped I/O in fs/xfs/xfs_aops.c Kernel: kvm: use after free in complete_emulated_mmio Kernel: kvm: page reference leakage in handle_vmon kernel: Null pointer dereference in search_keyring kernel: ping socket / AF_LLC connect() sin_family race kernel: S_ISGD is not cleared when setting posix ACLs in tmpfs (CVE-2016-7097 incomplete fix) kernel: ipv4: Invalid IP options could cause skb-&amp;gt;dst drop kernel…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2017:1842</guid>
    </item>
    <item>
      <title>RHSA-2017:2793 — Red Hat Security Advisory: kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2017:2793</link>
      <description>&lt;p&gt;kernel: load_elf_ binary() does not take account of the need to allocate sufficient space for the entire binary&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: load_elf_ binary() does not take account of the need to allocate sufficient space for the entire binary&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2017:2793</guid>
    </item>
    <item>
      <title>SUSE-SU-2017:2723-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2017:2723-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-2017:2723-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2017-1000253</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2017-1000253</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:14.04:LTS: linux&lt;/p&gt;
&lt;p&gt;Linux distributions that have not patched their long-term kernels with https://git.kernel.org/linus/a87938b2e246b81b4fb713edb371a9fa3c5c3c86 (committed on April 14, 2015). This kernel vulnerability was fixed in April 2015 by commit a87938b2e246b81b4fb713edb371a9fa3c5c3c86 (backported to Linux 3.10.77 in May 2015), but it was not recognized as a security threat. With CONFIG_ARCH_BINFMT_ELF_RANDOMIZE_PIE enabled, and a normal top-down address allocation strategy, load_elf_binary() will attempt to map a PIE binary into an address range immediately below mm-&amp;gt;mmap_base. Unfortunately, load_elf_ binary() does not take account of the need to allocate sufficient space for the entire binary which means that, while the first PT_LOAD segment is mapped below mm-&amp;gt;mmap_base, the subsequent PT_LOAD segment(s) end up being mapped above mm-&amp;gt;mmap_base into the are that is supposed to be the &amp;#34;gap&amp;#34; between the stack and the binary.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:14.04:LTS: linux&lt;/p&gt;
&lt;p&gt;Linux distributions that have not patched their long-term kernels with https://git.kernel.org/linus/a87938b2e246b81b4fb713edb371a9fa3c5c3c86 (committed on April 14, 2015). This kernel vulnerability was fixed in April 2015 by commit a87938b2e246b81b4fb713edb371a9fa3c5c3c86 (backported to Linux 3.10.77 in May 2015), but it was not recognized as a security threat. With CONFIG_ARCH_BINFMT_ELF_RANDOMIZE_PIE enabled, and a normal top-down address allocation strategy, load_elf_binary() will attempt to map a PIE binary into an address range immediately below mm-&amp;gt;mmap_base. Unfortunately, load_elf_ binary() does not take account of the need to allocate sufficient space for the entire binary which means that, while the first PT_LOAD segment is mapped below mm-&amp;gt;mmap_base, the subsequent PT_LOAD segment(s) end up being mapped above mm-&amp;gt;mmap_base into the are that is supposed to be the &amp;#34;gap&amp;#34; between the stack and the binary.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2017-1000253</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-2078 — Linux Kernel: Schwachstelle ermöglicht Privilegieneskalation</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-2078</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann eine Schwachstelle im Linux Kernel ausnutzen, um seine Privilegien zu erhöhen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann eine Schwachstelle im Linux Kernel ausnutzen, um seine Privilegien zu erhöhen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-2078</guid>
    </item>
  </channel>
</rss>
