CVE-2024-35806

soc: fsl: qbman: Always disable interrupts when taking cgr_lock

MEDIUM

5.5

CVSS Score

Published: May 17, 2024 at 01:23 PM UTC

Updated: June 17, 2026 at 07:35 AM UTC

2 products affected across 2 vendorsLinux KernelDebian Linux

Using Linux by Linux?

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

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM5.5

Exploit prediction

EPSS 0.2%

SSVC

No known exploit

Description

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.

Affected

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

Debian Linux · Debiandrupal

95%

10.0

Linux Kernel · Linux

95%

v ≥ 4.14.32v ≥ 4.15.15v ≥ 4.9.924.14.32 ≤ v < 4.154.15.15 ≤ v < 4.164.15.15 ≤ v < 4.19.3124.16 ≤ v < 4.19.3124.16 ≤ v < 5.10.2154.16 ≤ v < 5.15.1544.16 ≤ v < 5.4.2744.16 ≤ v < 6.1.844.16 ≤ v < 6.6.244.16 ≤ v < 6.7.124.16 ≤ v < 6.8.34.16 ≤ v < 6.94.20 ≤ v < 5.4.2744.9.92 ≤ v < 4.105.11 ≤ v < 5.15.1545.16 ≤ v < 6.1.845.5 ≤ v < 5.10.2156.2 ≤ v < 6.6.246.7 ≤ v < 6.7.126.8 ≤ v < 6.8.329cd9c2d1f428c281962135ea046a9d7bda88d144.14.32 4.15.15 4.16 4.9.925b10a404419f0532ef3ba990c12bebe118adb6d796f413f47677366e0ae03797409bfcc4151dbf9ea85c525bbff4d7467d7f0ab6fed8e2f787b073d6

Vendor states this is fixed in 0e6521b0f93ff350434ed4ae61a250907e65d397 (fixed)

Vendor states this is fixed in 276af8efb05c8e47acf2738a5609dd72acfc703f (fixed)

Vendor states this is fixed in 584c2a9184a33a40fceee838f856de3cffa19be3 (fixed)

Vendor states this is fixed in 62c3ecd2833cff0eff4a82af4082c44ca8d2518a (fixed)

Vendor states this is fixed in a62168653774c36398d65846a98034436ee66d03 (fixed)

Vendor states this is fixed in af25c5180b2b1796342798f6c56fcfd12f5035bd (fixed)

Vendor states this is fixed in b56a793f267679945d1fdb9a280013bd2d0ed7f9 (fixed)

Vendor states this is fixed in dd199e5b759ffe349622a4b8fbcafc51fc51b1ec (fixed)

Vendor states this is fixed in e6378314bb920acb39013051fa65d8f9f8030430 (fixed)

Affected range stops below 4.10, so it looks safe — our inference, not a vendor statement

Affected range stops below 4.15, so it looks safe — our inference, not a vendor statement

Vendor states this is fixed in 4.16 (unaffected)

Vendor states this is fixed in 4.19.312 (unaffected)

Vendor states this is fixed in 5.10.215 (unaffected)

Vendor states this is fixed in 5.15.154 (unaffected)

Vendor states this is fixed in 5.4.274 (unaffected)

Vendor states this is fixed in 6.1.84 (unaffected)

Vendor states this is fixed in 6.6.24 (unaffected)

Vendor states this is fixed in 6.7.12 (unaffected)

Vendor states this is fixed in 6.8.3 (unaffected)

Vendor states this is fixed in 6.9 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references