Security readout for executives and security teams
Plain-English summary
This is a Linux kernel availability flaw in the GICv3 ITS interrupt controller code. A local user could potentially trigger a kernel failure condition, causing service disruption. There is no source evidence of active exploitation, but systems running affected kernels should receive vendor kernel updates because the impact is availability, not data theft.
Executive priority
Treat as a scheduled but important kernel maintenance item. It is not currently sourced as actively exploited, but the worst-case impact is system outage, so prioritize high-availability Linux hosts and platforms where local users or workloads share kernel access.
Technical view
The bug is in irqchip/gic-v3-its within its_irq_set_vcpu_affinity(). A guard(raw_spinlock_irq) change could re-enable interrupts while still inside a nested interrupt-disabled section, causing warnings and unsafe lock-state handling. The upstream fix replaces it with guard(raw_spinlock). CVSS is 5.5, local, low-privilege, availability-high impact.
Likely exposure
Exposure is most likely on Linux systems using affected kernel builds that include the vulnerable gic-v3-its irqchip change. The source lists affected Linux versions including 6.10, 6.1.127, 6.6.74, 6.12.11, and 6.13, but distribution backport status must be verified with vendors.
Exploitation context
The CVE is not listed as KEV, and the supplied sources do not report active exploitation. The CVSS vector indicates local access with low privileges and no user interaction. The practical risk is denial of service or instability, not confidentiality or integrity compromise.
Researcher notes
The root cause is a locking primitive mismatch introduced by commit b97e8a2f7130. The fix changes the guard type to avoid enabling interrupts before irq_put_desc_unlock(). Source detail is sufficient for patch validation, but incomplete for distro-specific exposure without vendor advisories.
Mitigation direction
- Apply Linux kernel updates that include the referenced stable fixes.
- Use distribution advisories to confirm fixed package versions before rollout.
- Prioritize systems where kernel availability outages have high business impact.
- Track Debian or other vendor advisories if running packaged kernels.
Validation and detection
- Inventory running kernel versions across Linux hosts.
- Check whether vendor kernel packages include the stable fix commits.
- Review kernel logs for related interrupt or lock-state warnings.
- Confirm patched systems boot and pass normal workload health checks.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-667: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2024-57949 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H1.83.6CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
5.5MediumVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/d7b0e89610dd45ac6cf0d6f99bfa9ccc787db344CVE reference, Linux
- https://git.kernel.org/stable/c/6c84ff2e788fce0099ee3e71a3ed258b1ca1a223CVE reference, Linux
- https://git.kernel.org/stable/c/93955a7788121ab5a0f7f27e988b2ed1135a4866CVE reference, Linux
- https://git.kernel.org/stable/c/35cb2c6ce7da545f3b5cb1e6473ad7c3a6f08310CVE reference, Linux
- https://lists.debian.org/debian-lts-announce/2025/03/msg00001.htmlCVE reference, CVE
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Locking
Improper Locking represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.