LiveActive security incident?Get immediate response
CVE Record

CVE-2024-35806: soc: fsl: qbman: Always disable interrupts when taking cgr_lock

In the Linux kernel, the following vulnerability has been resolved: soc: fsl: qbman: Always disable interrupts when taking cgr_lock smp_call_function_single disables IRQs when executing the callback. To prevent deadlocks, we must disable IRQs when taking cgr_lock elsewhere. This is already done by qman_update_cgr and qman_delete_cgr; fix the other lockers.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2024-35806 is a Linux kernel flaw in the Freescale/NXP QorIQ queue manager area. The issue is incorrect interrupt handling around a shared lock, which can cause deadlocks. Business impact is primarily potential system availability disruption on affected kernels using this subsystem.

Executive priority

Track and remediate through normal kernel patch management unless the organization operates systems using the fsl qbman path. Elevate priority for embedded, network, or edge platforms where a kernel deadlock would create operational outages.

Technical view

The Linux kernel fix changes fsl qbman cgr_lock handling so interrupts are disabled consistently when acquiring the lock. The CVE description says smp_call_function_single executes callbacks with IRQs disabled, so other lockers must also disable IRQs to prevent deadlocks.

Likely exposure

Exposure is most likely on Linux systems running affected kernel versions with the fsl qbman subsystem present or enabled. The bundle lists affected Linux versions from 4.16 through 6.9 and fixed stable commits. General Linux fleets may be unaffected if this hardware-specific path is absent.

Exploitation context

The source bundle does not report active exploitation, public weaponization, or KEV listing. Evidence supports a kernel deadlock condition, not a documented remote exploit path. Treat exploitability as unclear without vendor-specific advisories or local kernel configuration review.

Researcher notes

The evidence is limited to the kernel CVE record, upstream stable commits, and Debian LTS notices. No CVSS, CWE, exploit status, or detailed attack preconditions are provided. Analysis should focus on code reachability, kernel configuration, and whether affected hardware support is present.

Mitigation direction

  • Apply the relevant Linux stable kernel fix or vendor kernel update.
  • Review Debian LTS and distribution advisories for packaged kernel updates.
  • Prioritize systems using fsl qbman or Freescale/NXP QorIQ-related kernel support.
  • Schedule kernel reboot or live-patching according to normal availability procedures.
  • If no vendor package exists, follow upstream kernel stable guidance.

Validation and detection

  • Inventory running kernel versions against the affected and fixed version ranges.
  • Check whether fsl qbman support is built into deployed kernels.
  • Confirm the applicable stable commit is present in the deployed kernel source or package changelog.
  • Review monitoring for kernel hangs, deadlocks, or availability symptoms on relevant systems.
  • Verify distribution advisories mark the installed kernel package as fixed.
Prepared
Confidence
medium
Sources
12

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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.

cve · low confidence lookup

CVE-2024-35806 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
3Timeline events
2ADP providers
12Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux96f413f47677366e0ae03797409bfcc4151dbf9e, 96f413f47677366e0ae03797409bfcc4151dbf9e, 96f413f47677366e0ae03797409bfcc4151dbf9e, 96f413f47677366e0ae03797409bfcc4151dbf9e, 96f413f47677366e0ae03797409bfcc4151dbf9e, 96f413f47677366e0ae03797409bfcc4151dbf9e, 96f413f47677366e0ae03797409bfcc4151dbf9e, 96f413f47677366e0ae03797409bfcc4151dbf9e, 96f413f47677366e0ae03797409bfcc4151dbf9e, a85c525bbff4d7467d7f0ab6fed8e2f787b073d6, 29cd9c2d1f428c281962135ea046a9d7bda88d14, 5b10a404419f0532ef3ba990c12bebe118adb6d7unaffected
LinuxLinux4.16, 0, 4.19.312, 5.4.274, 5.10.215, 5.15.154, 6.1.84, 6.6.24, 6.7.12, 6.8.3, 6.9affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.