Linux Kernel up to 5.18.3 xfrm4_protocol_init initialization

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.4 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in Linux Kernel up to 5.18.3. This vulnerability affects the function xfrm4_protocol_init. This manipulation causes initialization.
This vulnerability appears as CVE-2022-49345. There is no available exploit.
You should upgrade the affected component.
Details
A vulnerability classified as problematic was found in Linux Kernel up to 5.18.3. Affected by this vulnerability is the function xfrm4_protocol_init. The manipulation with an unknown input leads to a initialization vulnerability. The CWE definition for the vulnerability is CWE-665. The product does not initialize or incorrectly initializes a resource, which might leave the resource in an unexpected state when it is accessed or used. The impact remains unknown. The summary by CVE is:
In the Linux kernel, the following vulnerability has been resolved: net: xfrm: unexport __init-annotated xfrm4_protocol_init() EXPORT_SYMBOL and __init is a bad combination because the .init.text section is freed up after the initialization. Hence, modules cannot use symbols annotated __init. The access to a freed symbol may end up with kernel panic. modpost used to detect it, but it has been broken for a decade. Recently, I fixed modpost so it started to warn it again, then this showed up in linux-next builds. There are two ways to fix it: - Remove __init - Remove EXPORT_SYMBOL I chose the latter for this case because the only in-tree call-site, net/ipv4/xfrm4_policy.c is never compiled as modular. (CONFIG_XFRM is boolean)
The advisory is shared at git.kernel.org. This vulnerability is known as CVE-2022-49345 since 02/26/2025. Technical details are known, but no exploit is available.
The vulnerability scanner Nessus provides a plugin with the ID 241018 (EulerOS 2.0 SP13 : kernel (EulerOS-SA-2025-1704)), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 4.9.318, 4.14.283, 4.19.247, 5.4.198, 5.10.122, 5.15.47, 5.17.15 or 5.18.4 eliminates this vulnerability. Applying the patch c58d82a1264813e69119c13e9804e2e60b664ad5/e53cd3814504b2cadaba4d5a8a07eeea9ddacd03/31f3c6a4dcd3260a386e62cef2d5b36e902600a1/ef6d2354de238b065d8799c80da4be9a6af18e39/be3884d5cd04ccd58294b83a02d70b7c5fca19d3/85a055c03691e51499123194a14a0c249cf33227/e04d59cfe0c0129df7aba7ef7bb17b96be2a64f2/2b253fbc9f7b5db18d716436bdcf8ecef09fd63d/4a388f08d8784af48f352193d2b72aaf167a57a1 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the databases at Tenable (241018) and CERT Bund (WID-SEC-2025-2107). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Affected
- Google Container-Optimized OS
- Debian Linux
- Amazon Linux 2
- Red Hat Enterprise Linux
- Ubuntu Linux
- SUSE Linux
- Oracle Linux
- SUSE openSUSE
- Open Source Linux Kernel
- RESF Rocky Linux
- Dell Secure Connect Gateway
- IBM QRadar SIEM
- Dell NetWorker
Product
Type
Vendor
Name
Version
- 4.9.317
- 4.14.282
- 4.19.246
- 5.4.197
- 5.10.121
- 5.15.0
- 5.15.1
- 5.15.2
- 5.15.3
- 5.15.4
- 5.15.5
- 5.15.6
- 5.15.7
- 5.15.8
- 5.15.9
- 5.15.10
- 5.15.11
- 5.15.12
- 5.15.13
- 5.15.14
- 5.15.15
- 5.15.16
- 5.15.17
- 5.15.18
- 5.15.19
- 5.15.20
- 5.15.21
- 5.15.22
- 5.15.23
- 5.15.24
- 5.15.25
- 5.15.26
- 5.15.27
- 5.15.28
- 5.15.29
- 5.15.30
- 5.15.31
- 5.15.32
- 5.15.33
- 5.15.34
- 5.15.35
- 5.15.36
- 5.15.37
- 5.15.38
- 5.15.39
- 5.15.40
- 5.15.41
- 5.15.42
- 5.15.43
- 5.15.44
- 5.15.45
- 5.15.46
- 5.17.0
- 5.17.1
- 5.17.2
- 5.17.3
- 5.17.4
- 5.17.5
- 5.17.6
- 5.17.7
- 5.17.8
- 5.17.9
- 5.17.10
- 5.17.11
- 5.17.12
- 5.17.13
- 5.17.14
- 5.18.0
- 5.18.1
- 5.18.2
- 5.18.3
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 5.4
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.5
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: InitializationCWE: CWE-665
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: Partially
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 241018
Nessus Name: EulerOS 2.0 SP13 : kernel (EulerOS-SA-2025-1704)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Kernel 4.9.318/4.14.283/4.19.247/5.4.198/5.10.122/5.15.47/5.17.15/5.18.4
Patch: c58d82a1264813e69119c13e9804e2e60b664ad5/e53cd3814504b2cadaba4d5a8a07eeea9ddacd03/31f3c6a4dcd3260a386e62cef2d5b36e902600a1/ef6d2354de238b065d8799c80da4be9a6af18e39/be3884d5cd04ccd58294b83a02d70b7c5fca19d3/85a055c03691e51499123194a14a0c249cf33227/e04d59cfe0c0129df7aba7ef7bb17b96be2a64f2/2b253fbc9f7b5db18d716436bdcf8ecef09fd63d/4a388f08d8784af48f352193d2b72aaf167a57a1
Timeline
02/26/2025 🔍02/26/2025 🔍
02/26/2025 🔍
02/16/2026 🔍
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2022-49345 (🔍)
GCVE (CVE): GCVE-0-2022-49345
GCVE (VulDB): GCVE-100-296893
CERT Bund: WID-SEC-2025-2107 - Linux Kernel: Mehrere Schwachstellen
Entry
Created: 02/26/2025 08:16Updated: 02/16/2026 05:10
Changes: 02/26/2025 08:16 (58), 07/01/2025 15:04 (2), 09/23/2025 02:09 (11), 11/28/2025 05:54 (7), 01/12/2026 02:42 (1), 02/09/2026 04:04 (1), 02/16/2026 05:10 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.