Executive Summary

Informations
Name CVE-2025-21957 First vendor Publication 2025-04-01
Vendor Cve Last vendor Modification 2025-04-11

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:

scsi: qla1280: Fix kernel oops when debug level > 2

A null dereference or oops exception will eventually occur when qla1280.c driver is compiled with DEBUG_QLA1280 enabled and ql_debug_level > 2. I think its clear from the code that the intention here is sg_dma_len(s) not length of sg_next(s) when printing the debug info.

Original Source

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

CWE : Common Weakness Enumeration

% Id Name
100 % CWE-476 NULL Pointer Dereference

CPE : Common Platform Enumeration

TypeDescriptionCount
Application 8
Os 3712

Sources (Detail)

https://git.kernel.org/stable/c/11a8dac1177a596648a020a7f3708257a2f95fee
https://git.kernel.org/stable/c/24602e2664c515a4f2950d7b52c3d5997463418c
https://git.kernel.org/stable/c/5233e3235dec3065ccc632729675575dbe3c6b8a
https://git.kernel.org/stable/c/7ac2473e727d67a38266b2b7e55c752402ab588c
https://git.kernel.org/stable/c/af71ba921d08c241a817010f96458dc5e5e26762
https://git.kernel.org/stable/c/afa27b7c17a48e01546ccaad0ab017ad0496a522
https://git.kernel.org/stable/c/c737e2a5fb7f90b96a96121da1b50a9c74ae9b8c
https://git.kernel.org/stable/c/ea371d1cdefb0951c7127a33bcd7eb931cf44571
Source Url

Alert History

If you want to see full details history, please login or register.
0
1
2
3
Date Informations
2025-06-26 02:41:12
  • Multiple Updates
2025-06-25 12:38:17
  • Multiple Updates
2025-06-24 02:45:38
  • Multiple Updates
2025-05-27 02:53:40
  • First insertion