CVE-2024-57949

irqchip/gic-v3-its: Don't enable interrupts in its_irq_set_vcpu_affinity()

MEDIUM
5.5
CVSS Score
Published: February 9, 2025 at 11:37 AM UTC
Updated: June 17, 2026 at 08:14 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: irqchip/gic-v3-its: Don't enable interrupts in its_irq_set_vcpu_affinity() The following call-chain leads to enabling interrupts in a nested interrupt disabled section: irq_set_vcpu_affinity() irq_get_desc_lock() raw_spin_lock_irqsave() <--- Disable interrupts its_irq_set_vcpu_affinity() guard(raw_spinlock_irq) <--- Enables interrupts when leaving the guard() irq_put_desc_unlock() <--- Warns because interrupts are enabled This was broken in commit b97e8a2f7130, which replaced the original raw_spin_[un]lock() pair with guard(raw_spinlock_irq). Fix the issue by using guard(raw_spinlock). [ tglx: Massaged change log ]

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v ≥ 6.9.66.1.95 ≤ v < 6.1.1276.10 ≤ v < 6.12.116.10 ≤ v < 6.136.6.35 ≤ v < 6.6.746.9.6 ≤ v < 6.106.9.6 ≤ v < 6.12.112458f2362f695584bd824c922caa07ffc4fe0d5c5c0fb9cb404a2efbbc319ff9d1b877cf4e47e9506.1.956.13 rc16.13 rc26.13 rc36.13 rc46.13 rc56.13 rc66.13 rc76.6.356.9.6b97e8a2f7130a4b30d1502003095833d16c028b3c11039edbabdbccf0728844f1002d750d06f9eff
Vendor states this is fixed in 35cb2c6ce7da545f3b5cb1e6473ad7c3a6f08310 (fixed)
Vendor states this is fixed in 6c84ff2e788fce0099ee3e71a3ed258b1ca1a223 (fixed)
Vendor states this is fixed in 93955a7788121ab5a0f7f27e988b2ed1135a4866 (fixed)
Vendor states this is fixed in d7b0e89610dd45ac6cf0d6f99bfa9ccc787db344 (fixed)
Vendor states this is fixed in 6.1.127 (unaffected)
Vendor states this is fixed in 6.10 (unaffected)
Vendor states this is fixed in 6.12.11 (unaffected)
Vendor states this is fixed in 6.13 (unaffected)
Vendor states this is fixed in 6.6.74 (unaffected)

References (5)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/35cb2c6ce7da545f3b5cb1e6473ad7c3a6f08310
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/6c84ff2e788fce0099ee3e71a3ed258b1ca1a223
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/93955a7788121ab5a0f7f27e988b2ed1135a4866
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/d7b0e89610dd45ac6cf0d6f99bfa9ccc787db344
Source: af854a3a-2127-422b-91ae-364da2661108
https://lists.debian.org/debian-lts-announce/2025/03/msg00001.html

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

5.5MEDIUMCISA-ADP
Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-667

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card