Kernel panic via stack-canary reinitialization
Published Oct 1, 2025 · Updated Oct 1, 2025
Improper stack protection in Linux 2.6.30 through 6.4.3 allows remote attackers to cause a kernel panic during early boot. The start_kernel and secondary CPU startup callers invoke boot_init_stack_canary without suppressing stack-protector instrumentation, so canary initialization changes the caller's saved canary and sends execution to __stack_chk_fail. Exposure requires a kernel built with stack protection using a supporting compiler; the public record does not identify the network input that reaches this boot path.
Summary
What happened
Improper stack protection in Linux 2.6.30 through 6.4.3 allows remote attackers to cause a kernel panic during early boot. The start_kernel and secondary CPU startup callers invoke boot_init_stack_canary without suppressing stack-protector instrumentation, so canary initialization changes the caller's saved canary and sends execution to __stack_chk_fail. Exposure requires a kernel built with stack protection using a supporting compiler; the public record does not identify the network input that reaches this boot path.
The record
- CVE
- CVE-2023-53491
- Published
- Oct 1, 2025
- Updated
- Oct 1, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 1, 2025CVE publishedPublication date reported by the CVE source.
- Oct 1, 2025Record 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 <25e73018b4093e0cfbcec5dc4a4bb86d0b69ed56
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <514ca14ed5444b911de59ed3381dfd195d99fe4b
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