CVE-2021-47618

Kernel panic via KASAN-clobbered kprobe register bindings

Published Jun 20, 2024 · Updated May 11, 2026

Kernel panic in ARM32 Linux 2.6.25 through 5.17-rc1 allows local users to interrupt service when KASAN and kprobes are enabled. KASAN instrumentation in the ARM kprobe instruction-emulation code clobbers C register bindings used to construct the assembly execution environment, so emulate_ldr follows corrupted register state into a NULL-pointer dereference. An ARM32 kernel built with KASAN and kprobe support must execute a probe on an instruction handled by the software emulator; the resulting kernel panic stops the host.

CVSS severity5.5
Medium
EPSS probability0.24%
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 panic in ARM32 Linux 2.6.25 through 5.17-rc1 allows local users to interrupt service when KASAN and kprobes are enabled. KASAN instrumentation in the ARM kprobe instruction-emulation code clobbers C register bindings used to construct the assembly execution environment, so emulate_ldr follows corrupted register state into a NULL-pointer dereference. An ARM32 kernel built with KASAN and kprobe support must execute a probe on an instruction handled by the software emulator; the resulting kernel panic stops the host.

The record

CVE
CVE-2021-47618
Published
Jun 20, 2024
Updated
May 11, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
T1499.004
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Jun 20, 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=2.6.25
  2. Affected versionversion=35aa1df4328340f38edc46f00837f08d33d49f63 <1515e72aae803fc6b466adf918e71c4e4c9d5b3d
  3. Affected versionversion=35aa1df4328340f38edc46f00837f08d33d49f63 <8b59b0a53c840921b625378f137e88adfa87647e
  4. Affected versionversion=35aa1df4328340f38edc46f00837f08d33d49f63 <ba1863be105b06e10d0e2f6b1b8a0570801cfc71

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

The Linux Kernel Organization · Linuxversion=2.6.25; version=35aa1df4328340f38edc46f00837f08d33d49f63 <1515e72aae803fc6b466adf918e71c4e4c9d5b3d; version=35aa1df4328340f38edc46f00837f08d33d49f63 <8b59b0a53c840921b625378f137e88adfa87647e; version=35aa1df4328340f38edc46f00837f08d33d49f63 <ba1863be105b06e10d0e2f6b1b8a0570801cfc71

Published CVSS scores

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

T1499.004Application or System Exploitation

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