CVE-2022-49017Network attack vector

Kernel crash via stale TIPC packet control block

Published Oct 21, 2024 · Updated Aug 5, 2026

Use-after-free in the Linux kernel TIPC crypto receive path allows remote authenticated users to crash or corrupt the kernel via encrypted packets. The tipc_msg_validate function can free and replace the socket buffer, but tipc_crypto_rcv_complete continues dereferencing the control block from the freed buffer instead of fetching it from the replacement. Reachability requires an enabled TIPC bearer, TIPC encryption, and a peer holding the cluster key; the stale access can panic the host or corrupt kernel memory.

CVSS severity8.8
High
EPSS probability0.64%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Use-after-free in the Linux kernel TIPC crypto receive path allows remote authenticated users to crash or corrupt the kernel via encrypted packets. The tipc_msg_validate function can free and replace the socket buffer, but tipc_crypto_rcv_complete continues dereferencing the control block from the freed buffer instead of fetching it from the replacement. Reachability requires an enabled TIPC bearer, TIPC encryption, and a peer holding the cluster key; the stale access can panic the host or corrupt kernel memory.

The record

CVE
CVE-2022-49017
Published
Oct 21, 2024
Updated
Aug 5, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
CWE-416, T1499
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Oct 21, 2024CVE publishedPublication date reported by the CVE source.
  2. 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.

  1. Affected versionversion=5.5
  2. Affected versionversion=fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 <1daec0815655e110c6f206c5e777a4af8168ff58
  3. Affected versionversion=fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 <3067bc61fcfe3081bf4807ce65560f499e895e77
  4. Affected versionversion=fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 <a1ba595e35aa3afbe417ff0af353afb9f65559c0
  5. Affected versionversion=fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 <e128190adb2edfd5042105b5d1ed4553f295f5ef

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

The Linux Kernel Organization · Linuxversion=5.5; version=fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 <1daec0815655e110c6f206c5e777a4af8168ff58; version=fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 <3067bc61fcfe3081bf4807ce65560f499e895e77; version=fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 <a1ba595e35aa3afbe417ff0af353afb9f65559c0; version=fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 <e128190adb2edfd5042105b5d1ed4553f295f5ef

Published CVSS scores

8.8Linux CNACVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-416Use After Free
T1499Endpoint Denial of Service

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