<?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://db.gcve.eu</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>Thu, 19 Nov 2026 17:37:15 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-52444 — f2fs: fix to avoid dirent corruption</title>
      <link>https://db.gcve.eu/vuln/cve-2023-52444</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Siemens SIMATIC S7-1500 CPU 1518-4 PN/DP MFP, Siemens SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP, Siemens SIPLUS S7-1500 CPU 1518-4 PN/DP MFP&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;f2fs: fix to avoid dirent corruption&lt;/p&gt;
&lt;p&gt;As Al reported in link[1]:&lt;/p&gt;
&lt;p&gt;f2fs_rename()
...
	if (old_dir != new_dir &amp;amp;&amp;amp; !whiteout)
		f2fs_set_link(old_inode, old_dir_entry,
					old_dir_page, new_dir);
	else
		f2fs_put_page(old_dir_page, 0);&lt;/p&gt;
&lt;p&gt;You want correct inumber in the &amp;#34;..&amp;#34; link.  And cross-directory
rename does move the source to new parent, even if you&amp;#39;d been asked
to leave a whiteout in the old place.&lt;/p&gt;
&lt;p&gt;[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/&lt;/p&gt;
&lt;p&gt;With below testcase, it may cause dirent corruption, due to it missed
to call f2fs_set_link() to update &amp;#34;..&amp;#34; link to new directory.
- mkdir -p dir/foo
- renameat2 -w dir/foo bar&lt;/p&gt;
&lt;p&gt;[ASSERT] (__chk_dots_dentries:1421)  --&amp;gt; Bad inode number[0x4] for &amp;#39;..&amp;#39;, parent parent ino is [0x3]
[FSCK] other corrupted bugs                           [Fail]&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Siemens SIMATIC S7-1500 CPU 1518-4 PN/DP MFP, Siemens SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP, Siemens SIPLUS S7-1500 CPU 1518-4 PN/DP MFP&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;f2fs: fix to avoid dirent corruption&lt;/p&gt;
&lt;p&gt;As Al reported in link[1]:&lt;/p&gt;
&lt;p&gt;f2fs_rename()
...
	if (old_dir != new_dir &amp;amp;&amp;amp; !whiteout)
		f2fs_set_link(old_inode, old_dir_entry,
					old_dir_page, new_dir);
	else
		f2fs_put_page(old_dir_page, 0);&lt;/p&gt;
&lt;p&gt;You want correct inumber in the &amp;#34;..&amp;#34; link.  And cross-directory
rename does move the source to new parent, even if you&amp;#39;d been asked
to leave a whiteout in the old place.&lt;/p&gt;
&lt;p&gt;[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/&lt;/p&gt;
&lt;p&gt;With below testcase, it may cause dirent corruption, due to it missed
to call f2fs_set_link() to update &amp;#34;..&amp;#34; link to new directory.
- mkdir -p dir/foo
- renameat2 -w dir/foo bar&lt;/p&gt;
&lt;p&gt;[ASSERT] (__chk_dots_dentries:1421)  --&amp;gt; Bad inode number[0x4] for &amp;#39;..&amp;#39;, parent parent ino is [0x3]
[FSCK] other corrupted bugs                           [Fail]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2023-52444</guid>
    </item>
    <item>
      <title>USN-6688-1 — linux-oem-6.1 vulnerabilities</title>
      <link>https://db.gcve.eu/vuln/usn-6688-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:22.04:LTS: linux-oem-6.1&lt;/p&gt;
&lt;p&gt;Pratyush Yadav discovered that the Xen network backend implementation in
the Linux kernel did not properly handle zero length data request, leading
to a null pointer dereference vulnerability. An attacker in a guest VM
could possibly use this to cause a denial of service (host domain crash).
(CVE-2023-46838)&lt;/p&gt;
&lt;p&gt;It was discovered that the Habana&amp;#39;s AI Processors driver in the Linux
kernel did not properly initialize certain data structures before passing
them to user space. A local attacker could use this to expose sensitive
information (kernel memory). (CVE-2023-50431)&lt;/p&gt;
&lt;p&gt;Murray McAllister discovered that the VMware Virtual GPU DRM driver in the
Linux kernel did not properly handle memory objects when storing surfaces,
leading to a use-after-free vulnerability. A local attacker in a guest VM
could use this to cause a denial of service (system crash) or possibly
execute arbitrary code. (CVE-2023-5633)&lt;/p&gt;
&lt;p&gt;It was discovered that the CIFS network file system implementation in the
Linux kernel did not properly validate certain SMB messages, leading to an
out-of-bounds read vulnerability. An attacker could use this to cause a
denial of service (system crash) or possibly expose sensitive information.
(CVE-2023-6610)&lt;/p&gt;
&lt;p&gt;It was discovered that the VirtIO subsystem in the Linux kernel did not
properly initialize memory in some situations. A local attacker could use
this to possibly expose sensitive information (kernel memory).
(CVE-2024-0340)&lt;/p&gt;
&lt;p&gt;Lonial Con discovered that the netfilter subsystem…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:22.04:LTS: linux-oem-6.1&lt;/p&gt;
&lt;p&gt;Pratyush Yadav discovered that the Xen network backend implementation in
the Linux kernel did not properly handle zero length data request, leading
to a null pointer dereference vulnerability. An attacker in a guest VM
could possibly use this to cause a denial of service (host domain crash).
(CVE-2023-46838)&lt;/p&gt;
&lt;p&gt;It was discovered that the Habana&amp;#39;s AI Processors driver in the Linux
kernel did not properly initialize certain data structures before passing
them to user space. A local attacker could use this to expose sensitive
information (kernel memory). (CVE-2023-50431)&lt;/p&gt;
&lt;p&gt;Murray McAllister discovered that the VMware Virtual GPU DRM driver in the
Linux kernel did not properly handle memory objects when storing surfaces,
leading to a use-after-free vulnerability. A local attacker in a guest VM
could use this to cause a denial of service (system crash) or possibly
execute arbitrary code. (CVE-2023-5633)&lt;/p&gt;
&lt;p&gt;It was discovered that the CIFS network file system implementation in the
Linux kernel did not properly validate certain SMB messages, leading to an
out-of-bounds read vulnerability. An attacker could use this to cause a
denial of service (system crash) or possibly expose sensitive information.
(CVE-2023-6610)&lt;/p&gt;
&lt;p&gt;It was discovered that the VirtIO subsystem in the Linux kernel did not
properly initialize memory in some situations. A local attacker could use
this to possibly expose sensitive information (kernel memory).
(CVE-2024-0340)&lt;/p&gt;
&lt;p&gt;Lonial Con discovered that the netfilter subsystem…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/usn-6688-1</guid>
    </item>
  </channel>
</rss>
