This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.

Metrics

No CVSS v4.0

Attack Vector Local

Attack Complexity High

Privileges Required Low

Scope Unchanged

Confidentiality Impact High

Integrity Impact High

Availability Impact High

User Interaction None

No CVSS v3.0

No CVSS v2

This CVE is not in the KEV list.

No EPSS score available.

Key SSVC decision points have not yet been added.

Affected Vendors & Products

Vendors Products
Linux Subscribe
Linux Kernel Subscribe

No data.

No data.

OpenCVE Enrichment is a feature of OpenCVE that uses AI to automatically link vendors and products to CVEs. Learn more on GitHub.

Vendors Products
Linux Subscribe
Linux Kernel Subscribe
Advisories
Source ID Title
EUVD EUVD EUVD-2025-29983 This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
Fixes

Solution

No solution given by the vendor.

Workaround

No workaround given by the vendor.

References
Link Providers
https://lore.kernel.org/linux-cve-announce/2025091851-CVE-2022-50377-f43b@gregkh/T cve-icon
https://nvd.nist.gov/vuln/detail/CVE-2022-50377 cve-icon
https://www.cve.org/CVERecord?id=CVE-2022-50377 cve-icon
History

Fri, 19 Sep 2025 16:30:00 +0000

Type Values Removed Values Added
References

Fri, 19 Sep 2025 15:30:00 +0000

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: ext4: check and assert if marking an no_delete evicting inode dirty In ext4_evict_inode(), if we evicting an inode in the 'no_delete' path, it cannot be raced by another mark_inode_dirty(). If it happens, someone else may accidentally dirty it without holding inode refcount and probably cause use-after-free issues in the writeback procedure. It's indiscoverable and hard to debug, so add an WARN_ON_ONCE() to check and detect this issue in advance. This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
Title ext4: check and assert if marking an no_delete evicting inode dirty kernel: ext4: check and assert if marking an no_delete evicting inode dirty

Fri, 19 Sep 2025 09:45:00 +0000

Type Values Removed Values Added
First Time appeared Linux
Linux linux Kernel
Vendors & Products Linux
Linux linux Kernel

Fri, 19 Sep 2025 00:15:00 +0000

Type Values Removed Values Added
References
Metrics threat_severity

None

 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'}

threat_severity

Important

Thu, 18 Sep 2025 13:45:00 +0000

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: ext4: check and assert if marking an no_delete evicting inode dirty In ext4_evict_inode(), if we evicting an inode in the 'no_delete' path, it cannot be raced by another mark_inode_dirty(). If it happens, someone else may accidentally dirty it without holding inode refcount and probably cause use-after-free issues in the writeback procedure. It's indiscoverable and hard to debug, so add an WARN_ON_ONCE() to check and detect this issue in advance.
Title ext4: check and assert if marking an no_delete evicting inode dirty
References

Projects

Sign in to view the affected projects.

cve-icon MITRE

Status: REJECTED

Assigner: Linux

Published:

Updated: 2025-09-19T15:23:49.358Z

Reserved: 2025-09-17T14:53:06.996Z

Link: CVE-2022-50377

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Rejected

Published: 2025-09-18T14:15:36.397

Modified: 2025-09-19T16:15:40.350

Link: CVE-2022-50377

cve-icon Redhat

Severity : Important

Publid Date: 2025-09-18T00:00:00Z

Links: CVE-2022-50377 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2025-09-19T09:36:38Z

Weaknesses

No weakness.