Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-23110: scsi: core: Wake up the error handler when final completions race against each other

Noroxi assessment

Priority: Monitor (action score 18/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.11% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: Linux Linux 219f009ebfd1ef3970888ee9eef4c8a06357f862, 64ae21b9c4f0c7e60cf47a53fa7ab68852079ef0, 6d9a367be356101963c249ebf10ea10b32886607; cbl2 kernel 5.15.202.1-1 on CBL-Mariner 2.0 Release Notes.

Low priority for now. Upgrade to Linux Linux 219f009ebfd1ef3970888ee9eef4c8a06357f862, 64ae21b9c4f0c7e60cf47a53fa7ab68852079ef0, 6d9a367be356101963c249ebf10ea10b32886607; cbl2 kernel 5.15.202.1-1 on CBL-Mariner 2.0 Release Notes 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: scsi: core: Wake up the error handler when final completions race against each other The fragile ordering between marking commands completed or failed so that the error handler only wakes when the last running command completes or times out has race conditions. These race conditions can cause the SCSI layer to fail to wake the error handler, leaving I/O through the SCSI host stuck as the error state cannot advance. First, there is an memory ordering issue within scsi_dec_host_busy(). The write which clears SCMD_STATE_INFLIGHT may be reordered with reads counting in scsi_host_busy(). While the local CPU will see its own write, reordering can allow other CPUs in scsi_dec_host_busy() or scsi_eh_inc_host_failed() to see a raised busy count, causing no CPU to see a host busy equal to the host_failed count. This race condition can be prevented with a memory barrier on the error path to force the write to be visible before counting host busy commands. Second, there is a general ordering issue with scsi_eh_inc_host_failed(). By counting busy commands before incrementing host_failed, it can race with a final command in scsi_dec_host_busy(), such that scsi_dec_host_busy() does not see host_failed incremented but scsi_eh_inc_host_failed() counts busy commands before SCMD_STATE_INFLIGHT is cleared by scsi_dec_host_busy(), resulting in neither waking the error handler task. This needs the call to scsi_host_busy() to be moved after host_failed is incremented to close the race condition.

MediumCVSS 4.7 · v3.1—No exploit Fix available
Published
Feb 4, 2026
Updated
Oct 19, 2026
EPSS
0.1% · 1th percentile

Report tools

JSON

Action score

18

Monitor

Low priority for now.

CVSS
18 / 40 · 4.7 / 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-23110

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.5 and later · before 5.10.249
  • linux linux kernel5.11 and later · before 6.1.162
  • linux linux kernel6.2 and later · before 6.6.122
  • linux linux kernel6.7 and later · before 6.12.68
  • linux linux kernel6.13 and later · before 6.18.8
  • linux linux kernel6.19

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.5affected
    • 6eb045e092efefafc6687409a6fa6d1dabf0fb69 and later · before cc872e35c0df80062abc71268d690a2f749e542eaffected · git
    • 6eb045e092efefafc6687409a6fa6d1dabf0fb69 and later · before 6d9a367be356101963c249ebf10ea10b32886607affected · git
    • 6eb045e092efefafc6687409a6fa6d1dabf0fb69 and later · before 9fdc6f28d5e81350ab1d2cac8389062bd09e61e1affected · git
    • 6eb045e092efefafc6687409a6fa6d1dabf0fb69 and later · before 64ae21b9c4f0c7e60cf47a53fa7ab68852079ef0affected · git
    • 6eb045e092efefafc6687409a6fa6d1dabf0fb69 and later · before 219f009ebfd1ef3970888ee9eef4c8a06357f862affected · git
    • 6eb045e092efefafc6687409a6fa6d1dabf0fb69 and later · before fe2f8ad6f0999db3b318359a01ee0108c703a8c3affected · git
    • before 5.5not affected · semver
    • 5.10.249 and later · up to and including 5.10.*not affected · semver
    • 6.1.162 and later · up to and including 6.1.*not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
AlmaLinux:10kernelbefore 6.12.0-211.39.1.el10_26.12.0-211.39.1.el10_2
AlmaLinux:10kernel-64kbefore 6.12.0-211.39.1.el10_26.12.0-211.39.1.el10_2
AlmaLinux:10kernel-64k-corebefore 6.12.0-211.39.1.el10_26.12.0-211.39.1.el10_2
AlmaLinux:10kernel-64k-debugbefore 6.12.0-211.39.1.el10_26.12.0-211.39.1.el10_2
AlmaLinux:10kernel-64k-debug-corebefore 6.12.0-211.39.1.el10_26.12.0-211.39.1.el10_2
AlmaLinux:10kernel-64k-debug-develbefore 6.12.0-211.39.1.el10_26.12.0-211.39.1.el10_2
AlmaLinux:10kernel-64k-debug-devel-matchedbefore 6.12.0-211.39.1.el10_26.12.0-211.39.1.el10_2
AlmaLinux:10kernel-64k-debug-modulesbefore 6.12.0-211.39.1.el10_26.12.0-211.39.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-corebefore 6.12.0-211.39.1.el10_26.12.0-211.39.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-extrabefore 6.12.0-211.39.1.el10_26.12.0-211.39.1.el10_2
AlmaLinux:10kernel-64k-develbefore 6.12.0-211.39.1.el10_26.12.0-211.39.1.el10_2
AlmaLinux:10kernel-64k-devel-matchedbefore 6.12.0-211.39.1.el10_26.12.0-211.39.1.el10_2
AlmaLinux:10kernel-64k-modulesbefore 6.12.0-211.39.1.el10_26.12.0-211.39.1.el10_2
AlmaLinux:10kernel-64k-modules-corebefore 6.12.0-211.39.1.el10_26.12.0-211.39.1.el10_2
AlmaLinux:10kernel-64k-modules-extrabefore 6.12.0-211.39.1.el10_26.12.0-211.39.1.el10_2
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-211.39.1.el10_26.12.0-211.39.1.el10_2
AlmaLinux:10kernel-corebefore 6.12.0-211.39.1.el10_26.12.0-211.39.1.el10_2
AlmaLinux:10kernel-cross-headersbefore 6.12.0-211.39.1.el10_26.12.0-211.39.1.el10_2
AlmaLinux:10kernel-debugbefore 6.12.0-211.39.1.el10_26.12.0-211.39.1.el10_2
AlmaLinux:10kernel-debug-corebefore 6.12.0-211.39.1.el10_26.12.0-211.39.1.el10_2
AlmaLinux:10kernel-debug-develbefore 6.12.0-211.39.1.el10_26.12.0-211.39.1.el10_2
AlmaLinux:10kernel-debug-devel-matchedbefore 6.12.0-211.39.1.el10_26.12.0-211.39.1.el10_2
AlmaLinux:10kernel-debug-modulesbefore 6.12.0-211.39.1.el10_26.12.0-211.39.1.el10_2
AlmaLinux:10kernel-debug-modules-corebefore 6.12.0-211.39.1.el10_26.12.0-211.39.1.el10_2

+96

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-2026-23105Feb 4, 2026 · net/sched: qfq: Use cl_is_active to determine whether class is active in qfq_rm_from_ag
    22Monitor
  • ← EarlierCVE-2026-23108Feb 4, 2026 · can: usb_8dev: usb_8dev_read_bulk_callback(): fix URB memory leak
    22Monitor
  • Later →CVE-2026-23111Feb 13, 2026 · netfilter: nf_tables: fix inverted genmask check in nft_map_catchall_activate()
    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 Linux219f009ebfd1ef3970888ee9eef4c8a06357f862Vendor (CNA)
Linux Linux64ae21b9c4f0c7e60cf47a53fa7ab68852079ef0Vendor (CNA)
Linux Linux6d9a367be356101963c249ebf10ea10b32886607Vendor (CNA)
Linux Linux9fdc6f28d5e81350ab1d2cac8389062bd09e61e1Vendor (CNA)
Linux Linuxcc872e35c0df80062abc71268d690a2f749e542eVendor (CNA)
Linux Linuxfe2f8ad6f0999db3b318359a01ee0108c703a8c3Vendor (CNA)
cbl2 kernel 5.15.202.1-1 on CBL-Mariner 2.0Release NotesMicrosoft (MSRC)
almalinux:kernel5.14.0-687.29.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-687.29.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-687.29.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-687.29.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-687.29.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-687.29.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-687.29.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-687.29.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-687.29.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-687.29.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-687.29.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel-matched5.14.0-687.29.1.el9_8 · AlmaLinux:9Package registry (OSV)
debian:linux6.1.162-1 · Debian:12Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-687.29.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-687.29.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-687.29.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-687.29.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-687.29.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-687.29.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-687.29.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-687.29.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-687.29.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo0:5.14.0-687.29.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)

+3

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.

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.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

CVSS vector

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/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.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

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

References

Show all references (7 more)

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

All records