CVE-2024-26919

Local kernel code execution via stale ULPI entry

Published Apr 17, 2024 · Updated Aug 5, 2026

Use-after-free in the Linux kernel ULPI debugfs interface allows local users to execute kernel code by reading a stale regs file. ulpi_unregister_interface removes a directory named for the ULPI device even though registration names it for the parent, leaving the regs entry tied to a freed struct ulpi and its ops->read callback. The path requires an affected ULPI-bearing system and local access to mounted debugfs; a read can disclose kernel memory, hijack control flow, or crash the host.

CVSS severity7.8
High
EPSS probability0.23%
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

Use-after-free in the Linux kernel ULPI debugfs interface allows local users to execute kernel code by reading a stale regs file. ulpi_unregister_interface removes a directory named for the ULPI device even though registration names it for the parent, leaving the regs entry tied to a freed struct ulpi and its ops->read callback. The path requires an affected ULPI-bearing system and local access to mounted debugfs; a read can disclose kernel memory, hijack control flow, or crash the host.

The record

CVE
CVE-2024-26919
Published
Apr 17, 2024
Updated
Aug 5, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
T1068
Attack vector
local
Privileges
authenticated

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=5.18
  2. Affected versionversion=bd0a0a024f2a41e7cc8eadb9862f82c45884b69c <330d22aba17a4d30a56f007d0f51291d7e00862b
  3. Affected versionversion=bd0a0a024f2a41e7cc8eadb9862f82c45884b69c <33713945cc92ea9c4a1a9479d5c1b7acb7fc4df3
  4. Affected versionversion=bd0a0a024f2a41e7cc8eadb9862f82c45884b69c <3caf2b2ad7334ef35f55b95f3e1b138c6f77b368
  5. Affected versionversion=bd0a0a024f2a41e7cc8eadb9862f82c45884b69c <d31b886ed6a5095214062ee4fb55037eb930adb6

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

The Linux Kernel Organization · Linuxversion=5.18; version=bd0a0a024f2a41e7cc8eadb9862f82c45884b69c <330d22aba17a4d30a56f007d0f51291d7e00862b; version=bd0a0a024f2a41e7cc8eadb9862f82c45884b69c <33713945cc92ea9c4a1a9479d5c1b7acb7fc4df3; version=bd0a0a024f2a41e7cc8eadb9862f82c45884b69c <3caf2b2ad7334ef35f55b95f3e1b138c6f77b368; version=bd0a0a024f2a41e7cc8eadb9862f82c45884b69c <d31b886ed6a5095214062ee4fb55037eb930adb6

Published CVSS scores

7.8Linux kernel CNACVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
5.5NIST NVDCVSS: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

T1068Exploitation for Privilege Escalation

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