Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-56582: btrfs: fix use-after-free in btrfs_encoded_read_endio()

Noroxi assessment

Priority: Monitor (action score 31/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.23% (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 05b36b04d74a517d6675bf2f90829ff1ac7e28dc, 6228f13f1996a4feb9b601d6644bf0bfe03671dd, a40de0330af4fb7bc6b354250c24f294f8b826a0; azl3 kernel 6.6.64.2-9 on Azure Linux 3.0 6.6.76.1-1; azl3 kernel 6.6.76.1-1 on Azure Linux 3.0 6.6.76.1-1.

Low priority for now. Upgrade to Linux Linux 05b36b04d74a517d6675bf2f90829ff1ac7e28dc, 6228f13f1996a4feb9b601d6644bf0bfe03671dd, a40de0330af4fb7bc6b354250c24f294f8b826a0; azl3 kernel 6.6.64.2-9 on Azure Linux 3.0 6.6.76.1-1; azl3 kernel 6.6.76.1-1 on Azure Linux 3.0 6.6.76.1-1 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: fix use-after-free in btrfs_encoded_read_endio() Shinichiro reported the following use-after free that sometimes is happening in our CI system when running fstests' btrfs/284 on a TCMU runner device: BUG: KASAN: slab-use-after-free in lock_release+0x708/0x780 Read of size 8 at addr ffff888106a83f18 by task kworker/u80:6/219 CPU: 8 UID: 0 PID: 219 Comm: kworker/u80:6 Not tainted 6.12.0-rc6-kts+ #15 Hardware name: Supermicro Super Server/X11SPi-TF, BIOS 3.3 02/21/2020 Workqueue: btrfs-endio btrfs_end_bio_work [btrfs] Call Trace: <TASK> dump_stack_lvl+0x6e/0xa0 ? lock_release+0x708/0x780 print_report+0x174/0x505 ? lock_release+0x708/0x780 ? __virt_addr_valid+0x224/0x410 ? lock_release+0x708/0x780 kasan_report+0xda/0x1b0 ? lock_release+0x708/0x780 ? __wake_up+0x44/0x60 lock_release+0x708/0x780 ? __pfx_lock_release+0x10/0x10 ? __pfx_do_raw_spin_lock+0x10/0x10 ? lock_is_held_type+0x9a/0x110 _raw_spin_unlock_irqrestore+0x1f/0x60 __wake_up+0x44/0x60 btrfs_encoded_read_endio+0x14b/0x190 [btrfs] btrfs_check_read_bio+0x8d9/0x1360 [btrfs] ? lock_release+0x1b0/0x780 ? trace_lock_acquire+0x12f/0x1a0 ? __pfx_btrfs_check_read_bio+0x10/0x10 [btrfs] ? process_one_work+0x7e3/0x1460 ? lock_acquire+0x31/0xc0 ? process_one_work+0x7e3/0x1460 process_one_work+0x85c/0x1460 ? __pfx_process_one_work+0x10/0x10 ? assign_work+0x16c/0x240 worker_thread+0x5e6/0xfc0 ? __pfx_worker_thread+0x10/0x10 kthread+0x2c3/0x3a0 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x31/0x70 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 </TASK> Allocated by task 3661: kasan_save_stack+0x30/0x50 kasan_save_track+0x14/0x30 __kasan_kmalloc+0xaa/0xb0 btrfs_encoded_read_regular_fill_pages+0x16c/0x6d0 [btrfs] send_extent_data+0xf0f/0x24a0 [btrfs] process_extent+0x48a/0x1830 [btrfs] changed_cb+0x178b/0x2ea0 [btrfs] btrfs_ioctl_send+0x3bf9/0x5c20 [btrfs] _btrfs_ioctl_send+0x117/0x330 [btrfs] btrfs_ioctl+0x184a/0x60a0 [btrfs] __x64_sys_ioctl+0x12e/0x1a0 do_syscall_64+0x95/0x180 entry_SYSCALL_64_after_hwframe+0x76/0x7e Freed by task 3661: kasan_save_stack+0x30/0x50 kasan_save_track+0x14/0x30 kasan_save_free_info+0x3b/0x70 __kasan_slab_free+0x4f/0x70 kfree+0x143/0x490 btrfs_encoded_read_regular_fill_pages+0x531/0x6d0 [btrfs] send_extent_data+0xf0f/0x24a0 [btrfs] process_extent+0x48a/0x1830 [btrfs] changed_cb+0x178b/0x2ea0 [btrfs] btrfs_ioctl_send+0x3bf9/0x5c20 [btrfs] _btrfs_ioctl_send+0x117/0x330 [btrfs] btrfs_ioctl+0x184a/0x60a0 [btrfs] __x64_sys_ioctl+0x12e/0x1a0 do_syscall_64+0x95/0x180 entry_SYSCALL_64_after_hwframe+0x76/0x7e The buggy address belongs to the object at ffff888106a83f00 which belongs to the cache kmalloc-rnd-07-96 of size 96 The buggy address is located 24 bytes inside of freed 96-byte region [ffff888106a83f00, ffff888106a83f60) The buggy address belongs to the physical page: page: refcount:1 mapcount:0 mapping:0000000000000000 index:0xffff888106a83800 pfn:0x106a83 flags: 0x17ffffc0000000(node=0|zone=2|lastcpupid=0x1fffff) page_type: f5(slab) raw: 0017ffffc0000000 ffff888100053680 ffffea0004917200 0000000000000004 raw: ffff888106a83800 0000000080200019 00000001f5000000 0000000000000000 page dumped because: kasan: bad access detected Memory state around the buggy address: ffff888106a83e00: fa fb fb fb fb fb fb fb fb fb fb fb fc fc fc fc ffff888106a83e80: fa fb fb fb fb fb fb fb fb fb fb fb fc fc fc fc >ffff888106a83f00: fa fb fb fb fb fb fb fb fb fb fb fb fc fc fc fc ^ ffff888106a83f80: fa fb fb fb fb fb fb fb fb fb fb fb fc fc fc fc ffff888106a84000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ================================================================== Further analyzing the trace and ---truncated---

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Dec 27, 2024
Updated
Jun 17, 2026
EPSS
0.2% · 14th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

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.

Follow CVE-2024-56582

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi 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 help

Affected 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.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel5.18 and later · before 6.1.124
  • linux linux kernel6.2 and later · before 6.6.70
  • linux linux kernel6.7 and later · before 6.12.4
  • linux linux kernel6.13

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

    • 5.18affected
    • 1881fba89bd5dcd364d2e1bf561912a90a11c21a and later · before a40de0330af4fb7bc6b354250c24f294f8b826a0affected · git
    • 1881fba89bd5dcd364d2e1bf561912a90a11c21a and later · before 6228f13f1996a4feb9b601d6644bf0bfe03671ddaffected · git
    • 1881fba89bd5dcd364d2e1bf561912a90a11c21a and later · before f8a5129e4a9fc3f6aa3f137513253b51b31b94d4affected · git
    • 1881fba89bd5dcd364d2e1bf561912a90a11c21a and later · before 05b36b04d74a517d6675bf2f90829ff1ac7e28dcaffected · git
    • before 5.18not affected · semver
    • 6.1.124 and later · up to and including 6.1.*not affected · semver
    • 6.6.70 and later · up to and including 6.6.*not affected · semver
    • 6.12.4 and later · up to and including 6.12.*not affected · semver
    • 6.13 and laternot affected · original_commit_for_fix

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.124-16.1.124-1
Debian:13linuxbefore 6.12.5-16.12.5-1
SUSE:Linux Enterprise Live Patching 15 SP6kernel-livepatch-SLE15-SP6_Update_0before 18-150600.4.46.118-150600.4.46.1
SUSE:Linux Enterprise Live Patching 15 SP6kernel-livepatch-SLE15-SP6_Update_2before 16-150600.2.116-150600.2.1
SUSE:Linux Enterprise Live Patching 15 SP6kernel-livepatch-SLE15-SP6_Update_3before 16-150600.2.216-150600.2.2
SUSE:Linux Enterprise Live Patching 15 SP6kernel-livepatch-SLE15-SP6_Update_4before 12-150600.2.112-150600.2.1
SUSE:Linux Enterprise Live Patching 15 SP6kernel-livepatch-SLE15-SP6_Update_5before 11-150600.2.111-150600.2.1
SUSE:Linux Enterprise Live Patching 15 SP6kernel-livepatch-SLE15-SP6_Update_6before 7-150600.2.27-150600.2.2
SUSE:Linux Enterprise Live Patching 15 SP6kernel-livepatch-SLE15-SP6-RT_Update_0before 17-150600.3.117-150600.3.1
SUSE:Linux Enterprise Live Patching 15 SP6kernel-livepatch-SLE15-SP6-RT_Update_1before 16-150600.2.116-150600.2.1
SUSE:Linux Enterprise Live Patching 15 SP6kernel-livepatch-SLE15-SP6-RT_Update_2before 12-150600.2.112-150600.2.1
SUSE:Linux Enterprise Live Patching 15 SP6kernel-livepatch-SLE15-SP6-RT_Update_3before 12-150600.2.112-150600.2.1
SUSE:Linux Enterprise Live Patching 15 SP6kernel-livepatch-SLE15-SP6-RT_Update_5before 10-150600.2.110-150600.2.1
SUSE:Linux Enterprise Live Patching 15 SP6kernel-livepatch-SLE15-SP6-RT_Update_6before 7-150600.2.17-150600.2.1
SUSE:Linux Micro 6.0kernel-livepatch-MICRO-6-0_Update_2before 7-1.17-1.1
SUSE:Linux Micro 6.0kernel-livepatch-MICRO-6-0_Update_3before 7-1.27-1.2
SUSE:Linux Micro 6.0kernel-livepatch-MICRO-6-0_Update_4before 5-1.25-1.2
SUSE:Linux Micro 6.0kernel-livepatch-MICRO-6-0-RT_Update_2before 7-1.17-1.1
SUSE:Linux Micro 6.0kernel-livepatch-MICRO-6-0-RT_Update_3before 7-1.27-1.2
SUSE:Linux Micro 6.0kernel-livepatch-MICRO-6-0-RT_Update_4before 4-1.14-1.1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • 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 KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2024-56580Dec 27, 2024 · media: qcom: camss: fix error path on configuration of power domains
    22Monitor
  • ← EarlierCVE-2024-56581Dec 27, 2024 · btrfs: ref-verify: fix use-after-free after invalid ref action
    31Monitor
  • Later →CVE-2024-56583Dec 27, 2024 · sched/deadline: Fix warning in migrate_enable for boosted tasks
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux05b36b04d74a517d6675bf2f90829ff1ac7e28dcVendor (CNA)
Linux Linux6228f13f1996a4feb9b601d6644bf0bfe03671ddVendor (CNA)
Linux Linuxa40de0330af4fb7bc6b354250c24f294f8b826a0Vendor (CNA)
Linux Linuxf8a5129e4a9fc3f6aa3f137513253b51b31b94d4Vendor (CNA)
azl3 kernel 6.6.64.2-9 on Azure Linux 3.06.6.76.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 kernel 6.6.76.1-1 on Azure Linux 3.06.6.76.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
debian:linux6.1.124-1 · Debian:12Package registry (OSV)
suse:kernel-livepatch-SLE15-SP6_Update_018-150600.4.46.1 · SUSE:Linux Enterprise Live Patching 15 SP6Package registry (OSV)
suse:kernel-livepatch-SLE15-SP6_Update_216-150600.2.1 · SUSE:Linux Enterprise Live Patching 15 SP6Package registry (OSV)
suse:kernel-livepatch-SLE15-SP6_Update_316-150600.2.2 · SUSE:Linux Enterprise Live Patching 15 SP6Package registry (OSV)
suse:kernel-livepatch-SLE15-SP6_Update_412-150600.2.1 · SUSE:Linux Enterprise Live Patching 15 SP6Package registry (OSV)
suse:kernel-livepatch-SLE15-SP6_Update_511-150600.2.1 · SUSE:Linux Enterprise Live Patching 15 SP6Package registry (OSV)
suse:kernel-livepatch-SLE15-SP6_Update_67-150600.2.2 · SUSE:Linux Enterprise Live Patching 15 SP6Package registry (OSV)
suse:kernel-livepatch-SLE15-SP6-RT_Update_017-150600.3.1 · SUSE:Linux Enterprise Live Patching 15 SP6Package registry (OSV)
suse:kernel-livepatch-SLE15-SP6-RT_Update_116-150600.2.1 · SUSE:Linux Enterprise Live Patching 15 SP6Package registry (OSV)
suse:kernel-livepatch-SLE15-SP6-RT_Update_212-150600.2.1 · SUSE:Linux Enterprise Live Patching 15 SP6Package registry (OSV)
suse:kernel-livepatch-SLE15-SP6-RT_Update_312-150600.2.1 · SUSE:Linux Enterprise Live Patching 15 SP6Package registry (OSV)
suse:kernel-livepatch-SLE15-SP6-RT_Update_510-150600.2.1 · SUSE:Linux Enterprise Live Patching 15 SP6Package registry (OSV)
suse:kernel-livepatch-SLE15-SP6-RT_Update_67-150600.2.1 · SUSE:Linux Enterprise Live Patching 15 SP6Package 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.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

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
high · data or configuration can be modified
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
High
Availability impact
High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

c
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (4 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records