Kernel compromise via dangling IEEE 802.15.4 socket pointer
Published Dec 27, 2024 · Updated Aug 5, 2026
Use-after-free in Linux 2.6.31 and later allows local users to corrupt kernel memory through a failed IEEE 802.15.4 socket creation. sock_init_data() stores the allocated sk pointer in the supplied sock before ieee802154_create() completes, and a later error frees sk without clearing that reference. Triggering requires low-privileged local access and a post-initialization creation failure; reuse of the dangling pointer can compromise kernel confidentiality, integrity, and availability.
Summary
What happened
Use-after-free in Linux 2.6.31 and later allows local users to corrupt kernel memory through a failed IEEE 802.15.4 socket creation. sock_init_data() stores the allocated sk pointer in the supplied sock before ieee802154_create() completes, and a later error frees sk without clearing that reference. Triggering requires low-privileged local access and a post-initialization creation failure; reuse of the dangling pointer can compromise kernel confidentiality, integrity, and availability.
The record
- CVE
- CVE-2024-56602
- Published
- Dec 27, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-416, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 27, 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=2.6.31
- Affected versionversion=9ec7671603573ede31207eb5b0b3e1aa211b2854 <03caa9bfb9fde97fb53d33decd7364514e6825cb
- Affected versionversion=9ec7671603573ede31207eb5b0b3e1aa211b2854 <14959fd7538b3be6d7617d9e60e404d6a8d4fd1f
- Affected versionversion=9ec7671603573ede31207eb5b0b3e1aa211b2854 <1d5fe782c0ff068d80933f9cfd0fd39d5434bbc9
- Affected versionversion=9ec7671603573ede31207eb5b0b3e1aa211b2854 <2b46994a6e76c8cc5556772932b9b60d03a55cd8
- Affected versionversion=9ec7671603573ede31207eb5b0b3e1aa211b2854 <b4982fbf13042e3bb33e04eddfea8b1506b5ea65
- Affected versionversion=9ec7671603573ede31207eb5b0b3e1aa211b2854 <b4fcd63f6ef79c73cafae8cf4a114def5fc3d80d
- Affected versionversion=9ec7671603573ede31207eb5b0b3e1aa211b2854 <e8bd6c5f5dc2234b4ea714380aedeea12a781754
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.
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