LiveActive security incident?Get immediate response
CVE Record

CVE-2022-49852: riscv: process: fix kernel info leakage

In the Linux kernel, the following vulnerability has been resolved: riscv: process: fix kernel info leakage thread_struct's s[12] may contain random kernel memory content, which may be finally leaked to userspace. This is a security hole. Fix it by clearing the s[12] array in thread_struct when fork. As for kthread case, it's better to clear the s[12] array as well.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This CVE describes a Linux kernel information leak on RISC-V systems. Uninitialized saved-register storage in a new thread could contain kernel memory and later be exposed to userspace. The supplied sources do not provide CVSS, confirmed exploitation, or impact beyond information disclosure.

Executive priority

Treat this as a kernel hygiene issue for RISC-V assets, not an internet-wide emergency based on supplied evidence. Patch through normal maintenance, faster for shared systems or environments handling sensitive workloads.

Technical view

The issue is in RISC-V process handling: thread_struct's s[12] array may retain random kernel memory across fork or kthread creation. The upstream fix clears this array when creating threads, reducing leakage of stale kernel data to userspace.

Likely exposure

Exposure appears limited to Linux kernels on RISC-V where the vulnerable process code exists, including affected stable ranges listed in the CVE bundle. Non-RISC-V exposure is not indicated by the supplied sources.

Exploitation context

The CVE is not listed as KEV in the bundle, and no provided source claims active exploitation or public exploit availability. The described attacker value is kernel information disclosure, which could support later attacks if sensitive data is exposed.

Researcher notes

The evidence supports a RISC-V Linux kernel info leak caused by uninitialized thread_struct saved-register state. Severity scoring, exploitability details, and affected distribution package mappings are not provided in the bundle and should be verified with vendor advisories.

Mitigation direction

  • Update affected RISC-V Linux kernels to a version containing the referenced stable fixes.
  • Use distribution vendor kernel advisories where kernels are backported instead of version-matched.
  • Prioritize vendor guidance if package status differs from upstream Linux versions.
  • Track this with regular kernel patch management unless local RISC-V exposure is high.

Validation and detection

  • Inventory RISC-V Linux systems and record running kernel versions.
  • Check vendor advisories or package changelogs for CVE-2022-49852 or listed fix commits.
  • Confirm the kernel source initializes thread_struct s[12] during fork and kthread creation.
  • Verify patched kernels are deployed and active after reboot.
Prepared
Confidence
medium
Sources
8

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2022-49852 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
7Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux7db91e57a0acde126a162ababfb1e0ab190130cb, 7db91e57a0acde126a162ababfb1e0ab190130cb, 7db91e57a0acde126a162ababfb1e0ab190130cb, 7db91e57a0acde126a162ababfb1e0ab190130cb, 7db91e57a0acde126a162ababfb1e0ab190130cb, 7db91e57a0acde126a162ababfb1e0ab190130cbunaffected
LinuxLinux4.15, 0, 4.19.267, 5.4.225, 5.10.155, 5.15.79, 6.0.9, 6.1affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.