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-49854block, bfq: fix uaf for accessing waker_bfqq after splitting

Description

In the Linux kernel, the following vulnerability has been resolved: block, bfq: fix uaf for accessing waker_bfqq after splitting After commit 42c306ed7233 ("block, bfq: don't break merge chain in bfq_split_bfqq()"), if the current procress is the last holder of bfqq, the bfqq can be freed after bfq_split_bfqq(). Hence recored the bfqq and then access bfqq->waker_bfqq may trigger UAF. What's more, the waker_bfqq may in the merge chain of bfqq, hence just recored waker_bfqq is still not safe. Fix the problem by adding a helper bfq_waker_bfqq() to check if bfqq->waker_bfqq is in the merge chain, and current procress is the only holder.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 22 months 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-49854, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.21% · top 88% of all CVEs (18 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: High 7.8.

Affected products

  • Linux · Linux

    • affected e0c20d88b7dce85d2703bb6ba77bf359959675cd – < 63a07379fdb6c72450cb05294461c6016b8b7726
    • affected de6c5e3a456019d2182e345730e59721714fa0b5 – < de0456460f2abf921e356ed2bd8da87a376680bd
    • affected 19f3bec2ac4be329b9bd12b18a989b867618d2d8 – < 0780451f03bf518bc032a7c584de8f92e2d39d7f
    • affected 13b3d0e8cb121f99b11918a0d4bcc1ce4647d352 – < 0b8bda0ff17156cd3f60944527c9d8c9f99f1583
    • affected 4780f50ea50cfe8e89fc3747bf3dd155488433bb – < cae58d19121a70329cf971359e2518c93fec04fe
    • affected 42c306ed723321af4003b2a41bb73728cab54f85 – < 1ba0403ac6447f2d63914fb760c44a3b19c44eaf
    • affected 9e813033594b141f61ff0ef0cfaaef292564b041
    • affected 3a5f45a4ad4e1fd36b0a998eef03d76a4f02a2a8
    • affected 3630a18846c7853aa326d3b42fd0a855af7b41bc
    • affected 4.19.323 – < 4.20
    • affected 5.4.285 – < 5.5
    • affected 5.10.227 – < 5.11
  • Linux · Linux

    All versions: unaffected

References

References7

Sources

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

Badge for a README or a ticket

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

Record last updated .