Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-31580: bcache: fix cached_dev.sb_bio use-after-free and crash

HighCVSS 7.8 · v3.1—No exploit Fix available

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.13% (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 2d6965581e164fa2ba3f7652ddae5535f6336576, 383f7fec0de8cee1cf7ae1f9d9f14044a61f10f9, 47fa09fe7f3e09df28a51cb2cbd8f5d2f7f6edc1.

Low priority for now. Upgrade to Linux Linux 2d6965581e164fa2ba3f7652ddae5535f6336576, 383f7fec0de8cee1cf7ae1f9d9f14044a61f10f9, 47fa09fe7f3e09df28a51cb2cbd8f5d2f7f6edc1 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: bcache: fix cached_dev.sb_bio use-after-free and crash In our production environment, we have received multiple crash reports regarding libceph, which have caught our attention: ``` [6888366.280350] Call Trace: [6888366.280452] blk_update_request+0x14e/0x370 [6888366.280561] blk_mq_end_request+0x1a/0x130 [6888366.280671] rbd_img_handle_request+0x1a0/0x1b0 [rbd] [6888366.280792] rbd_obj_handle_request+0x32/0x40 [rbd] [6888366.280903] __complete_request+0x22/0x70 [libceph] [6888366.281032] osd_dispatch+0x15e/0xb40 [libceph] [6888366.281164] ? inet_recvmsg+0x5b/0xd0 [6888366.281272] ? ceph_tcp_recvmsg+0x6f/0xa0 [libceph] [6888366.281405] ceph_con_process_message+0x79/0x140 [libceph] [6888366.281534] ceph_con_v1_try_read+0x5d7/0xf30 [libceph] [6888366.281661] ceph_con_workfn+0x329/0x680 [libceph] ``` After analyzing the coredump file, we found that the address of dc->sb_bio has been freed. We know that cached_dev is only freed when it is stopped. Since sb_bio is a part of struct cached_dev, rather than an alloc every time. If the device is stopped while writing to the superblock, the released address will be accessed at endio. This patch hopes to wait for sb_write to complete in cached_dev_free. It should be noted that we analyzed the cause of the problem, then tell all details to the QWEN and adopted the modifications it made.

Published
Apr 24, 2026
Updated
Nov 11, 2026
EPSS
0.1% · 2th 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.1%

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.

Follow CVE-2026-31580

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 every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • 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, at most 30 a day (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.

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 kernelbefore 6.6.136
  • linux linux kernel6.12 and later · before 6.12.83
  • linux linux kernel6.13 and later · before 6.18.24
  • linux linux kernel6.19 and later · before 6.19.14
  • linux linux kernel7.0 and later · before 7.0.1

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.10affected
    • cafe563591446cf80bfbc2fe3bc72a2e36cf1060 and later · before 81f44ed8c3f54abb7561ece774ea4cca5070b2f2affected · git
    • cafe563591446cf80bfbc2fe3bc72a2e36cf1060 and later · before f50e7c325ab1207fe941555bcff659f6d7050572affected · git
    • cafe563591446cf80bfbc2fe3bc72a2e36cf1060 and later · before 9467d360be70e6ee55b0c1cd2a1f1424f57b5b85affected · git
    • cafe563591446cf80bfbc2fe3bc72a2e36cf1060 and later · before 47fa09fe7f3e09df28a51cb2cbd8f5d2f7f6edc1affected · git
    • cafe563591446cf80bfbc2fe3bc72a2e36cf1060 and later · before add4982510f3b7c318a2dd7438bdc9c63171e753affected · git
    • cafe563591446cf80bfbc2fe3bc72a2e36cf1060 and later · before 2d6965581e164fa2ba3f7652ddae5535f6336576affected · git
    • cafe563591446cf80bfbc2fe3bc72a2e36cf1060 and later · before 4f71c8ba2dc009042493021d94a9718fbe2ebf27affected · git
    • cafe563591446cf80bfbc2fe3bc72a2e36cf1060 and later · before 383f7fec0de8cee1cf7ae1f9d9f14044a61f10f9affected · git
    • cafe563591446cf80bfbc2fe3bc72a2e36cf1060 and later · before fec114a98b8735ee89c75216c45a78e28be0f128affected · git

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.176-16.1.176-1
Debian:13linuxbefore 6.12.85-16.12.85-1
Debian:14linuxbefore 6.19.14-16.19.14-1
openSUSE:Tumbleweedkernel-sourcebefore 7.0.3-1.17.0.3-1.1
SUSE:Linux Enterprise Live Patching 12 SP5kernel-defaultbefore 4.12.14-122.320.14.12.14-122.320.1
SUSE:Linux Enterprise Live Patching 12 SP5kgraft-patch-SLE12-SP5_Update_85before 1-8.3.11-8.3.1
SUSE:Linux Enterprise Server 12 SP5-LTSSkernel-sourcebefore 4.12.14-122.320.14.12.14-122.320.1
SUSE:Linux Enterprise Server 12 SP5-LTSSkernel-symsbefore 4.12.14-122.320.14.12.14-122.320.1
SUSE:Linux Micro Extras 6.2kernel-obs-buildbefore 6.12.0-160000.34.16.12.0-160000.34.1
SUSE:Linux Micro Extras 6.2kernel-symsbefore 6.12.0-160000.34.16.12.0-160000.34.1

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-2026-31578Apr 24, 2026 · media: as102: fix to not free memory after the device is registered in as102_usb_probe()
    31Monitor
  • ← EarlierCVE-2026-31579Apr 24, 2026 · wireguard: device: use exit_rtnl callback instead of manual rtnl_lock in pre_exit
    22Monitor
  • Later →CVE-2026-31581Apr 24, 2026 · ALSA: 6fire: fix use-after-free on disconnect
    31Monitor

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 Linux2d6965581e164fa2ba3f7652ddae5535f6336576Vendor (CNA)
Linux Linux383f7fec0de8cee1cf7ae1f9d9f14044a61f10f9Vendor (CNA)
Linux Linux47fa09fe7f3e09df28a51cb2cbd8f5d2f7f6edc1Vendor (CNA)
Linux Linux4f71c8ba2dc009042493021d94a9718fbe2ebf27Vendor (CNA)
Linux Linux81f44ed8c3f54abb7561ece774ea4cca5070b2f2Vendor (CNA)
Linux Linux9467d360be70e6ee55b0c1cd2a1f1424f57b5b85Vendor (CNA)
Linux Linuxadd4982510f3b7c318a2dd7438bdc9c63171e753Vendor (CNA)
Linux Linuxf50e7c325ab1207fe941555bcff659f6d7050572Vendor (CNA)
Linux Linuxfec114a98b8735ee89c75216c45a78e28be0f128Vendor (CNA)
debian:linux6.1.176-1 · Debian:12Package registry (OSV)
opensuse:kernel-source7.0.3-1.1 · openSUSE:TumbleweedPackage registry (OSV)
suse:kernel-default4.12.14-122.320.1 · SUSE:Linux Enterprise Live Patching 12 SP5Package registry (OSV)
suse:kernel-obs-build6.12.0-160000.34.1 · SUSE:Linux Micro Extras 6.2Package registry (OSV)
suse:kernel-source4.12.14-122.320.1 · SUSE:Linux Enterprise Server 12 SP5-LTSSPackage registry (OSV)
suse:kernel-syms6.12.0-160000.34.1 · SUSE:Linux Micro Extras 6.2Package registry (OSV)
suse:kgraft-patch-SLE12-SP5_Update_851-8.3.1 · SUSE:Linux Enterprise Live Patching 12 SP5Package 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.

No history yet (it accumulates with the daily EPSS job).

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.

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.

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. SSVC exploitation— → none
  2. Fix✗ → ✓

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

References

All records