Kernel crash via uninitialized IPVS protocol buffer
Published Jan 11, 2025 · Updated May 11, 2026
Undefined behavior in Linux kernel IPVS allows local users to crash the kernel when the affected module initializes. The ip_vs_protocol_init() function passes an uninitialized 64-byte stack buffer to strnlen(); under affected Clang/LLVM and CONFIG_FORTIFY_SOURCE builds, optimization can remove its terminator and let execution fall through. Loading IPVS can cause a kernel oops, while kernels with IPVS built in can panic during boot, limiting the reported impact to service interruption.
Summary
What happened
Undefined behavior in Linux kernel IPVS allows local users to crash the kernel when the affected module initializes. The ip_vs_protocol_init() function passes an uninitialized 64-byte stack buffer to strnlen(); under affected Clang/LLVM and CONFIG_FORTIFY_SOURCE builds, optimization can remove its terminator and let execution fall through. Loading IPVS can cause a kernel oops, while kernels with IPVS built in can panic during boot, limiting the reported impact to service interruption.
The record
- CVE
- CVE-2024-53680
- Published
- Jan 11, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-908
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Jan 11, 2025CVE publishedPublication date reported by the CVE source.
- 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.
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <0b2cbed82b7c6504a8a0fbd181f92dd56b432c12
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <124834133b32f9386bb2d8581d9ab92f65e951e4
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <146b6f1112eb30a19776d6c323c994e9d67790db
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <31d1ddc1ce8e8d3f101a679243abb42a313ee88a
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <48130002e64fd191b7d18efeb4d253fcc23e4688
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <664d0feab92495b6a27edc3d1119e232c0fe8b2b
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <d6e1776f51c95827142f1d7064118e255e2deec1
- Affected versionversion=2.6.12
What conditions does exploitation require?
What is affected?
Published CVSS scores
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.
Weakness, pattern, technique
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