CVE-2023-53055
published 2025-05-02CVE-2023-53055: In the Linux kernel, the following vulnerability has been resolved: fscrypt: destroy keyring after security_sb_delete() fscrypt_destroy_keyring() must be…
PriorityP419medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.19%
8.7th percentile
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
19 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.1.25-1 (bookworm) | linux 6.1.25-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | — | — |
| linux | linux | — | — |
| linux | linux | >= 5.10.154 < 5.11 | 5.11 |
| linux | linux | >= 5.15.78 < 5.15.105 | 5.15.105 |
| linux | linux | >= 6.0.8 < 6.1 | 6.1 |
| linux | linux | >= d7e7b9af104c7b389a0c21eb26532511bce4b510 < d77531fac6a1fd9f1db0195438ba5419d72b96c4 | d77531fac6a1fd9f1db0195438ba5419d72b96c4 |
| linux | linux | >= d7e7b9af104c7b389a0c21eb26532511bce4b510 < 497ab5d9c7852dfedab2c9de75e41b60e54b7c5d | 497ab5d9c7852dfedab2c9de75e41b60e54b7c5d |
| linux | linux | >= d7e7b9af104c7b389a0c21eb26532511bce4b510 < ccb820dc7d2236b1af0d54ae038a27b5b6d5ae5a | ccb820dc7d2236b1af0d54ae038a27b5b6d5ae5a |
| linux | linux | >= e6f4fd85ef1ee6ab356bfbd64df28c1cb73aee7e < 992a3f3e8a0c92151dfdf65fc85567c865fd558a | 992a3f3e8a0c92151dfdf65fc85567c865fd558a |
| linux | linux_kernel | — | — |
| linux | linux_kernel | >= 0 < 6.1.25-1 | 6.1.25-1 |
| linux | linux_kernel | >= 0 < 6.1.25-1 | 6.1.25-1 |
| linux | linux_kernel | >= 0 < 6.1.25-1 | 6.1.25-1 |
| linux | linux_kernel | >= 5.10.154 < 5.11 | 5.11 |
| linux | linux_kernel | >= 5.15.78 < 5.15.105 | 5.15.105 |
| linux | linux_kernel | >= 6.0.8 < 6.1.22 | 6.1.22 |
| linux | linux_kernel | >= 6.2 < 6.2.9 | 6.2.9 |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv5.5MEDIUM
vendor_debian5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-77x5-pwh8-3qq8: In the Linux kernel, the following vulnerability has been resolved:
fscrypt: destroy keyring after security_sb_delete()
fscrypt_destroy_keyring() mu
ghsa_unreviewed·2025-05-02
CVE-2023-53055 [MEDIUM] CWE-476 GHSA-77x5-pwh8-3qq8: In the Linux kernel, the following vulnerability has been resolved:
fscrypt: destroy keyring after security_sb_delete()
fscrypt_destroy_keyring() mu
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.
OSV
CVE-2023-53055: In the Linux kernel, the following vulnerability has been resolved: fscrypt: destroy keyring after security_sb_delete() fscrypt_destroy_keyring() must
osv·2025-05-02·CVSS 5.5
CVE-2023-53055 [MEDIUM] CVE-2023-53055: In the Linux kernel, the following vulnerability has been resolved: fscrypt: destroy keyring after security_sb_delete() fscrypt_destroy_keyring() must
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.
Red Hat
kernel: fscrypt: destroy keyring after security_sb_delete()
vendor_redhat·2025-05-02·CVSS 5.5
CVE-2023-53055 [MEDIUM] kernel: fscrypt: destroy keyring after security_sb_delete()
kernel: fscrypt: destroy keyring after security_sb_delete()
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.
Statement: A logic bug in the unmount sequence could lead to a NULL pointer dereference when encrypted inodes are used in conjunction with the Landlock Linux Security Module (LSM).
Debian
CVE-2023-53055: linux - In the Linux kernel, the following vulnerability has been resolved: fscrypt: de...
vendor_debian·2023·CVSS 5.5
CVE-2023-53055 [MEDIUM] CVE-2023-53055: linux - In the Linux kernel, the following vulnerability has been resolved: fscrypt: de...
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.
Scope: local
bookworm: resolved (fixed in 6.1.25-1)
bullseye: open
forky: resolved (fixed in 6.1.25-1)
sid: resolved (fixed in 6.1.25-1)
trixie: resolved (fixed in 6.1.25-1)
No detection rules found.
No public exploits indexed.
2025-05-02
Published