Executive Summary

Informations
Name CVE-2025-21849 First vendor Publication 2025-03-12
Vendor Cve Last vendor Modification 2025-03-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:

drm/i915/gt: Use spin_lock_irqsave() in interruptible context

spin_lock/unlock() functions used in interrupt contexts could result in a deadlock, as seen in GitLab issue #13399, which occurs when interrupt comes in while holding a lock.

Try to remedy the problem by saving irq state before spin lock acquisition.

v2: add irqs' state save/restore calls to all locks/unlocks in
signal_irq_work() execution (Maciej)

v3: use with spin_lock_irqsave() in guc_lrc_desc_unpin() instead
of other lock/unlock calls and add Fixes and Cc tags (Tvrtko);
change title and commit message

(cherry picked from commit c088387ddd6482b40f21ccf23db1125e8fa4af7e)

Original Source

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

CWE : Common Weakness Enumeration

% Id Name
100 % CWE-667 Insufficient Locking

CPE : Common Platform Enumeration

TypeDescriptionCount
Application 8
Os 3704

Sources (Detail)

https://git.kernel.org/stable/c/2bf1f4c129db7a10920655b000f0292f1ee509c2
https://git.kernel.org/stable/c/47ae46ac5407646420e06b78e0dad331e56a4bb4
https://git.kernel.org/stable/c/e49477f7f78598295551d486ecc7f020d796432e
Source Url

Alert History

If you want to see full details history, please login or register.
0
1
2
3
4
5
6
7
8
Date Informations
2025-03-29 03:46:36
  • Multiple Updates
2025-03-28 13:49:06
  • Multiple Updates
2025-03-28 03:24:27
  • Multiple Updates
2025-03-25 03:30:15
  • Multiple Updates
2025-03-19 00:20:33
  • Multiple Updates
2025-03-18 00:20:36
  • Multiple Updates
2025-03-14 00:20:47
  • Multiple Updates
2025-03-13 21:20:37
  • Multiple Updates
2025-03-12 13:20:39
  • First insertion