Kernel assertion via incorrect btrfs device match
Published May 1, 2025 · Updated May 23, 2026
Improper device matching in Linux btrfs 5.15.54 through 5.15.78 and 5.16 through 6.0.8 allows local users to trigger a kernel assertion. The dev_args_match_device function skips devid comparison when ioctl input sets devid to the sentinel value, so an unrelated device can match. Access to the affected btrfs ioctl is required, and the demonstrated consequence is the assertion failure in fs/btrfs/volumes.c.
Summary
What happened
Improper device matching in Linux btrfs 5.15.54 through 5.15.78 and 5.16 through 6.0.8 allows local users to trigger a kernel assertion. The dev_args_match_device function skips devid comparison when ioctl input sets devid to the sentinel value, so an unrelated device can match. Access to the affected btrfs ioctl is required, and the demonstrated consequence is the assertion failure in fs/btrfs/volumes.c.
The record
- CVE
- CVE-2022-49849
- Published
- May 1, 2025
- Updated
- May 23, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-20, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 1, 2025CVE publishedPublication date reported by the CVE source.
- May 23, 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=5.15.54 <5.15.79
- Affected versionversion=5.16
- Affected versionversion=5578b681fbf2b22d61189a2539efd3009518b328 <c9fe4719c662e0af17eea723cf345e37719fd3c9
- Affected versionversion=562d7b1512f7369a19bca2883e2e8672d78f0481 <0fca385d6ebc3cabb20f67bcf8a71f1448bdc001
- Affected versionversion=562d7b1512f7369a19bca2883e2e8672d78f0481 <bc6c127c377010f136360552ebf91c2723081c1b
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.
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