CVE-2024-26890

Kernel memory corruption via missing HCI allocation

Published Apr 17, 2024 · Updated Aug 5, 2026

Out-of-bounds write in affected Linux kernel releases allows attackers to corrupt kernel memory during Realtek HCI UART power-on. The btrtl initialization path stores struct btrealtek_data after hci_dev even though the hci_h5 registration path allocates no private tail space there. Reachability requires the btrtl driver over the HCI H5 UART transport on compatible Bluetooth hardware; ordinary btusb use allocates the required private data.

CVSS severity6.5
Medium
EPSS probability0.60%
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

Out-of-bounds write in affected Linux kernel releases allows attackers to corrupt kernel memory during Realtek HCI UART power-on. The btrtl initialization path stores struct btrealtek_data after hci_dev even though the hci_h5 registration path allocates no private tail space there. Reachability requires the btrtl driver over the HCI H5 UART transport on compatible Bluetooth hardware; ordinary btusb use allocates the required private data.

The record

CVE
CVE-2024-26890
Published
Apr 17, 2024
Updated
Aug 5, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
CWE-125
Attack vector
local
Privileges
Unavailable

Timeline

How it unfolded

  1. Apr 17, 2024CVE publishedPublication date reported by the CVE source.
  2. Aug 5, 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=5b355944b19011011dd3fd4187444c5ff1d76ad2 <0c657e641df1e77d6087688190f632cad9c0439b
  2. Affected versionversion=5b355944b19011011dd3fd4187444c5ff1d76ad2 <2f232bc389a4f5943c40733582f9edf77b89e499
  3. Affected versionversion=5b355944b19011011dd3fd4187444c5ff1d76ad2 <dd163fa34c483f1674aa2510accce11a224f649e
  4. Affected versionversion=5b355944b19011011dd3fd4187444c5ff1d76ad2 <de4e88ec58c4202efd1f02eebb4939bbf6945358
  5. Affected versionversion=6.2

What conditions does exploitation require?

Attack vectorlocal
Required privilegesUnavailable in this record.

What is affected?

The Linux Kernel Organization · Linuxversion=5b355944b19011011dd3fd4187444c5ff1d76ad2 <0c657e641df1e77d6087688190f632cad9c0439b; version=5b355944b19011011dd3fd4187444c5ff1d76ad2 <2f232bc389a4f5943c40733582f9edf77b89e499; version=5b355944b19011011dd3fd4187444c5ff1d76ad2 <dd163fa34c483f1674aa2510accce11a224f649e; version=5b355944b19011011dd3fd4187444c5ff1d76ad2 <de4e88ec58c4202efd1f02eebb4939bbf6945358; version=6.2

Published CVSS scores

6.5CISA ADPCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L
7.0SUSECVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/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
PrivilegesUnavailable
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-125Out-of-bounds Read

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