CVE-2022-50377

kernel: ext4: check and assert if marking an no_delete evicting inode dirty

Published Sep 18, 2025 CVSS 3.1 · 7.0 High EPSS n/a KEV · Not listed

Description

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

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

No data.

No data available yet.

No remediation available yet

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

No CVSS v4.0

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.

References

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

History

Type	Values Removed	Values Added
References	https://git.kernel.org/stable/c/0c026f975d24701766cf4ac63995ead9f6d57a59 https://git.kernel.org/stable/c/318cdc822c63b6e2befcfdc2088378ae6fa18def https://git.kernel.org/stable/c/9020f56a3cad1c97b81c7dab2aa67027b59c8f73 https://git.kernel.org/stable/c/91009e361e8cb2cbd1dc9496cb5fb4f8de3f4b11 https://git.kernel.org/stable/c/f1ec687ebd1bf146333955b7e209d21508c3ba9f

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

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

Type	Values Removed	Values Added
References		https://lore.kernel.org/linux-cve-announce/2025091851-CVE-2022-50377-f43b@gregkh/T https://nvd.nist.gov/vuln/detail/CVE-2022-50377 https://www.cve.org/CVERecord?id=CVE-2022-50377
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`

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		https://git.kernel.org/stable/c/0c026f975d24701766cf4ac63995ead9f6d57a59 https://git.kernel.org/stable/c/318cdc822c63b6e2befcfdc2088378ae6fa18def https://git.kernel.org/stable/c/9020f56a3cad1c97b81c7dab2aa67027b59c8f73 https://git.kernel.org/stable/c/91009e361e8cb2cbd1dc9496cb5fb4f8de3f4b11 https://git.kernel.org/stable/c/f1ec687ebd1bf146333955b7e209d21508c3ba9f