https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 30 Sep 2026 22:15:06 +0000 https://db.gcve.eu/vuln/cve-2026-93106 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>crash_dump: release keyring reference at the correct time</p> <p>restore_dm_crypt_keys_to_thread_keyring() gets a reference to the user keyring before restoring the saved dm-crypt keys.</p> <p>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.</p> <p>When more than five keys are restored, a refcount underflow/use-after-free warning can be triggered.</p> <p>The early error paths after lookup_user_key() also return without dropping the keyring reference.</p> <p>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.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>crash_dump: release keyring reference at the correct time</p> <p>restore_dm_crypt_keys_to_thread_keyring() gets a reference to the user keyring before restoring the saved dm-crypt keys.</p> <p>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.</p> <p>When more than five keys are restored, a refcount underflow/use-after-free warning can be triggered.</p> <p>The early error paths after lookup_user_key() also return without dropping the keyring reference.</p> <p>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.</p> https://db.gcve.eu/vuln/cve-2026-93106