Executive Summary
Informations | |||
---|---|---|---|
Name | CVE-2024-45009 | First vendor Publication | 2024-09-11 |
Vendor | Cve | Last vendor Modification | 2024-09-13 |
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: mptcp: pm: only decrement add_addr_accepted for MPJ req Adding the following warning ... WARN_ON_ONCE(msk->pm.add_addr_accepted == 0) ... before decrementing the add_addr_accepted counter helped to find a bug when running the "remove single subflow" subtest from the mptcp_join.sh selftest. Removing a 'subflow' endpoint will first trigger a RM_ADDR, then the subflow closure. Before this patch, and upon the reception of the RM_ADDR, the other peer will then try to decrement this add_addr_accepted. That's not correct because the attached subflows have not been created upon the reception of an ADD_ADDR. A way to solve that is to decrement the counter only if the attached subflow was an MP_JOIN to a remote id that was not 0, and initiated by the host receiving the RM_ADDR. |
Original Source
Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-45009 |
CPE : Common Platform Enumeration
Sources (Detail)
Alert History
Date | Informations |
---|---|
2025-01-08 03:04:59 |
|
2025-01-07 03:04:32 |
|
2024-12-25 03:03:10 |
|
2024-12-12 03:06:06 |
|
2024-11-23 03:03:07 |
|
2024-11-22 03:01:17 |
|
2024-11-20 02:59:37 |
|
2024-11-14 02:59:55 |
|
2024-11-09 02:59:55 |
|
2024-10-26 02:57:18 |
|
2024-10-25 02:59:11 |
|
2024-10-23 02:58:23 |
|
2024-10-03 02:53:34 |
|
2024-10-02 02:51:58 |
|
2024-09-14 21:29:47 |
|
2024-09-13 21:28:12 |
|
2024-09-12 17:27:27 |
|
2024-09-11 21:27:24 |
|