# rtc: class: Fix potential memleak in devm_rtc_allocate_device()

CVE record · `CVE-2022-50477`

- **Identifiers:** `CVE-2022-50477`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 4 Oct 2025
- **Updated:** 5 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 4 Oct 2025, 15:16 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `24d23181e43d72ca692a479e70dfe5b0b5dd33f1 to before 0bcfc8fd3e596994f527b46730579428b3a4fa5f` (git)
  - affected: `24d23181e43d72ca692a479e70dfe5b0b5dd33f1 to before 59457a0f079eae19aaf322b3cc1c8ba66f55c5f3` (git)
  - affected: `24d23181e43d72ca692a479e70dfe5b0b5dd33f1 to before 60da73808298ff2cfa9f165d55eb3d7aa7078601` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `5.16`
  - unaffected: `before 5.16` (semver)
  - unaffected: `6.0.16 to 6.0.*, inclusive` (semver)
  - unaffected: `6.1.2 to 6.1.*, inclusive` (semver)
  - unaffected: `6.2 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Linux kernel versions from 5.16 up to the fixed releases have a memory leak in the rtc class function devm_rtc_allocate_device(): if setting the device name fails, the allocated device is never freed. The source gives few details on attacker access or impact. Upgrade to 6.0.16 or later in the 6.0 series, 6.1.2 or later in the 6.1 series, or 6.2 or later.

Written 16 Nov 2026.

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0016, the 4th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 4 Oct 2025, 15:16 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2022-50477)
- 4 Oct 2025, 16:15 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2022-50477)

## Sources

- [CVE List: CVE-2022-50477](https://www.cve.org/CVERecord?id=CVE-2022-50477)
- [NVD: CVE-2022-50477](https://nvd.nist.gov/vuln/detail/CVE-2022-50477)

### References from the CNA

- <https://git.kernel.org/stable/c/0bcfc8fd3e596994f527b46730579428b3a4fa5f>
- <https://git.kernel.org/stable/c/59457a0f079eae19aaf322b3cc1c8ba66f55c5f3>
- <https://git.kernel.org/stable/c/60da73808298ff2cfa9f165d55eb3d7aa7078601>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2022-50477>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2022-50477/>. Everything for agents: <https://agentprime.io/llms.txt>.
