Kernel crash via invalid nilfs2 inode type
Published Aug 22, 2025 · Updated May 11, 2026
Improper inode validation in Linux nilfs2 from 2.6.30 allows local users to crash the kernel via a malformed filesystem image. The __nilfs_read_inode function treats an unrecognized on-disk i_mode file type as a special inode and passes it to VFS instead of returning a filesystem error. Reaching the flaw requires local access to a crafted nilfs2 image; the demonstrated consequence is an assertion failure that interrupts the host.
Summary
What happened
Improper inode validation in Linux nilfs2 from 2.6.30 allows local users to crash the kernel via a malformed filesystem image. The __nilfs_read_inode function treats an unrecognized on-disk i_mode file type as a special inode and passes it to VFS instead of returning a filesystem error. Reaching the flaw requires local access to a crafted nilfs2 image; the demonstrated consequence is an assertion failure that interrupts the host.
The record
- CVE
- CVE-2025-38663
- Published
- Aug 22, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 22, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record 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=05fe58fdc10df9ebea04c0eaed57adc47af5c184 <1a5c204e175a78556b8ef1f7683249fa5197295a
- Affected versionversion=05fe58fdc10df9ebea04c0eaed57adc47af5c184 <2cf0c4130bf340be3935d097a3dcbfefdcf65815
- Affected versionversion=05fe58fdc10df9ebea04c0eaed57adc47af5c184 <42cd46b3a8b1497b9258dc7ac445dbd6beb73e2f
- Affected versionversion=05fe58fdc10df9ebea04c0eaed57adc47af5c184 <4aead50caf67e01020c8be1945c3201e8a972a27
- Affected versionversion=05fe58fdc10df9ebea04c0eaed57adc47af5c184 <79663a15a1c70ca84f86f2dbba07b423fe7d5d4f
- Affected versionversion=05fe58fdc10df9ebea04c0eaed57adc47af5c184 <98872a934ea6a95985fb6a3655a78a5f0c114e82
- Affected versionversion=05fe58fdc10df9ebea04c0eaed57adc47af5c184 <bf585ee198bba4ff25b0d80a0891df4656cb0d08
- Affected versionversion=05fe58fdc10df9ebea04c0eaed57adc47af5c184 <dd298c0b889acd3ecaf48b6e840c9ab91882e342
- Affected versionversion=2.6.30
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
No sourced classifications are available.
Public exploit references
- syzkaller kernel BUG in may_open reproducerproof of concept · demonstrated
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