Executive Summary
Informations | |||
---|---|---|---|
Name | CVE-2024-46678 | First vendor Publication | 2024-09-13 |
Vendor | Cve | Last vendor Modification | 2024-09-23 |
Security-Database Scoring CVSS v3
Cvss vector : CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H | |||
---|---|---|---|
Overall CVSS Score | 5.5 | ||
Base Score | 5.5 | Environmental Score | 5.5 |
impact SubScore | 3.6 | Temporal Score | 5.5 |
Exploitabality Sub Score | 1.8 | ||
Attack Vector | Local | Attack Complexity | Low |
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: bonding: change ipsec_lock from spin lock to mutex In the cited commit, bond->ipsec_lock is added to protect ipsec_list, hence xdo_dev_state_add and xdo_dev_state_delete are called inside this lock. As ipsec_lock is a spin lock and such xfrmdev ops may sleep, "scheduling while atomic" will be triggered when changing bond's active slave. [ 101.055189] BUG: scheduling while atomic: bash/902/0x00000200 [ 101.055726] Modules linked in: [ 101.058211] CPU: 3 PID: 902 Comm: bash Not tainted 6.9.0-rc4+ #1 [ 101.058760] Hardware name: [ 101.059434] Call Trace: [ 101.059436] As bond_ipsec_add_sa_all and bond_ipsec_del_sa_all are only called from bond_change_active_slave, which requires holding the RTNL lock. And bond_ipsec_add_sa and bond_ipsec_del_sa are xfrm state xdo_dev_state_add and xdo_dev_state_delete APIs, which are in user context. So ipsec_lock doesn't have to be spin lock, change it to mutex, and thus the above issue can be resolved. |
Original Source
Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-46678 |
CWE : Common Weakness Enumeration
% | Id | Name |
---|---|---|
100 % | CWE-667 | Insufficient Locking |
CPE : Common Platform Enumeration
Sources (Detail)
Alert History
Date | Informations |
---|---|
2025-01-08 03:05:09 |
|
2025-01-07 03:04:42 |
|
2024-12-25 03:03:20 |
|
2024-12-12 03:06:16 |
|
2024-11-23 03:03:16 |
|
2024-11-22 03:01:26 |
|
2024-11-20 02:59:46 |
|
2024-11-14 03:00:05 |
|
2024-11-09 03:00:04 |
|
2024-10-26 02:57:27 |
|
2024-10-25 02:59:20 |
|
2024-10-23 02:58:31 |
|
2024-10-03 02:53:41 |
|
2024-10-02 00:27:57 |
|
2024-09-23 21:27:59 |
|
2024-09-14 02:48:03 |
|
2024-09-14 02:47:03 |
|
2024-09-13 21:27:37 |
|
2024-09-13 13:27:27 |
|