Kernel panic via NFS direct-write buffer overrun
Published Jun 2, 2021 · Updated Aug 4, 2024
Out-of-bounds write in the RHEL 7 NFS client allows local users with high privileges to crash the kernel during direct I/O writes. nfs_direct_write_schedule_segment indexes past a kmalloc-allocated buffer while scheduling a direct NFS write, corrupting adjacent kernel memory. Reaching the RHEL-only 3.10 kernel path requires high local privileges and an NFS client; the corruption can expose kernel data or cause a panic.
Summary
What happened
Out-of-bounds write in the RHEL 7 NFS client allows local users with high privileges to crash the kernel during direct I/O writes. nfs_direct_write_schedule_segment indexes past a kmalloc-allocated buffer while scheduling a direct NFS write, corrupting adjacent kernel memory. Reaching the RHEL-only 3.10 kernel path requires high local privileges and an NFS client; the corruption can expose kernel data or cause a panic.
The record
- CVE
- CVE-2020-10742
- Published
- Jun 2, 2021
- Updated
- Aug 4, 2024
- Vendor
- Red Hat
- Product
- Red Hat Enterprise Linux 7
- Classifications
- CWE-787, T1499.004
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Jun 2, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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=kernel 3.10.0
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.
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