Diagnostic ambiguity via duplicate init symbols
Published Feb 26, 2025 · Updated May 11, 2026
Improper function naming in the virtio_console driver in Linux 2.6.24 through 5.17.2 causes ambiguous kernel diagnostics. The driver registers anonymous module_init() and module_exit() functions that emit identical init symbol names instead of unique driver-specific names. The ambiguity appears in System.map, crash, oops, bug, and initcall_debug output and is limited to identifying the responsible initialization or exit function.
Summary
What happened
Improper function naming in the virtio_console driver in Linux 2.6.24 through 5.17.2 causes ambiguous kernel diagnostics. The driver registers anonymous module_init() and module_exit() functions that emit identical init symbol names instead of unique driver-specific names. The ambiguity appears in System.map, crash, oops, bug, and initcall_debug output and is limited to identifying the responsible initialization or exit function.
The record
- CVE
- CVE-2022-49100
- Published
- Feb 26, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- 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=2.6.24
- Affected versionversion=31610434bc3523c0b01a10917a1185096a03c4c8 <0f3d824bd70a1303464d5e93ee3e7afe7832fe89
- Affected versionversion=31610434bc3523c0b01a10917a1185096a03c4c8 <3504b0a177208eda85bf472bbf7c9aa77d2b8343
- Affected versionversion=31610434bc3523c0b01a10917a1185096a03c4c8 <3fd5dee7404ce40c79cba468bb2510115639d975
- Affected versionversion=31610434bc3523c0b01a10917a1185096a03c4c8 <44c2d5fbe7b2bd1f8cb114d608a591a73a5d4ae6
- Affected versionversion=31610434bc3523c0b01a10917a1185096a03c4c8 <71612aee09ecea3475f8751dc841d75a011b1fd0
- Affected versionversion=31610434bc3523c0b01a10917a1185096a03c4c8 <7deaddb704713608e0ae559e27185581b9af71a0
- Affected versionversion=31610434bc3523c0b01a10917a1185096a03c4c8 <93e3d88321d2274fa4e26b006e19cc10fec331c2
- Affected versionversion=31610434bc3523c0b01a10917a1185096a03c4c8 <c69b442125bf009fce26e15aa5616caf8a3673c3
- Affected versionversion=31610434bc3523c0b01a10917a1185096a03c4c8 <fefb8a2a941338d871e2d83fbd65fbfa068857bd
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
No sourced classifications are available.
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