rtc: class: Fix potential memleak in devm_rtc_allocate_device()

Description

In the Linux kernel, the following vulnerability has been resolved: rtc: class: Fix potential memleak in devm_rtc_allocate_device() 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. unreferenced object 0xffff888110a53000 (size 2048): comm "python3", 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: [<000000004aac0364>] kmalloc_trace+0x21/0x110 [<000000000ff02202>] devm_rtc_allocate_device+0xd4/0x400 [<000000001bdf5639>] devm_rtc_device_register+0x1a/0x80 [<00000000351bf81c>] rx4581_probe+0xdd/0x110 [rtc_rx4581] [<00000000f0eba0ae>] spi_probe+0xde/0x130 [<00000000bff89ee8>] really_probe+0x175/0x3f0 [<00000000128e8d84>] __driver_probe_device+0xe6/0x170 [<00000000ee5bf913>] device_driver_attach+0x32/0x80 [<00000000f3f28f92>] bind_store+0x10b/0x1a0 [<000000009ff812d8>] drv_attr_store+0x49/0x70 [<000000008139c323>] sysfs_kf_write+0x8d/0xb0 [<00000000b6146e01>] kernfs_fop_write_iter+0x214/0x2d0 [<00000000ecbe3895>] vfs_write+0x61a/0x7d0 [<00000000aa2196ea>] ksys_write+0xc8/0x190 [<0000000046a600f5>] do_syscall_64+0x37/0x90 [<00000000541a336f>] entry_SYSCALL_64_after_hwframe+0x63/0xcd

Scores

EPSS (exploitation in 30 days)

0.16% · top 95% of all CVEs (6 Nov 2026)

CISA SSVC

Exploitation: none · Automatable: no · Technical impact: partial

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Weakness

• CWE-401 (opens in a new tab)All about CWE-401 and its CVEs

Affected products

• Linux · Linux

  • affected 24d23181e43d72ca692a479e70dfe5b0b5dd33f1 – < 0bcfc8fd3e596994f527b46730579428b3a4fa5f
  • affected 24d23181e43d72ca692a479e70dfe5b0b5dd33f1 – < 59457a0f079eae19aaf322b3cc1c8ba66f55c5f3
  • affected 24d23181e43d72ca692a479e70dfe5b0b5dd33f1 – < 60da73808298ff2cfa9f165d55eb3d7aa7078601

• Linux · Linux

  • affected 5.16
  • unaffected < 5.16
  • unaffected 6.0.16 – ≤ 6.0.*
  • unaffected 6.1.2 – ≤ 6.1.*
  • unaffected 6.2 – ≤ *

References (3)

• https://git.kernel.org/stable/c/0bcfc8fd3e596994f527b46730579428b3a4fa5f (opens in a new tab)
• https://git.kernel.org/stable/c/59457a0f079eae19aaf322b3cc1c8ba66f55c5f3 (opens in a new tab)
• https://git.kernel.org/stable/c/60da73808298ff2cfa9f165d55eb3d7aa7078601 (opens in a new tab)

Sources

The same CVE in the primary databases and aggregators, to check against.

• CVE.org record (opens in a new tab)
• CVE List JSON (GitHub) (opens in a new tab)
• NVD (opens in a new tab)
• FIRST EPSS (opens in a new tab)
• OSV.dev (opens in a new tab)
• GitHub Advisories (opens in a new tab)
• CIRCL Vulnerability-Lookup (opens in a new tab)

Badge for a README or a ticket

[![CVE-2022-50477](https://trackcve.app/badge/CVE-2022-50477.svg)](https://trackcve.app/cve/CVE-2022-50477)

Record last updated 5 Nov 2026, 20:20 UTC.