7
CVE-2022-3649
- EPSS 0.09%
- Published 21.10.2022 20:15:09
- Last modified 21.11.2024 07:19:57
- Source cna@vuldb.com
- Teams watchlist Login
- Open Login
A vulnerability was found in Linux Kernel. It has been classified as problematic. Affected is the function nilfs_new_inode of the file fs/nilfs2/inode.c of the component BPF. The manipulation leads to use after free. It is possible to launch the attack remotely. It is recommended to apply a patch to fix this issue. The identifier of this vulnerability is VDB-211992.
Data is provided by the National Vulnerability Database (NVD)
Linux ≫ Linux Kernel Version < 4.9.331
Linux ≫ Linux Kernel Version >= 4.10 < 4.14.296
Linux ≫ Linux Kernel Version >= 4.15 < 4.19.262
Linux ≫ Linux Kernel Version >= 4.20 < 5.4.220
Linux ≫ Linux Kernel Version >= 5.5 < 5.10.148
Linux ≫ Linux Kernel Version >= 5.11 < 5.15.74
Linux ≫ Linux Kernel Version >= 5.16 < 5.19.16
Linux ≫ Linux Kernel Version >= 6.0 < 6.0.2
Debian ≫ Debian Linux Version10.0
Netapp ≫ Active Iq Unified Manager Version- SwPlatformvsphere
Netapp ≫ H300s Firmware Version-
Netapp ≫ H500s Firmware Version-
Netapp ≫ H700s Firmware Version-
Netapp ≫ H410s Firmware Version-
Zu dieser CVE wurde keine CISA KEV oder CERT.AT-Warnung gefunden.
| Type | Source | Score | Percentile |
|---|---|---|---|
| EPSS | FIRST.org | 0.09% | 0.255 |
| Source | Base Score | Exploit Score | Impact Score | Vector string |
|---|---|---|---|---|
| nvd@nist.gov | 7 | 1 | 5.9 |
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
|
| cna@vuldb.com | 3.1 | 1.6 | 1.4 |
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L
|
CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data.
CWE-416 Use After Free
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.