LiveActive security incident?Get immediate response
CVE Record

CVE-2024-35988: riscv: Fix TASK_SIZE on 64-bit NOMMU

In the Linux kernel, the following vulnerability has been resolved: riscv: Fix TASK_SIZE on 64-bit NOMMU On NOMMU, userspace memory can come from anywhere in physical RAM. The current definition of TASK_SIZE is wrong if any RAM exists above 4G, causing spurious failures in the userspace access routines.

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

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue affects a narrow hardware and configuration set: 64-bit RISC-V systems running without an MMU. If those systems have RAM above 4GB, the kernel can misjudge user memory boundaries and cause user access operations to fail unexpectedly.

Executive priority

Handle as a targeted platform hygiene issue, not a broad emergency. Prioritize asset owners managing RISC-V embedded, industrial, or appliance Linux systems over general enterprise servers.

Technical view

The RISC-V 64-bit NOMMU TASK_SIZE definition was incorrect for physical memory above 4GB. Because NOMMU userspace memory can be anywhere in RAM, this could produce false failures in userspace access routines. The source bundle lists upstream stable fixes and affected Linux version data, but no CVSS score.

Likely exposure

Likely limited to Linux deployments using 64-bit RISC-V NOMMU configurations, especially embedded or appliance environments with RAM above 4GB. General MMU-based Linux systems are not indicated by the provided sources.

Exploitation context

The bundle does not show KEV listing, active exploitation, exploit availability, or a security impact beyond spurious userspace access failures. Treat exploitation evidence as absent, not disproven.

Researcher notes

The available evidence describes a correctness defect in RISC-V NOMMU memory boundary handling. Severity, CWE, and CVSS are not provided. Avoid broad claims about privilege escalation, data exposure, or remote exploitability without additional vendor analysis.

Mitigation direction

  • Identify RISC-V 64-bit NOMMU Linux systems in the environment.
  • Check whether affected systems have physical RAM above 4GB.
  • Apply vendor or upstream stable kernel updates containing the referenced fixes.
  • Review Debian and Siemens advisories if those distributions or products are used.
  • If no vendor fix is available, request vendor-specific guidance.

Validation and detection

  • Confirm kernel version and vendor build lineage for RISC-V NOMMU devices.
  • Verify whether CONFIG_MMU is disabled on candidate systems.
  • Check hardware memory maps for RAM above the 4GB boundary.
  • Map installed kernels against the CVE record and vendor advisories.
  • After updating, confirm the kernel includes the relevant stable commit.
Prepared
Confidence
medium
Sources
10

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-2024-35988 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
3ADP providers
9Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

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.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container
siemens-SADPADP container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux6bd33e1ece528f67646db33bf97406b747dafda0, 6bd33e1ece528f67646db33bf97406b747dafda0, 6bd33e1ece528f67646db33bf97406b747dafda0, 6bd33e1ece528f67646db33bf97406b747dafda0, 6bd33e1ece528f67646db33bf97406b747dafda0, 6bd33e1ece528f67646db33bf97406b747dafda0unaffected
LinuxLinux5.5, 0, 5.10.216, 5.15.158, 6.1.90, 6.6.30, 6.8.9, 6.9affected
Weakness

CWE details

No CWE listed

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