Linux Kernel POSIX File Lock fs/locks.c filelock_init allocation of resources

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.9 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Linux Kernel. It has been classified as problematic. This vulnerability affects the function filelock_init of the file fs/locks.c of the component POSIX File Lock Handler. The manipulation leads to allocation of resources.
This vulnerability is referenced as CVE-2022-0480. Remote exploitation of the attack is possible. No exploit is available.
Applying a patch is the recommended action to fix this issue.
Details
A vulnerability was found in Linux Kernel (Operating System) (unknown version). It has been rated as critical. This issue affects the function filelock_init of the file fs/locks.c of the component POSIX File Lock Handler. The manipulation with an unknown input leads to a allocation of resources vulnerability. Using CWE to declare the problem leads to CWE-770. The product allocates a reusable resource or group of resources on behalf of an actor without imposing any restrictions on the size or number of resources that can be allocated, in violation of the intended security policy for that actor. Impacted is availability. The summary by CVE is:
A flaw was found in the filelock_init in fs/locks.c function in the Linux kernel. This issue can lead to host memory exhaustion due to memcg not limiting the number of Portable Operating System Interface (POSIX) file locks.
The weakness was published 08/29/2022. The advisory is shared at bugzilla.redhat.com. The identification of this vulnerability is CVE-2022-0480 since 02/02/2022. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1499 for this issue.
The vulnerability scanner Nessus provides a plugin with the ID 240010 (TencentOS Server 2: kernel (TSSA-2024:1031)), which helps to determine the existence of the flaw in a target environment.
Applying a patch is able to eliminate this problem. The bugfix is ready for download at git.kernel.org.
The vulnerability is also documented in the vulnerability database at Tenable (240010). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.0VulDB Meta Temp Score: 5.9
VulDB Base Score: 6.5
VulDB Temp Score: 6.2
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: Allocation of resourcesCWE: CWE-770 / CWE-400 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: Yes
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: 240010
Nessus Name: TencentOS Server 2: kernel (TSSA-2024:1031)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
0-Day Time: 🔍
Patch: git.kernel.org
Timeline
02/02/2022 🔍08/29/2022 🔍
08/29/2022 🔍
06/17/2025 🔍
Sources
Vendor: kernel.orgAdvisory: 3373
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2022-0480 (🔍)
GCVE (CVE): GCVE-0-2022-0480
GCVE (VulDB): GCVE-100-207485
Entry
Created: 08/29/2022 18:33Updated: 06/17/2025 16:23
Changes: 08/29/2022 18:33 (43), 10/09/2022 09:56 (1), 10/09/2022 09:58 (11), 06/17/2025 16:23 (16)
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.