https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-23T21:52:00.999504+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/bdu:2025-06838 bdu:2025-06838 2026-10-23T21:52:01.155386+00:00 bdu:2025-06838 https://cve.radiocsirt.org/vuln/bell-cve-2023-53055 BELL-CVE-2023-53055 2026-10-23T21:52:01.155427+00:00

Affected: Alpaquita:stream: linux-lts

 https://cve.radiocsirt.org/vuln/euvd-2026-320450 EUVD-2026-320450 2026-10-23T21:52:01.155455+00:00 EUVD-2026-320450 https://cve.radiocsirt.org/vuln/fkie_cve-2023-53055 fkie_cve-2023-53055 2026-10-23T21:52:01.155468+00:00

In the Linux kernel, the following vulnerability has been resolved:

fscrypt: destroy keyring after security_sb_delete()

fscrypt_destroy_keyring() must be called after all potentially-encrypted inodes were evicted; otherwise it cannot safely destroy the keyring. Since inodes that are in-use by the Landlock LSM don't get evicted until security_sb_delete(), this means that fscrypt_destroy_keyring() must be called *after* security_sb_delete().

This fixes a WARN_ON followed by a NULL dereference, only possible if Landlock was being used on encrypted files.

 https://cve.radiocsirt.org/vuln/ghsa-77x5-pwh8-3qq8 GHSA-77x5-pwh8-3qq8 2026-10-23T21:52:01.155500+00:00

In the Linux kernel, the following vulnerability has been resolved:

fscrypt: destroy keyring after security_sb_delete()

fscrypt_destroy_keyring() must be called after all potentially-encrypted inodes were evicted; otherwise it cannot safely destroy the keyring. Since inodes that are in-use by the Landlock LSM don't get evicted until security_sb_delete(), this means that fscrypt_destroy_keyring() must be called *after* security_sb_delete().

This fixes a WARN_ON followed by a NULL dereference, only possible if Landlock was being used on encrypted files.

 https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-53055 UBUNTU-CVE-2023-53055 2026-10-23T21:52:01.155520+00:00

Affected: Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 100 more

In the Linux kernel, the following vulnerability has been resolved: fscrypt: destroy keyring after security_sb_delete() fscrypt_destroy_keyring() must be called after all potentially-encrypted inodes were evicted; otherwise it cannot safely destroy the keyring. Since inodes that are in-use by the Landlock LSM don't get evicted until security_sb_delete(), this means that fscrypt_destroy_keyring() must be called *after* security_sb_delete(). This fixes a WARN_ON followed by a NULL dereference, only possible if Landlock was being used on encrypted files.