Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-26935: scsi: core: Fix unremoved procfs host directory regression

Noroxi assessment

Priority: Monitor (action score 22/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 0053f15d50d50c9312d8ab9c11e2e405812dfcac, 3678cf67ff7136db1dd3bf63c361650db5d92889, 5.10.215; azl3 hyperv-daemons 6.6.22.1-2 on Azure Linux 3.0 6.6.35.1-1; azl3 hyperv-daemons 6.6.35.1-1 on Azure Linux 3.0 6.6.35.1-1.

Low priority for now. Upgrade to Linux Linux 0053f15d50d50c9312d8ab9c11e2e405812dfcac, 3678cf67ff7136db1dd3bf63c361650db5d92889, 5.10.215; azl3 hyperv-daemons 6.6.22.1-2 on Azure Linux 3.0 6.6.35.1-1; azl3 hyperv-daemons 6.6.35.1-1 on Azure Linux 3.0 6.6.35.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: scsi: core: Fix unremoved procfs host directory regression Commit fc663711b944 ("scsi: core: Remove the /proc/scsi/${proc_name} directory earlier") fixed a bug related to modules loading/unloading, by adding a call to scsi_proc_hostdir_rm() on scsi_remove_host(). But that led to a potential duplicate call to the hostdir_rm() routine, since it's also called from scsi_host_dev_release(). That triggered a regression report, which was then fixed by commit be03df3d4bfe ("scsi: core: Fix a procfs host directory removal regression"). The fix just dropped the hostdir_rm() call from dev_release(). But it happens that this proc directory is created on scsi_host_alloc(), and that function "pairs" with scsi_host_dev_release(), while scsi_remove_host() pairs with scsi_add_host(). In other words, it seems the reason for removing the proc directory on dev_release() was meant to cover cases in which a SCSI host structure was allocated, but the call to scsi_add_host() didn't happen. And that pattern happens to exist in some error paths, for example. Syzkaller causes that by using USB raw gadget device, error'ing on usb-storage driver, at usb_stor_probe2(). By checking that path, we can see that the BadDevice label leads to a scsi_host_put() after a SCSI host allocation, but there's no call to scsi_add_host() in such path. That leads to messages like this in dmesg (and a leak of the SCSI host proc structure): usb-storage 4-1:87.51: USB Mass Storage device detected proc_dir_entry 'scsi/usb-storage' already registered WARNING: CPU: 1 PID: 3519 at fs/proc/generic.c:377 proc_register+0x347/0x4e0 fs/proc/generic.c:376 The proper fix seems to still call scsi_proc_hostdir_rm() on dev_release(), but guard that with the state check for SHOST_CREATED; there is even a comment in scsi_host_dev_release() detailing that: such conditional is meant for cases where the SCSI host was allocated but there was no calls to {add,remove}_host(), like the usb-storage case. This is what we propose here and with that, the error path of usb-storage does not trigger the warning anymore.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
May 1, 2024
Updated
Oct 15, 2026
EPSS
0.2% · 15th percentile
CWE
—

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 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.

Follow CVE-2024-26935

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
debiandebian linux

Affected versions

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

  • debian debian linux10.0
  • linux linux kernel5.10.176 and later · before 5.10.215
  • linux linux kernel5.15.104 and later · before 5.15.154
  • linux linux kernel6.1.21 and later · before 6.1.84
  • linux linux kernel6.2.8 and later · before 6.3
  • linux linux kernel5.4.238 and later · before 5.4.274
  • linux linux kernel6.7 and later · before 6.7.12
  • linux linux kernel6.8 and later · before 6.8.3
  • linux linux kernel6.3.1 and later · before 6.6.24
  • linux linux kernel6.3
  • linux linux kernel6.9

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

    • 73f030d4ef6d1ad17f824a0a2eb637ef7a9c7d51, 6.3affected
    • 88c3d3bb6469cea929ac68fd326bdcbefcdfdd83 and later · before 0053f15d50d50c9312d8ab9c11e2e405812dfcacaffected · git
    • 68c665bb185037e7eb66fb792c61da9d7151e99c and later · before 5c2386ba80e779a92ec3bb64ccadbedd88f779b1affected · git
    • 2a764d55e938743efa7c2cba7305633bcf227f09 and later · before cea234bb214b17d004dfdccce4491e6ff57c96eeaffected · git
    • 7e0ae8667fcdd99d1756922e1140cac75f5fa279 and later · before 3678cf67ff7136db1dd3bf63c361650db5d92889affected · git
    • be03df3d4bfe7e8866d4aa43d62e648ffe884f5f and later · before d4c34782b6d7b1e68d18d9549451b19433bd4c6caffected · git
    • be03df3d4bfe7e8866d4aa43d62e648ffe884f5f and later · before e293c773c13b830cdc251f155df2254981abc320affected · git
    • be03df3d4bfe7e8866d4aa43d62e648ffe884f5f and later · before f4ff08fab66eb5c0b97e1a24edac052fb40bf5d7affected · git
    • be03df3d4bfe7e8866d4aa43d62e648ffe884f5f and later · before f23a4d6e07570826fe95023ca1aa96a011fa9f84affected · git
    • 5.4.238 and later · before 5.4.274affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
AlmaLinux:8bpftoolbefore 4.18.0-553.37.1.el8_104.18.0-553.37.1.el8_10
AlmaLinux:8kernelbefore 4.18.0-553.37.1.el8_104.18.0-553.37.1.el8_10
AlmaLinux:8kernel-abi-stablelistsbefore 4.18.0-553.37.1.el8_104.18.0-553.37.1.el8_10
AlmaLinux:8kernel-corebefore 4.18.0-553.37.1.el8_104.18.0-553.37.1.el8_10
AlmaLinux:8kernel-cross-headersbefore 4.18.0-553.37.1.el8_104.18.0-553.37.1.el8_10
AlmaLinux:8kernel-debugbefore 4.18.0-553.37.1.el8_104.18.0-553.37.1.el8_10
AlmaLinux:8kernel-debug-corebefore 4.18.0-553.37.1.el8_104.18.0-553.37.1.el8_10
AlmaLinux:8kernel-debug-develbefore 4.18.0-553.37.1.el8_104.18.0-553.37.1.el8_10
AlmaLinux:8kernel-debug-modulesbefore 4.18.0-553.37.1.el8_104.18.0-553.37.1.el8_10
AlmaLinux:8kernel-debug-modules-extrabefore 4.18.0-553.37.1.el8_104.18.0-553.37.1.el8_10
AlmaLinux:8kernel-develbefore 4.18.0-553.37.1.el8_104.18.0-553.37.1.el8_10
AlmaLinux:8kernel-docbefore 4.18.0-553.37.1.el8_104.18.0-553.37.1.el8_10
AlmaLinux:8kernel-headersbefore 4.18.0-553.37.1.el8_104.18.0-553.37.1.el8_10
AlmaLinux:8kernel-modulesbefore 4.18.0-553.37.1.el8_104.18.0-553.37.1.el8_10
AlmaLinux:8kernel-modules-extrabefore 4.18.0-553.37.1.el8_104.18.0-553.37.1.el8_10
AlmaLinux:8kernel-rtbefore 4.18.0-553.37.1.rt7.378.el8_104.18.0-553.37.1.rt7.378.el8_10
AlmaLinux:8kernel-rt-corebefore 4.18.0-553.37.1.rt7.378.el8_104.18.0-553.37.1.rt7.378.el8_10
AlmaLinux:8kernel-rt-debugbefore 4.18.0-553.37.1.rt7.378.el8_104.18.0-553.37.1.rt7.378.el8_10
AlmaLinux:8kernel-rt-debug-corebefore 4.18.0-553.37.1.rt7.378.el8_104.18.0-553.37.1.rt7.378.el8_10
AlmaLinux:8kernel-rt-debug-develbefore 4.18.0-553.37.1.rt7.378.el8_104.18.0-553.37.1.rt7.378.el8_10
AlmaLinux:8kernel-rt-debug-modulesbefore 4.18.0-553.37.1.rt7.378.el8_104.18.0-553.37.1.rt7.378.el8_10
AlmaLinux:8kernel-rt-debug-modules-extrabefore 4.18.0-553.37.1.rt7.378.el8_104.18.0-553.37.1.rt7.378.el8_10
AlmaLinux:8kernel-rt-develbefore 4.18.0-553.37.1.rt7.378.el8_104.18.0-553.37.1.rt7.378.el8_10
AlmaLinux:8kernel-rt-modulesbefore 4.18.0-553.37.1.rt7.378.el8_104.18.0-553.37.1.rt7.378.el8_10

+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-2024-27021May 1, 2024 · r8169: fix LED-related deadlock on module removal
    31Monitor
  • ← EarlierCVE-2024-26934May 1, 2024 · USB: core: Fix deadlock in usb_deauthorize_interface()
    31Monitor
  • Later →CVE-2024-26937May 1, 2024 · drm/i915/gt: Reset queue_priority_hint on parking
    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 Linux0053f15d50d50c9312d8ab9c11e2e405812dfcacVendor (CNA)
Linux Linux3678cf67ff7136db1dd3bf63c361650db5d92889Vendor (CNA)
Linux Linux5.10.215Vendor (CNA)
Linux Linux5.15.154Vendor (CNA)
Linux Linux5.4.274Vendor (CNA)
Linux Linux5c2386ba80e779a92ec3bb64ccadbedd88f779b1Vendor (CNA)
Linux Linux6.1.84Vendor (CNA)
Linux Linux6.3Vendor (CNA)
Linux Linuxcea234bb214b17d004dfdccce4491e6ff57c96eeVendor (CNA)
Linux Linuxd4c34782b6d7b1e68d18d9549451b19433bd4c6cVendor (CNA)
Linux Linuxe293c773c13b830cdc251f155df2254981abc320Vendor (CNA)
Linux Linuxf23a4d6e07570826fe95023ca1aa96a011fa9f84Vendor (CNA)
Linux Linuxf4ff08fab66eb5c0b97e1a24edac052fb40bf5d7Vendor (CNA)
azl3 hyperv-daemons 6.6.22.1-2 on Azure Linux 3.06.6.35.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 hyperv-daemons 6.6.35.1-1 on Azure Linux 3.06.6.35.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
almalinux:bpftool7.3.0-427.42.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel5.14.0-427.42.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-427.42.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-427.42.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-427.42.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-427.42.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-427.42.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-427.42.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-427.42.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-427.42.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-427.42.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-427.42.1.el9_4 · AlmaLinux:9Package registry (OSV)
debian:linux6.1.85-1 · Debian:12Package registry (OSV)
red hat:bpftool-debuginfo0:7.3.0-427.42.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-427.42.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)

+12

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.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
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
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:L/AC:L/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.

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 (9 more)

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

All records