Kernel disclosure and crash via invalid TIPC address
Published Aug 17, 2024 · Updated Aug 5, 2026
Buffer over-read in affected Linux kernel branches from 4.1 allows remote attackers to disclose memory or crash systems via TIPC UDP. The tipc_udp_addr2str() helper reports success for an invalid UDP protocol value, so tipc_media_addr_printf() consumes a buffer that was not populated. Reachability requires an enabled TIPC UDP bearer to process the invalid address; no credentials or user interaction are required.
Summary
What happened
Buffer over-read in affected Linux kernel branches from 4.1 allows remote attackers to disclose memory or crash systems via TIPC UDP. The tipc_udp_addr2str() helper reports success for an invalid UDP protocol value, so tipc_media_addr_printf() consumes a buffer that was not populated. Reachability requires an enabled TIPC UDP bearer to process the invalid address; no credentials or user interaction are required.
The record
- CVE
- CVE-2024-42284
- Published
- Aug 17, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-754
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 17, 2024CVE 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=4.1
- Affected versionversion=d0f91938bede204a343473792529e0db7d599836 <253405541be2f15ffebdeac2f4cf4b7e9144d12f
- Affected versionversion=d0f91938bede204a343473792529e0db7d599836 <2abe350db1aa599eeebc6892237d0bce0f1de62a
- Affected versionversion=d0f91938bede204a343473792529e0db7d599836 <5eea127675450583680c8170358bcba43227bd69
- Affected versionversion=d0f91938bede204a343473792529e0db7d599836 <728734352743a78b4c5a7285b282127696a4a813
- Affected versionversion=d0f91938bede204a343473792529e0db7d599836 <76ddf84a52f0d8ec3f5db6ccce08faf202a17d28
- Affected versionversion=d0f91938bede204a343473792529e0db7d599836 <7ec3335dd89c8d169e9650e4bac64fde71fdf15b
- Affected versionversion=d0f91938bede204a343473792529e0db7d599836 <aa38bf74899de07cf70b50cd17f8ad45fb6654c8
- Affected versionversion=d0f91938bede204a343473792529e0db7d599836 <fa96c6baef1b5385e2f0c0677b32b3839e716076
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