Bug 2363485 (CVE-2022-49897) - CVE-2022-49897 kernel: fscrypt: fix keyring memory leak on mount failure
Summary: CVE-2022-49897 kernel: fscrypt: fix keyring memory leak on mount failure
Keywords:
Status: NEW
Alias: CVE-2022-49897
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-01 15:06 UTC by OSIDB Bzimport
Modified: 2025-07-10 19:49 UTC (History)
4 users (show)

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


Attachments (Terms of Use)

Description OSIDB Bzimport 2025-05-01 15:06:37 UTC
In the Linux kernel, the following vulnerability has been resolved:

fscrypt: fix keyring memory leak on mount failure

Commit d7e7b9af104c ("fscrypt: stop using keyrings subsystem for
fscrypt_master_key") moved the keyring destruction from __put_super() to
generic_shutdown_super() so that the filesystem's block device(s) are
still available.  Unfortunately, this causes a memory leak in the case
where a mount is attempted with the test_dummy_encryption mount option,
but the mount fails after the option has already been processed.

To fix this, attempt the keyring destruction in both places.

Comment 1 Avinash Hanwate 2025-05-02 04:01:44 UTC
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2025050100-CVE-2022-49897-6af8@gregkh/T

Comment 4 TEJ RATHI 2025-05-29 06:41:55 UTC
This CVE has been rejected by the Linux kernel community. Refer to the announcement: https://lore.kernel.org/linux-cve-announce/2025050810-REJECTED-10a2@gregkh/

Comment added by: Automated Script


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