Executive Summary
| Informations | |||
|---|---|---|---|
| Name | CVE-2024-36930 | First vendor Publication | 2024-05-30 |
| Vendor | Cve | Last vendor Modification | 2024-06-10 |
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: spi: fix null pointer dereference within spi_sync If spi_sync() is called with the non-empty queue and the same spi_message is then reused, the complete callback for the message remains set while the context is cleared, leading to a null pointer dereference when the callback is invoked from spi_finalize_current_message(). With function inlining disabled, the call stack might look like this: _raw_spin_lock_irqsave from complete_with_flags+0x18/0x58 Fix this by also setting message->complete to NULL when the transfer is complete. |
Original Source
| Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-36930 |
CWE : Common Weakness Enumeration
| % | Id | Name |
|---|---|---|
| 100 % | CWE-476 | NULL Pointer Dereference |
CPE : Common Platform Enumeration
Sources (Detail)
Alert History
| Date | Informations |
|---|---|
| 2024-10-23 02:56:36 |
|
| 2024-10-03 02:51:57 |
|
| 2024-10-02 02:50:22 |
|
| 2024-09-15 02:48:14 |
|
| 2024-09-12 02:47:47 |
|
| 2024-09-06 02:46:02 |
|
| 2024-09-04 02:49:17 |
|
| 2024-08-22 02:47:20 |
|
| 2024-08-02 13:56:24 |
|
| 2024-08-02 01:35:41 |
|
| 2024-06-11 00:27:30 |
|
| 2024-05-31 00:27:31 |
|
| 2024-05-30 21:27:22 |
|
