Kernel panic via freed initialization symbol
Published Feb 26, 2025 · Updated May 11, 2026
Use-after-free in Linux kernel IPv6 segment-routing HMAC code from 4.10 allows local users to trigger a kernel panic through a module call. The exported seg6_hmac_init symbol remains initialization-annotated after its .init.text storage is freed, so a later module call accesses released kernel code. Reachability requires a module to invoke that symbol after initialization; successful triggering panics the kernel without reported code execution or data access.
Summary
What happened
Use-after-free in Linux kernel IPv6 segment-routing HMAC code from 4.10 allows local users to trigger a kernel panic through a module call. The exported seg6_hmac_init symbol remains initialization-annotated after its .init.text storage is freed, so a later module call accesses released kernel code. Reachability requires a module to invoke that symbol after initialization; successful triggering panics the kernel without reported code execution or data access.
The record
- CVE
- CVE-2022-49339
- Published
- Feb 26, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 26, 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=4.10
- Affected versionversion=bf355b8d2c30a289232042cacc1cfaea4923936c <1084716f76c8045eadf92a9d9a62641f3c8d8c90
- Affected versionversion=bf355b8d2c30a289232042cacc1cfaea4923936c <317260b3eb6384a05a8af212308fa50f3b2e8290
- Affected versionversion=bf355b8d2c30a289232042cacc1cfaea4923936c <3e6de5037148c5a93a436b1e8d2edad3dac11755
- Affected versionversion=bf355b8d2c30a289232042cacc1cfaea4923936c <5801f064e35181c71857a80ff18af4dbec3c5f5c
- Affected versionversion=bf355b8d2c30a289232042cacc1cfaea4923936c <5d9c1b081ad28c852a97e10dd75412546497694a
- Affected versionversion=bf355b8d2c30a289232042cacc1cfaea4923936c <64aef8efe96c1616142c4476a05731306fc4494e
- Affected versionversion=bf355b8d2c30a289232042cacc1cfaea4923936c <9ba4416b831eeb4d185e88e73488d1d21288e63a
- Affected versionversion=bf355b8d2c30a289232042cacc1cfaea4923936c <ab8b2c2de273ec1d698a18e399896a6febb5cda0
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