Bug 2363730 (CVE-2023-53055) - CVE-2023-53055 kernel: fscrypt: destroy keyring after security_sb_delete()
Summary: CVE-2023-53055 kernel: fscrypt: destroy keyring after security_sb_delete()
Keywords:
Status: NEW
Alias: CVE-2023-53055
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-05-02 16:03 UTC by OSIDB Bzimport
Modified: 2025-05-05 04:49 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2025-05-02 16:03:32 UTC
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.

Comment 1 Avinash Hanwate 2025-05-05 04:44:21 UTC
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2025050207-CVE-2023-53055-afd1@gregkh/T


Note You need to log in before you can comment on or make changes to this bug.