System crash via fanotify stale file descriptor
Published Jun 9, 2022 · Updated Aug 3, 2024
Use-after-free in Linux kernel 5.13 through 5.17-rc2 allows local users to crash the system through a fanotify error path. In copy_event_to_user(), failure of copy_info_records_to_user() wrongly releases a file after fd_install() has exposed its descriptor, leaving a stale descriptor-table entry. The path requires CAP_SYS_ADMIN in the initial user namespace, effectively root, and the grounded consequence is a system crash rather than lower-privileged escalation.
Summary
What happened
Use-after-free in Linux kernel 5.13 through 5.17-rc2 allows local users to crash the system through a fanotify error path. In copy_event_to_user(), failure of copy_info_records_to_user() wrongly releases a file after fd_install() has exposed its descriptor, leaving a stale descriptor-table entry. The path requires CAP_SYS_ADMIN in the initial user namespace, effectively root, and the grounded consequence is a system crash rather than lower-privileged escalation.
The record
- CVE
- CVE-2022-1998
- Published
- Jun 9, 2022
- Updated
- Aug 3, 2024
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Jun 9, 2022CVE 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=Linux kernel 5.17-rc3
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