CVE-2022-50477
published 2025-10-04CVE-2022-50477: In the Linux kernel, the following vulnerability has been resolved: rtc: class: Fix potential memleak in devm_rtc_allocate_device() devm_rtc_allocate_device()…
PriorityP420medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.14%
4.1th percentile
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:
[] kmalloc_trace+0x21/0x110
[] devm_rtc_allocate_device+0xd4/0x400
[] devm_rtc_device_register+0x1a/0x80
[] rx4581_probe+0xdd/0x110 [rtc_rx4581]
[] spi_probe+0xde/0x130
[] really_probe+0x175/0x3f0
[] __driver_probe_device+0xe6/0x170
[] device_driver_attach+0x32/0x80
[] bind_store+0x10b/0x1a0
[] drv_attr_store+0x49/0x70
[] sysfs_kf_write+0x8d/0xb0
[] kernfs_fop_write_iter+0x214/0x2d0
[] vfs_write+0x61a/0x7d0
[] ksys_write+0xc8/0x190
[] do_syscall_64+0x37/0x90
[] entry_SYSCALL_64_after_hwframe+0x63/0xcd
Affected
10 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.1.4-1 (bookworm) | linux 6.1.4-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= 24d23181e43d72ca692a479e70dfe5b0b5dd33f1 < 0bcfc8fd3e596994f527b46730579428b3a4fa5f | 0bcfc8fd3e596994f527b46730579428b3a4fa5f |
| linux | linux | >= 24d23181e43d72ca692a479e70dfe5b0b5dd33f1 < 59457a0f079eae19aaf322b3cc1c8ba66f55c5f3 | 59457a0f079eae19aaf322b3cc1c8ba66f55c5f3 |
| linux | linux | >= 24d23181e43d72ca692a479e70dfe5b0b5dd33f1 < 60da73808298ff2cfa9f165d55eb3d7aa7078601 | 60da73808298ff2cfa9f165d55eb3d7aa7078601 |
| linux | linux_kernel | >= 0 < 6.1.4-1 | 6.1.4-1 |
| linux | linux_kernel | >= 0 < 6.1.4-1 | 6.1.4-1 |
| linux | linux_kernel | >= 0 < 6.1.4-1 | 6.1.4-1 |
| linux | linux_kernel | >= 5.16 < 6.0.16 | 6.0.16 |
| linux | linux_kernel | >= 6.1 < 6.1.2 | 6.1.2 |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv5.5MEDIUM
vendor_debian5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
kernel: rtc: class: Fix potential memleak in devm_rtc_allocate_device()
vendor_redhat·2025-10-04·CVSS 5.5
CVE-2022-50477 [MEDIUM] CWE-772 kernel: rtc: class: Fix potential memleak in devm_rtc_allocate_device()
kernel: rtc: class: Fix potential memleak in devm_rtc_allocate_device()
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:
[] kmalloc_trace+0x21/0x110
[] devm_rtc_allocate_device+0xd4/0x400
[] devm_rtc_device_register+0
Debian
CVE-2022-50477: linux - In the Linux kernel, the following vulnerability has been resolved: rtc: class:...
vendor_debian·2022·CVSS 5.5
CVE-2022-50477 [MEDIUM] CVE-2022-50477: linux - In the Linux kernel, the following vulnerability has been resolved: rtc: class:...
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: [] kmalloc_trace+0x21/0x110 [] devm_rtc_allocate_device+0xd4/0x400 [] devm_rtc_device_register+0x1a/0x80 [] rx4581_probe+0xdd/0x110 [rtc_rx4581] [] spi_probe+0xde/0x130
GHSA
GHSA-wq62-9p2f-cfr9: In the Linux kernel, the following vulnerability has been resolved:
rtc: class: Fix potential memleak in devm_rtc_allocate_device()
devm_rtc_allocat
ghsa_unreviewed·2025-10-04
CVE-2022-50477 [MEDIUM] CWE-401 GHSA-wq62-9p2f-cfr9: In the Linux kernel, the following vulnerability has been resolved:
rtc: class: Fix potential memleak in devm_rtc_allocate_device()
devm_rtc_allocat
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:
[] kmalloc_trace+0x21/0x110
[] devm_rtc_allocate_device+0xd4/0x400
[] devm_rtc_device_register+0x1a/0x80
[] rx4581_probe+0xdd/0x110 [rtc_rx4581]
[] spi_probe+0xde/0x1
OSV
CVE-2022-50477: In the Linux kernel, the following vulnerability has been resolved: rtc: class: Fix potential memleak in devm_rtc_allocate_device() devm_rtc_allocate_
osv·2025-10-04·CVSS 5.5
CVE-2022-50477 [MEDIUM] CVE-2022-50477: In the Linux kernel, the following vulnerability has been resolved: rtc: class: Fix potential memleak in devm_rtc_allocate_device() devm_rtc_allocate_
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: [] kmalloc_trace+0x21/0x110 [] devm_rtc_allocate_device+0xd4/0x400 [] devm_rtc_device_register+0x1a/0x80 [] rx4581_probe+0xdd/0x110 [rtc_rx4581] [] spi_probe+0xde/0x130
No detection rules found.
No public exploits indexed.
2025-10-04
Published