Kernel-data disclosure via unchecked NET/ROM frame length
Published Jan 15, 2025 · Updated Aug 5, 2026
Uninitialized-memory use in the Linux NET/ROM router allows remote attackers to disclose kernel data or interrupt networking via short AX.25 frames. The nr_route_frame function reads callsign and routing fields from skb->data without first verifying that skb->len covers those fields. A reachable NET/ROM-over-AX.25 path is required, but no authentication or user interaction is needed; repeated frames can leak stale heap bytes, corrupt routing state, or crash instrumented and panic-on-warning kernels.
Summary
What happened
Uninitialized-memory use in the Linux NET/ROM router allows remote attackers to disclose kernel data or interrupt networking via short AX.25 frames. The nr_route_frame function reads callsign and routing fields from skb->data without first verifying that skb->len covers those fields. A reachable NET/ROM-over-AX.25 path is required, but no authentication or user interaction is needed; repeated frames can leak stale heap bytes, corrupt routing state, or crash instrumented and panic-on-warning kernels.
The record
- CVE
- CVE-2024-57802
- Published
- Jan 15, 2025
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-908, T1210
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 15, 2025CVE publishedPublication date reported by the CVE source.
- 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.
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <3ba7f80d98d4965349cfcd258dd78418496c1625
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <64e9f54a14f2887be8634fb85cd2f13bec18a184
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <769e36c2119a51070faf58819c58274f57a088db
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <78a110332ae268d0b005247c3b9a7d703b875c49
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <a4fd163aed2edd967a244499754dec991d8b4c7d
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <cf6befa7c569787f53440274bbed1405fc07738d
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f647d72245aadce30618f4c8fd3803904418dbec
- Affected versionversion=2.6.12
What conditions does exploitation require?
What is affected?
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