Executive Summary

Informations
Name CVE-2022-49640 First vendor Publication 2025-02-26
Vendor Cve Last vendor Modification 2025-03-11

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:

sysctl: Fix data races in proc_douintvec_minmax().

A sysctl variable is accessed concurrently, and there is always a chance of data-race. So, all readers and writers need some basic protection to avoid load/store-tearing.

This patch changes proc_douintvec_minmax() to use READ_ONCE() and WRITE_ONCE() internally to fix data-races on the sysctl side. For now, proc_douintvec_minmax() itself is tolerant to a data-race, but we still need to add annotations on the other subsystem's side.

Original Source

Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-49640

CWE : Common Weakness Enumeration

% Id Name
100 % CWE-362 Race Condition

CPE : Common Platform Enumeration

TypeDescriptionCount
Application 8
Os 3545

Sources (Detail)

https://git.kernel.org/stable/c/2d3b559df3ed39258737789aae2ae7973d205bc1
https://git.kernel.org/stable/c/40e0477a7371d101c55b69d9c32a7a1ed82ab5ea
https://git.kernel.org/stable/c/b60eddf98b9716651069dfda296c91311a7a6293
https://git.kernel.org/stable/c/e3a2144b3b6bf9ecafd91087c8b8b48171ec19df
Source Url

Alert History

If you want to see full details history, please login or register.
0
1
2
3
4
5
6
7
8
9
10
11
12
Date Informations
2025-06-26 02:10:07
  • Multiple Updates
2025-06-25 12:22:57
  • Multiple Updates
2025-06-24 02:14:42
  • Multiple Updates
2025-05-27 02:11:27
  • Multiple Updates
2025-03-29 03:15:01
  • Multiple Updates
2025-03-28 13:35:20
  • Multiple Updates
2025-03-28 02:57:25
  • Multiple Updates
2025-03-19 00:20:46
  • Multiple Updates
2025-03-18 00:20:49
  • Multiple Updates
2025-03-14 00:21:16
  • Multiple Updates
2025-03-13 21:21:10
  • Multiple Updates
2025-03-12 05:50:02
  • Multiple Updates
2025-02-26 17:20:29
  • First insertion