<?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>Tue, 29 Sep 2026 19:33:49 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-50477 — rtc: class: Fix potential memleak in devm_rtc_allocate_device()</title>
      <link>https://db.gcve.eu/vuln/cve-2022-50477</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;rtc: class: Fix potential memleak in devm_rtc_allocate_device()&lt;/p&gt;
&lt;p&gt;devm_rtc_allocate_device() will alloc a rtc_device first, and then run
dev_set_name(). If dev_set_name() failed, the rtc_device will memleak.
Move devm_add_action_or_reset() in front of dev_set_name() to prevent
memleak.&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff888110a53000 (size 2048):
  comm &amp;#34;python3&amp;#34;, pid 470, jiffies 4296078308 (age 58.882s)
  hex dump (first 32 bytes):
    00 00 00 00 00 00 00 00 08 30 a5 10 81 88 ff ff  .........0......
    08 30 a5 10 81 88 ff ff 00 00 00 00 00 00 00 00  .0..............
  backtrace:
    [&amp;lt;000000004aac0364&amp;gt;] kmalloc_trace+0x21/0x110
    [&amp;lt;000000000ff02202&amp;gt;] devm_rtc_allocate_device+0xd4/0x400
    [&amp;lt;000000001bdf5639&amp;gt;] devm_rtc_device_register+0x1a/0x80
    [&amp;lt;00000000351bf81c&amp;gt;] rx4581_probe+0xdd/0x110 [rtc_rx4581]
    [&amp;lt;00000000f0eba0ae&amp;gt;] spi_probe+0xde/0x130
    [&amp;lt;00000000bff89ee8&amp;gt;] really_probe+0x175/0x3f0
    [&amp;lt;00000000128e8d84&amp;gt;] __driver_probe_device+0xe6/0x170
    [&amp;lt;00000000ee5bf913&amp;gt;] device_driver_attach+0x32/0x80
    [&amp;lt;00000000f3f28f92&amp;gt;] bind_store+0x10b/0x1a0
    [&amp;lt;000000009ff812d8&amp;gt;] drv_attr_store+0x49/0x70
    [&amp;lt;000000008139c323&amp;gt;] sysfs_kf_write+0x8d/0xb0
    [&amp;lt;00000000b6146e01&amp;gt;] kernfs_fop_write_iter+0x214/0x2d0
    [&amp;lt;00000000ecbe3895&amp;gt;] vfs_write+0x61a/0x7d0
    [&amp;lt;00000000aa2196ea&amp;gt;] ksys_write+0xc8/0x190
    [&amp;lt;0000000046a600f5&amp;gt;] do_syscall_64+0x37/0x90
    [&amp;lt;00000000541a336f&amp;gt;] entry_SYSCALL_64_after_hwframe+…&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;rtc: class: Fix potential memleak in devm_rtc_allocate_device()&lt;/p&gt;
&lt;p&gt;devm_rtc_allocate_device() will alloc a rtc_device first, and then run
dev_set_name(). If dev_set_name() failed, the rtc_device will memleak.
Move devm_add_action_or_reset() in front of dev_set_name() to prevent
memleak.&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff888110a53000 (size 2048):
  comm &amp;#34;python3&amp;#34;, pid 470, jiffies 4296078308 (age 58.882s)
  hex dump (first 32 bytes):
    00 00 00 00 00 00 00 00 08 30 a5 10 81 88 ff ff  .........0......
    08 30 a5 10 81 88 ff ff 00 00 00 00 00 00 00 00  .0..............
  backtrace:
    [&amp;lt;000000004aac0364&amp;gt;] kmalloc_trace+0x21/0x110
    [&amp;lt;000000000ff02202&amp;gt;] devm_rtc_allocate_device+0xd4/0x400
    [&amp;lt;000000001bdf5639&amp;gt;] devm_rtc_device_register+0x1a/0x80
    [&amp;lt;00000000351bf81c&amp;gt;] rx4581_probe+0xdd/0x110 [rtc_rx4581]
    [&amp;lt;00000000f0eba0ae&amp;gt;] spi_probe+0xde/0x130
    [&amp;lt;00000000bff89ee8&amp;gt;] really_probe+0x175/0x3f0
    [&amp;lt;00000000128e8d84&amp;gt;] __driver_probe_device+0xe6/0x170
    [&amp;lt;00000000ee5bf913&amp;gt;] device_driver_attach+0x32/0x80
    [&amp;lt;00000000f3f28f92&amp;gt;] bind_store+0x10b/0x1a0
    [&amp;lt;000000009ff812d8&amp;gt;] drv_attr_store+0x49/0x70
    [&amp;lt;000000008139c323&amp;gt;] sysfs_kf_write+0x8d/0xb0
    [&amp;lt;00000000b6146e01&amp;gt;] kernfs_fop_write_iter+0x214/0x2d0
    [&amp;lt;00000000ecbe3895&amp;gt;] vfs_write+0x61a/0x7d0
    [&amp;lt;00000000aa2196ea&amp;gt;] ksys_write+0xc8/0x190
    [&amp;lt;0000000046a600f5&amp;gt;] do_syscall_64+0x37/0x90
    [&amp;lt;00000000541a336f&amp;gt;] entry_SYSCALL_64_after_hwframe+…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2022-50477</guid>
    </item>
  </channel>
</rss>
