LiveActive security incident?Get immediate response
CVE Record

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

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.
Prepared
Confidence
medium
Sources
5

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.

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
2ADP providers
4Source 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
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxe5ef93d02d6c9cc3a14e7348481c9e41a528caa1, e5ef93d02d6c9cc3a14e7348481c9e41a528caa1, e5ef93d02d6c9cc3a14e7348481c9e41a528caa1unaffected
LinuxLinux6.6, 0, 6.6.18, 6.7.6, 6.8affected
Weakness

CWE details

No CWE listed

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