Executive Summary
| Informations | |||
|---|---|---|---|
| Name | CVE-2022-49414 | First vendor Publication | 2025-02-26 |
| Vendor | Cve | Last vendor Modification | 2025-04-17 |
Security-Database Scoring CVSS v3
| Cvss vector : CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H | |||
|---|---|---|---|
| Overall CVSS Score | 4.7 | ||
| Base Score | 4.7 | Environmental Score | 4.7 |
| impact SubScore | 3.6 | Temporal Score | 4.7 |
| Exploitabality Sub Score | 1 | ||
| Attack Vector | Local | Attack Complexity | High |
| Privileges Required | Low | User Interaction | None |
| Scope | Unchanged | Confidentiality Impact | None |
| Integrity Impact | None | Availability Impact | High |
| Calculate full CVSS 3.0 Vectors scores | |||
Security-Database Scoring CVSS v2
| Cvss vector : | |||
|---|---|---|---|
| Cvss Base Score | N/A | Attack Range | N/A |
| Cvss Impact Score | N/A | Attack Complexity | N/A |
| Cvss Expoit Score | N/A | Authentication | N/A |
| Calculate full CVSS 2.0 Vectors scores | |||
Detail
| In the Linux kernel, the following vulnerability has been resolved: ext4: fix race condition between ext4_write and ext4_convert_inline_data Hulk Robot reported a BUG_ON: Above issue may happen as follows: The lock held by ext4_convert_inline_data is xattr_sem, but the lock held by generic_perform_write is i_rwsem. Therefore, the two locks can be concurrent. To solve above issue, we add inode_lock() for ext4_convert_inline_data(). At the same time, move ext4_convert_inline_data() in front of ext4_punch_hole(), remove similar handling from ext4_punch_hole(). |
Original Source
| Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-49414 |
CWE : Common Weakness Enumeration
| % | Id | Name |
|---|---|---|
| 100 % | CWE-362 | Race Condition |
CPE : Common Platform Enumeration
Sources (Detail)
Alert History
| Date | Informations |
|---|---|
| 2025-06-26 02:09:41 |
|
| 2025-06-25 12:22:32 |
|
| 2025-06-24 02:14:17 |
|
| 2025-05-27 02:11:02 |
|
| 2025-02-26 17:20:31 |
|
