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-26791btrfs: dev-replace: properly validate device names

Description

In the Linux kernel, the following vulnerability has been resolved: btrfs: dev-replace: properly validate device names There's a syzbot report that device name buffers passed to device replace are not properly checked for string termination which could lead to a read out of bounds in getname_kernel(). Add a helper that validates both source and target device name buffers. For devid as the source initialize the buffer to empty string in case something tries to read it later. This was originally analyzed and fixed in a different way by Edward Adam Davis (see links).

Timeline

  1. ID reserved

    By Linux

  2. · 45 days later

    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-26791, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1High7.1CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
EPSS (exploitation in 30 days)
0.25% · top 84% of all CVEs (19 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.1.

Affected products

  • Linux · Linux

    • affected e93c89c1aaaaaec3487c4c18dd02360371790722 – < 11d7a2e429c02d51e2dc90713823ea8b8d3d3a84
    • affected e93c89c1aaaaaec3487c4c18dd02360371790722 – < c6652e20d7d783d060fe5f987eac7b5cabe31311
    • affected e93c89c1aaaaaec3487c4c18dd02360371790722 – < 2886fe308a83968dde252302884a1e63351cf16d
    • affected e93c89c1aaaaaec3487c4c18dd02360371790722 – < ab2d68655d0f04650bef09fee948ff80597c5fb9
    • affected e93c89c1aaaaaec3487c4c18dd02360371790722 – < f590040ce2b712177306b03c2a63b16f7d48d3c8
    • affected e93c89c1aaaaaec3487c4c18dd02360371790722 – < b1690ced4d2d8b28868811fb81cd33eee5aefee1
    • affected e93c89c1aaaaaec3487c4c18dd02360371790722 – < 343eecb4ff49a7b1cc1dfe86958a805cf2341cfb
    • affected e93c89c1aaaaaec3487c4c18dd02360371790722 – < 9845664b9ee47ce7ee7ea93caf47d39a9d4552c4
  • Linux · Linux

    • affected 3.8
    • unaffected < 3.8
    • unaffected 4.19.309 – ≤ 4.19.*
    • unaffected 5.4.271 – ≤ 5.4.*
    • unaffected 5.10.212 – ≤ 5.10.*
    • unaffected 5.15.151 – ≤ 5.15.*
    • unaffected 6.1.81 – ≤ 6.1.*
    • unaffected 6.6.21 – ≤ 6.6.*
    • unaffected 6.7.9 – ≤ 6.7.*
    • unaffected 6.8 – ≤ *

References

References10

Sources

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

Badge for a README or a ticket

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

Record last updated .