CVE-2024-35987

{"dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": {"cveId": "CVE-2024-35987", "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "state": "PUBLISHED", "assignerShortName": "Linux", "dateReserved": "2024-05-17T13:50:33.145Z", "datePublished": "2024-05-20T09:47:53.717Z", "dateUpdated": "2026-08-05T11:31:25.006Z"}, "containers": {"cna": {"providerMetadata": {"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "shortName": "Linux", "dateUpdated": "2026-08-05T11:31:25.006Z"}, "descriptions": [{"lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nriscv: Fix loading 64-bit NOMMU kernels past the start of RAM\n\ncommit 3335068f8721 (\"riscv: Use PUD/P4D/PGD pages for the linear\nmapping\") added logic to allow using RAM below the kernel load address.\nHowever, this does not work for NOMMU, where PAGE_OFFSET is fixed to the\nkernel load address. Since that range of memory corresponds to PFNs\nbelow ARCH_PFN_OFFSET, mm initialization runs off the beginning of\nmem_map and corrupts adjacent kernel memory. Fix this by restoring the\nprevious behavior for NOMMU kernels."}], "metrics": [{"cvssV3_1": {"version": "3.1", "vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "baseScore": 8.4, "baseSeverity": "HIGH"}, "scenarios": [{"lang": "en", "value": "AV:L - The corruption occurs in `setup_bootmem()`/`free_area_init()` on the local machine's own boot path, with no network, adjacent-network, or remote-peer data anywhere in the path; anyone able to power-cycle or reset an affected RISC-V NOMMU board triggers it, and no device insertion or physical bus access is involved, so it scores L rather than P.\nAC:L - On an affected deployment (64-bit RISC-V NOMMU with RAM below the kernel load address) the failure is fully deterministic on every single boot \u2014 `min_low_pfn < ARCH_PFN_OFFSET` forces the negative `__pfn_to_page()` index unconditionally, with no race, timing window, or memory-layout grooming required.\nPR:N - The corrupting code runs during early memory-management initialization, long before userspace, login, or any credential check exists, so no account, capability, or namespace gates it.\nUI:N - Both `setup_bootmem()` and mm initialization execute autonomously as part of kernel startup; no administrator or user has to mount anything, open a device node, or take any action.\nS:U - The out-of-bounds writes and the skewed `__va`/`__pa` translation both corrupt the kernel's own memory and allocator state, remaining entirely within the kernel's security authority \u2014 no hypervisor, IOMMU, or sandbox boundary is crossed.\nC:H - Corrupted `struct page` metadata and a systematically wrong `kernel_map.va_pa_offset` make `pfn_to_page()`/`page_address()`/`virt_to_phys()` resolve to the wrong physical memory, so the page allocator can hand out pages still holding kernel data; on NOMMU there is no MMU-enforced separation to prevent a user process from reading that kernel memory.\nI:H - `__init_single_page()` writes roughly 64 bytes of page flags, refcounts, and list pointers per PFN at a negative index before `mem_map`, giving an out-of-bounds write into adjacent kernel memory, and the wrong `va_pa_offset` additionally directs DMA and linear-map writes to incorrect physical addresses.\nA:H - The commit states mm initialization \"corrupts adjacent kernel memory\"; the resulting damage to page-allocator structures plus universally wrong physical-address translation renders the system unbootable or crashes it, and recurs on every boot while the affected memory layout is present."}]}], "affected": [{"product": "Linux", "vendor": "Linux", "defaultStatus": "unaffected", "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "programFiles": ["arch/riscv/include/asm/page.h", "arch/riscv/mm/init.c"], "versions": [{"version": "3335068f87217ea59d08f462187dc856652eea15", "lessThan": "b008e327fa570aca210f98c817757649bae56694", "status": "affected", "versionType": "git"}, {"version": "3335068f87217ea59d08f462187dc856652eea15", "lessThan": "ea6628e4e2353978af7e3b4ad4fdaab6149acf3d", "status": "affected", "versionType": "git"}, {"version": "3335068f87217ea59d08f462187dc856652eea15", "lessThan": "aea702dde7e9876fb00571a2602f25130847bf0f", "status": "affected", "versionType": "git"}]}, {"product": "Linux", "vendor": "Linux", "defaultStatus": "affected", "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "programFiles": ["arch/riscv/include/asm/page.h", "arch/riscv/mm/init.c"], "versions": [{"version": "6.4", "status": "affected"}, {"version": "0", "lessThan": "6.4", "status": "unaffected", "versionType": "semver"}, {"version": "6.6.30", "lessThanOrEqual": "6.6.*", "status": "unaffected", "versionType": "semver"}, {"version": "6.8.9", "lessThanOrEqual": "6.8.*", "status": "unaffected", "versionType": "semver"}, {"version": "6.9", "lessThanOrEqual": "*", "status": "unaffected", "versionType": "original_commit_for_fix"}]}], "cpeApplicability": [{"nodes": [{"operator": "OR", "negate": false, "cpeMatch": [{"vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "6.4", "versionEndExcluding": "6.6.30"}, {"vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "6.4", "versionEndExcluding": "6.8.9"}, {"vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "6.4", "versionEndExcluding": "6.9"}]}]}], "references": [{"url": "https://git.kernel.org/stable/c/b008e327fa570aca210f98c817757649bae56694"}, {"url": "https://git.kernel.org/stable/c/ea6628e4e2353978af7e3b4ad4fdaab6149acf3d"}, {"url": "https://git.kernel.org/stable/c/aea702dde7e9876fb00571a2602f25130847bf0f"}], "title": "riscv: Fix loading 64-bit NOMMU kernels past the start of RAM", "x_generator": {"engine": "bippy-1.2.0"}}, "adp": [{"title": "CISA ADP Vulnrichment", "metrics": [{"other": {"type": "ssvc", "content": {"id": "CVE-2024-35987", "role": "CISA Coordinator", "options": [{"Exploitation": "none"}, {"Automatable": "no"}, {"Technical Impact": "partial"}], "version": "2.0.3", "timestamp": "2024-05-21T15:11:39.923129Z"}}}], "providerMetadata": {"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "shortName": "CISA-ADP", "dateUpdated": "2024-06-04T17:34:49.643Z"}}, {"providerMetadata": {"orgId": "af854a3a-2127-422b-91ae-364da2661108", "shortName": "CVE", "dateUpdated": "2024-08-02T03:30:12.480Z"}, "title": "CVE Program Container", "references": [{"url": "https://git.kernel.org/stable/c/b008e327fa570aca210f98c817757649bae56694", "tags": ["x_transferred"]}, {"url": "https://git.kernel.org/stable/c/ea6628e4e2353978af7e3b4ad4fdaab6149acf3d", "tags": ["x_transferred"]}, {"url": "https://git.kernel.org/stable/c/aea702dde7e9876fb00571a2602f25130847bf0f", "tags": ["x_transferred"]}]}]}}

{"dataType": "CVE_RECORD", "containers": {"adp": [{"title": "CVE Program Container", "references": [{"url": "https://git.kernel.org/stable/c/b008e327fa570aca210f98c817757649bae56694", "tags": ["x_transferred"]}, {"url": "https://git.kernel.org/stable/c/ea6628e4e2353978af7e3b4ad4fdaab6149acf3d", "tags": ["x_transferred"]}, {"url": "https://git.kernel.org/stable/c/aea702dde7e9876fb00571a2602f25130847bf0f", "tags": ["x_transferred"]}], "providerMetadata": {"orgId": "af854a3a-2127-422b-91ae-364da2661108", "shortName": "CVE", "dateUpdated": "2024-08-02T03:30:12.480Z"}}, {"metrics": [{"other": {"type": "ssvc", "content": {"id": "CVE-2024-35987", "role": "CISA Coordinator", "options": [{"Exploitation": "none"}, {"Automatable": "no"}, {"Technical Impact": "partial"}], "version": "2.0.3", "timestamp": "2024-05-21T15:11:39.923129Z"}}}], "providerMetadata": {"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "shortName": "CISA-ADP", "dateUpdated": "2024-05-23T19:01:25.150Z"}, "title": "CISA ADP Vulnrichment"}], "cna": {"title": "riscv: Fix loading 64-bit NOMMU kernels past the start of RAM", "metrics": [{"cvssV3_1": {"version": "3.1", "baseScore": 8.4, "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"}, "scenarios": [{"lang": "en", "value": "AV:L - The corruption occurs in `setup_bootmem()`/`free_area_init()` on the local machine's own boot path, with no network, adjacent-network, or remote-peer data anywhere in the path; anyone able to power-cycle or reset an affected RISC-V NOMMU board triggers it, and no device insertion or physical bus access is involved, so it scores L rather than P.\nAC:L - On an affected deployment (64-bit RISC-V NOMMU with RAM below the kernel load address) the failure is fully deterministic on every single boot \u2014 `min_low_pfn < ARCH_PFN_OFFSET` forces the negative `__pfn_to_page()` index unconditionally, with no race, timing window, or memory-layout grooming required.\nPR:N - The corrupting code runs during early memory-management initialization, long before userspace, login, or any credential check exists, so no account, capability, or namespace gates it.\nUI:N - Both `setup_bootmem()` and mm initialization execute autonomously as part of kernel startup; no administrator or user has to mount anything, open a device node, or take any action.\nS:U - The out-of-bounds writes and the skewed `__va`/`__pa` translation both corrupt the kernel's own memory and allocator state, remaining entirely within the kernel's security authority \u2014 no hypervisor, IOMMU, or sandbox boundary is crossed.\nC:H - Corrupted `struct page` metadata and a systematically wrong `kernel_map.va_pa_offset` make `pfn_to_page()`/`page_address()`/`virt_to_phys()` resolve to the wrong physical memory, so the page allocator can hand out pages still holding kernel data; on NOMMU there is no MMU-enforced separation to prevent a user process from reading that kernel memory.\nI:H - `__init_single_page()` writes roughly 64 bytes of page flags, refcounts, and list pointers per PFN at a negative index before `mem_map`, giving an out-of-bounds write into adjacent kernel memory, and the wrong `va_pa_offset` additionally directs DMA and linear-map writes to incorrect physical addresses.\nA:H - The commit states mm initialization \"corrupts adjacent kernel memory\"; the resulting damage to page-allocator structures plus universally wrong physical-address translation renders the system unbootable or crashes it, and recurs on every boot while the affected memory layout is present."}]}], "affected": [{"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "product": "Linux", "versions": [{"status": "affected", "version": "3335068f87217ea59d08f462187dc856652eea15", "lessThan": "b008e327fa570aca210f98c817757649bae56694", "versionType": "git"}, {"status": "affected", "version": "3335068f87217ea59d08f462187dc856652eea15", "lessThan": "ea6628e4e2353978af7e3b4ad4fdaab6149acf3d", "versionType": "git"}, {"status": "affected", "version": "3335068f87217ea59d08f462187dc856652eea15", "lessThan": "aea702dde7e9876fb00571a2602f25130847bf0f", "versionType": "git"}], "programFiles": ["arch/riscv/include/asm/page.h", "arch/riscv/mm/init.c"], "defaultStatus": "unaffected"}, {"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "product": "Linux", "versions": [{"status": "affected", "version": "6.4"}, {"status": "unaffected", "version": "0", "lessThan": "6.4", "versionType": "semver"}, {"status": "unaffected", "version": "6.6.30", "versionType": "semver", "lessThanOrEqual": "6.6.*"}, {"status": "unaffected", "version": "6.8.9", "versionType": "semver", "lessThanOrEqual": "6.8.*"}, {"status": "unaffected", "version": "6.9", "versionType": "original_commit_for_fix", "lessThanOrEqual": "*"}], "programFiles": ["arch/riscv/include/asm/page.h", "arch/riscv/mm/init.c"], "defaultStatus": "affected"}], "references": [{"url": "https://git.kernel.org/stable/c/b008e327fa570aca210f98c817757649bae56694"}, {"url": "https://git.kernel.org/stable/c/ea6628e4e2353978af7e3b4ad4fdaab6149acf3d"}, {"url": "https://git.kernel.org/stable/c/aea702dde7e9876fb00571a2602f25130847bf0f"}], "x_generator": {"engine": "bippy-1.2.0"}, "descriptions": [{"lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nriscv: Fix loading 64-bit NOMMU kernels past the start of RAM\n\ncommit 3335068f8721 (\"riscv: Use PUD/P4D/PGD pages for the linear\nmapping\") added logic to allow using RAM below the kernel load address.\nHowever, this does not work for NOMMU, where PAGE_OFFSET is fixed to the\nkernel load address. Since that range of memory corresponds to PFNs\nbelow ARCH_PFN_OFFSET, mm initialization runs off the beginning of\nmem_map and corrupts adjacent kernel memory. Fix this by restoring the\nprevious behavior for NOMMU kernels."}], "cpeApplicability": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "vulnerable": true, "versionEndExcluding": "6.6.30", "versionStartIncluding": "6.4"}, {"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "vulnerable": true, "versionEndExcluding": "6.8.9", "versionStartIncluding": "6.4"}, {"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "vulnerable": true, "versionEndExcluding": "6.9", "versionStartIncluding": "6.4"}], "operator": "OR"}]}], "providerMetadata": {"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "shortName": "Linux", "dateUpdated": "2026-08-05T11:31:25.006Z"}}}, "cveMetadata": {"cveId": "CVE-2024-35987", "state": "PUBLISHED", "dateUpdated": "2026-08-05T11:31:25.006Z", "dateReserved": "2024-05-17T13:50:33.145Z", "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "datePublished": "2024-05-20T09:47:53.717Z", "assignerShortName": "Linux"}, "dataVersion": "5.2"}

{"affected": [{"affectedData": [{"defaultStatus": "unaffected", "product": "Linux", "programFiles": ["arch/riscv/include/asm/page.h", "arch/riscv/mm/init.c"], "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "versions": [{"lessThan": "b008e327fa570aca210f98c817757649bae56694", "status": "affected", "version": "3335068f87217ea59d08f462187dc856652eea15", "versionType": "git"}, {"lessThan": "ea6628e4e2353978af7e3b4ad4fdaab6149acf3d", "status": "affected", "version": "3335068f87217ea59d08f462187dc856652eea15", "versionType": "git"}, {"lessThan": "aea702dde7e9876fb00571a2602f25130847bf0f", "status": "affected", "version": "3335068f87217ea59d08f462187dc856652eea15", "versionType": "git"}]}, {"defaultStatus": "affected", "product": "Linux", "programFiles": ["arch/riscv/include/asm/page.h", "arch/riscv/mm/init.c"], "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "versions": [{"status": "affected", "version": "6.4"}, {"lessThan": "6.4", "status": "unaffected", "version": "0", "versionType": "semver"}, {"lessThanOrEqual": "6.6.*", "status": "unaffected", "version": "6.6.30", "versionType": "semver"}, {"lessThanOrEqual": "6.8.*", "status": "unaffected", "version": "6.8.9", "versionType": "semver"}, {"lessThanOrEqual": "*", "status": "unaffected", "version": "6.9", "versionType": "original_commit_for_fix"}]}], "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}], "configurations": [{"nodes": [{"cpeMatch": [{"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "matchCriteriaId": "690AEB51-07F0-40A3-9967-DE94D673735E", "versionEndExcluding": "6.6.30", "versionStartIncluding": "6.4", "vulnerable": true}, {"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "matchCriteriaId": "5F9041E5-8358-4EF7-8F98-B812EDE49612", "versionEndExcluding": "6.8.9", "versionStartIncluding": "6.7", "vulnerable": true}, {"criteria": "cpe:2.3:o:linux:linux_kernel:6.9:rc1:*:*:*:*:*:*", "matchCriteriaId": "22BEDD49-2C6D-402D-9DBF-6646F6ECD10B", "vulnerable": true}, {"criteria": "cpe:2.3:o:linux:linux_kernel:6.9:rc2:*:*:*:*:*:*", "matchCriteriaId": "DF73CB2A-DFFD-46FB-9BFE-AA394F27EA37", "vulnerable": true}, {"criteria": "cpe:2.3:o:linux:linux_kernel:6.9:rc3:*:*:*:*:*:*", "matchCriteriaId": "52048DDA-FC5A-4363-95A0-A6357B4D7F8C", "vulnerable": true}, {"criteria": "cpe:2.3:o:linux:linux_kernel:6.9:rc4:*:*:*:*:*:*", "matchCriteriaId": "A06B2CCF-3F43-4FA9-8773-C83C3F5764B2", "vulnerable": true}, {"criteria": "cpe:2.3:o:linux:linux_kernel:6.9:rc5:*:*:*:*:*:*", "matchCriteriaId": "F850DCEC-E08B-4317-A33B-D2DCF39F601B", "vulnerable": true}], "negate": false, "operator": "OR"}]}], "cveTags": [], "descriptions": [{"lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nriscv: Fix loading 64-bit NOMMU kernels past the start of RAM\n\ncommit 3335068f8721 (\"riscv: Use PUD/P4D/PGD pages for the linear\nmapping\") added logic to allow using RAM below the kernel load address.\nHowever, this does not work for NOMMU, where PAGE_OFFSET is fixed to the\nkernel load address. Since that range of memory corresponds to PFNs\nbelow ARCH_PFN_OFFSET, mm initialization runs off the beginning of\nmem_map and corrupts adjacent kernel memory. Fix this by restoring the\nprevious behavior for NOMMU kernels."}, {"lang": "es", "value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: riscv: se corrigi\u00f3 la carga de kernels NOMMU de 64 bits despu\u00e9s del inicio de la confirmaci\u00f3n de RAM. 3335068f8721 (\"riscv: use p\u00e1ginas PUD/P4D/PGD para el mapeo lineal\") se agreg\u00f3 l\u00f3gica para permitir el uso RAM debajo de la direcci\u00f3n de carga del kernel. Sin embargo, esto no funciona para NOMMU, donde PAGE_OFFSET est\u00e1 fijado a la direcci\u00f3n de carga del kernel. Dado que ese rango de memoria corresponde a los PFN por debajo de ARCH_PFN_OFFSET, la inicializaci\u00f3n de mm se ejecuta desde el principio de mem_map y corrompe la memoria del kernel adyacente. Solucione este problema restaurando el comportamiento anterior de los n\u00facleos NOMMU."}], "id": "CVE-2024-35987", "lastModified": "2026-08-04T11:18:19.157", "metrics": {"cvssMetricV31": [{"cvssData": {"attackComplexity": "LOW", "attackVector": "LOCAL", "availabilityImpact": "HIGH", "baseScore": 8.4, "baseSeverity": "HIGH", "confidentialityImpact": "HIGH", "integrityImpact": "HIGH", "privilegesRequired": "NONE", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "version": "3.1"}, "exploitabilityScore": 2.5, "impactScore": 5.9, "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "type": "Secondary"}, {"cvssData": {"attackComplexity": "LOW", "attackVector": "LOCAL", "availabilityImpact": "HIGH", "baseScore": 5.5, "baseSeverity": "MEDIUM", "confidentialityImpact": "NONE", "integrityImpact": "NONE", "privilegesRequired": "LOW", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H", "version": "3.1"}, "exploitabilityScore": 1.8, "impactScore": 3.6, "source": "nvd@nist.gov", "type": "Primary"}], "ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2024-35987", "options": [{"exploitation": "none"}, {"automatable": "no"}, {"technicalImpact": "partial"}], "role": "CISA Coordinator", "timestamp": "2024-05-21T15:11:39.923129Z", "version": "2.0.3"}}]}, "published": "2024-05-20T10:15:13.057", "references": [{"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "tags": ["Patch"], "url": "https://git.kernel.org/stable/c/aea702dde7e9876fb00571a2602f25130847bf0f"}, {"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "tags": ["Patch"], "url": "https://git.kernel.org/stable/c/b008e327fa570aca210f98c817757649bae56694"}, {"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "tags": ["Patch"], "url": "https://git.kernel.org/stable/c/ea6628e4e2353978af7e3b4ad4fdaab6149acf3d"}, {"source": "af854a3a-2127-422b-91ae-364da2661108", "tags": ["Patch"], "url": "https://git.kernel.org/stable/c/aea702dde7e9876fb00571a2602f25130847bf0f"}, {"source": "af854a3a-2127-422b-91ae-364da2661108", "tags": ["Patch"], "url": "https://git.kernel.org/stable/c/b008e327fa570aca210f98c817757649bae56694"}, {"source": "af854a3a-2127-422b-91ae-364da2661108", "tags": ["Patch"], "url": "https://git.kernel.org/stable/c/ea6628e4e2353978af7e3b4ad4fdaab6149acf3d"}], "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "vulnStatus": "Modified", "weaknesses": [{"description": [{"lang": "en", "value": "NVD-CWE-noinfo"}], "source": "nvd@nist.gov", "type": "Primary"}]}

{"bugzilla": {"description": "kernel: riscv: Fix loading 64-bit NOMMU kernels past the start of RAM", "id": "2281852", "url": "https://bugzilla.redhat.com/show_bug.cgi?id=2281852"}, "csaw": false, "cvss3": {"cvss3_base_score": "5.5", "cvss3_scoring_vector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H", "status": "draft"}, "details": ["In the Linux kernel, the following vulnerability has been resolved:\nriscv: Fix loading 64-bit NOMMU kernels past the start of RAM\ncommit 3335068f8721 (\"riscv: Use PUD/P4D/PGD pages for the linear\nmapping\") added logic to allow using RAM below the kernel load address.\nHowever, this does not work for NOMMU, where PAGE_OFFSET is fixed to the\nkernel load address. Since that range of memory corresponds to PFNs\nbelow ARCH_PFN_OFFSET, mm initialization runs off the beginning of\nmem_map and corrupts adjacent kernel memory. Fix this by restoring the\nprevious behavior for NOMMU kernels.", "A vulnerability was found in the Linux kernel that affects 64-bit No Memory Management Unit (NOMMU) systems. The issue arose from a change that allowed using RAM below the kernel load address, which conflicts with the fixed `PAGE_OFFSET` in NOMMU systems. This leads to memory initialization errors and potential kernel memory corruption."], "mitigation": {"lang": "en:us", "value": "Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability."}, "name": "CVE-2024-35987", "package_state": [{"cpe": "cpe:/o:redhat:enterprise_linux:6", "fix_state": "Not affected", "package_name": "kernel", "product_name": "Red Hat Enterprise Linux 6"}, {"cpe": "cpe:/o:redhat:enterprise_linux:7", "fix_state": "Out of support scope", "package_name": "kernel", "product_name": "Red Hat Enterprise Linux 7"}, {"cpe": "cpe:/o:redhat:enterprise_linux:7", "fix_state": "Out of support scope", "package_name": "kernel-rt", "product_name": "Red Hat Enterprise Linux 7"}, {"cpe": "cpe:/o:redhat:enterprise_linux:8", "fix_state": "Not affected", "package_name": "kernel", "product_name": "Red Hat Enterprise Linux 8"}, {"cpe": "cpe:/o:redhat:enterprise_linux:8", "fix_state": "Not affected", "package_name": "kernel-rt", "product_name": "Red Hat Enterprise Linux 8"}, {"cpe": "cpe:/o:redhat:enterprise_linux:9", "fix_state": "Not affected", "package_name": "kernel", "product_name": "Red Hat Enterprise Linux 9"}, {"cpe": "cpe:/o:redhat:enterprise_linux:9", "fix_state": "Not affected", "package_name": "kernel-rt", "product_name": "Red Hat Enterprise Linux 9"}], "public_date": "2024-05-20T00:00:00Z", "references": ["https://www.cve.org/CVERecord?id=CVE-2024-35987\nhttps://nvd.nist.gov/vuln/detail/CVE-2024-35987\nhttps://lore.kernel.org/linux-cve-announce/2024052019-CVE-2024-35987-c5e7@gregkh/T"], "statement": "Red Hat Enterprise Linux is not vulnerable to this CVE, as it does not affect the versions or configurations of the Linux kernel used in its distributions.", "threat_severity": "Moderate"}

{"created": "2025-07-13T11:31:20.899376+00:00", "updated": "2025-07-13T11:31:20.899431+00:00", "vendors": ["linux", "linux$PRODUCT$linux_kernel"]}