Kernel panic via attacker-controlled ext error policy
Published Nov 29, 2021 · Updated Aug 3, 2024
Improper input validation in UDisks before 2.9.4 allows local users to trigger a kernel panic by mounting a crafted ext filesystem image. Its ext2/3/4 mount helpers honor the attacker-controlled s_errors superblock field instead of forcing errors=remount-ro, so an injected filesystem error selects panic behavior. An unprivileged user able to mount an image through udisksctl or an automounting desktop or embedded system can halt the Linux host.
Summary
What happened
Improper input validation in UDisks before 2.9.4 allows local users to trigger a kernel panic by mounting a crafted ext filesystem image. Its ext2/3/4 mount helpers honor the attacker-controlled s_errors superblock field instead of forcing errors=remount-ro, so an injected filesystem error selects panic behavior. An unprivileged user able to mount an image through udisksctl or an automounting desktop or embedded system can halt the Linux host.
The record
- CVE
- CVE-2021-3802
- Published
- Nov 29, 2021
- Updated
- Aug 3, 2024
- Vendor
- Storaged Project
- Product
- UDisks
- Classifications
- CWE-20, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 29, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record 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=udisks-2.9.4
What conditions does exploitation require?
What is affected?
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
- Crafted ext4 filesystem image proof of conceptproof 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