<?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>Mon, 28 Sep 2026 23:55:31 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-49256 — watch_queue: Actually free the watch</title>
      <link>https://db.gcve.eu/vuln/cve-2022-49256</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;watch_queue: Actually free the watch&lt;/p&gt;
&lt;p&gt;free_watch() does everything barring actually freeing the watch object.  Fix
this by adding the missing kfree.&lt;/p&gt;
&lt;p&gt;kmemleak produces a report something like the following.  Note that as an
address can be seen in the first word, the watch would appear to have gone
through call_rcu().&lt;/p&gt;
&lt;p&gt;BUG: memory leak
unreferenced object 0xffff88810ce4a200 (size 96):
  comm &amp;#34;syz-executor352&amp;#34;, pid 3605, jiffies 4294947473 (age 13.720s)
  hex dump (first 32 bytes):
    e0 82 48 0d 81 88 ff ff 00 00 00 00 00 00 00 00  ..H.............
    80 a2 e4 0c 81 88 ff ff 00 00 00 00 00 00 00 00  ................
  backtrace:
    [&amp;lt;ffffffff8214e6cc&amp;gt;] kmalloc include/linux/slab.h:581 [inline]
    [&amp;lt;ffffffff8214e6cc&amp;gt;] kzalloc include/linux/slab.h:714 [inline]
    [&amp;lt;ffffffff8214e6cc&amp;gt;] keyctl_watch_key+0xec/0x2e0 security/keys/keyctl.c:1800
    [&amp;lt;ffffffff8214ec84&amp;gt;] __do_sys_keyctl+0x3c4/0x490 security/keys/keyctl.c:2016
    [&amp;lt;ffffffff84493a25&amp;gt;] do_syscall_x64 arch/x86/entry/common.c:50 [inline]
    [&amp;lt;ffffffff84493a25&amp;gt;] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
    [&amp;lt;ffffffff84600068&amp;gt;] entry_SYSCALL_64_after_hwframe+0x44/0xae&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;watch_queue: Actually free the watch&lt;/p&gt;
&lt;p&gt;free_watch() does everything barring actually freeing the watch object.  Fix
this by adding the missing kfree.&lt;/p&gt;
&lt;p&gt;kmemleak produces a report something like the following.  Note that as an
address can be seen in the first word, the watch would appear to have gone
through call_rcu().&lt;/p&gt;
&lt;p&gt;BUG: memory leak
unreferenced object 0xffff88810ce4a200 (size 96):
  comm &amp;#34;syz-executor352&amp;#34;, pid 3605, jiffies 4294947473 (age 13.720s)
  hex dump (first 32 bytes):
    e0 82 48 0d 81 88 ff ff 00 00 00 00 00 00 00 00  ..H.............
    80 a2 e4 0c 81 88 ff ff 00 00 00 00 00 00 00 00  ................
  backtrace:
    [&amp;lt;ffffffff8214e6cc&amp;gt;] kmalloc include/linux/slab.h:581 [inline]
    [&amp;lt;ffffffff8214e6cc&amp;gt;] kzalloc include/linux/slab.h:714 [inline]
    [&amp;lt;ffffffff8214e6cc&amp;gt;] keyctl_watch_key+0xec/0x2e0 security/keys/keyctl.c:1800
    [&amp;lt;ffffffff8214ec84&amp;gt;] __do_sys_keyctl+0x3c4/0x490 security/keys/keyctl.c:2016
    [&amp;lt;ffffffff84493a25&amp;gt;] do_syscall_x64 arch/x86/entry/common.c:50 [inline]
    [&amp;lt;ffffffff84493a25&amp;gt;] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
    [&amp;lt;ffffffff84600068&amp;gt;] entry_SYSCALL_64_after_hwframe+0x44/0xae&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2022-49256</guid>
    </item>
  </channel>
</rss>
