Kernel oops via unmapped ramoops lowmem access
Published Dec 30, 2025 · Updated Dec 30, 2025
Denial of service in the Linux kernel pstore RAM backend allows local users to trigger a kernel oops by reading /proc/kcore. persistent_ram_vmap maps reserved ramoops pages through vmap without VM_IOREMAP, while aligned_vread later passes their page structures to kmap_atomic as though direct lowmem mappings existed. The trigger requires a device configured with the pstore RAM backend and access to /proc/kcore; the bounded consequence is a kernel oops.
Summary
What happened
Denial of service in the Linux kernel pstore RAM backend allows local users to trigger a kernel oops by reading /proc/kcore. persistent_ram_vmap maps reserved ramoops pages through vmap without VM_IOREMAP, while aligned_vread later passes their page structures to kmap_atomic as though direct lowmem mappings existed. The trigger requires a device configured with the pstore RAM backend and access to /proc/kcore; the bounded consequence is a kernel oops.
The record
- CVE
- CVE-2022-50849
- Published
- Dec 30, 2025
- Updated
- Dec 30, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 30, 2025CVE publishedPublication date reported by the CVE source.
- Dec 30, 2025Record 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=3.4
- Affected versionversion=404a6043385de17273624b076599669db5ad891f <1579bed1613802a323a1e14567faa95c149e105e
- Affected versionversion=404a6043385de17273624b076599669db5ad891f <295f59cd2cdeed841850d02dddde3a122cbf6fc6
- Affected versionversion=404a6043385de17273624b076599669db5ad891f <2f82381d0681b10f9ddd27be98c27363b5a3cd1c
- Affected versionversion=404a6043385de17273624b076599669db5ad891f <4d3126f242a0090342ffe925c35fb4f4252b7562
- Affected versionversion=404a6043385de17273624b076599669db5ad891f <69dbff7d2681c55a4d979fd9b75576303e69979f
- Affected versionversion=404a6043385de17273624b076599669db5ad891f <6d9460214e363e1f3d0756ee5d947e76e3e6f86c
- Affected versionversion=404a6043385de17273624b076599669db5ad891f <e6b842741b4f39007215fd7e545cb55aa3d358a2
- Affected versionversion=404a6043385de17273624b076599669db5ad891f <ebc73c4f266281e2cad1a372ecd81572d95375b6
- Affected versionversion=404a6043385de17273624b076599669db5ad891f <fdebcc33b663d2e8da937653ddfbfc1315047eaa
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