Loading story…
CVE-2021-47455 is a low-severity Linux kernel memory leak in the Precision Time Protocol (PTP) subsystem. If posix_clock_register() fails during ptp_clock_register(), a device name allocated through dev_set_name() can remain unreleased. The flaw, in drivers/ptp/ptp_clock.c, was introduced in Linux 5.5 and is resolved by calling put_device(), enabling cleanup routines to release the device name and associated memory.
The upstream fix is included in Linux 5.14.15 and 5.15, with affected stable branches receiving backports. Red Hat rated the issue CVSS 3.1 5.1 and delivered RHEL 8 kernel and kernel-rt fixes through RHSA-2024:7000 and RHSA-2024:7001; RHEL 9 kernel packages were fixed previously, while the RHEL 9 kernel-rt fix remains deferred. Organizations should deploy current vendor-supported kernel updates rather than cherry-picking the individual patch.
See affected versions and whether adversaries are exploiting it.
6 events from the most recent confirmed update back to the earliest known activity.
Red Hat issued RHSA-2024:7000 for the RHEL 8 kernel and RHSA-2024:7001 for the RHEL 8 kernel-rt package, remediating CVE-2021-47455.
Red Hat recorded CVE-2021-47455 as Bug 2282903, classifying the Linux kernel PTP memory-leak issue as low priority and low severity.
Red Hat released RHSA-2022:8267 to remediate CVE-2021-47455 in the Red Hat Enterprise Linux 9 kernel.
The issue was fixed in Linux kernel versions 5.14.15 and 5.15, including through commits 95c0a0c5ec88 and 4225fea1cb28. Fixes were also backported to several older stable branches.
The Linux kernel CVE team assigned CVE-2021-47455 to the PTP ptp_clock_register() memory-leak issue. The remediation adds put_device() on the registration-error path so cleanup routines can release the device name and associated PTP-clock resources.
The PTP clock-registration memory leak in drivers/ptp/ptp_clock.c was introduced in Linux 5.5 by commit a33121e5487b. On an error from posix_clock_register(), the affected path failed to release a device name allocated through dev_set_name().
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
3 references tracked. Mallory keeps watching after this page renders.
bugzilla.redhat.com
Open sourceredhat.com
Open sourcelore.kernel.org
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Red Hat addressed **CVE-2021-47287**, a Linux kernel driver-core flaw in `drivers/base/auxiliary.c` that leaks memory when `driver_register()` fails. In the affected `__auxiliary_driver_register()` path, memory allocated for `auxdrv->driver.name` was not released before the function returned, creating a local denial-of-service risk through resource exhaustion. Red Hat assigns the issue a CVSS 3.1 score of 5.5 (medium), with low-privilege local access required and availability as the affected security property. The defect was introduced in Linux kernel 5.11 and fixed upstream in versions 5.13.6 and 5.14. Red Hat released fixes for affected RHEL 8 `kernel` and `kernel-rt` packages through **RHSA-2024:7000** and **RHSA-2024:7001**; RHEL 6, 7, and 9 kernel variants are listed as not affected. Organizations running affected RHEL 8 systems should apply the advisory updates and reboot into the updated kernel; upstream recommends using the latest stable kernel release rather than cherry-picking the patch.
Aug 26, 2026
**CVE-2021-47466** affects the Linux kernel's SLUB allocator in `mm/slub.c`, where the error path in `kmem_cache_open()` can fail to release a cache's `random_seq` resource after initialization fails. Introduced in kernel version 4.8, the flaw can cause a memory leak and potentially degrade system availability. It carries a CVSS v3.1 score of 5.5 and requires local access with low privileges. Upstream fixes are available in kernel versions 5.4.156, 5.10.76, 5.14.15, and 5.15 and later; the Linux kernel CVE team recommends deploying a current stable kernel rather than backporting an individual patch. Red Hat remediated affected RHEL 8 kernel and `kernel-rt` packages through advisories **RHSA-2024:7000** and **RHSA-2024:7001**. RHEL 9 and its real-time kernel are not affected, while unsupported RHEL 6 and 7 deployments should be treated as potentially vulnerable unless separately mitigated or upgraded.
Aug 26, 2026
A **double-free vulnerability** tracked as `CVE-2026-52993` was disclosed in the Linux kernel's Transparent Inter-Process Communication (**TIPC**) subsystem, specifically in `tipc_buf_append()` within `net/tipc/msg.c`. The bug occurs when `tipc_msg_validate()` reallocates a socket buffer, frees the original buffer, and subsequent error handling frees the stale pointer again, creating conditions for **system instability, denial of service, and possible arbitrary code execution** in some scenarios. The flaw affects code introduced in kernel `4.15`, and the Linux kernel CVE team said it was fixed across multiple stable and mainline branches. Red Hat rated the issue **Important** with a **CVSS v3 score of 7.0** and said fixes were released through security errata for **Red Hat Enterprise Linux 8, 9, and 10** kernel packages. At the time of Red Hat's advisory, **RHEL 9 `kernel-rt`** remained affected, while **RHEL 6 and 7** kernel variants were not impacted because the vulnerable code was absent. Upstream maintainers advised organizations to update to the latest stable kernel releases rather than cherry-picking individual patches.
Aug 25, 2026