CVE-2024-46687

Kernel crash via split-bio error-path double free

Published Sep 13, 2024 · Updated Aug 5, 2026

Use-after-free in the Btrfs I/O path in affected Linux releases allows local users to crash the kernel through split read bio errors. In btrfs_submit_chunk(), a mapping failure on the second half of a split read bio calls btrfs_bio_end_io(), whose original end handler frees the parent bio while the submitted first half still references its iterator. Reachability requires local file I/O on a mounted Btrfs filesystem, a bio crossing stripes, and a later mapping error; the resulting stale access or second free corrupts kernel memory and crashes the system.

CVSS severity7.8
High
EPSS probability0.21%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Use-after-free in the Btrfs I/O path in affected Linux releases allows local users to crash the kernel through split read bio errors. In btrfs_submit_chunk(), a mapping failure on the second half of a split read bio calls btrfs_bio_end_io(), whose original end handler frees the parent bio while the submitted first half still references its iterator. Reachability requires local file I/O on a mounted Btrfs filesystem, a bio crossing stripes, and a later mapping error; the resulting stale access or second free corrupts kernel memory and crashes the system.

The record

CVE
CVE-2024-46687
Published
Sep 13, 2024
Updated
Aug 5, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
CWE-416, CWE-415, T1499.004
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Sep 13, 2024CVE publishedPublication date reported by the CVE source.
  2. Aug 5, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=6.3
  2. Affected versionversion=852eee62d31abd695cd43e1b875d664ed292a8ca <10d9d8c3512f16cad47b2ff81ec6fc4b27d8ee10
  3. Affected versionversion=852eee62d31abd695cd43e1b875d664ed292a8ca <4a3b9e1a8e6cd1a8d427a905e159de58d38941cc
  4. Affected versionversion=852eee62d31abd695cd43e1b875d664ed292a8ca <51722b99f41f5e722ffa10b8f61e802a0e70b331

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

The Linux Kernel Organization · Linuxversion=6.3; version=852eee62d31abd695cd43e1b875d664ed292a8ca <10d9d8c3512f16cad47b2ff81ec6fc4b27d8ee10; version=852eee62d31abd695cd43e1b875d664ed292a8ca <4a3b9e1a8e6cd1a8d427a905e159de58d38941cc; version=852eee62d31abd695cd43e1b875d664ed292a8ca <51722b99f41f5e722ffa10b8f61e802a0e70b331

Published CVSS scores

7.8NIST NVDCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-416Use After Free
CWE-415Double Free
T1499.004Application or System Exploitation

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo