CVE-2021-47455
published 2024-05-22CVE-2021-47455: In the Linux kernel, the following vulnerability has been resolved: ptp: Fix possible memory leak in ptp_clock_register() I got memory leak as follows when…
PriorityP417medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.24%
14.8th percentile
In the Linux kernel, the following vulnerability has been resolved:
ptp: Fix possible memory leak in ptp_clock_register()
I got memory leak as follows when doing fault injection test:
unreferenced object 0xffff88800906c618 (size 8):
comm "i2c-idt82p33931", pid 4421, jiffies 4294948083 (age 13.188s)
hex dump (first 8 bytes):
70 74 70 30 00 00 00 00 ptp0....
backtrace:
[] __kmalloc_track_caller+0x19f/0x3a0
[] kvasprintf+0xb5/0x150
[] kvasprintf_const+0x60/0x190
[] kobject_set_name_vargs+0x56/0x150
[] dev_set_name+0xc0/0x100
[] ptp_clock_register+0x9f4/0xd30 [ptp]
[] idt82p33_probe.cold+0x8b6/0x1561 [ptp_idt82p33]
When posix_clock_register() returns an error, the name allocated
in dev_set_name() will be leaked, the put_device() should be used
to give up the device reference, then the name will be freed in
kobject_cleanup() and other memory will be freed in ptp_clock_release().
Affected
28 ranges· showing 25
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 5.14.16-1 (bookworm) | linux 5.14.16-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | — | — |
| linux | linux | — | — |
| linux | linux | — | — |
| linux | linux | — | — |
| linux | linux | — | — |
| linux | linux | — | — |
| linux | linux | >= 3.16.83 < 3.17 | 3.17 |
| linux | linux | >= 4.14.162 < 4.15 | 4.15 |
| linux | linux | >= 4.19.93 < 4.20 | 4.20 |
| linux | linux | >= 4.4.224 < 4.5 | 4.5 |
| linux | linux | >= 4.9.224 < 4.10 | 4.10 |
| linux | linux | >= 5.4.8 < 5.5 | 5.5 |
| linux | linux | >= a33121e5487b424339636b25c35d3a180eaa5f5e < f1c96d8085588e1b997a96214b409ac3be20b524 | f1c96d8085588e1b997a96214b409ac3be20b524 |
| linux | linux | >= a33121e5487b424339636b25c35d3a180eaa5f5e < 95c0a0c5ec8839f8f21672be786e87a100319ca8 | 95c0a0c5ec8839f8f21672be786e87a100319ca8 |
| linux | linux | >= a33121e5487b424339636b25c35d3a180eaa5f5e < 4225fea1cb28370086e17e82c0f69bec2779dca0 | 4225fea1cb28370086e17e82c0f69bec2779dca0 |
| linux | linux_kernel | — | — |
| linux | linux_kernel | >= 0 < 5.10.244-1 | 5.10.244-1 |
| linux | linux_kernel | >= 0 < 5.14.16-1 | 5.14.16-1 |
| linux | linux_kernel | >= 0 < 5.14.16-1 | 5.14.16-1 |
| linux | linux_kernel | >= 0 < 5.14.16-1 | 5.14.16-1 |
| linux | linux_kernel | >= 3.16.83 < 3.17 | 3.17 |
| linux | linux_kernel | >= 4.14.162 < 4.15 | 4.15 |
| linux | linux_kernel | >= 4.19.93 < 4.20 | 4.20 |
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: ptp: Fix possible memory leak in ptp_clock_register()
vendor_redhat·2024-05-22·CVSS 5.5
CVE-2021-47455 [MEDIUM] kernel: ptp: Fix possible memory leak in ptp_clock_register()
kernel: ptp: Fix possible memory leak in ptp_clock_register()
In the Linux kernel, the following vulnerability has been resolved:
ptp: Fix possible memory leak in ptp_clock_register()
I got memory leak as follows when doing fault injection test:
unreferenced object 0xffff88800906c618 (size 8):
comm "i2c-idt82p33931", pid 4421, jiffies 4294948083 (age 13.188s)
hex dump (first 8 bytes):
70 74 70 30 00 00 00 00 ptp0....
backtrace:
[] __kmalloc_track_caller+0x19f/0x3a0
[] kvasprintf+0xb5/0x150
[] kvasprintf_const+0x60/0x190
[] kobject_set_name_vargs+0x56/0x150
[] dev_set_name+0xc0/0x100
[] ptp_clock_register+0x9f4/0xd30 [ptp]
[] idt82p33_probe.cold+0x8b6/0x1561 [ptp_idt82p33]
When posix_clock_register() returns an error, the name allocated
in dev_set_name() will be leaked, the put_device() sh
Debian
CVE-2021-47455: linux - In the Linux kernel, the following vulnerability has been resolved: ptp: Fix po...
vendor_debian·2021·CVSS 5.5
CVE-2021-47455 [MEDIUM] CVE-2021-47455: linux - In the Linux kernel, the following vulnerability has been resolved: ptp: Fix po...
In the Linux kernel, the following vulnerability has been resolved: ptp: Fix possible memory leak in ptp_clock_register() I got memory leak as follows when doing fault injection test: unreferenced object 0xffff88800906c618 (size 8): comm "i2c-idt82p33931", pid 4421, jiffies 4294948083 (age 13.188s) hex dump (first 8 bytes): 70 74 70 30 00 00 00 00 ptp0.... backtrace: [] __kmalloc_track_caller+0x19f/0x3a0 [] kvasprintf+0xb5/0x150 [] kvasprintf_const+0x60/0x190 [] kobject_set_name_vargs+0x56/0x150 [] dev_set_name+0xc0/0x100 [] ptp_clock_register+0x9f4/0xd30 [ptp] [] idt82p33_probe.cold+0x8b6/0x1561 [ptp_idt82p33] When posix_clock_register() returns an error, the name allocated in dev_set_name() will be leaked, the put_device() should be used to give up the device reference, then the name wil
OSV
CVE-2021-47455: In the Linux kernel, the following vulnerability has been resolved: ptp: Fix possible memory leak in ptp_clock_register() I got memory leak as follows
osv·2024-05-22·CVSS 5.5
CVE-2021-47455 [MEDIUM] CVE-2021-47455: In the Linux kernel, the following vulnerability has been resolved: ptp: Fix possible memory leak in ptp_clock_register() I got memory leak as follows
In the Linux kernel, the following vulnerability has been resolved: ptp: Fix possible memory leak in ptp_clock_register() I got memory leak as follows when doing fault injection test: unreferenced object 0xffff88800906c618 (size 8): comm "i2c-idt82p33931", pid 4421, jiffies 4294948083 (age 13.188s) hex dump (first 8 bytes): 70 74 70 30 00 00 00 00 ptp0.... backtrace: [] __kmalloc_track_caller+0x19f/0x3a0 [] kvasprintf+0xb5/0x150 [] kvasprintf_const+0x60/0x190 [] kobject_set_name_vargs+0x56/0x150 [] dev_set_name+0xc0/0x100 [] ptp_clock_register+0x9f4/0xd30 [ptp] [] idt82p33_probe.cold+0x8b6/0x1561 [ptp_idt82p33] When posix_clock_register() returns an error, the name allocated in dev_set_name() will be leaked, the put_device() should be used to give up the device reference, then the name wil
GHSA
GHSA-2r2x-3jh4-chhv: In the Linux kernel, the following vulnerability has been resolved:
ptp: Fix possible memory leak in ptp_clock_register()
I got memory leak as follo
ghsa_unreviewed·2024-05-22
CVE-2021-47455 [MEDIUM] CWE-401 GHSA-2r2x-3jh4-chhv: In the Linux kernel, the following vulnerability has been resolved:
ptp: Fix possible memory leak in ptp_clock_register()
I got memory leak as follo
In the Linux kernel, the following vulnerability has been resolved:
ptp: Fix possible memory leak in ptp_clock_register()
I got memory leak as follows when doing fault injection test:
unreferenced object 0xffff88800906c618 (size 8):
comm "i2c-idt82p33931", pid 4421, jiffies 4294948083 (age 13.188s)
hex dump (first 8 bytes):
70 74 70 30 00 00 00 00 ptp0....
backtrace:
[] __kmalloc_track_caller+0x19f/0x3a0
[] kvasprintf+0xb5/0x150
[] kvasprintf_const+0x60/0x190
[] kobject_set_name_vargs+0x56/0x150
[] dev_set_name+0xc0/0x100
[] ptp_clock_register+0x9f4/0xd30 [ptp]
[] idt82p33_probe.cold+0x8b6/0x1561 [ptp_idt82p33]
When posix_clock_register() returns an error, the name allocated
in dev_set_name() will be leaked, the put_device() should be used
to give up the device reference, then the name
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/4225fea1cb28370086e17e82c0f69bec2779dca0https://git.kernel.org/stable/c/95c0a0c5ec8839f8f21672be786e87a100319ca8https://git.kernel.org/stable/c/f1c96d8085588e1b997a96214b409ac3be20b524https://git.kernel.org/stable/c/4225fea1cb28370086e17e82c0f69bec2779dca0https://git.kernel.org/stable/c/95c0a0c5ec8839f8f21672be786e87a100319ca8https://lists.debian.org/debian-lts-announce/2025/10/msg00007.html
2024-05-22
Published