Local availability failure via unsynchronized FIB threshold read
Published Feb 26, 2025 · Updated May 11, 2026
Race condition in the IPv4 FIB trie in Linux 5.2 through 5.18.12 allows local users to cause an unspecified availability failure. The tnode_free function compares accumulated freed-trie memory with sysctl_fib_sync_mem while that writable threshold can change concurrently, so the read is not atomic. Low-privilege local access and precise timing are required; public sources do not specify whether the resulting failure is a hang, crash, or another interruption.
Summary
What happened
Race condition in the IPv4 FIB trie in Linux 5.2 through 5.18.12 allows local users to cause an unspecified availability failure. The tnode_free function compares accumulated freed-trie memory with sysctl_fib_sync_mem while that writable threshold can change concurrently, so the read is not atomic. Low-privilege local access and precise timing are required; public sources do not specify whether the resulting failure is a hang, crash, or another interruption.
The record
- CVE
- CVE-2022-49637
- Published
- Feb 26, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-362
- 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=5.2
- Affected versionversion=9ab948a91b2c2abc8e82845c0e61f4b1683e3a4f <190cd4ff128373271e065afb20f1d2247b3f10c3
- Affected versionversion=9ab948a91b2c2abc8e82845c0e61f4b1683e3a4f <418b191d5f223a8cb6cab09eae1f72c04ba6adf2
- Affected versionversion=9ab948a91b2c2abc8e82845c0e61f4b1683e3a4f <73318c4b7dbd0e781aaababff17376b2894745c0
- Affected versionversion=9ab948a91b2c2abc8e82845c0e61f4b1683e3a4f <7c1acd98fb221dc0d847451b9ab86319f8b9916c
- Affected versionversion=9ab948a91b2c2abc8e82845c0e61f4b1683e3a4f <9be8aac91960ea32fd0e874758c9afee665c57d2
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