CVE-2024-26705: Vulnerability in Linux Linux
In the Linux kernel, the following vulnerability has been resolved: parisc: BTLB: Fix crash when setting up BTLB at CPU bringup When using hotplug and bringing up a 32-bit CPU, ask the firmware about the BTLB information to set up the static (block) TLB entries. For that write access to the static btlb_info struct is needed, but since it is marked __ro_after_init the kernel segfaults with missing write permissions. Fix the crash by dropping the __ro_after_init annotation.
AI Analysis
Technical Summary
CVE-2024-26705 is a vulnerability identified in the Linux kernel specifically affecting the PA-RISC (parisc) architecture's handling of the Block Translation Lookaside Buffer (BTLB) during CPU hotplug operations. The issue arises when a 32-bit CPU is brought online (CPU bringup) and the kernel attempts to query firmware for BTLB information to set up static TLB entries. The vulnerability is due to improper handling of write permissions on the static btlb_info structure, which is marked with the __ro_after_init annotation, indicating it should be read-only after initialization. However, during CPU hotplug, the kernel attempts to write to this structure, leading to a segmentation fault (kernel crash) because write access is denied. The fix involves removing the __ro_after_init annotation from the btlb_info structure, allowing the necessary write access during CPU bringup and preventing the kernel crash. This vulnerability is a stability and availability issue rather than a direct security exploit, as it causes a denial of service (DoS) condition by crashing the kernel. It does not appear to allow privilege escalation, code execution, or data leakage. The affected versions are specific Linux kernel commits identified by the given hashes, and the vulnerability is relevant only to systems running the Linux kernel on PA-RISC architecture hardware, which is a niche and legacy platform. There are no known exploits in the wild, and no CVSS score has been assigned yet.
Potential Impact
For European organizations, the impact of CVE-2024-26705 is primarily related to system stability and availability on affected hardware. Since the vulnerability causes kernel crashes during CPU hotplug operations on PA-RISC systems, organizations using such legacy hardware could experience unexpected downtime or service interruptions. This could affect critical infrastructure or legacy systems that have not been migrated to more modern architectures. However, the PA-RISC architecture is rare in modern data centers and enterprise environments, especially in Europe, limiting the scope of impact. Organizations relying on legacy PA-RISC Linux systems in sectors such as manufacturing, research, or specialized industrial control may face operational disruptions. The vulnerability does not pose a direct confidentiality or integrity risk, nor does it facilitate remote code execution or privilege escalation. Therefore, the threat is mainly a denial of service risk affecting availability. Given the limited affected hardware and lack of known exploits, the overall risk to most European organizations is low, but those with legacy PA-RISC Linux deployments should prioritize patching to maintain system stability.
Mitigation Recommendations
To mitigate CVE-2024-26705, organizations should: 1) Identify any Linux systems running on PA-RISC architecture within their infrastructure, focusing on legacy or specialized hardware. 2) Apply the official Linux kernel patches that remove the __ro_after_init annotation from the btlb_info structure as soon as they become available from trusted Linux kernel sources or distributions. 3) Test patches in a controlled environment to ensure stability before deployment, given the niche hardware involved. 4) Avoid CPU hotplug operations on affected systems until patched, or schedule such operations during maintenance windows to minimize impact. 5) Monitor system logs and kernel crash reports for signs of this vulnerability causing instability. 6) Consider long-term migration plans away from PA-RISC hardware to more widely supported architectures to reduce exposure to legacy vulnerabilities. 7) Maintain updated inventories of hardware and kernel versions to quickly identify vulnerable systems in the future. These steps go beyond generic advice by focusing on the specific architecture and operational context of the vulnerability.
Affected Countries
Germany, France, United Kingdom, Netherlands, Italy
CVE-2024-26705: Vulnerability in Linux Linux
Description
In the Linux kernel, the following vulnerability has been resolved: parisc: BTLB: Fix crash when setting up BTLB at CPU bringup When using hotplug and bringing up a 32-bit CPU, ask the firmware about the BTLB information to set up the static (block) TLB entries. For that write access to the static btlb_info struct is needed, but since it is marked __ro_after_init the kernel segfaults with missing write permissions. Fix the crash by dropping the __ro_after_init annotation.
AI-Powered Analysis
Technical Analysis
CVE-2024-26705 is a vulnerability identified in the Linux kernel specifically affecting the PA-RISC (parisc) architecture's handling of the Block Translation Lookaside Buffer (BTLB) during CPU hotplug operations. The issue arises when a 32-bit CPU is brought online (CPU bringup) and the kernel attempts to query firmware for BTLB information to set up static TLB entries. The vulnerability is due to improper handling of write permissions on the static btlb_info structure, which is marked with the __ro_after_init annotation, indicating it should be read-only after initialization. However, during CPU hotplug, the kernel attempts to write to this structure, leading to a segmentation fault (kernel crash) because write access is denied. The fix involves removing the __ro_after_init annotation from the btlb_info structure, allowing the necessary write access during CPU bringup and preventing the kernel crash. This vulnerability is a stability and availability issue rather than a direct security exploit, as it causes a denial of service (DoS) condition by crashing the kernel. It does not appear to allow privilege escalation, code execution, or data leakage. The affected versions are specific Linux kernel commits identified by the given hashes, and the vulnerability is relevant only to systems running the Linux kernel on PA-RISC architecture hardware, which is a niche and legacy platform. There are no known exploits in the wild, and no CVSS score has been assigned yet.
Potential Impact
For European organizations, the impact of CVE-2024-26705 is primarily related to system stability and availability on affected hardware. Since the vulnerability causes kernel crashes during CPU hotplug operations on PA-RISC systems, organizations using such legacy hardware could experience unexpected downtime or service interruptions. This could affect critical infrastructure or legacy systems that have not been migrated to more modern architectures. However, the PA-RISC architecture is rare in modern data centers and enterprise environments, especially in Europe, limiting the scope of impact. Organizations relying on legacy PA-RISC Linux systems in sectors such as manufacturing, research, or specialized industrial control may face operational disruptions. The vulnerability does not pose a direct confidentiality or integrity risk, nor does it facilitate remote code execution or privilege escalation. Therefore, the threat is mainly a denial of service risk affecting availability. Given the limited affected hardware and lack of known exploits, the overall risk to most European organizations is low, but those with legacy PA-RISC Linux deployments should prioritize patching to maintain system stability.
Mitigation Recommendations
To mitigate CVE-2024-26705, organizations should: 1) Identify any Linux systems running on PA-RISC architecture within their infrastructure, focusing on legacy or specialized hardware. 2) Apply the official Linux kernel patches that remove the __ro_after_init annotation from the btlb_info structure as soon as they become available from trusted Linux kernel sources or distributions. 3) Test patches in a controlled environment to ensure stability before deployment, given the niche hardware involved. 4) Avoid CPU hotplug operations on affected systems until patched, or schedule such operations during maintenance windows to minimize impact. 5) Monitor system logs and kernel crash reports for signs of this vulnerability causing instability. 6) Consider long-term migration plans away from PA-RISC hardware to more widely supported architectures to reduce exposure to legacy vulnerabilities. 7) Maintain updated inventories of hardware and kernel versions to quickly identify vulnerable systems in the future. These steps go beyond generic advice by focusing on the specific architecture and operational context of the vulnerability.
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.158Z
- Cisa Enriched
- true
- Cvss Version
- null
- State
- PUBLISHED
Threat ID: 682d982ac4522896dcbe389d
Added to database: 5/21/2025, 9:08:58 AM
Last enriched: 6/29/2025, 5:40:41 PM
Last updated: 12/4/2025, 1:28:55 AM
Views: 36
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2025-62173: CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in FreePBX security-reporting
HighCVE-2025-64055: n/a
UnknownCVE-2025-66404: CWE-77: Improper Neutralization of Special Elements used in a Command ('Command Injection') in Flux159 mcp-server-kubernetes
MediumCVE-2025-66293: CWE-125: Out-of-bounds Read in pnggroup libpng
HighCVE-2025-65868: n/a
UnknownActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.