System crash via oversized TIPC bearer name
Published Feb 26, 2025 · Updated May 11, 2026
Use of uninitialized memory in affected Linux kernel releases allows local users to crash the system via a crafted TIPC bearer name. The __tipc_nl_bearer_enable path accepts TIPC_NLA_BEARER_NAME without checking its attribute length, then treats its data as a terminated string during bearer validation and error logging. Reaching the Generic Netlink operation requires local low-privileged access; the published assessment identifies availability loss only, with no data disclosure or modification.
Summary
What happened
Use of uninitialized memory in affected Linux kernel releases allows local users to crash the system via a crafted TIPC bearer name. The __tipc_nl_bearer_enable path accepts TIPC_NLA_BEARER_NAME without checking its attribute length, then treats its data as a terminated string during bearer validation and error logging. Reaching the Generic Netlink operation requires local low-privileged access; the published assessment identifies availability loss only, with no data disclosure or modification.
The record
- CVE
- CVE-2022-49374
- Published
- Feb 26, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-908, T1499
- 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.17
- Affected versionversion=cb30a63384bc91d5da06e1cede1115f666a29271 <292be63c382ce20673ee61dff1ee9ed4a3dcaae7
- Affected versionversion=cb30a63384bc91d5da06e1cede1115f666a29271 <3af15272cde28fe5c8489174b8624e232c1775ec
- Affected versionversion=cb30a63384bc91d5da06e1cede1115f666a29271 <7f36f798f89bf32c0164049cb0e3fd1af613d0bb
- Affected versionversion=cb30a63384bc91d5da06e1cede1115f666a29271 <8b91d0dfc839e67708c905648cd0e7507a2263e5
- Affected versionversion=cb30a63384bc91d5da06e1cede1115f666a29271 <92a930fcf4250fe961f6238b99af0bc405799f39
- Affected versionversion=cb30a63384bc91d5da06e1cede1115f666a29271 <b8fac8e321044a9ac50f7185b4e9d91a7745e4b0
- Affected versionversion=cb30a63384bc91d5da06e1cede1115f666a29271 <f07670871f4d19e613740eebe210e7e9ea535973
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.
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