CVE-2024-26705

Host crash via read-only BTLB write

Published Apr 3, 2024 · Updated May 11, 2026

Kernel crash in Linux 6.6 through 6.7.5 and 6.8-rc1/rc2 allows local users to interrupt service during 32-bit PA-RISC CPU hotplug. During per-CPU BTLB setup, the PA-RISC hotplug path writes firmware BTLB data into the static btlb_info structure after __ro_after_init has removed write permission, causing a kernel segmentation fault. Reaching the fault requires local access capable of bringing up a hot-plugged 32-bit PA-RISC CPU; the bounded consequence is a host crash rather than data disclosure or modification.

CVSS severity5.5
Medium
EPSS probability0.19%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Kernel crash in Linux 6.6 through 6.7.5 and 6.8-rc1/rc2 allows local users to interrupt service during 32-bit PA-RISC CPU hotplug. During per-CPU BTLB setup, the PA-RISC hotplug path writes firmware BTLB data into the static btlb_info structure after __ro_after_init has removed write permission, causing a kernel segmentation fault. Reaching the fault requires local access capable of bringing up a hot-plugged 32-bit PA-RISC CPU; the bounded consequence is a host crash rather than data disclosure or modification.

The record

CVE
CVE-2024-26705
Published
Apr 3, 2024
Updated
May 11, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
CWE-862, T1499
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Apr 3, 2024CVE publishedPublication date reported by the CVE source.
  2. May 11, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=6.6
  2. Affected versionversion=e5ef93d02d6c9cc3a14e7348481c9e41a528caa1 <54944f45470af5965fb9c28cf962ec30f38a8f5b
  3. Affected versionversion=e5ef93d02d6c9cc3a14e7348481c9e41a528caa1 <913b9d443a0180cf0de3548f1ab3149378998486
  4. Affected versionversion=e5ef93d02d6c9cc3a14e7348481c9e41a528caa1 <aa52be55276614d33f22fbe7da36c40d6432d10b

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

The Linux Kernel Organization · Linuxversion=6.6; version=e5ef93d02d6c9cc3a14e7348481c9e41a528caa1 <54944f45470af5965fb9c28cf962ec30f38a8f5b; version=e5ef93d02d6c9cc3a14e7348481c9e41a528caa1 <913b9d443a0180cf0de3548f1ab3149378998486; version=e5ef93d02d6c9cc3a14e7348481c9e41a528caa1 <aa52be55276614d33f22fbe7da36c40d6432d10b

Published CVSS scores

5.5NIST NVDCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
5.5Canonical UbuntuCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-862Missing Authorization
T1499Endpoint Denial of Service

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo