Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2024-35819soc: fsl: qbman: Use raw spinlock for cgr_lock

Description

In the Linux kernel, the following vulnerability has been resolved: soc: fsl: qbman: Use raw spinlock for cgr_lock smp_call_function always runs its callback in hard IRQ context, even on PREEMPT_RT, where spinlocks can sleep. So we need to use a raw spinlock for cgr_lock to ensure we aren't waiting on a sleeping task. Although this bug has existed for a while, it was not apparent until commit ef2a8d5478b9 ("net: dpaa: Adjust queue depth on rate change") which invokes smp_call_function_single via qman_update_cgr_safe every time a link goes up or down.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 2 years later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-35819, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.23% · top 86% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 96f413f47677366e0ae03797409bfcc4151dbf9e – < 2b3fede8225133671ce837c0d284804aa3bc7a02
    • affected 96f413f47677366e0ae03797409bfcc4151dbf9e – < ff50716b7d5b7985979a5b21163cd79fb3d21d59
    • affected 96f413f47677366e0ae03797409bfcc4151dbf9e – < 32edca2f03a6cc42c650ddc3ad83d086e3f365d1
    • affected 96f413f47677366e0ae03797409bfcc4151dbf9e – < 9a3ca8292ce9fdcce122706c28c3f07bc857fe5e
    • affected 96f413f47677366e0ae03797409bfcc4151dbf9e – < d6b5aac451c9cc12e43ab7308e0e2ddc52c62c14
    • affected 96f413f47677366e0ae03797409bfcc4151dbf9e – < 54d26adf64c04f186098b39dba86b86037084baa
    • affected 96f413f47677366e0ae03797409bfcc4151dbf9e – < f39d36b7540cf0088ed7ce2de2794f2aa237f6df
    • affected 96f413f47677366e0ae03797409bfcc4151dbf9e – < cd53a8ae5aacb4ecd25088486dea1cd02e74b506
    • affected 96f413f47677366e0ae03797409bfcc4151dbf9e – < fbec4e7fed89b579f2483041fabf9650fb0dd6bc
    • affected a85c525bbff4d7467d7f0ab6fed8e2f787b073d6
    • affected 29cd9c2d1f428c281962135ea046a9d7bda88d14
    • affected 5b10a404419f0532ef3ba990c12bebe118adb6d7
    • affected 4.9.92 – < 4.10
    • affected 4.14.32 – < 4.15
    • affected 4.15.15 – < 4.16
  • Linux · Linux

    • affected 4.16
    • unaffected < 4.16
    • unaffected 4.19.312 – ≤ 4.19.*
    • unaffected 5.4.274 – ≤ 5.4.*
    • unaffected 5.10.215 – ≤ 5.10.*
    • unaffected 5.15.154 – ≤ 5.15.*
    • unaffected 6.1.84 – ≤ 6.1.*
    • unaffected 6.6.24 – ≤ 6.6.*
    • unaffected 6.7.12 – ≤ 6.7.*
    • unaffected 6.8.3 – ≤ 6.8.*
    • unaffected 6.9 – ≤ *

References

References11

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-35819 badge
[![CVE-2024-35819](https://cveledger.app/badge/CVE-2024-35819.svg)](https://cveledger.app/cve/CVE-2024-35819)

Record last updated .