Description
This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
Published: 2025-05-01
Score: 7.0 High
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Analysis and contextual insights are available on OpenCVE Cloud.

Remediation

No vendor fix or workaround currently provided.

Additional remediation guidance may be available on OpenCVE Cloud.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
EUVD EUVD EUVD-2025-12877 This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
History

Sat, 07 Jun 2025 03:00:00 +0000

Type Values Removed Values Added
Metrics cvssV3_1

{'score': 5.5, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}

 cvssV3_1

{'score': 7.0, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H'}

Thu, 08 May 2025 11:45:00 +0000

Type Values Removed Values Added
References

Thu, 08 May 2025 10:45:00 +0000

Type Values Removed Values Added
Description 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. This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
Title fscrypt: fix keyring memory leak on mount failure kernel: fscrypt: fix keyring memory leak on mount failure

Fri, 02 May 2025 14:00:00 +0000

Type Values Removed Values Added
References
Metrics threat_severity

None

 cvssV3_1

{'score': 5.5, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}

threat_severity

Moderate

Thu, 01 May 2025 14:30:00 +0000

Type Values Removed Values Added
Description 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.
Title fscrypt: fix keyring memory leak on mount failure
References

Subscriptions

No data.

cve-icon MITRE

Status: REJECTED

Assigner: Linux

Published:

Updated: 2025-05-08T10:24:05.564Z

Reserved: 2025-05-01T14:05:17.244Z

Link: CVE-2022-49897

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Rejected

Published: 2025-05-01T15:16:14.747

Modified: 2025-05-08T11:15:51.677

Link: CVE-2022-49897

cve-icon Redhat

Severity : Moderate

Publid Date: 2025-05-01T00:00:00Z

Links: CVE-2022-49897 - Bugzilla

cve-icon OpenCVE Enrichment

No data.

Weaknesses

No weakness.