CVE-2023-53055

fscrypt: destroy keyring after security_sb_delete()

MEDIUM
5.5
CVSS Score
Published: May 2, 2025 at 03:55 PM UTC
Updated: June 17, 2026 at 06:44 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.2%

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v ≥ 5.10.154v ≥ 6.0.85.10.154 ≤ v < 5.115.15.78 ≤ v < 5.15.1056.0.8 ≤ v < 6.16.0.8 ≤ v < 6.1.226.1 ≤ v < 6.1.226.1 ≤ v < 6.2.96.1 ≤ v < 6.36.2 ≤ v < 6.2.9391cceee6d435e616f68631e68f5b32d480b1e675.10.1545.15.786.0.86.16.3 rc16.3 rc26.3 rc368d15d6558a386f46d815a6ac39edecad713a1bfd7e7b9af104c7b389a0c21eb26532511bce4b510e6f4fd85ef1ee6ab356bfbd64df28c1cb73aee7e
Vendor states this is fixed in 497ab5d9c7852dfedab2c9de75e41b60e54b7c5d (fixed)
Vendor states this is fixed in 992a3f3e8a0c92151dfdf65fc85567c865fd558a (fixed)
Vendor states this is fixed in ccb820dc7d2236b1af0d54ae038a27b5b6d5ae5a (fixed)
Vendor states this is fixed in d77531fac6a1fd9f1db0195438ba5419d72b96c4 (fixed)
Affected range stops below 5.11, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 5.15.105 (unaffected)
Vendor states this is fixed in 6.1 (unaffected)
Vendor states this is fixed in 6.1.22 (unaffected)
Vendor states this is fixed in 6.2.9 (unaffected)
Vendor states this is fixed in 6.3 (unaffected)

References (4)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/497ab5d9c7852dfedab2c9de75e41b60e54b7c5d
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/992a3f3e8a0c92151dfdf65fc85567c865fd558a
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/ccb820dc7d2236b1af0d54ae038a27b5b6d5ae5a
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/d77531fac6a1fd9f1db0195438ba5419d72b96c4

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-476

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card