CVE-2024-26705: parisc: BTLB: Fix crash when setting up BTLB at CPU bringup
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.
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue can crash affected PA-RISC systems when a 32-bit CPU is brought online using hotplug. The impact described is system instability, not data theft or remote compromise. The public sources do not provide CVSS, CWE, or evidence of exploitation.
Executive priority
Treat this as a targeted reliability issue for PA-RISC Linux environments. It does not warrant broad emergency response unless those systems support critical operations and use CPU hotplug workflows.
Technical view
The bug is in PA-RISC BTLB setup during CPU bringup. Firmware-provided BTLB data must be written to a static btlb_info structure, but the structure was marked __ro_after_init, causing a kernel fault when write access is needed. The fix removes that annotation.
Likely exposure
Exposure appears limited to Linux systems using the PA-RISC architecture, specifically scenarios involving 32-bit CPU hotplug or bringup. Organizations without PA-RISC Linux systems are unlikely to be exposed based on the supplied sources.
Exploitation context
The bundle states KEV is false and provides no source showing active exploitation. The described trigger is CPU bringup/hotplug behavior, suggesting an operational crash condition rather than a broadly reachable remote attack path.
Researcher notes
Evidence is narrow: the CVE text describes a resolved kernel crash, affected Linux versions, and stable commit references. No CVSS, CWE, exploitability analysis, or public exploitation evidence is included in the provided bundle.
Mitigation direction
Apply Linux stable kernel updates that include the referenced fixes.
Check distribution vendor advisories for packaged kernel availability.
Prioritize PA-RISC systems that use CPU hotplug or 32-bit CPU bringup.
Avoid unsupported kernel builds on affected PA-RISC hosts.
Review vendor guidance before applying temporary operational workarounds.
Validation and detection
Inventory Linux systems running on PA-RISC architecture.
Check kernel versions and whether referenced stable commits are included.
Review logs for crashes during CPU hotplug or CPU bringup.
Confirm production PA-RISC hosts have vendor-supported fixed kernels.
Document any remaining PA-RISC systems awaiting maintenance windows.
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-26705 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.