Executive Summary
| Informations | |||
|---|---|---|---|
| Name | CVE-2022-48648 | First vendor Publication | 2024-04-28 |
| Vendor | Cve | Last vendor Modification | 2025-01-14 |
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: sfc: fix null pointer dereference in efx_hard_start_xmit Trying to get the channel from the tx_queue variable here is wrong because we can only be here if tx_queue is NULL, so we shouldn't dereference it. As the above comment in the code says, this is very unlikely to happen, but it's wrong anyway so let's fix it. I hit this issue because of a different bug that caused tx_queue to be NULL. If that happens, this is the error message that we get here: |
Original Source
| Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-48648 |
CWE : Common Weakness Enumeration
| % | Id | Name |
|---|---|---|
| 100 % | CWE-476 | NULL Pointer Dereference |
CPE : Common Platform Enumeration
Sources (Detail)
Alert History
| Date | Informations |
|---|---|
| 2025-06-26 02:08:18 |
|
| 2025-06-25 12:21:05 |
|
| 2025-06-24 02:13:00 |
|
| 2025-05-27 13:22:25 |
|
| 2025-05-27 02:08:04 |
|
| 2025-03-29 03:13:16 |
|
| 2025-03-28 13:33:37 |
|
| 2025-03-28 02:55:52 |
|
| 2025-03-19 02:52:33 |
|
| 2025-03-18 03:04:13 |
|
| 2025-03-14 02:53:14 |
|
| 2025-02-22 03:01:50 |
|
| 2025-01-14 17:21:08 |
|
| 2024-11-25 09:25:57 |
|
| 2024-04-29 17:27:26 |
|
| 2024-04-28 17:27:28 |
|
