CVE-2024-26791: btrfs: dev-replace: properly validate device names
Noroxi assessment
Priority: Monitor (action score 28/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.24% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 11d7a2e429c02d51e2dc90713823ea8b8d3d3a84, 2886fe308a83968dde252302884a1e63351cf16d, 343eecb4ff49a7b1cc1dfe86958a805cf2341cfb.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 11d7a2e429c02d51e2dc90713823ea8b8d3d3a84, 2886fe308a83968dde252302884a1e63351cf16d, 343eecb4ff49a7b1cc1dfe86958a805cf2341cfb or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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).
- Published
- Apr 4, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 16th percentile
- CWE
- CWE-125
Report tools
Action score
28
Low priority for now.
- CVSS
- 28 / 40 · 7.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 3.8affected
- e93c89c1aaaaaec3487c4c18dd02360371790722 and later · before 11d7a2e429c02d51e2dc90713823ea8b8d3d3a84affected · git
- e93c89c1aaaaaec3487c4c18dd02360371790722 and later · before c6652e20d7d783d060fe5f987eac7b5cabe31311affected · git
- e93c89c1aaaaaec3487c4c18dd02360371790722 and later · before 2886fe308a83968dde252302884a1e63351cf16daffected · git
- e93c89c1aaaaaec3487c4c18dd02360371790722 and later · before ab2d68655d0f04650bef09fee948ff80597c5fb9affected · git
- e93c89c1aaaaaec3487c4c18dd02360371790722 and later · before f590040ce2b712177306b03c2a63b16f7d48d3c8affected · git
- e93c89c1aaaaaec3487c4c18dd02360371790722 and later · before b1690ced4d2d8b28868811fb81cd33eee5aefee1affected · git
- e93c89c1aaaaaec3487c4c18dd02360371790722 and later · before 343eecb4ff49a7b1cc1dfe86958a805cf2341cfbaffected · git
- e93c89c1aaaaaec3487c4c18dd02360371790722 and later · before 9845664b9ee47ce7ee7ea93caf47d39a9d4552c4affected · git
- before 3.8not affected · semver
Affected versions · NVD (8)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernelbefore 4.19.309
- linux linux kernel4.20 and later · before 5.4.271
- linux linux kernel5.5 and later · before 5.10.212
- linux linux kernel5.11 and later · before 5.15.151
- linux linux kernel5.16 and later · before 6.1.81
- linux linux kernel6.2 and later · before 6.6.21
- linux linux kernel6.7 and later · before 6.7.9
- linux linux kernel6.8
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.82-1 | 6.1.82-1 |
| Debian:13 | linux | before 6.7.9-1 | 6.7.9-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2024-26789Apr 4, 2024 · crypto: arm64/neonbs - fix out-of-bounds access on short input31Monitor
- ← EarlierCVE-2024-26790Apr 4, 2024 · dmaengine: fsl-qdma: fix SoC may hang on 16 byte unaligned read22Monitor
- Later →CVE-2024-26792Apr 4, 2024 · btrfs: fix double free of anonymous device after snapshot creation failure31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 11d7a2e429c02d51e2dc90713823ea8b8d3d3a84 | Vendor (CNA) |
| Linux Linux | 2886fe308a83968dde252302884a1e63351cf16d | Vendor (CNA) |
| Linux Linux | 343eecb4ff49a7b1cc1dfe86958a805cf2341cfb | Vendor (CNA) |
| Linux Linux | 9845664b9ee47ce7ee7ea93caf47d39a9d4552c4 | Vendor (CNA) |
| Linux Linux | ab2d68655d0f04650bef09fee948ff80597c5fb9 | Vendor (CNA) |
| Linux Linux | b1690ced4d2d8b28868811fb81cd33eee5aefee1 | Vendor (CNA) |
| Linux Linux | c6652e20d7d783d060fe5f987eac7b5cabe31311 | Vendor (CNA) |
| Linux Linux | f590040ce2b712177306b03c2a63b16f7d48d3c8 | Vendor (CNA) |
| debian:linux | 6.1.82-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-0273 · Apr 5, 2024(Linux Kernel Güncellemesi)
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-125 · Out-of-bounds ReadCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (9 more)Show less
- git.kernel.org/stable/c/2886fe308a83968dde252302884a1e63351cf16d
- git.kernel.org/stable/c/343eecb4ff49a7b1cc1dfe86958a805cf2341cfb
- git.kernel.org/stable/c/9845664b9ee47ce7ee7ea93caf47d39a9d4552c4
- git.kernel.org/stable/c/ab2d68655d0f04650bef09fee948ff80597c5fb9
- git.kernel.org/stable/c/b1690ced4d2d8b28868811fb81cd33eee5aefee1
- git.kernel.org/stable/c/c6652e20d7d783d060fe5f987eac7b5cabe31311
- git.kernel.org/stable/c/f590040ce2b712177306b03c2a63b16f7d48d3c8
- lists.debian.org/debian-lts-announce/2024/06/msg00017.html
- lists.debian.org/debian-lts-announce/2024/06/msg00020.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.