Kernel panic via skipped page-writeback wait
Published May 21, 2024 · Updated May 11, 2026
A writeback synchronization flaw in the Linux kernel allows local users to trigger a kernel panic during inode eviction after memory unmapping. The memory_failure path calls identify_page_state without waiting for writeback after __munlock_pagevec clears the page LRU without locking the page, and truncate_error_page then clears its mapping before writeback completion can clear inode state. Low-privileged local access and the required mmap, unmap, memory-failure, and unlink sequence are needed; the documented consequence is a host crash.
Summary
What happened
A writeback synchronization flaw in the Linux kernel allows local users to trigger a kernel panic during inode eviction after memory unmapping. The memory_failure path calls identify_page_state without waiting for writeback after __munlock_pagevec clears the page LRU without locking the page, and truncate_error_page then clears its mapping before writeback completion can clear inode state. Low-privileged local access and the required mmap, unmap, memory-failure, and unlink sequence are needed; the documented consequence is a host crash.
The record
- CVE
- CVE-2021-47256
- Published
- May 21, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 21, 2024CVE 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=0bc1f8b0682caa39f45ce1e0228ebf43acb46111 <28788dc5c70597395b6b451dae4549bbaa8e2c56
- Affected versionversion=0bc1f8b0682caa39f45ce1e0228ebf43acb46111 <566345aaabac853aa866f53a219c4b02a6beb527
- Affected versionversion=0bc1f8b0682caa39f45ce1e0228ebf43acb46111 <6d210d547adc2218ef8b5bcf23518c5f2f1fd872
- Affected versionversion=0bc1f8b0682caa39f45ce1e0228ebf43acb46111 <9e379da727a7a031be9b877cde7b9c34a0fb8306
- Affected versionversion=0bc1f8b0682caa39f45ce1e0228ebf43acb46111 <d05267fd27a5c4f54e06daefa3035995d765ca0c
- Affected versionversion=0bc1f8b0682caa39f45ce1e0228ebf43acb46111 <e8675d291ac007e1c636870db880f837a9ea112a
- Affected versionversion=3.16
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