Local system crash via checkpoint warning mishandling
Published Oct 7, 2025 · Updated Oct 7, 2025
Improper warning handling in Linux kernel 2.6.30 through 6.0.1 allows local users to crash the system via corrupted NILFS2 metadata. The nilfs_segctor_create_checkpoint and nilfs_segctor_fill_in_checkpoint functions invoke WARN_ON for corruption-related checkpoint acquisition errors instead of reporting a filesystem error. A crash requires anomalous on-disk checkpoint metadata and panic_on_warn to be enabled; the reported consequence is loss of system availability.
Summary
What happened
Improper warning handling in Linux kernel 2.6.30 through 6.0.1 allows local users to crash the system via corrupted NILFS2 metadata. The nilfs_segctor_create_checkpoint and nilfs_segctor_fill_in_checkpoint functions invoke WARN_ON for corruption-related checkpoint acquisition errors instead of reporting a filesystem error. A crash requires anomalous on-disk checkpoint metadata and panic_on_warn to be enabled; the reported consequence is loss of system availability.
The record
- CVE
- CVE-2022-50519
- Published
- Oct 7, 2025
- Updated
- Oct 7, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 7, 2025CVE publishedPublication date reported by the CVE source.
- Oct 7, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <090fcfb6edeb9367a915b2749e2bd1f8b48d8898
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <259c0f68168ac6a598db3486597b10e74d625db0
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <5c0776b5bc31de7cd28afb558fae37a20f33602e
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <723ac751208f6d6540191689cfbf6c77135a7a1b
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <8a18fdc5ae8e6d7ac33c6ee0a2e5f9f1414ef412
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ae16440c44ae2acda6d72aff9d74eccf8967dae5
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b63026b5e13040cd5afa11769dd0d9e1504b031a
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <bf98be80cbe3b4e6c86c36ed00457389aca3eb15
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <c0c3d3d3ea41cb5228ee90568bb953f9a56c3227
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo