CVE-2022-0847
Linux Kernel 5.8 – 5.10.102
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2022-0847 is a high-severity Improper Initialization (CWE-665) vulnerability in Redhat Enterprise Linux Eus. Its CVSS base score is 7.8 (High).
Operationally, ranked in the top 0.2% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog; a public proof-of-concept is referenced.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2022-0847 is a flaw in the Linux kernel arising from improper initialization of the "flags" member in the new pipe buffer structure within the copy_page_to_iter_pipe and push_pipe functions. The uninitialized field can retain stale values, enabling writes to pages in the page cache that are backed by read-only files. The affected component is the Linux kernel; the issue carries a CVSS 3.1 score of 7.8 and is associated with CWE-665.
An unprivileged local user can exploit the flaw to modify read-only file contents cached in memory and thereby escalate privileges on the system. Exploitation requires local access and does not depend on user interaction or special network conditions.
Public exploit code targeting the vulnerability has been posted to Packet Storm, and a Red Hat Bugzilla entry provides additional technical details. The EPSS score currently stands at 0.8108 with a recorded peak of 0.8461, indicating sustained exploitation interest after disclosure.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2022-15890
Vulnerability Data
A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe and push_pipe functions in the Linux kernel and could thus contain stale values. An unprivileged local user could…
more
use this flaw to write to pages in the page cache backed by read only files and as such escalate their privileges on the system.
- CWE(s)
- KEV Date Added
- 25 April 2022
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Ensures shared resources are explicitly initialized or cleared on allocation, preventing exposure of prior contents to new users or processes.
Mandates that every instance begins in a known (presumably clean) state, eliminating reliance on residual or uninitialized state left by prior executions.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
A.8.25 mandates security requirements, checkpoints, secure coding, testing and developer capability in the SDLC which reaches improper initialization as a design/coding defect, but leaves a bounded remainder (e.g. initialization of third-party components or libraries chosen in procurement, and post-deployment configuration defaults).
A.8.27 mandates security-by-design principles (least privilege, default-deny, fail-securely, distrust-external-input, hardening) plus explicit design reviews that can catch and block many uninitialized-resource cases before they ship, but leaves a bounded remainder (e.g. vendor libraries, runtime-initialization bugs, or post-review code changes) that can still be present and exploitable.
Secure coding standards explicitly forbid uninitialized variables and mandate proper resource initialization before use.
Security testing can detect uninitialized variables but does not itself enforce initialization practices.
defining, enforcing, and monitoring secure configuration templates (including defaults, disabled services, changed vendor passwords, minimized privileges) directly stops most improper-initialization cases from being exploitable; the bounded remainder is initialization logic inside custom application code that no configuration template reaches
Hardening callouts derived
DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.
- No fine-grained STIG row for CWE-665, a class-level weakness. Rules are authored against its narrower children: CWE-770.