Kernel memory corruption via rearmed RxRPC keepalive timer
Published Feb 26, 2025 · Updated Aug 5, 2026
Use-after-free in Linux's RxRPC network namespace teardown allows local users to crash the kernel during namespace cleanup. In rxrpc_exit_net(), the keepalive worker can observe rxnet->live before it is cleared, then rearm peer_keepalive_timer after del_timer_sync() returns and before cancellation completes. Local low-privileged access is required; the resulting timer can outlive the freed network namespace and corrupt kernel memory, causing a host crash or broader kernel compromise.
Summary
What happened
Use-after-free in Linux's RxRPC network namespace teardown allows local users to crash the kernel during namespace cleanup. In rxrpc_exit_net(), the keepalive worker can observe rxnet->live before it is cleared, then rearm peer_keepalive_timer after del_timer_sync() returns and before cancellation completes. Local low-privileged access is required; the resulting timer can outlive the freed network namespace and corrupt kernel memory, causing a host crash or broader kernel compromise.
The record
- CVE
- CVE-2022-49087
- Published
- Feb 26, 2025
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-416
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 26, 2025CVE 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.17
- Affected versionversion=ace45bec6d77bc061c3c3d8ad99e298ea9800c2b <08ff0e74fab517dbc44e11b8bc683dd4ecc65950
- Affected versionversion=ace45bec6d77bc061c3c3d8ad99e298ea9800c2b <1946014ca3b19be9e485e780e862c375c6f98bad
- Affected versionversion=ace45bec6d77bc061c3c3d8ad99e298ea9800c2b <41024a40f6c793abbb916a857f18fb009f07464c
- Affected versionversion=ace45bec6d77bc061c3c3d8ad99e298ea9800c2b <571d8e1d154ca18f08dcb72b69318d36e10010a0
- Affected versionversion=ace45bec6d77bc061c3c3d8ad99e298ea9800c2b <7ee84d29f22de6f6c63fad6c54690517659862f1
- Affected versionversion=ace45bec6d77bc061c3c3d8ad99e298ea9800c2b <864297ee30727ae6233f80296b7fc91442620b05
- Affected versionversion=ace45bec6d77bc061c3c3d8ad99e298ea9800c2b <cd8aef1f30d1215648e4e6686cfb422004851429
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