CVE-2024-26947: Vulnerability in Linux Linux
In the Linux kernel, the following vulnerability has been resolved: ARM: 9359/1: flush: check if the folio is reserved for no-mapping addresses Since commit a4d5613c4dc6 ("arm: extend pfn_valid to take into account freed memory map alignment") changes the semantics of pfn_valid() to check presence of the memory map for a PFN. A valid page for an address which is reserved but not mapped by the kernel[1], the system crashed during some uio test with the following memory layout: node 0: [mem 0x00000000c0a00000-0x00000000cc8fffff] node 0: [mem 0x00000000d0000000-0x00000000da1fffff] the uio layout is:0xc0900000, 0x100000 the crash backtrace like: Unable to handle kernel paging request at virtual address bff00000 [...] CPU: 1 PID: 465 Comm: startapp.bin Tainted: G O 5.10.0 #1 Hardware name: Generic DT based system PC is at b15_flush_kern_dcache_area+0x24/0x3c LR is at __sync_icache_dcache+0x6c/0x98 [...] (b15_flush_kern_dcache_area) from (__sync_icache_dcache+0x6c/0x98) (__sync_icache_dcache) from (set_pte_at+0x28/0x54) (set_pte_at) from (remap_pfn_range+0x1a0/0x274) (remap_pfn_range) from (uio_mmap+0x184/0x1b8 [uio]) (uio_mmap [uio]) from (__mmap_region+0x264/0x5f4) (__mmap_region) from (__do_mmap_mm+0x3ec/0x440) (__do_mmap_mm) from (do_mmap+0x50/0x58) (do_mmap) from (vm_mmap_pgoff+0xfc/0x188) (vm_mmap_pgoff) from (ksys_mmap_pgoff+0xac/0xc4) (ksys_mmap_pgoff) from (ret_fast_syscall+0x0/0x5c) Code: e0801001 e2423001 e1c00003 f57ff04f (ee070f3e) ---[ end trace 09cf0734c3805d52 ]--- Kernel panic - not syncing: Fatal exception So check if PG_reserved was set to solve this issue. [1]: https://lore.kernel.org/lkml/Zbtdue57RO0QScJM@linux.ibm.com/
AI Analysis
Technical Summary
CVE-2024-26947 is a vulnerability identified in the Linux kernel specifically affecting ARM architecture systems. The issue arises from a change introduced in commit a4d5613c4dc6, which modified the behavior of the pfn_valid() function to check the presence of the memory map for a Page Frame Number (PFN). This change inadvertently caused the kernel to mishandle reserved but unmapped memory addresses. In particular, when the kernel attempts to flush the kernel data cache for such addresses (via the b15_flush_kern_dcache_area function), it can trigger a kernel panic due to an invalid memory access. The vulnerability manifests during operations involving the Userspace I/O (UIO) subsystem, specifically during memory mapping (mmap) of device memory regions that are reserved but not mapped. The kernel fails to properly check if the folio (a collection of pages) is reserved, leading to attempts to flush cache lines for addresses that are not validly mapped, resulting in a fatal exception and system crash. The root cause is the lack of verification that the PG_reserved flag is set for these no-mapping addresses before cache flush operations. This flaw can cause system instability and denial of service (DoS) conditions on affected ARM-based Linux systems. Although no known exploits are reported in the wild, the vulnerability is significant because it affects kernel stability and could be triggered by local processes performing mmap operations on device memory. The fix involves adding checks to ensure that reserved pages are correctly identified and handled during cache flush operations, preventing invalid memory accesses and kernel panics.
Potential Impact
For European organizations, the impact of CVE-2024-26947 primarily involves potential denial of service due to kernel panics on ARM-based Linux systems. This is particularly relevant for enterprises and service providers using ARM servers, embedded devices, or IoT infrastructure running affected Linux kernel versions. Critical infrastructure sectors such as telecommunications, manufacturing, and automotive industries in Europe increasingly rely on ARM-based platforms for edge computing and embedded control systems. A kernel panic triggered by this vulnerability could lead to unexpected system downtime, disrupting services and operational technology environments. Additionally, organizations deploying Linux-based network equipment or virtualization hosts on ARM hardware may experience instability, affecting availability and reliability. Although the vulnerability does not directly enable privilege escalation or data breaches, the resulting system crashes could be exploited to cause denial of service or to disrupt critical applications. The absence of known exploits reduces immediate risk, but the vulnerability's presence in widely used Linux kernels necessitates prompt attention to avoid operational disruptions.
Mitigation Recommendations
To mitigate CVE-2024-26947, European organizations should: 1) Apply the latest Linux kernel patches that address this issue as soon as they become available from trusted sources or Linux distributions. Monitor vendor advisories for updated kernel releases incorporating the fix. 2) For embedded and IoT devices running custom or vendor-provided kernels, coordinate with device manufacturers to obtain patched firmware or kernel updates. 3) Implement rigorous testing of kernel updates in staging environments, especially for ARM-based systems, to verify stability and compatibility before production deployment. 4) Restrict access to systems where untrusted users could perform mmap operations on device memory, minimizing the risk of accidental or malicious triggering of the vulnerability. 5) Employ kernel hardening techniques and runtime integrity monitoring to detect abnormal kernel panics or crashes, enabling rapid incident response. 6) Maintain comprehensive backup and recovery procedures to minimize downtime impact in case of kernel crashes. 7) For critical infrastructure, consider deploying redundant systems or failover mechanisms to maintain availability during patching or unexpected crashes.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Finland, Italy, Spain
CVE-2024-26947: Vulnerability in Linux Linux
Description
In the Linux kernel, the following vulnerability has been resolved: ARM: 9359/1: flush: check if the folio is reserved for no-mapping addresses Since commit a4d5613c4dc6 ("arm: extend pfn_valid to take into account freed memory map alignment") changes the semantics of pfn_valid() to check presence of the memory map for a PFN. A valid page for an address which is reserved but not mapped by the kernel[1], the system crashed during some uio test with the following memory layout: node 0: [mem 0x00000000c0a00000-0x00000000cc8fffff] node 0: [mem 0x00000000d0000000-0x00000000da1fffff] the uio layout is:0xc0900000, 0x100000 the crash backtrace like: Unable to handle kernel paging request at virtual address bff00000 [...] CPU: 1 PID: 465 Comm: startapp.bin Tainted: G O 5.10.0 #1 Hardware name: Generic DT based system PC is at b15_flush_kern_dcache_area+0x24/0x3c LR is at __sync_icache_dcache+0x6c/0x98 [...] (b15_flush_kern_dcache_area) from (__sync_icache_dcache+0x6c/0x98) (__sync_icache_dcache) from (set_pte_at+0x28/0x54) (set_pte_at) from (remap_pfn_range+0x1a0/0x274) (remap_pfn_range) from (uio_mmap+0x184/0x1b8 [uio]) (uio_mmap [uio]) from (__mmap_region+0x264/0x5f4) (__mmap_region) from (__do_mmap_mm+0x3ec/0x440) (__do_mmap_mm) from (do_mmap+0x50/0x58) (do_mmap) from (vm_mmap_pgoff+0xfc/0x188) (vm_mmap_pgoff) from (ksys_mmap_pgoff+0xac/0xc4) (ksys_mmap_pgoff) from (ret_fast_syscall+0x0/0x5c) Code: e0801001 e2423001 e1c00003 f57ff04f (ee070f3e) ---[ end trace 09cf0734c3805d52 ]--- Kernel panic - not syncing: Fatal exception So check if PG_reserved was set to solve this issue. [1]: https://lore.kernel.org/lkml/Zbtdue57RO0QScJM@linux.ibm.com/
AI-Powered Analysis
Technical Analysis
CVE-2024-26947 is a vulnerability identified in the Linux kernel specifically affecting ARM architecture systems. The issue arises from a change introduced in commit a4d5613c4dc6, which modified the behavior of the pfn_valid() function to check the presence of the memory map for a Page Frame Number (PFN). This change inadvertently caused the kernel to mishandle reserved but unmapped memory addresses. In particular, when the kernel attempts to flush the kernel data cache for such addresses (via the b15_flush_kern_dcache_area function), it can trigger a kernel panic due to an invalid memory access. The vulnerability manifests during operations involving the Userspace I/O (UIO) subsystem, specifically during memory mapping (mmap) of device memory regions that are reserved but not mapped. The kernel fails to properly check if the folio (a collection of pages) is reserved, leading to attempts to flush cache lines for addresses that are not validly mapped, resulting in a fatal exception and system crash. The root cause is the lack of verification that the PG_reserved flag is set for these no-mapping addresses before cache flush operations. This flaw can cause system instability and denial of service (DoS) conditions on affected ARM-based Linux systems. Although no known exploits are reported in the wild, the vulnerability is significant because it affects kernel stability and could be triggered by local processes performing mmap operations on device memory. The fix involves adding checks to ensure that reserved pages are correctly identified and handled during cache flush operations, preventing invalid memory accesses and kernel panics.
Potential Impact
For European organizations, the impact of CVE-2024-26947 primarily involves potential denial of service due to kernel panics on ARM-based Linux systems. This is particularly relevant for enterprises and service providers using ARM servers, embedded devices, or IoT infrastructure running affected Linux kernel versions. Critical infrastructure sectors such as telecommunications, manufacturing, and automotive industries in Europe increasingly rely on ARM-based platforms for edge computing and embedded control systems. A kernel panic triggered by this vulnerability could lead to unexpected system downtime, disrupting services and operational technology environments. Additionally, organizations deploying Linux-based network equipment or virtualization hosts on ARM hardware may experience instability, affecting availability and reliability. Although the vulnerability does not directly enable privilege escalation or data breaches, the resulting system crashes could be exploited to cause denial of service or to disrupt critical applications. The absence of known exploits reduces immediate risk, but the vulnerability's presence in widely used Linux kernels necessitates prompt attention to avoid operational disruptions.
Mitigation Recommendations
To mitigate CVE-2024-26947, European organizations should: 1) Apply the latest Linux kernel patches that address this issue as soon as they become available from trusted sources or Linux distributions. Monitor vendor advisories for updated kernel releases incorporating the fix. 2) For embedded and IoT devices running custom or vendor-provided kernels, coordinate with device manufacturers to obtain patched firmware or kernel updates. 3) Implement rigorous testing of kernel updates in staging environments, especially for ARM-based systems, to verify stability and compatibility before production deployment. 4) Restrict access to systems where untrusted users could perform mmap operations on device memory, minimizing the risk of accidental or malicious triggering of the vulnerability. 5) Employ kernel hardening techniques and runtime integrity monitoring to detect abnormal kernel panics or crashes, enabling rapid incident response. 6) Maintain comprehensive backup and recovery procedures to minimize downtime impact in case of kernel crashes. 7) For critical infrastructure, consider deploying redundant systems or failover mechanisms to maintain availability during patching or unexpected crashes.
Affected Countries
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- Linux
- Date Reserved
- 2024-02-19T14:20:24.197Z
- Cisa Enriched
- true
- Cvss Version
- null
- State
- PUBLISHED
Threat ID: 682d9821c4522896dcbddb8b
Added to database: 5/21/2025, 9:08:49 AM
Last enriched: 6/28/2025, 2:55:03 AM
Last updated: 7/28/2025, 5:49:33 PM
Views: 8
Related Threats
CVE-2025-38738: CWE-266: Incorrect Privilege Assignment in Dell SupportAssist for Home PCs
MediumCVE-2025-36612: CWE-266: Incorrect Privilege Assignment in Dell SupportAssist for Business PCs
MediumCVE-2025-9041: CWE-1287: Improper Validation of Specified Type of Input in Rockwell Automation FLEX 5000 I/O
HighCVE-2025-43983: n/a
CriticalCVE-2025-9042: CWE-1287: Improper Validation of Specified Type of Input in Rockwell Automation FLEX 5000 I/O
HighActions
Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.
External Links
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.